@wlcommunityusers

Hi,

Finally, I found the solution.
I changed java.security in WL-OPC disabling jdk.tls.disabledAlgorithms like this:

b0d4cae9-48f2-4ce0-9bf1-0afdaf93dcde-image.png

And then I removed all the arguments in JAVA_OPTIONS to default OPC installation.

I restarted OPC and I could add the domains without any problem.

Regards.

Hi,

I am happy that you are able to monitor your backend datasource JDBC monitoring. Yes, you can monitor all your datasources in the same dashboard.

Other APM tools injects runtime codes to your codes which creates a lot of overhead on your JVM instances. WLSDM uses native method and that’s why we call “native WebLogic monitoring”.

On the other hand; please follow “Generic DevOps MBean” tutorials and build your own dashboards and automate your WebLogic management.

https://medium.com/wlsdmforweblogic/how-to-create-server-machine-disk-usage-dashboard-and-trigger-delete-logs-devops-action-a267f439c68

Kind Regards…

@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.

@bibarrav

Hi,

Probably it is a WebLogic issue. If it is a “Devlopment Mode” WebLogic domain; you should not see the “Change Center” in WebLogic console. But, in your sceen capture “WebLogic Change Center” is available (attached below). We are recommending to setup your WebLogic domain from scratch as Development mode domain.

Regards…

image.png

@ozhana

Hi,

Are you sure all access and diagnostic logs are backuped?

Which WLSDM version are you using?

Kindly, please send reply at [email protected] email address.

Regards.

@can-sahin-wlsdmteam

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

@djviolli said in LDAP Configuration Access:

Problem solved by the support team, due to using the OUD for access, a base version was made!
I congratulate the WLSDM team for their attention and timely solution.

Thank you @djviolli very supportive and valuable feedback from you to the community. 👏

@cody-west Glad to hear that ! 🤗

@wlcommunityusers

Hi,

Default interval is 120 seconds and you can change this value in “system.monitoring.genericmbean.harvest.frequency” property as below.

PS: If you change this value, it will effect all “Custom MBeans”.

6.png

Regards.

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

Regards,
T N Prasad

@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

@wlsdmadmin I’ve already upgraded, have some issues, I’ll post it. Regards…

@vanrussell_nl

Hi,

It’s an WebLogic issue and unfortunately WebLogic does not serve JMX value at the same time. Anymore, you don’t need to live Java Mission Control connection. Just keep using WLSDM 😉

Best Regard…

Hi,

We have one more question: is there a chance to be wlsdm jar or war file is in the WebLogic classpath.
We are asking that because, the below log generally indicates that issue.

java.sql.SQLException: Failed to start database ‘WLSDM/db’ with class loader PolicyClassLoader ‘weblogic-launcher’ @50d0686 {file:/u01/app/oracle/product/fmw/wlserver/server/lib/weblogic-launcher.jar file:/u01/app/oracle/product/fmw/wlserver/server/lib/pcl2.jar … (642 more)}, see the next exception for details.

If it is not, the reason is may the database corruption you should try the fresh installation.
https://wlsdm.com/docs/README#VII.Upgrade&Reinstall&Uninstall

@hmurali said:

@wlsdmsupport Thanks for the update.

Do we also get alerts when the server health goes to warning/overloaded state and Server state goes to ADMIN/UNKNOWN status.

Kindly advise.

Thanks
Hari

Hi Hari,
Additionally please check this tutorial to find out and learn more: https://www.youtube.com/watch?v=PeKJusLuarI
Regards…

@haydar-seyfi-wlsdmteam Thanks for the info

SOLUTION:
The agent.jar was in the lib folder. The lib folder was on classpath.
I repaced the agent.jar. This solved the issue.

Thanks a lot.

Hi,
On the other hand, Make sure you have not applied wlsdm_agent JVM arguments to the AdminServer?
If you send the whole details and logs we would like to help you to alter this problem. We have never seen this error before. It looks like this is something relevant to this environment. Have you tried the installation on another domain environment?
Regards…

Thanks,

The point 1 resolved it. OHS was being used here. Using the listen port helped to resolve the issue.

Regards,

@catgovind said:

Thank you so much. It is working perfectly.

We will add additional NOTE to WLSDM readme in the next release. Thank you for reporting it.

Regards…

@Ramanpreet_Singh

Hi Ramanpreet,
We are happy to solve your issues. Thank you for the affirmative report.
Always use $IP:$PORT/console/WLSDM direct URL for accessing WebLogic WLSDM console.

Thank you for your interest. We trust our product very much and we thought every detail for WLSDM.

Here our comments;

First of all, your domain is really big and massive. But, we it is for sure we can handle it.

1 - For my experience what make the difference is collecting data… In order to monitoring historic information anda data (this help me in troubleshooting)
Yes, especially this size of domain is very hard to monitor. If you have any unused server, datasource, JMS definion please delete all, after that fresh resinstall WLSDM and do not track unused apps, servers, deployments… etc.
Historical data would be very useful for your problem troubleshooting. Especially, check notification pages.

2 - About deployments table your dashboard use to list applciation status in evey servers of my cluster and it is a little bit redundat
We have asynchronous backend health feature on health dashboard. Could you please enable it and let us know the result? (Go to Health Dashboard page, > Page Operations Menu> Switch the below button to ON)

save.jpg

By the way, we have JMX/t3 timeout on system.WLSDM tab at System Settings page. If your domain is not responsive has its own problem, we are cutting the request because of keeping WebLogic domain healthy. It’s default value is about 5sec. That’s why you can see the health status conflicts.

@sravanreddyg It’s standard feature of WLSDM. You should configure these settings while completing wizard. But it’s not problem. You still can update on Back-end tab on configuration pages. Just click on edit button for the JDBC entry; enable threshold and “store data”. That’s all. You can follow metric threshold documentation as a reference. Here is the doc URL: http://www.wlsdm.com/docs/help/#3.CompletingWLSDMWizard

@can-sahin-wlsdmteam

I think it works this time. Thanks

@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

@wlcommunityusers

Hi,

We fixed this issue in v3.9.2. If you upgrade the WLSDM domain v3.7.2 to v3.9.2 you will not face this issue any more.

Kind Regards,

WLSDM Support Team
https://community.wlsdm.com

Hi,

On the other hand, I’m trying to configure a script to be executed once I have a stuck thread alarm.
Is it possible to do that?

Yes, you can set alarm to scripts. Please check below tutorials.
OracleDB ACTIVE/INACTIVE Sessions monitoring on WebLogic: https://youtu.be/XjBz6zlKstM
Generic DevOps Disk Usage MBean Tutorial: https://youtu.be/OYkPEpxF66M

Kind Regards

Hi,

WLSDM fresh installation steps are below:

Replace the wlsdm_agent.jar file with the new release and keep wlsdm_agent.jar JVM arguments. *($JAVA_OPTIONS) Shutdown Administration Server Delete $DOMAIN_HOME/WLSDM runtime folder Replace wlsdm.war file with the new release to WebLogic domain’s console-ext folder Start WebLogic Administration Server and restart the Managed Server(s) which wlsdm_agent.jar installed That’s all! WLSDM will be reinstalled after restart processes Complete WLSDM configuration wizard

WLSDM wizard is going to be visible with the re-installation process

Reference: https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Kind regards…

Hi Karim,

You have Out of Memory error while opening this managed server. Please check below error in your managed server log.

You had better tune and optimize your WebLogic environment or increase server memory.

Kind Regards.

####<Jan 10, 2021 4:28:17 PM MYT> <Info> <Health> <WIHST03-VMAP03> <Server-4> <weblogic.GCMonitor> <<anonymous>> <> <> <1610267297840> <BEA-310002> <97% of the total memory in the server is free> ####<Jan 10, 2021 4:28:18 PM MYT> <Error> <HTTP> <WIHST03-VMAP03> <Server-4> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <fa71d3a8cd78f3f8:-638c60f4:176eb68c7a2:-7ffe-0000000000000004> <1610267298673> <BEA-101216> <Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war". java.lang.OutOfMemoryError: PermGen space at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at com.sun.xml.ws.server.sei.EndpointMethodHandlerFactory.create(EndpointMethodHandlerFactory.java:15) at com.sun.xml.ws.server.sei.ActionBasedDispatcher.<init>(ActionBasedDispatcher.java:92) at com.sun.xml.ws.server.sei.ActionBasedDispatcher.<init>(ActionBasedDispatcher.java:80) at com.sun.xml.ws.server.sei.EndpointMethodDispatcherGetter.<init>(EndpointMethodDispatcherGetter.java:75) at com.sun.xml.ws.server.sei.SEIInvokerTube.<init>(SEIInvokerTube.java:82) at weblogic.wsee.jaxws.WLSContainer$WLSEndpointFactory$1.createServer(WLSContainer.java:857) at weblogic.wsee.jaxws.ServerLateInitTube.postCreateEndpoint(ServerLateInitTube.java:63) at weblogic.wsee.jaxws.EndpointAwareLateInitTube.postCreateEndpoint(EndpointAwareLateInitTube.java:46) > ####<Jan 10, 2021 4:28:46 PM MYT> <Error> <Socket> <WIHST03-VMAP03> <Server-4> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1610267326402> <BEA-000405> <Uncaught Throwable in processSockets java.lang.OutOfMemoryError: PermGen space. java.lang.OutOfMemoryError: PermGen space >

####<Jan 10, 2021 4:29:29 PM MYT> <Error> <Socket> <WIHST03-VMAP03> <Server-4> <ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1610267369905> <BEA-000405> <Uncaught Throwable in processSockets java.lang.OutOfMemoryError: PermGen space. java.lang.OutOfMemoryError: PermGen space