JCo connection timeout parameter

Hi members,
I have a RFC to File Asynchronous scenario.
The problem I am facing is that, it works intermittently. i.e. it works once and then I keep getting the error "Bean <ZRFC NAme> not found on host xyz".
Also as expected, the number of simultaneous successful connection also depends on the parameter "Initial connection" on sender RFC channel.
So there is a keepalive time on all asynchronous RFC connections. Could someone please let me know if there is a parameter for Asynchronous connections that need to be set.
Thanks
Manish.

Hello Apurva,
Refer to this pdf. Most of your questions will be answered.
http://www.i-barile.it/SDN/HowToConfigureTheJCoDestinationSettings.pdf
Regards
Deb

Similar Messages

Display established connection timeout parameter for an ACE

We are using an ACE Software version A2(3,5) and we try to diagnos a parameter map probleme.
Is there a way to know what is the timeout parameter applied to an established connexion? The command "show conn address ip netmask mask detail" only show the elapse idle time.
Thanks

When one of our top management tries to access a particulat Dash Board in EP system for the first time in the morning
he gets an error connection to partner timeout after 60 seconds
He, he, he.... I wonder why thing like this always happen to the big chiefs...
Anyhow... Does this happen to anyone else?... if not then it could be a name resolution issue... also check the exceptions on the proxy settings of IE.
Regards
Juan

Connection timeout with derby

Hi All
i am using derby as my database. i am new to derby, using it only becuase it is light weight.
what about the connection timeout parameter in derby.
i have checked the urlAttributes given in apache site (derby developers manual)
But no attribute is present for this parameter.
i am a regular user of mysql.
in mysql we do have socketTimeout parameter for timeout functionality which will help us to avoid the hang stated
do we have anythinng like that for derby
i am using the java JDBC for connecting to the database
Thanks
Vijay Sunder

Interesting. I didn't find anything either.
Actually timeouts in connection strings is rather new, older drivers didn't allow it, so maybe it doesn't either.
You can get the source and look it up. Might just be a doc bug. And if not there you could add it.

JCO - Connection reset by peer - after 5 minute timeout

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

JCO timeout parameter?

Dear all,
We are trying to change a timeout parameter for JCO connections. We use ESS-MSS on our portal and when a user leave it without using the log off process, the system keep some RFC connections during one hour. We would like to keep those connections during only 30 minutes. Do you know how to proceed? Is there any parameter to change?
Please note that according to the note 947376 we know that 6 jco metadata connections are always alive to improve performance. But there are some others (for the users) that we would like to close automaticaly after 30 minutes.
Many thanks for your help!
Best regards,
Olivier

Hello Guys,
Thank you very much for your answer. Is there a way to close all JCO connections automaticaly from the abap or java stack or should I set a timeout for each JCO?
Thanks in advance,
Olivier

MII 12.1 time out for JCo Connection

I'm running this MII transaction that, is using a JCO connection to run a Function Module in SAP.
The problem we have is, that function module takes more than 60 seconds to run an return the values, that is correct because we are gathering a big amount of data, so if we run the function Module inside SAP it works ok, BUT, if we run the transaction from MII we receive a time out after exactly 60
seconds.
We have already modified several time out parameters inside MII
but those changes are not making any difference.
Do you know where that JCo time out parameter is inside MII 12.1?

Hi Salvador,
Try to increase the session timeout to 300 in SAP Menu --> System Properties. Initial it will be 60 sec only.
And increase MII workbench Read Timeout as well. Help --> Setting --> Read Timeout
If it doesn't solved your problem, go through below post
How to set timeout for each level in MII?
Regards,
Praveen Reddy

Unable to close metadata jco connection

Hi Experts,
when checking the JCo Connection Pools in Web Dynpro Console, I found that all MetaData JCo are in use and unable to disconnect automatically.
the following is metadata jco destination setting
Maximal Pool Size 1
Maximum Connections 5
Connection Timeout 60
Maximum Wait Time 10
how can i do to close these jco connection?

Hi Sidney,
I dont really understand why you want to remove the Jco connections. If you click on the "Remove" button as posted earlier by someone, it will completely remove your Jco configurations and you have to create them again on your own. SO, dont do that.
If you want to disconnect the Jco connection in webdynpro java, we can do that by using the following piece of code at the end of the connection process.
As far as I know, by default the Jco connections gets disconnected after certain time limit. Because, I never had to disconnect the Jco whenever I used one.
wdContext.currentModelElement().modelObject().modelInstance().disconnectIfAlive()
Regards,
Gopal.

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.

Creation of JCO connection

Hi all,
i'm having a problem when creating JCO connections for WebDynpro.
When I create an "Application data" connection with "Single Server Connection" the connection is created sucessfully and I have successfull test and ping.
If I create an "Application data" conncetion with "Load Balancing" then the connection returns an error
"com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection"
The Metadata connections it's only possible to create with "load-balanced connection" and then all of them gaves this last error.
Then, when I try to run an portal application for MSS/ESS it gave
"Failed to resolve connection parameter for 'SAP_R3_SelfServiceGenerics_MetaData'"
Someone knows why is that ? Can I pass over it !?!?
I'm stuck because I don't know what more can I do !!! I think that I've read all documentation about that !!
Best Regards,
Thanks very much
Pedro

Hi Narayana,
See this link for sample applcation
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc9baf90-0201-0010-479a-b49b25598ebf
Check this link too
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2ce854ed-0701-0010-deb5-ffd61d73fd9f
Jco Connections
Regards, Suresh KB

Connection timeout error in web report(portal)

Hi Experts,
Points to note about the 500 connection timeout error
1. Error persists only in portal. query/ report works fine in RSRT and Bex Analyser.
2.As per previous discussions tried implementing SAP notes to change ICM parameter for max of 10 minutes.
However, it is said by Basis team that they can change parameter only if all the report gives the same error.
Since all the report works fine they are nt ready to change the parameter.
4. Error: Time exceeds 600seconds
5.This issue arised only after upgrading the system to 7.3. post - upgrade. this report was working fine before.
6. Even in the portal, report works fine when we use ABAP web link.
Please share your suggestions.

In the trace file there is a error message for this report "Could not find a command, masscommand or group command with alias <new task>. It is defined in group . <TaskCollectionGroup>. pls any one help me. This is for 7.31 NW portal

Webservice Connection Timeout Error in Sun Java System Application server

I have a java code to connect to Ebay Shopping Webservice that uses the client stub generated through Axis. The code works fine when I run it from the main method of a stand alone Java application. Which means there is no issue with the Proxy settings or any other network setting that could block the webservice from my system. However when I use the same code inside a JSF based Web Application, a connection timeout error comes up. The Web application is deployed on the Sun Java System Application server. The stacktrace of the exception is
java.net.ConnectException: Connection timed out: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527)
     at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
     at java.net.Socket.connect(Socket.java:520)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:125)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.ebay.api.soap.ShoppingBindingStub.findProducts(ShoppingBindingStub.java:1217)
     at com.shopping.ebay.EbayServiceUtility.performEBaySearch(EbayServiceUtility.java:66)
     at searchProduct.SearchProductBean.search(SearchProductBean.java:98)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:151)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96)
     at javax.faces.component.UICommand.broadcast(UICommand.java:383)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:450)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:759)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
The JDK version on my machine is 1.5.0_14. Can somebody point me as where I should be looking for errors?

You need to delete all the files under the 'generated' directory to force the server to recompile them after the JDK upgrade. Also check in domain.xml and make sure the JVM parameter is pointing to the JDK that you have installed. It is also worthwhile to check asenv.conf to see which JDK that file is pointing to as well.

500 CONNECTION TIMEOUT ERROR

Hi Experts,
When try to test the url for c project I am getting this error.
Is there any way to change the connection time out.
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Tue Apr 29 14:19:08 2008
Module: icxxthr.c
Line: 2698
Server: m576_IDS_00
Error Tag: {-}
Detail: Connection to partner timed out after 60s
please guide me step step procedure I am functional consultant .
I found that it will be change in T CODE :RZ10
BUT IN THAT what parameter I NEED TO CHANGE PLEASE GUIDE ME
full points will be reward for help help full answer.
thanks
sunil jawalkar

Hi Sunil,
If you are using this particular cProjects URL for the first time, you should generate the screens using SGEN transaction. Select Web Dynpro for ABAP and give the cProjects application.
Having done SGEN, the page wouldnt take long to open up.
To increase the connection timeout, pl contact your basis guy.
Regards,
Reema.
Edited by: Reema Shahbazkar on Apr 29, 2008 6:05 PM

JCO connection without the use of HCM util.?

Hi Guru's!
I have developed a dynpage application where i call a function module inside sap, using the Sap Enterprise Connector.
I use this code to get the JCO connection, where "SystemIdentifier" is the System Alias parameter maintained in the portalapp.xml file eg. "SAP_R3_HumanResources"
the code looks like this:
public SapConnection(Object originator, IPortalComponentRequest request, String systemIdentifier) {
          try {
               IJCOClientPoolEntry poolEntry = Util.getJCoPoolEntry(originator, request, systemIdentifier);
               client = poolEntry.getJCOClient();
          } catch (BaseException e) {
               System.out.println("Fejl BaseException: " + e.getMessage());
          } catch (Exception e) {
               System.out.println("Fejl Exception: " + e.getMessage());
Normally this code works well, but today we where trying to use the iView in a portal which doesnt have ESS or MSS installed.
And therefore the HCM_util.jar is not deployed on the server.
So my question is: Is it possible to connect to the sap system using a System Alias, but wihtout the HCM_Util.jar ?
Help is very much apreciated!
Br
Ronni

Hi again.
Seems that i found another way to do this:
IJCOClientService clientService = (IJCOClientService)request.getService(IJCOClientService.KEY);
            IJCOClientPoolEntry poolEntry;
            try
                 poolEntry = clientService.getJCOClientPoolEntry(systemIdentifier, request);
Sorry for the commotion
Br
Ronni

How to change timeout parameter value in Oracle 10g R2

Anyone knows how to change timeout parameter value in Oracle 10g Database R2?

Waheed Azhar wrote:
actually i am getting ORA-01013 exception which directly relates to the timeout value but i think it's hidden parameter...What makes you think it's a hidden parameter?
A search of MetaLink for that error turns up a number of hits, most of which a very situational specific. Exactly what are you doing when you get this error? Are you connecting over an ODBC connection? Are you getting it on a connection request? At db shutdown? During a long-running query?

JCo connection timeout parameter

Similar Messages

Maybe you are looking for