Hi,
I put the Quiesce mode , but after Exits Quiesce Mode in the Administrator console when I click on Adapters it shows me nothing , so i can not Enable Connexion DB , and Unable to run adapter service DB in Designer .
i try this mode in 2 other Server , the same problem in all IS
do you have any idea please ?
Hi @bgh.said
A few questions to diagnose
- Are the other menu options available ( Server , Logs, etc)
- While exiting the quiesce mode, do you see any error messages in the server logs /error logs pointing to the issue.
- Which version are you using?
- Have the latest core fixes applied?
-NP
1 Like
Hi @Nagendra_Prasad
1.yes, the other menus are available
2.we are using 10.5 version
3. the laste core fixes are applied yes
logs/error
| 2022-03-29 07:55:36 EDT | wm.art.adapter.deployment:registerAdapterType | java.lang.NullPointerException at com.wm.pkg.art.ns.ConnectionDataNodeManager.createConnectionManager(ConnectionDataNodeManager.java:958) | Stack trace data … | 1dc2bbd5-9ffa-4f68-8828-82958761046c | NULL | 1dc2bbd5-9ffa-4f68-8828-82958761046c | |
|---|---|---|---|---|---|---|---|
| 2022-03-29 07:55:36 | |||||||
| EDT | wm.art.admin:startup | wm.art.admin:initializeGlobals | |||||
| wm.art.admin:startup(/0) | [ART.0000.0000] [ART.0000.0000] Error during Integration Runtime startup. | ||||||
| [ART.0000.0000] Error during Integration Runtime startup. | |||||||
| Caused by: com.wm.pkg.art.error.MultiReasonException: [ART.0000.0000] Error during Integration Runtime startup. | Stack trace data … | 1a752040-7558-4cd1-9aac-8eb13fb3cf01 | NULL | 1a752040-7558-4cd1-9aac-8eb13fb3cf01 | |||
| 2022-03-29 07:55:36 | |||||||
| EDT | wm.art.admin:initializeGlobals | [ART.0000.0000] [ART.0000.0000] Error during Integration Runtime startup. | |||||
| [ART.0000.0000] Error during Integration Runtime startup. | Stack trace data … | 5cefee85-639f-4798-8705-c1ad28e73012 | NULL | 5cefee85-639f-4798-8705-c1ad28e73012 | |||
| 2022-03-29 07:55:36 EDT | wm.art.admin:initializeGlobals | [ART.0000.0000] Error during Integration Runtime startup. | Stack trace data … | 992edfee-0791-4e6d-a1ff-c01cfa0b02fe | NULL | 992edfee-0791-4e6d-a1ff-c01cfa0b02fe | |
| 2022-03-29 07:55:36 EDT | wm.optimize.admin:startup | wm.optimize.admin:startup | java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0] | ||||
| Caused by: java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0] | |||||||
| Caused by: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0] | |||||||
| Caused by: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 | |||||||
| Caused by: com… |
This could be the reason for the issue, I would wait to see if there any other responses, else I would suggest you to raise a support ticket since a NullPointerException is a server side error caused by incorrect/missing data.
-NP
1 Like
yep I also agree with NP and further purse with SAG support team!
HTH,
RMG
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.