Hi,

Try to hard restart OPC by using opc command. After restarting OPC the problem should have resolved? Could you please confirm the result?

We’ve created an issue to solve the problem permanently.

@wlcommunityusers said in WLSDM Config- New managed server:

Hi,

We have added a new managed server to the domain. We want to configure alerts(Datasource, Backend Monitoring etc) like we configured for previous managed server. Please suggest.

Current config:
AdminServer
ManegedServer1
ManegedServer2

Regards.

Hi,

You can include new server to current configurations in “Response Time” monitoring but you need to add new back-end systems configuration for new server.

Please check below screen captures.

Response times configuration for newServer:

Go to “Configurations > Monitoring & Diagnostics” in WLSDM menu Follow below navigation and click “edit” button Select ManegedServer2 then save

reponse1.jpg

response2.jpg

Backend configuration for newServer:

Go to “Configurations > Monitoring & Diagnostics” in WLSDM menu Follow below navigation; click “page operations” button then select “New Back-end Systems Monitoring” Create new back-end configurations, add events ManegedServer2 then save

backend1.jpg

backend2.jpg

Kind Regards.

WLSDM Support
http://www.wlsdm.com

Hi,

We have resolved the DB purge issue in version 3.9.2. Which version is this WLSDM domain?

You have two options;

First is to upgrade WLSDM v3.9.2. (Keep in mind while you are opening the AdminServer; the purge operation would start automatically and it can took a lot time because of your db size)
https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Second is fresh re-installation which is explained as below steps. (Remember to take current configurations; if you have license issue we have already sent the trial license to skip config wizard)

Export WLSDM Configuration; follow the steps below

wlsdm_configuration.jpg

Shutdown AdminServer Delete WLSDM Runtime Folder (If background information is not important; in this case the past will delete) AdminServer start Complete WLSDM configuration wizard by importing export configurations

wizard_configuration.jpg

Re-installation procedure also available in here :
https://wlsdm.com/docs/README#IX.Upgrade&Reinstall&Uninstall

Kind Regards.

WLSDM Support
http://www.wlsdm.com

@wlcommunityusers

Hi,

Please follow screenshot’s steps and set the threshold as below.
–> WLSDM Dashboard Menu > Monitoring & Diagnostics > Back-end Systems tab

fileread2.jpg

fileread3.jpg

Kind Regards…

WLSDM Support
https://community.wlsdm.com

@wlcommunityusers

Hi,

WLSDM cron takes several minutes to return cycle. Reduce some minutes, Example 1430 rather then 1440.

Kind Regards…

WLSDM Support
https://community.wlsdm.com

Hi,

Did you upgrade the domain? Your latest screenshot says your WLSDM v3.7.2 but WL-OPC says WLSDM v3.9.2.

You can follow the below provided solution.

Check two way access between WL-OPC and WLSDM
WLSDMHostname$ telnet OPCHostname 8080
WL-OPCHostname$ telnet WLSDMHostname 7001 Open problematic domain’s wlsdm_agent.jar with winrar and check WLSDM-version in “META-INF> MANIFEST.MF” file. If there is old version just replace wlsdm_agent.jar with the new version in $DOMAIN_HOME\wlsdm_agent\ Unregister problematic WLSDM domain from WL-OPC Complete WLSDM installation wizard without WL-OPC registration Register WLSDM domain to WL-OPC in WL-OPC “Administration> WL Domain” page. If the problem is not resolved please send us $WL-OPC_HOME\bin\WLOPC\logs with the zip file

Kind regards.

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,

Could you check JVM Parameters for WLSDM? You can take the below page as a reference.

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

JVM Parameters for backend configurations:

jvmparameter.jpg

Kind Regards.

Hi,

SOA default dashboards are contains complete SOA monitoring and they are sufficient for monitoring SOA performance.

You can check https://medium.com/wlsdmforweblogic WLSDM Medium blog posts by WLSDM team and customer experiences.

You create new Devops MBean and new Dashbaord in WLSDM as below screnshots.

Also please check suggested blog posts:

https://medium.com/wlsdmforweblogic/how-to-create-server-machine-disk-usage-dashboard-and-trigger-delete-logs-devops-action-a267f439c68
https://medium.com/wlsdmforweblogic/how-to-create-a-custom-mbean-from-an-sql-query-in-weblogic-server-using-wlsdm-generic-devops-b978acb22401
https://medium.com/wlsdmforweblogic/advanced-weblogic-monitoring-develop-jmx-mbeans-and-automate-with-wlsdm-metric-actions-73580ca73782

• How to create new DevOps MBean in WLSDM

genericdevopsmbean.jpg

• How to create custom dashboard and create

create.jpg

Regards.

Hi,

Thanks, Incident: Clear.

Incident.png

Regards.

Hi,

You can change the JFR repository directory using the following JVM option:
WLSDM must delete those temp files which is older than two days (48 hours).

-XX:FlightRecorderOptions=repository=WLSDM/temp/JFR ( see: https://wlsdm.com/docs/#VI.Installation )

If you choose not to define (or remove) this JVM option, by default the files will be stored under the operating system temporary directory.

For more information see: https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
repository.png

Also, jfr files are static profiling files, not library files. You can delete them safely even runtime.

For the second question: You can achieve that using the “Downtime” feature:

1 – Go to WLSDM console / “Monitoring & Diagnostics” page.

schedule.png

2 – Open the page operations and click the “New Scheduled Job / Downtime”
newschedule.png

3 – Configure the downtime and click save.

At this point, you have two action option:
1 – Stop all notifications but keep monitoring
2 – Stop all monitoring

action.png

scheduletime.png

Regards.

Oh, that’s lovely, thank you very much!
Have installed 3.9.1 in out sandbox environment after receiving the newsletter last week, will give this a shot right away!

Hi Can,

This error is the wrong path for java in setenv.properties file configuration.
Because in Linux alternative link using for java path.
If you are using this command in terminal. “echo $JAVA_HOME” then it gives a true java path.
ex: echo $JAVA_HOME --> /usr/lib/java/jdk1.8.0_201
In setenv.properties file JAVA_HOME line change with your full java path.

Then you can start WL-OPC.

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

Hi,

You can follow WLSDM installation instructions in https://wlsdm.com/docs/#IV.Installation page.

There are notes as below for installation:

I. Known Issue: After the complete WLSDM installation if the “Smart Dashboards > JVM System Resources” page is not working well and does not show the metric values properly then add “-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder” JVM argument to the relevant Managed Server(s) and restart the server(s).
II. Do not install agents for whole servers. same cluster or same machine not needed WLSDM agent (as below screenshot).
III. Care “with Nodemanager” and “without Nodemanager” parameter step in wlsdm installation document then use one of them which are you using.

a2.jpg

Regards.

Hi,

It looks like SMTP Server that you are using requires authentication.
535 Authentication required com.sun.mail.smtp.SMTPSendFailedException: 535 Authentication required

Please make sure the SMTP username and password are set on the WLSDM.

smtp1.png

After that, you can check the setting by using the “Test Email Settings” button under the page operations dropdown menu.

smtp2.png

smtp3.png

smtp4.png

Regards.

Hi,

OPC default port is 8080, When you need to register domain to OPC first of all; check firewall rules for below ports with telnet.

OPC and agent both are communicating each other you need mutual firewall request.

From: ${WLSDM_AGENT’S_IP}
To: ${OPC_SERVER’S_IP:8080}

From: ${OPC_SERVER’S_IP}
To: ${WLSDM_AGENT’S_IP:WEBLOGIC_ADMIN_PORT}

Regards…

Hi,

Sometimes WebLogic blocks the direct access to the Java Native MBean Server from inside it for various reasons.
And that affects some modules functionality.

Please add the following startup argument to your managed server.

İf it does not solve the problem, please zip and send the “wlsdm.log” file to us for the detailed examination.
${DOMAIN_HOME}/WLSDM/logs/wlsdm.log

agent4.png

https://wlsdm.com/docs/#IV.Installation

Regards.

Hi,

This bug has fixed in v3.9.1 WLSDM version.

Regards.

You can analyze high CPU consumers and backend events in the “possible root cause page”/ “thread analyze page”. This page gives you important tips for errors/hogger/stuck threads.

You need to have a valid license to monitor these pages.

how can I know through the wlsm that queue mq is currently affecting the managed nodes?
Go to “Configuration > Metric Settings & JMX MBean Browser” then click “JMX MBean Browser (+Add New)” button for navigate below modal window then create new JMX MBean for JMS metrics in 8 steps.
1.jpg

how to know on which node managed I have agent configured from the wlsdm?
You can check which managed server has WLSDM agents in “Operational Tools & Utils > Monitor WLSDM Agents” page; but there is no need to WLSDM agent to monitor stuck threads.

because the stuck thread dashboard does not appear on the path: Smart Dashboards Servers, but I do see hoggingthreadcount information
• Check dashboard count for “StuckThreadCount” metric in “MBean Browser” pool it must be select at least 1 dashboard…
• If there is no “StuckThreadCount” metric; you must add from “JMX MBean Browser” button.
3.jpg

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

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,

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…

Hi,

Thanks for your kind support.
JMS Servers resources added successfully.

Hello,

When we skip the monitoring of DataSource and JMS server, setup finishes successfull.

Regards.

Yup. It work’s. Thanks.

Thanks

We checked the space in the database and it was without problems, what we did was to restart the opc application, thank you very much