Thanks for sharing this detailed analysis. I ran into a similar JMX class conflict on WebLogic 12.2.1.4 while testing monitoring agents. It covers some useful background on JVM service initialization issues. Removing -DUseSunHttpHandler=true from the startup args fixed it in my case as well.

ok, thanks

@federico

Hi Federico,

The error you received is due to differences in your jar and war file versions. You can verify the correctness of the jar and war files in the package you downloaded and then install WLSDM by placing them in the same environment again.

Kind regards.

@prakash_2006 said in WLSDM for Weblogic 14.1.2:

Hi Team,

Is the WLSDM cannot be used to monitor 14.1.2

Regards,
Prakash.

Hi,
WLSDM for WebLogic 14.1.2 has been released. You can download from https://www.wlsdm.com/download

Supported WebLogic Version --> https://wlsdm.com/download#SUPPORTED_WEBLOGIC_VERSIONS

325942f1-dd6d-44e1-827b-c4d99d51bfd9-image.png

@prakash_2006

It seems incompatible Java version error. Please confirm the correct Java version by following below document?

Download and install the latest JDK 1.8.x compatible with your OS platform

https://wlsdm.com/wl-opc/docs/readme#prerequisites

@wlcommunityusers

Hi,

Please follow below tutorials and blog posts about Log monitoring features of WLSDM. You can use WLDF query or use custom WLSDM log monitoring features. All details are available at below tutorials. Please read them all carefully and apply it to your WebLogic environments.

Log Monitoring Screencast: Monitor Every Text File On WebLogic -->
https://medium.com/wlsdmforweblogic/log-monitoring-screencast-monitor-every-text-file-on-weblogic-b7aac675d4dc

https://wlsdmforweblogic.medium.com/wlsdm-log-monitoring-db18942bcb1e

https://youtu.be/t33ZvlNArZI?si=Fw4stev0vGgn3CM9

https://medium.com/wlsdmforweblogic/weblogic-log-request-and-file-upload-solution-file-explorer-and-log-viewer-tailer-c0c74d26a68e

WebLogic Log Request and File Upload Solution: File Explorer and Log Viewer & Tailer

Regards…

@can-sahin-wlsdmteam
Hi,

Perfect I was able to remove it.
Would you know why the script I have is not reporting from all the servers in the chart ? when in SQL it is just a group.

I can create 6 charts but rather it work in one chart.

983196c3-91af-4559-b072-d5fa8b356096-image.png

@wlcommunityusers

Hi,

This property is for filtering the backend captions not for backend notification threshold.

Please go to “WLSDM Menu > Add Monitoring > Add/Update Monitoring & Diagnostics Configurations” page and switch to “Back-end Systems” tab. Click on relevant Managed_Server and update your “JDBC Statement Execute” threshold and save. Then repeat the same for each managed server.

94140c4b-2263-4ce6-ac8f-79af9f400969-image.png

Kind Regards…

@can-sahin-wlsdmteam

Thanks I will check with our guys here on the email.

@wlcommunityusers

Hi,

You can set the number of alarms for health status of servers by following the steps below.

c5a89e7d-bc16-4616-aea9-c25241a7757b-image.png

Best Regards.

@wlcommunityusers

Hi,

You can follow the tutorial below.

Link: https://youtu.be/gocp-6zWy00?si=2RnSB6yKGHgwz7O4

Best Regards.

@can-sahin-wlsdmteam

I think it works this time. Thanks

@gitodesign

A return was provided by mail.

Hi @stevediaz
Could you please check SOA datasource that WLSDM created? Is that datasource is active and working?

@lvzhongx said in How Jboss EAP MDB can connect to Weblogic queue:

I have a MDB deployed in Jboss EAP 7.4 and the destination is Weblogic queue. (Consume the messages in Weblogic queue) . I need to install weblogic JMS resource adapter , I would like to know if we have any reference guide to install this Weblogic JMS resource adapter in Jboss EAP , Thanks.

To connect JBoss EAP MDB to a WebLogic queue; deploy the WebLogic JMS resource adapter RAR in JBoss and configure it in standalone.xml. Check the JBoss EAP documentation for detailed steps on resource adapter configuration & JMS integration; or visit the JBoss Community for more support.

@traceyrawlings said in Log monitoring configurations are blocked:

Log monitoring are blocked but there are no files with .out0, or .log0
in the directory.

I see wlsdm.agent.DEServer1.log_.lck
and i see older log files wlsdm.agent.DEServer1.log
and i see older log files wlsdm.agent.DEServer1.log.1

Which files are we supposed to remove?

Hi,
These notifications are based on WLDF queries for your WebLogic server logs. If querying WebLogic logs through WLDF tooks long time, this notification visible to WebLogic administrators.
You need to check WebLogic logs not WLSDM logs. Keeping rotated WebLogic (*.out0, *.log0) logs cleaned and tidy would improve your WebLogic domain performance.

@arturrgdietrich said in Weblogic 14 option wlsdm.agent.extendedBackendMonitoringEnabled=true dont start server:

Weblogic 14:
if “-Dwlsdm.agent.extendedBackendMonitoringEnabled=true” option is included in start options from managed server it does not start. Removing this option it stars correctly!

ERROR:
.
.
.
<May 3, 2024 11:33:00 AM ART> <Unable to connect to the Administration Server. Waiting 5 second(s)
to retry (attempt number 1 of 3).>
<May 3, 2024 11:33:05 AM ART> <Unable to connect to the Administration Server. Waiting 5 second(s)
to retry (attempt number 2 of 3).>
.
.
.

Is there any solution for this ? What benefit will I lose if I don’t use this option?

If -DUseSunHttpHandler=true parameter is added to your WebLogic managed server probably you are having below known issue. Please consider to apply below solution to your case.

Known Issue - Conflict Between DUseSunHttpHandler and Dwlsdm.agent.extendedBackendMonitoringEnabled: When both -DUseSunHttpHandler=true and -Dwlsdm.agent.extendedBackendMonitoringEnabled=true are added to a WebLogic ManagedServer instances simultaneously, an error occurs: "java.lang.NoClassDefFoundError: com/vopm/collector/HTTPData" To resolve this issue, remove one of the conflicting parameters. Consider removing "-DUseSunHttpHandler=true" argument for monitoring remote HTTP(s) outbound connections if it is technically possible

Available at README: https://wlsdm.com/docs/README#VI.Installation

cb9db498-96b6-4248-a5f1-882f9e42ad7d-image.png

@takika said in Oracle JDK 11 vs WLSDM FlightRecorder:

@fevzi-korkutata-wlsdmteam
I just checked the README, but didn’t find anything about Java 11 and FlightRecorder. There is no JAVA_OPTIONS for Java 11.

Hi Takika,
You can find the JDK 11 update in Readme as stated in below screen capture. Cloud you please give a try again and let me know the latest status about your case. You should not get any error anymore with the v4.1.1 also please tell me your exact WLSDM for WebLogic version.

Latest Readme: https://wlsdm.com/docs/README

c86d391b-2889-4c61-8cbf-844d3804edf1-image.png

@jbrinker We have released v4.1.1. Could you please give a try with this version and let us know the result. https://wlsdm.com/download

@alan_aguinaga said in Console Admin Server is being down after install wlsdm:

It is pretty hard to understand why my AdminServer console went down before I installed this. I am searching in logs and just getting info and warning levels.

This deployment is shutting down my console. I just see some thread concurrence here.

Have you ever see this?

Hi Alan,
We were unable to hear you about our data requests. We had an experience like this before; “One of our client was deployed wlsdm.war as a web application by using Oracle WebLogic console instead of putting file to $DOMAIN_HOME/console-ext folder.” It might be also your case.
I am adding this information for any other person who might have face this.
Regards…

@fevzi-korkutata-wlsdmteam Thanks much Fevzi. Bypassing loadbalancer url, I’m able to complete the configuration.

Regards,
T N Prasad

@cody-west Glad to hear that ! 🤗

@salman said in Installation of WLSDM on Saperate Server:

We do not want to install WL-SDM on same server where Oracle Weblogic Is installed, is possible to install WLSDM on separate server?. It will be better not only w.r.t security prospective but also because monitoring Weblogic from outside the Weblogic server is more beneficial.

Hi,
WLSDM installation and montoring is very simple and works like native WebLogic console extension. If you want to monitor your domains from outside the WebLogic admin server we have another standalone solution which is WL-OPC ( https://wlsdm.com/wl-opc/ ) This product is the central WLSDM Operation Center product.
Hope this would help…

@wlcommunityusers
Hi,
We are glad that your problem has been solved for WLSDM installation. If you encounter any other problems, you can send an e-mail to our WLSDM Support team.

Kind regards.

Hi @wlcommunityusers,

You can change your mail configuration by following the steps below.

Go to WLSDM > Configuration > WLSDM System Settings > mail.account

feb9c61c-3584-4463-9119-2be0f0637fc5-image.png

Go to WLSDM > Configuration > WLSDM System Settings > mail.to

a1fd66ec-f3c3-4fd8-ad9b-10b7373183cb-image.png

We are very glad that you have resolved the issue and it was a great pleasure to support you.

Best regards

By default the JNDI resource is controlled by the Group: everyone policy and therefore anyone can access the resource using any method such as search or list. You need to make this authorization for WSDM. You can easily solve this problem by following the steps below:

Click on the managed server in the “RUNNING” state on WebLogic Consol. Click on the “View JNDI Tree” link just below the Configuration --> General tab.
b7ac04ff-f87d-4100-9701-a81cda39e599-image.png Switch to Security --> Policies tab from the “JNDI Tree Structure” page. Select “ALL” from the “Methods” drop-down list and click the “Add Conditions” button under the “Policy Conditions” heading.
bd632ff2-d19b-4449-9cdb-cfe46a10aeba-image.png Select “Group” from the “Predicate List” drop-down list. Click “Next”. Type everyone in the Group Argument Name: Textbox and click “Add” button.
c098eb25-f8ca-46c9-b7f9-ad615795a666-image.png Click Finish.

After the settings, Group : everyone will appear under Policy Conditions. Repeat these settings for each Managed Server where WLSDM Arguments are entered and restart all managed servers sequentially. Restart the Admin Server last. You will see that the problem is solved.

3412ed1a-f568-4ad8-8af4-6c25d57ccea1-image.png

98df401b-018c-4c00-ade5-4e989ce7ae5b-image.png

Best regards

@hedmondjohn

Hi Hedmond,

You can complete the WLSDM wizard by applying the solution below for the error you receive.

Solution:

WebLogic AdminServer port use which is pointed in below screen capture.

7ca7a3fd-932d-4302-96a7-f9274116909c-image.png

• Go to AdminServer > Protocols > General and increase the “Maximum Message Size” to “100000000”.

776232d7-7fda-4e92-bf70-3a854e221fc2-image.png

• Then click the HTTP section and make sure “Max Post Size” is “-1”.

e05ee5a3-9dbd-4d8e-9e8d-97df6562668c-image.png

Finally, activate your changes, restart the AdminServer and try to complete WLSDM Installation Wizard again.

@jonatanrocha

@jonatanrocha said in Monitoramento via API:

Gostaria de receber sugestões de como configurar e integrar o monitoramento do weblogic via api no zabbix.

Hi,
Please post in English. We can use Google Translate for this but we are preferring you do it instead 🙂
Regards…