on 11-24-2012 11:33 PM
Hi,
After splitting the java stiack using the same database as of Abap when I am trying to open the nwa link it's not working, even the user management link is not working, In the dev_server0 file it;s showing error as
[Thr 157008] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\DB8\JC04\exe\jvmx.jar
[Thr 170796] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3286]
[Thr 170796] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 30/sock 12500
(SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp 3286]
Do I need to add anything in the service file, Please suggest.
Thanks,
Jitendra
Hi,
Could you please check that java system is up n running?
Also attach default trc to thread.
Regards, Premsukh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
My java system is up and running after split but when i click on the nwa link it open another session with url as:
but nothing is displayed on the page, Please find a section my defaulttrace file
#
#1.5 #02505684491D005E00000025000425440004CF4E905A1483#1353836243209#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#0##n/a##b71be17036e311e2a0d602505684491d#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Found no client for parameter: null, useragent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; WOW64; Trident/5.0)
Exception id: [02505684491D005E00000023000425440004CF4E905A134F]#
#1.5 #02505684491D005E00000026000425440004CF4E905A1687#1353836243210#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#J2EE_GUEST#0##n/a##b71be17036e311e2a0d602505684491d#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain###application [webdynpro/dispatcher] Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Found no client for parameter: null, useragent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; WOW64; Trident/5.0))]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)
at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:984)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:973)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:878)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:869)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:412)
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(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)
#
#1.5 #02505684491D005E00000028000425440004CF4E905A1793#1353836243210#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#0##n/a##b71be17036e311e2a0d602505684491d#SAPEngine_Application_Thread[impl:3]_10##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Found no client for parameter: null, useragent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; WOW64; Trident/5.0))].
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
Exception id: [02505684491D005E00000026000425440004CF4E905A1687]#
Thanks,
Jitendra
Dear Jitendra
This means that you are not using a supported browser version. Can you try using IE8 or IE7 and reproduce the issue?
Otherwise, please refer to SAP note:
#1347768-Web Dynpro and Microsoft Internet Explorer Version 8.0
#991449 - Web Dynpro and Microsoft Internet Explorer Version 7.0
Please also make sure that you are on atleast minimum NW version from when support to IE9 starts.
I would strongly urge you to upgrade to our newer SPs of the NW you are using.
I hope this will help you.
Tapan
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.