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

Hi,

Email alert’s default sender value is “[email protected]”.

You can edit sender(from) as below.

Regards.

1.Go to “Configuration > WLSDM System Settings” in WLSDM menu.
menu.jpg

2.Be sure you are in “mail.account” tab then edit “mail.account.smtp.username” property.
sender.jpg

Set property value in modal window then save.
111111.jpg

Hi,

You can select any range by using date field. But the maximum backward range is the WLSDM monitoring start time.

Kind regards.

Hi,

WLSDM log viewer line limit is 1000 but you can search any string and find searched string where line is located in whole log file via “text filter”.

There is another way to view log files via WLSDM file explorer. Go to “Operational Tools & Utils -> File Explorer” pick “.log” file then click view button (max 1 mb view size). Also you can download log file to your local environment via file explorer.

Kind Regards…

Log viewer text filter:
1.png

File Explorer:
2.png

Hi,

The WLSDM and the WL-OPC have their own data-archive mechanism.

For the WLSDM, default data archive range is 90 days, and for the WL-OPC, default data archive range is 365 days.

You can find the settings below.

Kind regards.

WLSDM: Configuration > WLSDM System Settings > system.archive
77.jpg

WL-OPC: Administration > System Settings > Notification
88.jpg

Hi,

Non-adminstrator users not allowed for administrative operations by default as below screenshots.

Metric configuration for monitor user:
2..png

Metric configuration for adminstrator user:

3..png

File explorer for monitor user:

4..png

You can change access restriction configuration in “WLSDM System Settings > system.authorization” page.

Default value is OFF in “system.authorization.page.access.fileexplorer.allgroups” feature. It means only administrators can access to “file explorer”. If you turn on this feature, you must set access path for non-adminstrator users then non-adminstrator users only can access the path(s).

You can restrict log viewer access configuration via “system.authorization.page.access.logviewer”. Default value is on, it means all users can access log viewer, if you turn off this feature, non-adminstrator users will not able to access logviewer.
56.jpg

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…

Hi Jeba,

If you want to see File/Socket events you should increase your WLDF Diagnostic volume on WebLogic

Go to “Servers > $ManageServerName > General (tab)” page and set “Diagnostic Volume” high. Then you are able to see file read/write events.

Note: This option means additional overhead on your managedservers; just activate only one managedserver which file read/write monitoring is important.

Regards.

diagnostics.png

No; this property is usefull when OPC is down. You had better enable it. Disabling that property will NOT disable for all domains.

You can still configure notification settings on WLSDM part; like ON/OFF backend notifications… etc.

The configuration is still same; all the functionalities on WLSDM are still supported by OPC. If you have a specific case; then please let us know in detail to reproduce it.

Regards…

Thanks…

Hi,

This timeout value is a precaution to protect the system.

That’s why we can’t let the increase the timeout value by users.

If you need a long-running process; you can trigger your WLST script using a shell command.

That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).

Also, this type of usage means; The script is out of the control to WLSDM.

Kind regards.

Hi,

You can’t call the stored WLST scripts from the scheduler module.

And you need a shell script (custom action) to run an external WLST script from the scheduler module.

Kind regards.

@bibarrav

Hi Bibarrav,

WLSDM doesn’t support the feature you ask.

But you can complete the installation quickly using the wizard.

– How many domain installation planning you are exactly?

Kind Regards…