Urbancode Deploy Discovery stopped.
Good day, I am trying to add the WebSphere cell to the resources in my UDeploy environment for me to run a deployment but I am getting the error condition below.
Can someone please tell me what the cause of this is. I am running UCD 6.2 with the WebSphere plugin. -------------------------------------------------------------------------------------------------------------------------------
Using credentials
Caught: java.lang.RuntimeException: Did not receive WAS Topology JSON from server. Discovery stopped.
java.lang.RuntimeException: Did not receive WAS Topology JSON from server. Discovery stopped.
at wasConfig$_run_closure2.doCall(wasConfig.groovy:328)
at wasConfig$_run_closure2.doCall(wasConfig.groovy)
at wasConfig.run(wasConfig.groovy:334)
|
Accepted answer
Ralph Schoon (63.1k●3●36●46)
| answered Jul 18 '16, 3:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
If you want answers to your question make sure to pick the right forum. This is the Urbancode Forum: https://developer.ibm.com/answers/smartspace/urbancode/
I found it using google urbancode forum Ralph Schoon selected this answer as the correct answer
Comments
Jirong Hu
commented Feb 17 '17, 8:27 p.m.
I am having the same error with a simple Deby installation. Why this answer was accepted? Because this is the wrong forum. |
One other answer
The root cause is: I installed with WebSphere console without security, so no need to login with a password. You can actually use any user without a password to login. But in the UCD agent property I used "admin" as the WebSphere User. So in the UCD server log you can find this kind of error. Once I remove the user from the agent property, it works fine.
2017-02-17 20:47:06,628 INFO SaContainer-4 com.urbancode.ds.subsys.deploy.agent.discovery.ApplyConfigExecutionListener - Successfully auto configured T410Node01Cell for command WebSphere Topology Discovery
2017-02-17 20:47:06,675 WARN http-0.0.0.0-8443-3 com.urbancode.ds.subsys.deploy.logs.AgentLogFileService - Unable to rename temporary log file to permanent storage. C:\Tools\ibm-ucd-622\server\var\temp\rest-upload-8594209943450558351log copied to -> C:\Tools\ibm-ucd-622\server\bin..\appdata\logs\store\70\60\7060cc80-3d34-46a4-989e-0827599c4900\6e31ea4d-ff2a-45db-8f76-700b3ac2310c-stdOut.txt but failed to rename to -> C:\Tools\ibm-ucd-622\server\bin..\appdata\logs\store\70\60\7060cc80-3d34-46a4-989e-0827599c4900\stdOut.txt
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.