@asutosh said:

i have installed the WLSDM and set the java option as well. WLSDM console and agent loaded successfully.

But i am getting error when saving all monitoring setting

####<13-Mar-2018 13:50:16 GMT><Unparseable date: “-- 23:59:59”

java.text.ParseException: Unparseable date: “-- 23:59:59”
at java.text.DateFormat.parse(DateFormat.java:366)
at com.wlsdm.J.F.H(Unknown Source)
at com.wlsdm.J.D.hasLicense(Unknown Source)
at com.wlsdm.H.a$_A.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)

Please suggest how can we fix this

Hi,
wlsdm.log is available in $DOMAIN_HOME/WLSDM/logs folder. Just zip the whole folder and upload it. We will help you by investigating the real problem.
Regards…

@jeba said:

Hi,

On the Back End Reporting, by default EJB and JDBC events are captured and alerted. This is useful. But there are options like File Read, File Write and Web Service calls on the Back End Reports. We enabled these options for the Managed Server but none of these events are captured or displayed in those reports. But while restarting the Managed Server, if we include this JVM option,
“-XX:FlightRecorderOptions=defaultrecording=true”
Then I am able see all those File Read and File Write events are displayed and alerted. After removing the JFR default recording, then no events are captured. Is there any option or config we need? The downside of keeping the defaultrecording ON is that the Managed Server generates the JFR recording and the disk space grows exponentially which we don’t want.

Thanks,
Jeba.

Hi Jeba,

We analyzed your WebLogic monitoring request again and here our solution offer.

Please remove “-XX:FlightRecorderOptions=defaultrecording=true”, you do not need this option while using WLSDM. If you still 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.

image.png

Keep your file and socket read/write definitions on WLSDM.

Restart your managed server (it is needed after JVM parameter removing).

This is the best setup for monitoring your file/socket events. By this configuration you will not face any disk problem. Because; WLSDM will take care of JFR files.

Regards…

Thank you so much. I will give it a try and let you know whether this works in our scenario or not. Thanks.

Log Monitoring cycle default value is 120 seconds. You can configure it from “Configuration > WLSDM System Settings” page’s “system.monitoring” tab, property as below. It effects back-end, loginspector and response times frequency. No problem until 60 seconds but we suggest 120 seconds for high transaction traffic.

LOG.png

Thanks, I have tested on my local environment, it worked when I add boot.properties.

Weblogic version --> 12.1.3
Domain type --> OSB

@wlsdmadmin
Sorry for late reply. I’ve did as mentioned above and fixed as workaround. Thank you for the quick response.

@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

@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

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

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

@can-sahin-wlsdmteam

I was confused with console-ext folder before … issue resolved. Thank you very much!

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

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.

@wlsdmsupport said in IBM JDK (AIX) Java arguments for the WLSDM agent:

@wlcommunityusers said in IBM JDK (AIX) Java arguments for the WLSDM agent:

Requester: @dirk-nachbar
Hi WLSDM Team,
I’ve a request for providing the required Java Arguments for the WLSDM agent under IBM JDK (AIX) within your Installation Document Thanks in advance.

Hi Dirk,
These JFR (Java Fligh Recorder) arguments are valid from JDK 1.7_040 version. You can check this out: https://publib.boulder.ibm.com/httpserv/cookbook/Java-Java_Profilers.html (See “Java Mission Control (Formerly JRockit Mission Control)” section)

If your IBM-AIX environment works on Java 1.6.xx, there is no need to add these JFR parameters. Only add “-javaagent:/path/to/wlsdm_agent.jar -Dwlsdm.agent.logger.level=INFO” this means you are NOT able to monitor backend operations. But all the rest will work properly.
By the way, we are going to update our installation document by adding these additional information. Thank you for your contributions.

@dirk.nachbar On the other hand, we have released a new v2.5.2 and it covers the OSB module inline. Also update the website, blog site and community site 🙂 For your information…

Hi,

Thanks, Incident: Clear.

Incident.png

Regards.

Yup. It work’s. Thanks.

@wlsdmadmin

It worked like a charm 🙂 Missed the first grep parameter. Very useful feature. 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

Thanks…

Hi,

It looks like a WLSDM DB issue.

This is might be happening because you do not have enough disk space on the machine.

Please check your disk for enough space.

After that please restart the (only) AdminServer.

Kind regards.

Hi,

Unfortunately, we are not supporting “bash 3.2” version. At least you have to use “bash 4.x version”. Adding compatible bash version as below.

Here are our recommendations:

Our recommended OS is Linux. (centOS, Red Hat… etc.). You had better choose Linux servers. This information is already available in the help at the “prerequisite” section.

Upgrade your bash version to 4.1 at your current working Solaris server.

Kind Regards…

Hi,

This is a cache issue.

As a workaround: Please restart your WebLogic AdminServer to apply your new license.

Hi,

This is an “Internet Explorer” issue (also, previous issue too).

Please prefer the Chrome or the Firefox as browser while we fix the problem in next WL-OPC release.

Kind Regards…

Hi,

This script is endless; you should echo a result for capturing a variable in WLSDM.

You should use the ping command like i.e. “ping $servername –c 1” then extract output from the ping command.

We are recommending you to use the script which is available in WLSDM README for pinging database. Please follow the readme link here: http://www.wlsdm.com/docs/README#VI.ConsoleUsage&DevOpsMBean

Also we are pasting below.

Step-1 Write Shell Script: Ping database and calculate database response time using WebLogic API (weblogic.jar)

#Variables _dbStatus=0 #0:DB_DOWN,1:DB_UP #start DB Ping _startTime=$(($(date +%s%N)/1000000)) _pingResult=`java -cp weblogic.jar utils.dbping ORACLE_THIN $YOUR_USER_NAME $YOUR_PASSWORD $YOUR_IP:$YOUR_PORT/$YOUR_SERVICE_NAME` _endTime=$(($(date +%s%N)/1000000)) _dbResponseTime=`expr $_endTime - $_startTime` if [[ "$_pingResult" == *"Success!!!"* ]]; then _dbStatus=1 #echo "Database connection SUCCESS!!!" #DB_UP echo DatabaseStatus=$_dbStatus else _dbStatus=0 #echo "Database connection FAILURE!!!" #DB_DOWN echo DatabaseStatus=$_dbStatus fi echo DatabaseResponseTime=$_dbResponseTime```

Hi Vivek;
Actually 11g and 12c offers same health dashboard. Something is wrong about your 12c WebLogic environment.
Could you please zip $domain_home/WLSDM/logs folder and attach screen capture to support (at) wlsdm.com email.
Regards…

Hi,

Today we have worked on SOA-11g environment. JVM Resources Page and GarbageCollection Page problem has been resolved.

Please do the following when you face such a problem in another domain.

Kind Regards…

Backup startWeblogic.sh file of the domain

Add the “-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder” parameter to JAVA_OPTIONS in the file

JXM.Values.JVM.Resources.Dashborad.jpg

Hi,

“Thread Dump Analyzer” requires to full thread dump for analyzing.

Normally WLSDM gets a full thread dump. But if there is an exception, like in your case (connection timeout); by default, WLSDM tries to get it using WebLogic API. And sometimes WebLogic does not provide a full thread dump.

That’s why you didn’t get a full thread dump even your managed WebLogic server has a WLSDM agent.

Thanks.

Hi,

We are not supporting multiple log files (types) for a query/monitoring.

So currently you should repeat the monitoring queries.

But, you can assign the query to multiple servers for the “ServerLog”, “stdOut”, “stdErr” and “Diagnostic Log” types.

Kind Regards.

Hi,

WLSDM doesn’t support the multiple log files for log monitoring.

The current algorithm based on, “one log file, one search string” rule.

So, currently, there is no easy way to do this.

But we are going to report your request for the next WLSDM version.