• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5036
  • Last Modified:

Websphere DMGR Error : startmanager.sh doesn't work while startServer.sh dmgr does

[Dmgr]$ /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/bin/startManager                                                             .sh
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr profile
ADMU3100I: Reading configuration for server: dmgr
ADMU0111E: Program exiting with error: java.io.FileNotFoundException:
           /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/config/cells/Cell/nodes/Manager/servers/dmgr/server.xml
           (No such file or directory)
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
           /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/logs/dmgr/startServer.log

: Log /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/logs/dmgr/startServer.log has tonnes of errors

[10/12/10 7:14:19:045 BST] 0000000a AdminTool     A   ADMU0111E: Program exiting with error: java.io.FileNotFoundException:
/opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/config/cells/Cell/nodes/Manager/servers/dmgr/server.xml (No such file or directory)
        at java.io.FileInputStream.<init>(FileInputStream.java:135)
        at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createFileInputStream(URIConverterImpl.java:469)
        at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createInputStream(URIConverterImpl.java:431)
        at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:897)
        at org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.load(CompatibilityXMIResourceImpl.java:259)
        at com.ibm.websphere.resource.WASResourceImpl.load(WASResourceImpl.java:61)
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249)
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
        at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:390)
        at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:158)
        at com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:143)
        at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:326)
        at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:299)
        at com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:275)
        at com.ibm.ws.management.tools.WsServerLauncher.initializeRepositoryAndLauncher(WsServerLauncher.java:397)
        at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:265)
        at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
        at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:120)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)

System doesn't have
/opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/config/cells/Cell/nodes/Manager/servers/dmgr/server.xml but have
/opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/config/cells/Cell/nodes/Manager/servers/Dmgr/server.xml


------ StartServer Dmgr command works fine. Note it's "Dmgr" instead of "dmgr" here
$ /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/bin/startServer.sh Dmgr
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/Profile/Dmgr/logs/Dmgr/startServer.log
ADMU0128I: Starting tool with the Dmgr profile
ADMU3100I: Reading configuration for server: Dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server Dmgr open for e-business; process id is 2264

I had a look at the directories under WAS_PROFILE and I see DMGR profile was created as "Dmgr" while on startManager it is looking for "dmgr".
That upper and lower case due to UNIX OS is a problem here.
I am after xml config file which store these details and need to know if hand editing them is allright?

$pwd
/opt/IBM/WebSphere/AppServer/profiles/Profile

[Profile]$ ls -lrt
drwxr-xr-x 17 was61 web  12288 Sep 27 08:28 Node
drwxr-xr-x 18 was61 web   4096 Jul  4  2011 Dmgr
0
crazywolf2010
Asked:
crazywolf2010
1 Solution
 
Radek BaranowskiFull-stack Java DeveloperCommented:
you don't need to dig into xmls just if you want to use "startManager" and not "startServer Dmgr"

you need to change

#Common args...
D_DMGR="dmgr" to Dmgr

in file
 /opt/IBM/WebSphere/AppServer/bin/startManager.sh
if you cat
/opt/IBM/WebSphere/AppServer/profiles/Profile/bin/startManager.sh you'll se the previously listed file is referenced, and ther you can find parameters I wrote.

change D_DMGR to Dmgr and it should be fine.

regarding XML editing - it's not advisable as you may loose config consistency and WebSphere won't be able to operate on XMLs (WebSphere tracks all changes and each change has its sort of operation ID, which is used during validation)

good luck


0
 
crazywolf2010Author Commented:
Issue Resolved
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now