SOLVED I can’t seem to get the WLSDM wizard to complete.

[wlcommunityusers]

I have successfully configured 2 of our 4 domains. One of the SOA domains (SOATST) I can’t seem to get the WLSDM wizard to complete. The domain registers in the 4th step of the wizard, but fails on the 5th step reading the domain. Post registry, when I check WL-OPC I can see the domain, but the WLSDM console keeps reverting me back to step 1 of the wizard. I have the WAR file in place in console-ext, the library for the agent in the [DOMAIN_HOME]/wlsdm_agent directory. I’m attaching the Admin log, our setUserOverrides environment variable file, and an agent log for our OSB server.

I have stopped the domain and removed the WLSDM directories a couple of times and restarted. I imagine I’m missing something simple here, but can’t seem to find the issue.

####<Apr 18, 2023 3:43:07 PM PDT><SEVERE><WLSDM><BEA-000000><null

java.lang.NullPointerException
                at com.wlsdm.Q.K.getDeployedJMSServers(MetricUtilities.java:1326)
                at com.wlsdm.frontend.provider.WA.getJMSServerList(MetricsData.java:489)
                at com.wlsdm.P.J.E(Data.java:11019)
                at com.wlsdm.P.J.A(Data.java:336)
                at com.wlsdm.P.J.doGet(Data.java:171)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
                at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:295)
                at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
                at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
                at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:353)
                at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
                at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
                at com.wlsdm.P.D.doFilter(RRFilter.java:327)
                at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
                at com.bea.console.internal.ParamFilter.doFilter(ParamFilter.java:38)
                at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
                at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32)
                at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
                at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3800)
                at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3766)
                at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
                at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
                at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
                at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
                at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2454)
                at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2302)
                at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2280)
                at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1721)
                at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1681)
                at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:272)
                at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
                at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
                at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
                at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
                at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
                at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
                at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

[deniz.bedel-wlsdmteam]

@wlcommunityusers

We have reproduced the error you received in our own environment and released a special WLSDM version for you. You can find the WLSDM upgrade steps and JMS Dashboard creation guide below.

After doing the following operations, we kindly ask you to send us the log files for each server where WLSDM is installed. So we can check the correctness of the installation. Also, can you get feedback to us whether the dashboard creation process was successful or not?

WLSDM Upgrade

1. Install WLSDM Fix version. You can find the files from the link below.
   Link: —
2. Replace the wlsdm_agent.jar file with the new release and keep wlsdm_agent.jar JVM arguments. *($JAVA_OPTIONS)
3. Replace wlsdm.war file with the new release to WebLogic domain’s console-ext folder
4. (Re)start WebLogic Managed Server(s) then Administration Server
5. That’s all! WLSDM will be upgraded after restart processes

JMS Dashboard Creation Guide
We attach screenshots below the mail so that you can easily follow the steps here. You can follow the steps in order from the screenshots there.

1. Navigate to Configuration -> Metric Settings & JMX Mbean Browser category from the drop-down menu on the left. (Step 1 and 2)
2. Click on the JMX MBean Browser(+Add New) button on the top right. (Step 3) In the pop-up window that opens, you can select the metrics you want to create the dashboard.
3. Select the node you want to monitor. (step 4)
4. Type the metric you want to search in the metric group. We will write jms. Select the “Metric Group”, “Metric Instance” and “Metric” options selected in the 3rd picture from the list below. (Steps 5, 6 and 7)
5. Fill the Create Smart Dashboard field as “JMS_Server”. (Step 8 )
6. In the Metric Add Options category, move the JMS_Server parameter to the Applied Dashboard field. Just click on it (Step 9)
7. Click the “Add to List” button and save (Steps 10 and 11)
8. Click on the name of your server in the pop-up window that opens, move it to the Applied Servers field, and then click Continue. (Steps 12 and 13)
9. Go to the Smart Dashboard category and maximise the OSB Smart Dashboard subcategory. (Picture 5)
10. Check that your dashboard is created on the page that opens.

Screenshots
Picture 1

Picture 2

Picture 3

Metric Group: JMSDestinationRuntimeMBean
Metic Instance: com.bea:JMSServerRuntime=OSB-JMSServer,Name=<Your_JMS_Module_Name>ServerRuntime=osb_server
Metric: MessagesCurrentCount(long)

Picture 4

Picture 5

Picture 6

[deniz.bedel-wlsdmteam]

This problem is most probably caused by an incorrect JMS configuration; can you please also check your JMS configurations?

Could you provide us below information with screenshot?

1- WebLogic version
2- Java version

[wlcommunityusers]

@deniz-bedel-wlsdmteam Thank you. I don’t see any JMS configuration issues in our SOATST domain. The Weblogic version is 12.2.1.4 and is patched with Oracle’s Jan 2023 CPU patches. Our JDK version is 1.8.0_361. SOATST is configured as an enterprise deployment with admin server domain files on shared storage and managed server domain files on local storage on two separate hosts.

I’ll continue to review JMS. If you have any other suggestions please let me know.

[wlcommunityusers]

@wlcommunityusers
the config also seems to be erroring while analyzing the mounted file systems.

at com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.run(DiskSpaceRuntimePopulator.java:71) at 
com.wlsdm.monitoring.beans.GlobalPopulatorControl$Executer.run(GlobalPopulatorControl.java:49) at java.lang.Thread.run(Thread.java:750) > ####<Apr 23, 2023 8:33:40 PM 
PDT><SEVERE><WLSDM><BEA-000000><com.wlsdm.monitoring:MountPartitionName=/exagrid_tar,Type=DiskSpaceRuntime javax.management.InstanceNotFoundException: 
com.wlsdm.monitoring:MountPartitionName=/exagrid_tar,Type=DiskSpaceRuntime at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:295) at 
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:299) at javax.management.remote.rmi.RMIConnectionImpl_12214_WLStub.setAttribute(Unknown Source) at weblogic.management.remote.common.RMIConnectionWrapper$14.run(ClientProviderBase.java:1218) at 
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163) at 
weblogic.security.Security.runAs(Security.java:62) at weblogic.management.remote.common.RMIConnectionWrapper.setAttribute(ClientProviderBase.java:1216) at sun.reflect.GeneratedMethodAccessor924.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at 
java.lang.reflect.Method.invoke(Method.java:498) at weblogic.management.remote.common.InvocationContextProxyHandler.invoke(ClientProviderBase.java:684) at 
com.sun.proxy.$Proxy276.setAttribute(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.setAttribute(RMIConnector.java:961) at 
com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.doPopulate(DiskSpaceRuntimePopulator.java:288) at com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.doRemote(DiskSpaceRuntimePopulator.java:256) at 
com.wlsdm.monitoring.beans.DiskSpaceRuntimePopulator.run(DiskSpaceRuntimePopulator.java:71) at 
com.wlsdm.monitoring.beans.GlobalPopulatorControl$Executer.run(GlobalPopulatorControl.java:49) at java.lang.Thread.run(Thread.java:750) > ####<Apr 23, 2023 8:33:40 PM 
PDT><SEVERE><WLSDM><BEA-000000><com.wlsdm.monitoring:MountPartitionName=/exagrid_tar,Type=DiskSpaceRuntime javax.management.InstanceNotFoundException: 
com.wlsdm.monitoring:MountPartitionName=/exagrid_tar,Type=DiskSpaceRuntime

[deniz.bedel-wlsdmteam]

@wlcommunityusers

We have reproduced the error you received in our own environment and released a special WLSDM version for you. You can find the WLSDM upgrade steps and JMS Dashboard creation guide below.

After doing the following operations, we kindly ask you to send us the log files for each server where WLSDM is installed. So we can check the correctness of the installation. Also, can you get feedback to us whether the dashboard creation process was successful or not?

WLSDM Upgrade

1. Install WLSDM Fix version. You can find the files from the link below.
   Link: —
2. Replace the wlsdm_agent.jar file with the new release and keep wlsdm_agent.jar JVM arguments. *($JAVA_OPTIONS)
3. Replace wlsdm.war file with the new release to WebLogic domain’s console-ext folder
4. (Re)start WebLogic Managed Server(s) then Administration Server
5. That’s all! WLSDM will be upgraded after restart processes

JMS Dashboard Creation Guide
We attach screenshots below the mail so that you can easily follow the steps here. You can follow the steps in order from the screenshots there.

1. Navigate to Configuration -> Metric Settings & JMX Mbean Browser category from the drop-down menu on the left. (Step 1 and 2)
2. Click on the JMX MBean Browser(+Add New) button on the top right. (Step 3) In the pop-up window that opens, you can select the metrics you want to create the dashboard.
3. Select the node you want to monitor. (step 4)
4. Type the metric you want to search in the metric group. We will write jms. Select the “Metric Group”, “Metric Instance” and “Metric” options selected in the 3rd picture from the list below. (Steps 5, 6 and 7)
5. Fill the Create Smart Dashboard field as “JMS_Server”. (Step 8 )
6. In the Metric Add Options category, move the JMS_Server parameter to the Applied Dashboard field. Just click on it (Step 9)
7. Click the “Add to List” button and save (Steps 10 and 11)
8. Click on the name of your server in the pop-up window that opens, move it to the Applied Servers field, and then click Continue. (Steps 12 and 13)
9. Go to the Smart Dashboard category and maximise the OSB Smart Dashboard subcategory. (Picture 5)
10. Check that your dashboard is created on the page that opens.

Screenshots
Picture 1

Picture 2

Picture 3

Metric Group: JMSDestinationRuntimeMBean
Metic Instance: com.bea:JMSServerRuntime=OSB-JMSServer,Name=<Your_JMS_Module_Name>ServerRuntime=osb_server
Metric: MessagesCurrentCount(long)

Picture 4

Picture 5

Picture 6

[wlcommunityusers]

@deniz-bedel-wlsdmteam

Hello, after replacing the jar and war files and restarting servers, WLSDM is prompting me for a new license key. We only received a license for WL_OPC which is invalid for WLSDM. I imagine once the domain is registered I won’t require the WLSDM licesnse, but please confirm that is the case and let me know how to get past the license key now.

[deniz.bedel-wlsdmteam]

@wlcommunityusers

Hi ,

You can use the WLSDM Trial license I sent below. Then you can register the domain to WL-OPC.

---

License key has been delivered privately.

---

[wlcommunityusers]

@deniz-bedel-wlsdmteam

I can register the domain with the temporary license, but the wizard still fails to complete successfully.

Wlsdm.log:

####<May 16, 2023 2:12:21 PM PDT><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by wrong product name.>
####<May 16, 2023 2:12:39 PM PDT><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by wrong product name.>
####<May 16, 2023 2:14:55 PM PDT><INFO><WLSDM><BEA-000000><WLSDMOPCServer.RegisterController:: UpdateCreds response code: 200>
####<May 16, 2023 2:14:55 PM PDT><INFO><WLSDM><BEA-000000><WLSDMOPCServer.RegisterController:: UpdateCreds response: 1>
####<May 16, 2023 2:14:58 PM PDT><INFO><WLSDM><BEA-000000><License Published by the WL-OPC:
####<May 16, 2023 2:29:42 PM PDT><INFO><WLSDM><BEA-000000><WLSDMOPCServer.RegisterController:: UpdateCreds response code: 200>
####<May 16, 2023 2:29:42 PM PDT><INFO><WLSDM><BEA-000000><WLSDMOPCServer.RegisterController:: UpdateCreds response: 1>
####<May 16, 2023 2:29:45 PM PDT><INFO><WLSDM><BEA-000000><License Published by the WL-OPC:
####<May 16, 2023 2:36:39 PM PDT><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by expire.>
####<May 16, 2023 2:37:21 PM PDT><WARNING><WLSDM><BEA-000000><Has No Valid License. Caused by expire.>

[deniz.bedel-wlsdmteam]

@wlcommunityusers

Hi,

We need all log files to get more detailed information about the problem. Can you zip and send us the WLSDM/logs directory of all the servers you have?

[wlcommunityusers]

@deniz-bedel-wlsdmteam

I have sent a link to an FTP site containing a zip of the logs in a separate email.

[deniz.bedel-wlsdmteam]

@wlcommunityusers

We would like to have a meeting with you about the problem that occurs below.

We will schedule a meeting if you give us your available time in Date/Time.

[wlcommunityusers]

@deniz-bedel-wlsdmteam

As a follow up to yesterday’s meeting I wanted to let you know that I was able to configure our SOATST environment using the WLSDM setup wizard by bypassing our load balancer and OHS servers. There was a comment made in the meeting about the header size limit for the HTTP server specifically so I thought I would check and see if bypassing would allow the configuration. By bypassing, I was able to complete the configuration and set default metrics for Servers, Deployments, Data Sources and JMS.

[deniz.bedel-wlsdmteam]

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