Error in SAP JCO connection leads to SAP J2EE engine restart

Hi All
i am using SAP Jco 2.0 to connect to backend.The code runs fine for tables but when i try to access fields like
getExportParameterList().getField("EMPLOYEENUMBER").toString(); it leads to j2ee engine restarts.
Is it a bug?
Is it possible for an exception to restarts server even with error?
Regards
Shankar

Hi,
Does your application uses any property files or log files? If so, check if they are available in the specified location.
Check the defaultTrace, you will know why the server is getting restarted. Have a placeholder in the defaultTrace so that you can easily identify the error.
Thanks,
Venkat

Similar Messages

Error while obtaining JCO connection when creating JCO connection

Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at
com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at
com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes Defloo

Hi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

Error in launching guided procedure: Error while obtaining JCO connection.

Hello experts,
we've a problem with webdynpro java calling a guided procedure.
We've defined an endpoint for our callable object, as you can see the test of the connection works fine:
In the configuration of our callable object we use the endpoint above:
And we can test the callable object: it works well, call the right BAPI and find the results.
But when the GP is called and this callable object try to call the BAPI in the background it doesn't work at all.
In the log and trace of the portal we find this:
A technical callable object exception ocurred: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
com.sap.caf.eu.gp.model.co.tech.TechnicalCallableObjectException: Le service RecupActeurs n'a pas pu être exécuté : La connexion pour le nom de connexion SAP_R3_HumanResources n'a pas pu être chargée à partir de System Landscape Directory (SLD) : Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:101)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl$CallableObjectExecutor.run(BackgroundCOExecutorImpl.java:126)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:504)
at com.sap.caf.eu.gp.model.co.background.impl.BackgroundCOExecutorImpl.execute(BackgroundCOExecutorImpl.java:581)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.BackGroundActionProcessorHelper.processAction(BackGroundActionProcessorHelper.java:183)
at com.sap.caf.eu.gp.model.pfw.wfc.local.impl.queue.BackgroundCOQueueProcessor.run(BackgroundCOQueueProcessor.java:263)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.caf.eu.gp.base.exception.EngineException: Connection that belongs to connection name SAP_R3_HumanResources could not be loaded from System Landscape Directory (SLD): Error while obtaining JCO connection.
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:138)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.analyseConnectionMode(ConnectionDeliverRFC.java:185)
at com.sap.caf.eu.gp.model.connect.rfc.impl.ConnectionDeliverRFC.deliverConnection(ConnectionDeliverRFC.java:91)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SAPSystemConnector.deliverMetaData(SAPSystemConnector.java:116)
at com.sap.caf.eu.gp.model.connect.pvd.saprfc.impl.SAPRFCServiceProvider.executeExternalService(SAPRFCServiceProvider.java:232)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceManager.executeExternalService(ExternalServiceManager.java:139)
at com.sap.caf.eu.gp.model.connect.impl.ExternalServiceBackgroundCOContainer.execute(ExternalServiceBackgroundCOContainer.java:89)
... 9 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:160)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:41)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.resolveClientConnection(SLDConnectionManager.java:169)
at com.sap.caf.eu.gp.model.connect.rfc.impl.SLDConnectionManager.getClientConnection(SLDConnectionManager.java:102)
... 15 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'SAP_R3_HumanResources'
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:658)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:485)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:233)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
... 19 more
Caused by: com.sap.tc.webdynpro.services.sal.um.api.WDUMException: No client user defined for the current request (no regular Web Dynpro request as ITask is null.
at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory.getCurrentUser(AbstractClientUserFactory.java:48)
at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.getCurrentUser(WDClientUser.java:67)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:591)
It seems that the GP could not connect to the SLD to call the JCO, but as said before, when we test the callable object, it calls the BAPI without any problem.
We tried to recreat either the JCO and the Endpoint but without success.
Any help will be appreciated.
Thank you.

Hi.
Thanks for your answers.
Here are the things :
From the GP administration, the endpoint's test is working.
From the SLD, the JCO is working too.
From the Web Dynpro Content Administrator, the JCO's test is working too.
From the GP Desing Time, the callable object supposed to call the FM uses the right endpoint, and the test is working too, we retreive data from the backend.
From our app, calling the GP process that includes our callable object, we have errors pasted above...
Regards.

Sap jco connection

hi everyone,
         Here 2 problems are there:...............
1)   http://localhost:50000/index.html
       in browser i got this message
    404   Not Found
                         SAP NetWeaver Application Server 7.10 / AS Java 7.10
The requested resource does not exist.
Details: Go to main page of this application!
2) I just taken web moudle project in that i have taken one java class
   I written this program to connect to sap via jco
import com.sap.mw.jco.*;
public class Testing extends Object{
            JCO.Client mConnection;
             public Testing() {
                   try {
                  // Change the logon information to your own system/user
                  System.out.println("1");
                   mConnection =
             JCO.createClient("001", "userid", "password","language","localhost", "00");
                      System.out.println("2");
                  mConnection.connect();
                  System.out.println("3");
                  System.out.println(mConnection.getAttributes());
                  mConnection.disconnect();
               catch (Exception ex) { ex.printStackTrace(); System.exit(1);}
            public static void main (String args[]) {
               Testing app = new Testing();
while i run this java file it get error message: shown in below..............................
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM GWHOST=localhost, GWSERV=sapgw00, ASHOST=localhost, SYSNR=00
LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host 127.0.0.1, service 3300)
TIME        Wed Jan 31 16:56:55 2007
RELEASE     640
COMPONENT   NI (network interface)
VERSION     37
RC          -10
MODULE      nixxi_r.cpp
LINE        8716
DETAIL      NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
     at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeConnect(Native Method)
     at com.sap.mw.jco.rfc.MiddlewareRFC$Client.connect(MiddlewareRFC.java:1123)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3113)
     at com.Testing.<init>(Testing.java:27)
     at com.Testing.main(Testing.java:35)
what parameters should i pass to JCO.createClient("................"); here
where should i get this information..................to test connection to sap via jco
thanks,
tony

hi prince,
here j2ee engine is running in sapMMC ,it comes in green color....
   plz send me ........
thanks,
tony

Error while obtaining JCO connection.

Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
But when it signs the user gets the message Error while obtaining JCO connection.
I was reviewing my WebDynpro on my site by following these steps:
1 I will http://portal:port
2 I clicked Webdynpro
3 I click on Content Administrator
I clicked on 4 Maintain JCO destinations
and then I log shows the following:
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
    ... 39 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Version     null
DOM version     null
Client Type     ns7
Client Type Profile     nn7
ActiveX     disabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
J2EE Engine     7.00 patchlevel 109886.44
Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system     AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale     en_US
Time of Failure     Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available     null
sap.com/tcwddispwda
No information available     null
sap.com/tcwdcorecomp
No information available     null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
     at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
What should I do??

Hi Antonio,
Follow the below note for Jco related troubleshooting.
https://service.sap.com/sap/support/notes/919850
Are you able to see the 4 Jco connections green?
Regards,
Debasis.

Error while obtaing JCO connection

In Bussiness planning in portal. When i click Planning tab in Enterprise portal, its throwing an error that "error while obtaining JCO connection". I cant proceed furtherI
I am working in my own system.
I have checked many posts and i have done some JCO destinations as per the instructions but it's vain.
The detailed error is as follows;
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(CharRelInst): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.ip.bi.plan.workbench.wdp.InternalInfoprovController.wdGetCharRelInstInterface(InternalInfoprovController.java:296)
at com.sap.ip.bi.plan.workbench.InfoprovController.checkSavable(InfoprovController.java:254)
... 48 more
please give some pointers like what needs to be done JCO settings in Backend.
Thanks in advance.

Niranjan,
3 causes and many more....
First and most probable cause is that your CR content in SLD is old....
FIX - to fix this download latest cimsap and crcontent from service.sap.com and implement in SLD.
Second cause user is locked
FIX - unlock in R/3
Third cause could be that the connection pool in JCO is exhausted.
FIX - increase connection pool in JCO.
More causes.
With this new version it appears that any error before connection is created ends up showing this, so I would really go into default trace and look there for original errors, that is the way I found JCO pool was exhausted, that error was not being forwarded and instead it was showing this error...
reward points if helpful

Error while obtaining JCO connection in t-code RSPLAN

Hi Gurus,
I have installed ECC 6.0 SR3 and i have added BI_CONT and updated all the patches. But while trying to access the t-code RSPLAN and after clicking on the START MODELER button it is opening in a browser . after giving the user id and password in the browser , while opening the page it is showing the error " Error while obtaining JCO connection". and how to create jco connections in visual admin.
can anybody please help me in this issue.
Thanks in advance.
Regards,
Babu.

Hi,
when i was trying to open RSPLAN T-Code in BI, i able to open start modeller it says that http://udnubd1:8003/sap/public/myssocntl?sap-client=320 and says that cannot find server. So i request you please can anyone help me onthis issue.
Thanks,
Reddy

Error while testing JCO connections

Hi,
Can anyone please help me with the following error.I am getting this when I'm testing my JCO connection :
RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=cgnsap13 SYSNR=01 GWHOST=cgnsap13 GWSERV=sapgw01 PCS=1 LOCATION SAP-Gateway on host cgnsap13 / sapgw01 ERROR max no of cpic clients exceeded (300)
Thanks and regards,
Lisha

Hi
Please ensure that you have the msgserver entry in your services file. The problem you are getting is because of the message server. you need to have a entry like
sapms<System ID> tcp/3601
Also go to your SAP logon pad and check for groups. and type the sid in the box along with the appserver and then click on generate list. You should get some logon groups. If not you can be sure that your message server is not configured properly. Talk to your SAP Basis person
regards
Ravi

Error in creating JCo connection with destination type'Load-Balanced Con'

Hi,
I am working on webdynpro application(NW 04s), i need to connect with the backend system(ECC 6.0) using model.I configured my SLD and created technical system successfully.
The technical system got created with an error:
CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_BCApplicationServer.CreationClassName="SAP_BCApplicationServer",Name="ID1.Number.01.HostName.ahsides"
But the system got created so I proceeded with Jco connection creation:
I need to create 2 Jco connections for this,
First with Data Type 'Application Data' & Destination Type 'Single-Server connection'. Second with Data Type 'Data Dictionary' & Destination type 'Load-balanced Connection'.
The first Jco with 'Single-Server connection' got created successfully and ping and test is also successfull.
The second Jco connection with 'Load-Balanced Connection' got created successfull but it is throwing error while pinging and testing.
Ping Error : Failed to ping JCo destination 'WD_EMPLOYEE_RFC_METADATA_DEST'.
Test Error : com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call
Please help me in this.This problem was with 'Load-Balanced Connection' only.

Hi,
Have you taken a look at the file %windir%\system32\drivers\etc\services?
If you haven't, try and find the line sapms<sid>, where sid is de SID of the system you-re trying to reach.
If the line isn't there write it down like this.
sapms<sid> 36<nr>/tcp
That works for me.

Error creation of JCO connection: System Already Exist

Hi Experts,
We have created the SLD connection to the ECC6.0 from the Portal 7.0.
Created one JCO connection using that SLD successfully for the Clinet 100.
Now we required to create one more JCO Connection for client200 also. But it is giving the Error that
System Already Exist.
How can we resolve this. When we create the JCO connection for one client, con't we create one more JCO connection for the same system for the differt client or not?
If so How do it?
Regards

I think you can add one more client in the existing connection. well, I am not sure about that even.
nikhil

SAP netweaver developer studio - deploying to j2ee engine - URGENT!!

I am trying a deploy a j2ee application from SAP netweaver developer studio. It is asking for SAP J2EE engine's message server port. Do you know from where I can find that???

Hi,
the message server port is given in the profile file for the Central Services instance of the J2EE Engine. Here's the path to this file: \usr\sap\<SID>\SYS\profile directory. The file name is formed using the following scheme: <SID>_<Central_instance_name>_<hostname>.
Open it with a text editor and have a look at the value of the rdisp/msserv property (this is the port of the message server you need to use).
Regards,
Ivo

SAP ROUTER CONNECTION STRING FOR SAP SERVERS

Hi,
I want to create saprouter string for accessing ecc6.0 server, router is given with one public ip and my server is in domain,help me in creating saprouter string.
Thanks & Have a good day
Naveen

Hi Naveen,
There are some SAP notes that can help you understand how to create such strings.
The main idea is to create a string like this:
/H/<ip address of your saprouter>/S/<service port of your saprouter>/H/
Regards,
Val

SAP XI connection path with SAP

Hi,
Anyone can elaborate about the path of SAP XI with SAP or any other Application S/w. How to configure with SAP SRM 7.0 (SUS).

Hello Sanjit,
This thread will be really helpful to you.please check
SRM XI scenario
Regards,
Amit Barnawal

ERROR:can't find native registration class while J2EE Engine startup

Hi
Iam trying to integrate a Java Profiler application which contains a native library(namely ProfilerDLL.dll) with the J2EE Server.Here are the steps which i had followed
1. Added the following Java option through the config tool of WebAS.<b> -XrunProfilerDLL</b>.
2.Restarted the server.
Server does not starup and throws a error with exit
code -1 .
Here is the log
JStartupIReadSection: read node properties [ID7217950]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_04
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.library.path=/usr/sap/J2E/JC00/j2ee/os_libs -XX:NewSize=32m -XX:MaxNewSize=64m -XX:NewRatio=3 -XX:+DisableExplicitGC -XX:MaxPermSize=128m -XrunProfilerDLL:1 -Xbootclasspath/a:jakarta-regexp.jar;profiler_trace.jar;commons-lang.jar -D__PROFILER_PACKAGE_FILTER=__A__com.sap.engine.boot.Start;__M__sun.;__M__com.sun.;__M__java.;__M__javax.; -D__PROFILER_TIMING_METHOD=1 -Drdbms.driverLocation=C:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global/
-> java vm version : 1.4.2_04-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 256M
-> init heap size : 128M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : no
-> debug mode      : no
-> debug port      : 1024
-> shutdown timeout: 120000
[Thr 420] JLaunchISetDebugMode: set debug mode [no]
[Thr 5780] JLaunchIStartFunc: Thread 5780 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: -Denv.class.path=;C:\D\vim\Intellisense\javaft.jar;C:\j2sdk1.4.2_04\lib\tools.jar
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djava.library.path=/usr/sap/J2E/JC00/j2ee/os_libs
-> arg[ 9]: -XX:NewSize=32m
-> arg[ 10]: -XX:MaxNewSize=64m
-> arg[ 11]: -XX:NewRatio=3
-> arg[ 12]: -XX:+DisableExplicitGC
-> arg[ 13]: -XX:MaxPermSize=128m
-> arg[ 14]: -XrunProfilerDLL:1
-> arg[ 15]: -Xbootclasspath/a:jakarta-regexp.jar;profiler_trace.jar;commons-lang.jar
-> arg[ 16]: -D__PROFILER_PACKAGE_FILTER=__A__com.sap.engine.boot.Start;__M__sun.;__M__com.sun.;__M__java.;__M__javax.;
-> arg[ 17]: -D__PROFILER_TIMING_METHOD=1
-> arg[ 18]: -Drdbms.driverLocation=C:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 19]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global/
-> arg[ 20]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 21]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 22]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 23]: -Djava.library.path=C:\j2sdk1.4.2_04\jre\bin\server;C:\j2sdk1.4.2_04\jre\bin;C:\j2sdk1.4.2_04\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\PROGRA1\SECUDE\SECUDE1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;c:\progra~1\ixos\bin;C:\j2sdk1.4.2_04\bin;C:\j2sdk1.4.2_04\jre\bin\server;C:\j2sdk1.4.2_04\lib\tools.jar;C:\Program Files\JProbe Profiler 5.2.1\bin;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\sherlok;C:\cygwin\bin;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\JVMStatAnalysis\jvmstat\bat;;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 24]: -Dmemory.manager=256M
-> arg[ 25]: -Xmx256M
-> arg[ 26]: -Xms128M
-> arg[ 27]: -DLoadBalanceRestricted=no
-> arg[ 28]: -Djstartup.mode=JCONTROL
-> arg[ 29]: -Djstartup.ownProcessId=1740
-> arg[ 30]: -Djstartup.ownHardwareId=I1361390454
-> arg[ 31]: -Djstartup.whoami=server
-> arg[ 32]: -Djstartup.debuggable=no
-> arg[ 33]: -DSAPINFO=J2E_00_server
-> arg[ 34]: -DSAPSTARTUP=1
-> arg[ 35]: -DSAPSYSTEM=00
-> arg[ 36]: -DSAPSYSTEMNAME=J2E
-> arg[ 37]: -DSAPMYNAME=INLD50035793_J2E_00
-> arg[ 38]: -DSAPDBHOST=
-> arg[ 39]: -Dj2ee.dbhost=INLD50035793
[Thr 5780] Wed Sep 22 15:30:06 2004
[Thr 5780] JHVM_LoadJavaVM: Java VM created OK.
<u>[Thr 5780] ***ERROR => can't find native registration class [com.sap.bc.proj.jstartup.JStartupNatives] [jhvmxx.c     417]
[Thr 5780] JLaunchCloseProgram: good bye (exitcode=-1)</u>
Any ideas how to fix this problem?
Thanks
S.Shylaja

Btw: I get the warning starting IIS - It seems to me that IIS tries to load Tomcat on-the-fly. The Tomcat load the fails and IIS continues to load successfully.
The beginning of the IIS Event log outputs this:
Apache Jakarta Connector2, Information, Info: [jk_vm_default.c (340)]: vm.detach() ok
Apache Jakarta Connector2, Warning, Error: [jk_worker_jni.c (308)]: Can't find class org/apache/jk/apr/AprImpl
Apache Jakarta Connector2, Information, Info: [jk_worker_jni.c (297)]: Loaded org/apache/jk/apr/TomcatStarter
Apache Jakarta Connector2, None, Debug: [jk_vm_default.c (302)]: vm.attach() allready attached
Apache Jakarta Connector2, Information, Info: [jk_worker_jni.c (252)]: jni.validate() class= org/apache/jk/apr/TomcatStarter
Apache Jakarta Connector2, Information, Info: [jk_vm_default.c (607)]: vm.open2() done
Apache Jakarta Connector2, Information, Info: [jk_vm_default.c (500)]: vm.init(): Jni lib: C:\wwwapps\j2sdk1.4.2_01\jre\bin\client\jvm.dll
/watson

Error in SAP JCO connection leads to SAP J2EE engine restart

Similar Messages

Maybe you are looking for