can't start app server run as lawson to start

 1 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Xin Li
Veteran Member Send Private Message
Posts: 134
Veteran Member

As required by landmark to run nodeagent and application server run as lawson. I can't start the application server. In the system error log it said " The file access permissions do not allow the specified action. - received while attempting to open server socket on port 1 ]." . I have made the whole Websphere directory wide open 777 and owned by lawson. still can't get app server to start.

Any idea? 

 

Below is the error message.

 

[8/20/15 13:39:57:448 CDT] 00000000 ORBRas        E com.ibm.ws.orbimpl.transport.WSTransport createServerSocket P=996968=0:CT ORBX0390E: Cannot create listener thread. Exception=[ java.net.BindExcept
ion: The file access permissions do not allow the specified action. - received while attempting to open server socket on port 1 ].
[8/20/15 13:39:57:607 CDT] 00000000 WsServerImpl  E   WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4  vmcid: 0x49421000  minor code: 56  completed: No
        at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:439)
        at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
        at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
        at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
        at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:502)
        at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298)
        at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
        at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
        at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
        at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
        at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
        at org.eclipse.core.launcher.Main.run(Main.java:981)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:341)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4  vmcid: 0x49421000  minor code: 56  completed: No
        at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:867)
        at com.ibm.ccess permissions do not allow the specified action. - received while attempting to open server socket on port 1 ].ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:60
5)


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Xin Li
Veteran Member Send Private Message
Posts: 134
Veteran Member

got it resolved by changing port for CRB listener to 0 in serverindex.xml file. IBM log file message is very misleading.