SOLVED delete domain after shutdown adminserver
-
Hi All,
we received this messasge, but in WL-OPC the domain was deleted but in logfile we find this.
2025-09-17 11:17:28.581 INFO 3751753 — [MessageBroker-3] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:18:28.379 INFO 3751753 — [MessageBroker-2] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:19:28.373 INFO 3751753 — [MessageBroker-4] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:20:28.391 INFO 3751753 — [MessageBroker-4] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:21:28.358 INFO 3751753 — [MessageBroker-2] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:22:28.354 INFO 3751753 — [MessageBroker-4] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:23:28.360 INFO 3751753 — [MessageBroker-2] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:24:28.352 INFO 3751753 — [MessageBroker-1] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:25:28.368 INFO 3751753 — [MessageBroker-2] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:26:28.352 INFO 3751753 — [MessageBroker-3] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001
2025-09-17 11:27:28.362 INFO 3751753 — [MessageBroker-3] com.wlsdm.opc.stats.ScheduledController : Trying to send unregister command to the WLSDM domain: [email protected]:7001Can help us to fic it?
Thannks -
Hi Federico,
If you are experiencing issues with WLSDM, could you please contact us by sending an email to [email protected]?
Kind regards.
-
Hi Federico,
Can you stop and restart WL-OPC? If this situation occurs again in the log, please let us know.
Kind regards.
-
Hi @can-sahin-wlsdmteam ,
after restart wl-opc errors was fix.
Thanks for your help.
And I ask you something…
How can fix this, if domain was shutdown and server was deleted in vcenter.this is the error
2025-09-22 10:33:46.839 ERROR 362132 — [MessageBroker-4] com.wlsdm.opc.D.C : LNK3662.servicios.redlink.com.ar ## Destination: LNK3662.servicios.redlink.com.ar:7001
java.net.UnknownHostException: LNK3662.servicios.redlink.com.ar
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:196) ~[na:1.8.0_301]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:394) ~[na:1.8.0_301]
at java.net.Socket.connect(Socket.java:606) ~[na:1.8.0_301]
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:287) ~[na:1.8.0_301]
at sun.net.NetworkClient.doConnect(NetworkClient.java:175) ~[na:1.8.0_301]
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) ~[na:1.8.0_301]
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) ~[na:1.8.0_301]
at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:292) ~[na:1.8.0_301]
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:395) ~[na:1.8.0_301]
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:203) ~[na:1.8.0_301]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162) ~[na:1.8.0_301]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056) ~[na:1.8.0_301]
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:189) ~[na:1.8.0_301]
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1340) ~[na:1.8.0_301]
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1315) ~[na:1.8.0_301]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:264) ~[na:1.8.0_301]
at com.wlsdm.opc.D.C.doPostRequest(Statics.java:967) ~[classes!/:v1.9.2]
at com.wlsdm.opc.controller.provider.WLSDMData.A(WLSDMData.java:627) [classes!/:v1.9.2]
at com.wlsdm.opc.controller.provider.WLSDMData.setDomainProperty(WLSDMData.java:76) [classes!/:v1.9.2]
at com.wlsdm.opc.stats.ScheduledController.checkDeletingDomains(ScheduledController.java:139) [classes!/:v1.9.2]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_301]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_301]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_301]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_301]
at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65) [spring-context-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_301]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_301]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_301]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_301]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_301]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_301]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_301]server LNK3662.servicios.redlink.com.ar was deleted and shutdown we cannot recovery it
Thanks
-
Hi Federico,
If you are experiencing issues with WLSDM, could you please contact us by sending an email to [email protected]?
Kind regards.
-
ok, thanks
