Well!! n-th run, build failed again with same message as posted here - http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html
After this step. installation aborts.
Checked the App Server installation log, it was a successful installation.
Though its a failed installation, I tried to start the app server services.
I found some *amazing* things in startServer.log -
[11/25/09 22:31:28:005 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[11/25/09 22:31:28:157 EST] 0000000a AdminTool A ADMU0128I: Starting tool with the wp_profile profile
[11/25/09 22:31:28:159 EST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: WebSphere_Portal
[11/25/09 22:31:32:605 EST] 0000000a WsServerLaunc E ADMU3002E: Exception attempting to process server WebSphere_Portal
[11/25/09 22:31:32:607 EST] 0000000a WsServerLaunc E ADMU3007E: Exception com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E: Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:159)
at com.ibm.ws.process.ProcessFactory.create(ProcessFactory.java:69)
at com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.java:70)
at com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand.java:246)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:309)
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)
This line in the above stack trace *Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.* amazed me.
Why startServer is trying to look for java in /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java?
So, I have created folder structure like /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/ and created a softlink to original appserver/java/bin/java.
But, its looking for remaining binaries in the same location.
So, need to create softlink for the entiar installation under /opt/XYZWEBSPHEREXYZ/AppServer/
Lets see...
BTW - Found a technote on this -
http://www-01.ibm.com/support/docview.wss?uid=swg21202564
The technote mentions that, because its a broken installation, you get such an error.
11/26/09
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment