Exception occured while maintaining JCo in EP

[former_member472138]

Exception occured while maintaining JCo - Please someone can provide sol.,

Its an urgent...Thanks in advance

500 Internal Server Error

Web Dynpro Container/SAP J2EE Engine/6.40

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.tools.explorer.JCOConnectionsDetails.onActionPingConnection(JCOConnectionsDetails.java:432)

at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdInvokeEventHandler(InternalJCOConnectionsDetails.java:355)

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)

... 23 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)

Version

DOM version

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, Build ID: 6.4018.00.0000.20061128094033.0000 (release=NW04_18_REL, buildtime=2006-11-28:09:27:30[UTC], changelist=21883, host=PWDFM087)

J2EE Engine 6.40 patchlevel 105424.313

Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2 1.4.2.11-060824-14:41-PA_RISC2.0W PA2.0W (aCC_AP), vendor: Hewlett-Packard Company

Operating system HP-UX, version: B.11.11, architecture: PA_RISC2.0W

Other

Session Locale en_GB

Time of Failure Fri Dec 14 08:33:33 GMT 2007 (Java Time: 1197621213336)

Web Dynpro Code Generation Infos

sap.com/tc_wdtools

No information available

sap.com/tc_wddispwda

No information available

sap.com/tc_wdcorecomp

No information available

Detailed Error Information

Detailed Exception Chain

java.lang.NullPointerException

at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.onActionPingConnection(JCOConnectionsDetails.java:432)

at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdInvokeEventHandler(InternalJCOConnectionsDetails.java:355)

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(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

[former_member265210]

hi,

is portal connected to SLD? is SDL connection test working fine?

check tc/wd/ application are up in Visual admin> deploy > application ...

if it did not help then redeploy the SAP_JTECHS SC.

Regards

Shridhar Gowda

[former_member472138]

Yes we had seen in VADM and well working. This problem is happening only for some users not for all. Others can do with out having any problem. Also i can say this is not user specific. Then what would be the wrong...