WebIOException

Hi,
I am trying to migrate the MedRec Application available with BEAWeblogin to SAP WAS. While deploying the .ear file i am getting com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException
The details are as follows:
Caused by: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Error while parsing the taglib tag in web.xml or the .tld file of the taglib library.
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:138)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse0(JspDirective.java:141)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspDirective.parse(JspDirective.java:102)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ElementCollection.parse(ElementCollection.java:89)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.ParserImpl.parse(ParserImpl.java:525)
at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:339)
at
com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
Caused by: java.lang.ClassCastException
at com.sap.engine.services.servlets_jsp.descriptor.taglib.TagLibDescriptorDocument.getTagInfo(TagLibDescriptorDocument.java:513)
at com.sap.engine.services.servlets_jsp.descriptor.taglib.TagLibDescriptorDocument.loadDescriptorFromElement(TagLibDescriptorDocument.java:444)
at com.sap.engine.services.servlets_jsp.descriptor.taglib.TagLibDescriptorDocument.loadDescriptorFromDocument(TagLibDescriptorDocument.java:100)
at com.sap.engine.services.servlets_jsp.lib.jspparser.syntax.JspTaglibDirective.verifyAttributes(JspTaglibDirective.java:128)
This is caused in the start.jsp file.
It makes use of:
    struts-html.tld
    struts-bean.tld
Both of these are placed in WEB-INF dir, and have corressponding entries in the web.xml file.
Kindly guide,
Thanks and Regards,
Prasita

Hi Prasita,
it seems that some of this TLDs has tag with tei clas that doesn't implement javax.servlet.jsp.tagextTagExtraInfo class.
You can check these classes , descibed in <tei-class> tags in tld files.
Regards
Bojidar

Similar Messages

  • SAP E-Commerce 5.0 - SAP Internet Sales (R/3) Edition - WebIOException

    When choosing the same item from the catalog twice and proceeding to order we are getting a runtime error. In the logs we can see the error detail below:
    application [] Error in finalizing PageContext.  The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
                at com.sap.engine.services.servlets_jsp.server.jsp.JspWriterImpl.ensureOpen(JspWriterImpl.java:262)
                at com.sap.engine.services.servlets_jsp.server.jsp.JspWriterImpl.flushBuffer(JspWriterImpl.java:130)
                at com.sap.engine.services.servlets_jsp.server.jsp.JspWriterImpl.flush(JspWriterImpl.java:189)
                at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.release(PageContextImpl.java:306)
                at com.sap.engine.services.servlets_jsp.server.jsp.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:83)
                at jsp_frameset_help1212589480125._jspService(jsp_frameset_help1212589480125.java:65535)
                at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
                at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
                at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
                at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
                at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
                at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
                at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
                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:102)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    We have checked OSS and found note 928444 but this is for an older version. We are on Kernel 7.0 with the latest patch level.
    Any ideas on a solution for this?
    Thanks!
    Gráinne

    Yes, you need to follow the path:
    swdc > Download > Installations and Upgrades > Entry by Application Group > SAP Application Components > SAP E-COMMERCE FOR SAP R/3 > SAP INTERNET SALES R/3 4.0 > Installation
    Here you should find two files.
    Direct links to files (hope they work):
    <a href="https://smpdl.sap-ag.de/~swdc/012002523100000044422003E/51019974.ZIP?_ACTION=DL_DIRECT">Part I</a>
    <a href="https://smpdl.sap-ag.de/~swdc/012002523100000045402003E/51019848.ZIP?_ACTION=DL_DIRECT">Part II</a>
    Hope it helps.
    Regards,
    Kaushal

  • Com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:

    Hi Subhra/ Asit,
    The following is the main information form the log file and attched logfile with full info for your reference.
    #1.5#00188B874AFD00320000000A000007B4000447710E97B363#1204450808802#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
    usr
    sap
    SPP
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.portal.layouts.default
    jsp
    fullWidth.jsp [email protected]a6d4d7#
    #1.5#00188B874AFD00320000000B000007B4000447710E97BD23#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]a6d4d7#
    #1.5#00188B874AFD00200000000B000007B4000447710E97C15A#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
    usr
    sap
    SPP
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.portal.layouts.framework
    jsp
    WAandNavPanel.jsp [email protected]16c192#
    #1.5#00188B874AFD00200000000C000007B4000447710E97CCCC#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]16c192#
    #1.5#00188B874AFD002900000049000007B4000447710EA4FBF8#1204450809677#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.
    [EXCEPTION]
    #2#fonterra.com/cmtuwlcmir~dispform/CMIRCreateNotificationDisplay#java.lang.NullPointerException
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
                at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
                at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
                at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
                at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
                at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
                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.bindRoot(ViewManager.java:579)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
                at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
                at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
                at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
                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)
    #1.5#00188B874AFD00290000004A000007B4000447710EA7E5F6#1204450809865#com.tssap.dtr.client.lib.protocol.session.Cookies#sap.com/tcwddispwda#com.tssap.dtr.client.lib.protocol.session.Cookies.setCookie(Cookie)#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Java###rejecting invalid cookie for domain "": #2#.fonterra.com#JSESSIONID#
    #1.5#00188B874AFD00290000004B000007B4000447710EA8000D#1204450809880#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
                at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
                at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
                at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
                at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
                at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
                at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
                at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
                at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
                at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
                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.bindRoot(ViewManager.java:579)
                at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
                at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
                at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
                at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
                at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
                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)
    #1.5#00188B874AFD00290000004D000007B4000447710EA803B8#1204450809880#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: java.lang.NullPointerException: null
    Exception id: [00188B874AFD00290000004B000007B4000447710EA8000D]#
    #1.5#00188B874AFD00290000004E000007B4000447710EA82DD2#1204450809896#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
                at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:168)
                at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:135)
                at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendBodyText(HttpServletResponseFacade.java:957)
                at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:948)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
                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: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)
    #1.5#00188B874AFD002900000050000007B4000447710EA82F56#1204450809896#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
    Exception id: [00188B874AFD00290000004E000007B4000447710EA82DD2]#
    Regards
    Krishna K

    kinldy let me know what was the solution to this problem

  • Error Parsing: WebIOException

    Hi all!!!
    I am having some problems when I deployed my EAR in AS. The application launch the error bellow when I try to get acess in the page that are not linking with the rol.
    com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
      Error parsing [/cargarMensajes.htm] of alias [AMCyC-DEV] of J2EE application [sap.com/AMCyCDEVEAR].
    Please, if somebody knows the solution or cause of this error tell me about it.
    Thanks a lot,

    Hi!!!
    thanks for your answer.
    Well my app I have proved many times in my localhost (resin) and all of links are ok. But when I deploy in SAP WAS the app lauch that error.
    It's very strange because the app is working correctly in a local way.
    What other cause could be happend??
    Thanks a lot..

  • WebIOException on custom B2B vanilla

    Hi gurus,
    in order to create 2 custom B2B projects, we created another custom B2B, named B2B_xyz without sources' modifications, to evaluate the correct creation of track, import into NWDS and finally the deployment.
    Our CRM is a 7.02 and we followed all SAP documents that we found.
    Now we deployed B2B_xyz and we can see it with URL: http://<hostname>:<port>/PB2B5_xyz.
    The Administration Console (http://<hostname>:<port>/PB2B5_xyz/admin) works fine, but when we go on XCM page we have this message error:
    ISA Framework: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [/usr/sap/AJS/JC12/j2ee/cluster/server0/apps/sap.com/B2B_xyz/servlet_jsp/B2B_xyz/root/admin/xcm/MainConfig.jsp].
    We made the same operation also with the original B2B and it works fine, so we think that the custom B2B has some parameters wrong.
    Can someone help us?

    On reading the log I found this error:
    application [B2B_xyz] Runtime error in compiling of the JSP file </usr/sap/AJS/JC12/j2ee/cluster/server0/apps/sap.com/B2B_xyz/servlet_jsp/B2B_xyz/root/admin/xcm/MainConfig.jsp> !
    The error is: com.sap.engine.services.servlets_jsp.lib.jspparser.exceptions.JspParseException: Cannot parse custom tag with short name [encodeHiddenFormField].
    Caused by: java.lang.ClassNotFoundException: com.sap.isa.dependencies.xsrf.tags.EncodeHiddenFormFieldTag
    Some ideas?

  • Servlets_jsp.server.exceptions.WebIOException :: What is the problem ?

    Hi all
      I have modified an SAP CRM User Admin application.
      And deployed the Application and tried accessing the application .
    I get the follwoing Error message:
    <b>Application error occurred during the request procession.</b>
    Details:   <b>com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:</b>
      Error parsing [/start.jsp] of alias [myFridayTest] of J2EE application [sap.com/myFridayEar].
    Exception id: [0015605365DE00620000003C000013CC000413045A1FAF96]
    Any Idea !!!
    Thanks
    KK
    Message was edited by: KK

    Errors Log are in order :
    <b>An error occured while copying configurations for application sap.com/myFridayEar</b>. Reason: com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path "webservices/services/sap.com/myFridayEar" does not exist.
    java.util.zip.ZipException: invalid CEN header (bad signature)
         at java.util.zip.ZipFile.open(Native Method)
         at java.util.zip.ZipFile.<init>(ZipFile.java:111)
         at java.util.jar.JarFile.<init>(JarFile.java:127)
         at java.util.jar.JarFile.<init>(JarFile.java:65)
         at com.sap.engine.boot.JarFilter.<init>(JarFilter.java:28)
         at com.sap.engine.frame.core.load.res.JarResource.openJar(JarResource.java:404)
         at com.sap.engine.frame.core.load.res.JarResource.getURL(JarResource.java:148)
         at com.sap.engine.frame.core.load.res.MultipleResource.getURLs(MultipleResource.java:96)
         at com.sap.engine.frame.core.load.ResourceLoader.findLocalResources(ResourceLoader.java:279)
         at com.sap.engine.frame.core.load.ResourceLoader.findResources(ResourceLoader.java:218)
         at java.lang.ClassLoader.getResources(ClassLoader.java:851)
         at com.sun.naming.internal.VersionHelper12$5.run(VersionHelper12.java:145)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.naming.internal.VersionHelper12.getResources(VersionHelper12.java:142)
         at com.sun.naming.internal.ResourceManager.getApplicationResources(ResourceManager.java:468)
         at com.sun.naming.internal.ResourceManager.getInitialEnvironment(ResourceManager.java:159)
         at javax.naming.InitialContext.init(InitialContext.java:215)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.createNamingContexts(WebApplicationConfig.java:633)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:106)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:600)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:540)
         at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:50)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:398)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:239)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:187)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeNestedParallelTransaction(ApplicationTransaction.java:578)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.finalActions(UpdateTransaction.java:615)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:656)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
         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)
    Error parsing tag library descriptors from JAR files. The error is: java.util.zip.ZipException: invalid CEN header (bad signature)
         at java.util.zip.ZipFile.open(Native Method)
         at java.util.zip.ZipFile.<init>(ZipFile.java:111)
         at java.util.jar.JarFile.<init>(JarFile.java:127)
         at java.util.jar.JarFile.<init>(JarFile.java:92)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.processTldJars(ApplicationThreadInitializer.java:142)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:105)
         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)
    Processing HTTP request to servlet [jsp] finished with error.
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [E:/usr/sap/JD1/JC75/j2ee/cluster/server0/apps/sap.com/myFridayEar/servlet_jsp/myFridayTest/root/start.jsp].
    Exception id: [0015605365DE005F000000A0000013CC0004130577B67EE8]
    any Help !!!
    Thanks

  • Error in processing [/useradmin/index.jsp]

    In our PI system 7.1, when we try the below url
    http://hostname.xx.xxx.com:50000/useradmin/index.jsp
    we are getting the below error
    "500   Internal Server Error
      SAP NetWeaver Application Server 7.11 / AS Java 7.11 
      Error: "Error in processing [/useradmin/index.jsp] in application [sap.com/com.sap.security.core.admin]."
      Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
    Details: "The WebApplicationException log ID is [AA4FB520760500F20000000000AC0064]."
    the Default trace file has the below error message:
    #2.#2011 10 10 16:23:19:399#0-400#Error#com.sap.engine.services.servlets_jsp.ISE500#
    com.sap.ASJ.web.000500#BC-JAS-SEC-UME#sap.com/com.sap.security.core.admin#AA4FB520760500EF0000000300AC0064#4047350000000004#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.ISE500#J2EE_GUEST#0##B15C71CBF37D11E0C7CC0000003DC1F6#b15c71cbf37d11e0c7cc0000003dc1f6#b15c71cbf37d11e0c7cc0000003dc1f6#0#Thread[HTTP Worker [@501859437],5,Dedicated_Application_Thread]#Plain##
    500 Internal Server Error is returned for HTTP request [http://hostname.xx.xxxx.com:50000/useradmin/index.jsp]:
      component [jsp],
      web module [useradmin],
      application [sap.com/com.sap.security.core.admin],
      DC name [sap.com/com.sap.security.core.admin],
      CSN component[BC-JAS-SEC-UME],
      problem categorization [com.sap.ASJ.web.000137],
      internal categorization [-1555343295].
    [EXCEPTION]
    com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error occurred while parsing the jsp page [/usr/sap/P1X/DVEBMGS00/j2ee/cluster/apps/sap.com/com.sap.security.core.admin/servlet_jsp/useradmin/root/index.jsp].
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:200)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
            at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
            at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
            at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
            at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
            at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
            at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
            at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
            at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    Caused by: com.sap.engine.services.servlets_jsp.jspparser_api.exception.JspParseException: [/usr/sap/P1X/DVEBMGS00/j2ee/cluster/apps/sap.com/com.sap.security.core.admin/servlet_jsp/useradmin/root/index.jsp]
            at com.sap.engine.services.servlets_jsp.jspparser_api.JspParser.generateJspClass(JspParser.java:160)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:192)
            ... 37 more
    Has anyone faced this issue?
    Regards
    Senthil

    Hi,
    Please check with your Basis Team if User Management services and applications are running. It is under Operations Managemenr -> Systems -> Start & Stop.
    Regards,
    Jenny

  • Unable to create RFC iviews - connection test of the system failed

    hello,
    I always try to configure my system to run an RFC iView...
    The connection of myt system is failed for 1 of the 4 tests.
    i don't know why.
    I have filled this fields :
    - application host
    - ITS host name
    - ITS path
    - ITS protocol
    - Logical system name (not sure it's correct)
    - Sap client
    - Sap system ID
    - SAP system number
    - Server port (not sure it's correct)
    - System type
    - Web as host name
    - Web as path
    - Web as protocol
    and i have this error :
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check if the system can be retrieved
    3. Check if a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Check HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
    5. HTTP/S connection successful
    ITS Connection
      Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check if the system can be retrieved
    3. Check if the system object has a valid system alias
    4. Check if a SAP system is defined in the system object
    5. Validate the following parameters: ITS protocol; ITS host name
    6. Check the validity of any user mapping in the system object
    7. Check HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. Retrieval of the default alias was successful
    4. The system object represents an SAP system
    5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
    6. HTTP/S connection successful
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
    Test Connection through the DQE
      Test Details:
    The test consists of the following steps:
    1. Checks the existence of a backend admin user ID/password in the system properties.
    2. Checks the existence of a default alias for the system.
    3. Checks the DQE connection.
      Results
    1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.
    2. Default alias of the system exists.
    3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.
    can you help me to end this configuration?
    thanks a lot.
    (reward points for helful answers...)
    Adrien

    doesn't work, doesn't work... :o(
    I found this in "analysis" -> "Debug"
      error 3 mai 2007 16:49:32:168 Failed to get connection for system final
    /System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638
      error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.
    /System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638
    i found too a -BIG- file in the directories, "last block" of the file
    #1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
    Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#
    #1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. 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:952)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
         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: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)
    #1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
    Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#
    and with another test connector
    #1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
    Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#
    #1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#
    #1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#
    #1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tcwddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#
    #1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#
    #1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#
    #1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#
    #1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#
    i happy to carry my life's number one goal with another guy
    (thanks, again and again)
    Adrien
    Message was edited by:
            Adrien Loire

  • JAVA Application Error in BI 7.0

    Hi All,
    I am encountering a peculiar problem in BI Quality System. It is an ABAP + JAVA stack with ABAP being the datasource.The problem I am facing is as below:
    1.> I create a userid for eg testdm in my ABAP engine using su01.
    2.> Now when I login into the JAVA URL using the same login credentials it gives me the below error
    Application error occurred during the request procession.
      Details:   com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
      Error compiling [/firstDM.jsp] of alias [DMSSO] of J2EE application [sap.com/DMApplication].
    Exception id: [00145E47D2A4006900000014001C608200045FCE704E90E5]
    3.> I checked the default trace file at the location /usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/log
    4.> Below is the output of tail -50 of the default trace file
    The system is out of resources.
    Consult the following stack trace for details.
    java.lang.OutOfMemoryError
    Exception id: [00145E47D2A4006E00000777001C608200045FCE1E9B5C61]#
    #1.#00145E47D2A4006900000014001C608200045FCE704E90E5#1231240158941#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/DMApplication#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#TESTDM4#319##a92sv093bw001_Q3W_101805350#Guest#750e34a0dbe211dd9b3200145e47d2a4#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###application [DMSSO] Processing HTTP request to servlet [jsp] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [/usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/apps/sap.com/DMApplication/servlet_jsp/DMSSO/work/jsp_firstDM1231240157028.java:22: package edu.yale.its.tp.cas.client does not exist
    import edu.yale.its.tp.cas.client.*;
    ^
    /usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/apps/sap.com/DMApplication/servlet_jsp/DMSSO/work/jsp_firstDM1231240157028.java:44: package edu.yale.its.tp.cas.client.filter does not exist
                              String casUser = (String) session.getAttribute(edu.yale.its.tp.cas.client.filter.CASFilter.CAS_FILTER_USER);
                                                                                    ^
    2 errors
            at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compileExternal(JavaCompiler.java(Compiled Code))
            at com.sap.engine.services.servlets_jsp.server.jsp.JavaCompiler.compile(JavaCompiler.java:238)
            at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.generateJavaFile(JSPParser.java:369)
            at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:107)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:242)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:434)
            at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:173)
            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.doPrivileged1(Native Method)
            at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    #1.#00145E47D2A4006900000016001C608200045FCE704EDE75#1231240158961#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/DMApplication#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#TESTDM4#319##a92sv093bw001_Q3W_101805350#Guest#750e34a0dbe211dd9b3200145e47d2a4#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server/WebRequests#Plain###application [DMSSO] Processing HTTP request to servlet [jsp] finished with error.
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [/usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/apps/sap.com/DMApplication/servlet_jsp/DMSSO/work/jsp_firstDM1231240157028.java:22: package edu.yale.its.tp.cas.client does not exist
    import edu.yale.its.tp.cas.client.*;
    ^
    /usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/apps/sap.com/DMApplication/servlet_jsp/DMSSO/work/jsp_firstDM1231240157028.java:44: package edu.yale.its.tp.cas.client.filter does not exist
                              String casUser = (String) session.getAttribute(edu.yale.its.tp.cas.client.filter.CASFilter.CAS_FILTER_USER);
                                                                                    ^
    2 errors
    Exception id: [00145E47D2A4006900000014001C608200045FCE704E90E5]#
    Kindly help me in resolving this issue.

    Hi Amit,
    It is an application error as I had earlier stated. When I checked the default trace file it has the below line:
    com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [/usr/sap/Q3W/DVEBMGS10/j2ee/cluster/server0/apps/sap.com/DMApplication/servlet_jsp/DMSSO/work/jsp_firstDM1231245715241.java:22: package edu.yale.its.tp.cas.client does not exist
    I have talked to the customer since it is an application error and this is customised URL the developers need to work on this.
    I am closing this thread. Thanks for your help anyway.

  • Error on using MyFaces component

    Hy all,
    I don't know if someone as already tested to work with JSF and MyFaces on its WebAS.
    In fact I've started by developping a simple JSF page
    and next I would like to add some sweet component  by using MyFaces and Tomawakh.
    For the JSF page, no problem, it rulez, but, when I <b>just</b> add "myfaces-api-1.1.3.jar" and
    "my-faces-impl-1.1.3.jar" and deploy it to my server.
    No error during deploying but when I'm trying to open a
    JSF page I get this long error :
    #1.5#000D606F6C2B0026000000270000137800041B1DE87681AB#1155715175094#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/NewsDisplayJSFApp#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#Guest#2####2839db702cfd11db94ff000d606f6c2b#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Server#Plain###Runtime error in compiling of the JSP file <D:/usr/sap/DEP/JC00/j2ee/cluster/server0/apps/sap.com/NewsDisplayJSFApp/servlet_jsp/newsDisplayJSF/root/NewsError.jsp> !
    The error is: java.lang.NullPointerException: null
    Exception id: [000D606F6C2B0026000000260000137800041B1DE8767EC8]#
    #1.5#000D606F6C2B0026000000280000137800041B1DE8768B06#1155715175094#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/NewsDisplayJSFApp#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####2839db702cfd11db94ff000d606f6c2b#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Processing HTTP request to servlet [Faces Servlet] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [D:/usr/sap/DEP/JC00/j2ee/cluster/server0/apps/sap.com/NewsDisplayJSFApp/servlet_jsp/newsDisplayJSF/root/NewsError.jsp].
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:117)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:429)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
         at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
         at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
         at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100)
         at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:64)
         at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:224)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
         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)
    Caused by: java.lang.NullPointerException
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.validate(JSPParser.java:235)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:348)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
         ... 30 more
    I mean, in each JSP page I'm trying to use those standard taglib :
    <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
    <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
    It crashes.
    I've try to add in my web-inf/lib some jar like : servlet_api.jar, servlet.jar, and so on but nothing seam to be working.
    I've also try to define the extensionFilter of myfaces in my web.xml but it doesn't help me
    Anyone has an idea ? I'll give reward
    Thx.

    Hy,
    try do do this:
    1) extract the JSF Tag-Lib's from the Jar-File in a folder under the WebContent folder (in my example named as "tld")
    2) Add some TagLib- Entries in the WEB.XML like this:
    <taglib>
       <taglib-uri>http://java.sun.com/jsf/core</taglib-uri>
       <taglib-location>tld/jsf_core.tld</taglib-location>
    </taglib>
      <taglib>
       <taglib-uri>http://java.sun.com/jsf/html</taglib-uri>
       <taglib-location>tld/html_basic.tld</taglib-location>
    </taglib>
    <taglib-uri> ist the URL that you use in the JSF Pages and <taglib-location> is the location of the expanded Tag-Libary.
    The example above ist based on the Sun-Faces components but it works in the same way for Myfaces oder for the Oracle ADF faces.
    Instead of the both Jar's myFaces-api and mafaces-imp I have use the myfaces-all.jar.
    I hope this informatin will help you.

  • Error on deploying JSP web module

    Hi,
    I've created a JSP web module that consumes a web service. I'm following this tutorial
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0cf9e42-ccb0-2c10-d0a4-f5aa8a79e19a?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0cf9e42-ccb0-2c10-d0a4-f5aa8a79e19a?quicklink=index&overridelayout=true]
    But when I deploy my ear project, I had this error
    Application error occurred during the request procession.
    Details:   com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
    Error compiling [/sample.jsp] of alias [LocalDevelopmentdc_webmodulesap.com] of J2EE application [sap.com/dc_webmoduleear].
    Exception id: [001CC43ABAC00086000056FB00006CEA0004A5A7E1A64FD3]
    Here's the java code in the JSP:
    InitialContext ctx = new InitialContext();
    WS_Preview obj = (WS_Preview).ctx.lookup("java:comp/env/newproxy");
    WS_PreviewViDocument port = (WS_PreviewViDocument)obj.getLogicalPort("Config1Port_Document",WS_PreviewViDocument.class);
    GetElementXHTMLValueResponse result = new GetElementXHTMLValueResponse();
    result = port.GetElementXHTMLValue("A","A","A");
    out.print(result);
    Does anyone know how to solve this error? Thanks

    Because you do not have an infrastructure database, you will not be able to deploy your web service from OEM as one of its steps is to register the service in the UDDI registy - the Web service deployment and UDDI registration are tied tightly together in OEM right now.
    All is not lost, however. You have two routes to deploy the Web Service on Oracle9iAS:
    1. Use DCM, which is the command line interface to deploy applications/webservices/wars/ears on Oracle9iAS. It does not have the dependency on UDDI.
    To deploy a Web service using DCM, say your Web service ear file were named test.ear your deployment command would look something like:
    c:\oracle\ora903\dcm\bin\dcmctl deployApplication -file test.ear
    See the doc for much more detail to let you tailor DCM to do all the stuff that is available through EM or specific to your application:
    http://download-west.oracle.com/docs/cd/A97329_03/core.902/a92171/dcm.htm#643834
    2. In JDeveloper 9.0.3, there is a DCM Servlet that lets you do remote deployment to Oracle9iAS:
    http://otn.oracle.com/products/jdev/htdocs/readme_9031.html#viadcm
    I suspect your deployment problem from Oracle9i JDeveloper may be (this may be an incorrect assumption) due to trying to use a connection that is setup as if Oracle9iAS is a standalone OC4J.
    Mike.

  • UME not working for WAS 700

    Hi,
           we are working on SAP WAS 700. We have just moved from WAS 640 and NWDS 2.0.09 to WAS 700 and NWDS 640. I am having a problem that when I try to open the UME from the WAS home page, I get the following error :
    Application error occurred during the request procession.
      Details:   com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
      Error compiling [/index.jsp] of alias [useradmin] of J2EE application [sap.com/com.sap.security.core.admin].
    The log gives the following message for this :
    #1.5#00174212003F004C000002D000000ADC00043341A6CA4DEF#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.engine.docs.examples finished successfully on server 307377350#
    #1.5#00174212003F004C000002D100000ADC00043341A6CA4E37#1182256971041#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.engine.docs.examples finished on current cluster node for 52474 ms.#
    #1.5#00174212003F004C000002D200000ADC00043341A6D48193#1182256971713#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.engine.class.download] finished successfully on Web Container.#
    #1.5#00174212003F004C000002D300000ADC00043341A6D483EC#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.engine.class.download finished successfully on server 307377350#
    #1.5#00174212003F004C000002D400000ADC00043341A6D48446#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.engine.class.download finished on current cluster node for 672 ms.#
    #1.5#00174212003F004C000002D500000ADC00043341A6D4A26C#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafummetadata~content finished successfully on server 307377350#
    #1.5#00174212003F004C000002D600000ADC00043341A6D4A2D8#1182256971713#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafummetadata~content finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002D700000ADC00043341A6DB2A79#1182256972135#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.lcr.saprfc finished successfully on server 307377350#
    #1.5#00174212003F004C000002D800000ADC00043341A6DB2AE9#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.lcr.saprfc finished on current cluster node for 438 ms.#
    #1.5#00174212003F004C000002D900000ADC00043341A6DB482F#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugp~content finished successfully on server 307377350#
    #1.5#00174212003F004C000002DA00000ADC00043341A6DB489B#1182256972151#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugp~content finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002E200000ADC00043341A6E854CD#1182256973010#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafruntimemonitoring~ear] finished successfully on Web Container.#
    #1.5#00174212003F004C000002E300000ADC00043341A6E85755#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/cafruntimemonitoringear : Application sap.com/cafruntimemonitoringear has a weak reference to resource jmsfactory/TopicConnectionFactory with type javax.jms.TopicConnectionFactory but the resource is not available and the application may not work correctly!#
    #1.5#00174212003F004C000002E400000ADC00043341A6E857BE#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafruntimemonitoring~ear finished successfully on server 307377350#
    #1.5#00174212003F004C000002E500000ADC00043341A6E85806#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafruntimemonitoring~ear finished on current cluster node for 859 ms.#
    #1.5#00174212003F004C000002E600000ADC00043341A6E87157#1182256973010#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
    usr
    sap
    F48
    JC30
    j2ee
    cluster
    server0
    apps
    sap.com/com.sap.ip.bi.sdk.dac.olap
    bi_sdk_olap.jar will be downloaded.#
    #1.5#00174212003F004C000002E700000ADC00043341A7042104#1182256974823#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###New internal library C:
    usr
    sap
    F48
    JC30
    j2ee
    cluster
    server0
    apps
    sap.com/com.sap.ip.bi.sdk.dac.olap
    bi_sdk_olap_xmi.jar will be downloaded.#
    #1.5#00174212003F004C000002E800000ADC00043341A732696B#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.dac.olap finished successfully on server 307377350#
    #1.5#00174212003F004C000002E900000ADC00043341A73269DB#1182256977854#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.dac.olap finished on current cluster node for 4844 ms.#
    #1.5#00174212003F004C000002EA00000ADC00043341A7383749#1182256978245#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.ip.bi.sdk.monitoring] finished successfully on Web Container.#
    #1.5#00174212003F004C000002EB00000ADC00043341A73839D0#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.monitoring finished successfully on server 307377350#
    #1.5#00174212003F004C000002EC00000ADC00043341A7383A33#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.monitoring finished on current cluster node for 375 ms.#
    #1.5#00174212003F004C000002ED00000ADC00043341A7385752#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugpmodelpwflocaluwlconn finished successfully on server 307377350#
    #1.5#00174212003F004C000002EE00000ADC00043341A73857C1#1182256978245#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugpmodelpwflocaluwlconn finished on current cluster node for 0 ms.#
    #1.5#00174212003F004C000002F600000ADC00043341A796016E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/plain, appName sap.com/tclmwebadminsldstartapp#
    #1.5#00174212003F004C000002F700000ADC00043341A796024E#1182256984386#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /SLDStart/secure, appName sap.com/tclmwebadminsldstartapp#
    #1.5#00174212003F004C000002F800000ADC00043341A79602A2#1182256984386#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsldstartapp] finished successfully on Web Container.#
    #1.5#00174212003F004C000002F900000ADC00043341A79605A7#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/tclmwebadminsldstartapp : JAR File: sap.comtclmwebadminsldstart~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
    #1.5#00174212003F004C000002FA00000ADC00043341A7960610#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminsldstartapp finished successfully on server 307377350#
    #1.5#00174212003F004C000002FB00000ADC00043341A7960657#1182256984386#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminsldstartapp finished on current cluster node for 6141 ms.#
    #1.5#00174212003F004C000002FC00000ADC00043341A83A10A5#1182256995138#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.bc.uwl.moni] finished successfully on Web Container.#
    #1.5#00174212003F004C000002FD00000ADC00043341A83A1407#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.moni finished successfully on server 307377350#
    #1.5#00174212003F004C000002FE00000ADC00043341A83A1524#1182256995138#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.moni finished on current cluster node for 10752 ms.#
    #1.5#00174212003F004C000002FF00000ADC00043341A84C226F#1182256996325#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcwdpdfsvrchal] finished successfully on Web Container.#
    #1.5#00174212003F004C0000030000000ADC00043341A84C2558#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcwdpdfsvrchal finished successfully on server 307377350#
    #1.5#00174212003F004C0000030100000ADC00043341A84C25DE#1182256996325#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcwdpdfsvrchal finished on current cluster node for 1187 ms.#
    #1.5#00174212003F004C0000030900000ADC00043341A9823866#1182257016640#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tc~uddi' application started successfully.#
    #1.5#00174212003F004C0000030A00000ADC00043341A98238DF#1182257016640#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~uddi] finished successfully on Web Container.#
    #1.5#00174212003F004C0000030B00000ADC00043341A9823B30#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tc~uddi finished successfully on server 307377350#
    #1.5#00174212003F004C0000030C00000ADC00043341A9823B84#1182257016640#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tc~uddi finished on current cluster node for 20315 ms.#
    #1.5#00174212003F004C0000031400000ADC00043341A99803D0#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcsupportplatformwd finished successfully on server 307377350#
    #1.5#00174212003F004C0000031500000ADC00043341A998043E#1182257018078#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcsupportplatformwd finished on current cluster node for 1438 ms.#
    #1.5#00174212003F004C0000031600000ADC00043341A9C56179#1182257021047#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/cafeugpmodeliforms~eap] finished successfully on Web Container.#
    #1.5#00174212003F004C0000031700000ADC00043341A9C563D0#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/cafeugpmodeliformseap : JAR File: sap.comcafeugpmodeliforms~ejb.jar XML file: ejb-j2ee-engine.xml Element: description is empty. It is not recommended to use empty value elements. Please remove the element or define its value!#
    #1.5#00174212003F004C0000031800000ADC00043341A9C56434#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/cafeugpmodeliforms~eap finished successfully on server 307377350#
    #1.5#00174212003F004C0000031900000ADC00043341A9C5647C#1182257021047#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/cafeugpmodeliforms~eap finished on current cluster node for 2969 ms.#
    #1.5#00174212003F004C0000031A00000ADC00043341A9F0EE76#1182257023891#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminsysconfigapp] finished successfully on Web Container.#
    #1.5#00174212003F004C0000031B00000ADC00043341A9F0F0C9#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminsysconfigapp finished successfully on server 307377350#
    #1.5#00174212003F004C0000031C00000ADC00043341A9F0F120#1182257023891#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminsysconfigapp finished on current cluster node for 2844 ms.#
    #1.5#00174212003F004C0000032400000ADC00043341AA3CEBEA#1182257028876#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tclmwebadminperformanceprovider_ear] finished successfully on Web Container.#
    #1.5#00174212003F004C0000032500000ADC00043341AA3CEE34#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminperformanceprovider_ear finished successfully on server 307377350#
    #1.5#00174212003F004C0000032600000ADC00043341AA3CEE8D#1182257028876#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminperformanceprovider_ear finished on current cluster node for 4970 ms.#
    #1.5#00174212003F004C0000032E00000ADC00043341AAB4C8A8#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerUtilities/Config1, appName sap.com/tcbizcws~ear#
    #1.5#00174212003F004C0000032F00000ADC00043341AAB4CA9D#1182257036736#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /BizcCommLayerAuthoring/Config1, appName sap.com/tcbizcws~ear#
    #1.5#00174212003F004C0000033000000ADC00043341AAB4CAF2#1182257036736#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcbizcws~ear] finished successfully on Web Container.#
    #1.5#00174212003F004C0000033100000ADC00043341AAB4CD69#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcbizcws~ear finished successfully on server 307377350#
    #1.5#00174212003F004C0000033200000ADC00043341AAB4CDBF#1182257036736#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcbizcws~ear finished on current cluster node for 7860 ms.#
    #1.5#00174212003F004C0000033300000ADC00043341AAB582F5#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/caf~km.ep.kmtaskservice finished successfully on server 307377350#
    #1.5#00174212003F004C0000033400000ADC00043341AAB58363#1182257036783#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/caf~km.ep.kmtaskservice finished on current cluster node for 47 ms.#
    #1.5#00174212003F004C0000033500000ADC00043341AB3A1074#1182257045471#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader com.sap/irj on the system, but will register reference for furture usage.#2#sap.com/sap.comtckmccoll.room.wsdepl#com.sap/irj#
    #1.5#00174212003F004C0000033600000ADC00043341AB4D215A#1182257046721#/System/Server##com.sap.engine.services.webservices.server.deploy.WSDeployer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.webservices.server.deploy.WSDeployer#Plain###FastEJB is set for endpointid: /RoomABAPWS/Config1, appName sap.com/sap.comtckmccoll.room.wsdepl#
    #1.5#00174212003F004C0000033700000ADC00043341AB4D21D7#1182257046721#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/sap.comtckmccoll.room.wsdepl] finished successfully on Web Container.#
    #1.5#00174212003F004C0000033800000ADC00043341AB4D24E1#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has hard reference to application sap.com/com.sap.km.application and is starting it!#
    #1.5#00174212003F004C0000033900000ADC00043341AB4D2542#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application sap.com/com.sap.netweaver.coll.appl.room.rfcadapter and is starting it!#
    #1.5#00174212003F004C0000033A00000ADC00043341AB4D2599#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/sap.comtckmccoll.room.wsdepl : Application sap.com/sap.comtckmccoll.room.wsdepl has weak reference to application com.sap/irj and is starting it!#
    #1.5#00174212003F004C0000033B00000ADC00043341AB4D25E8#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/sap.comtckmccoll.room.wsdepl finished successfully on server 307377350#
    #1.5#00174212003F004C0000033C00000ADC00043341AB4D262F#1182257046721#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/sap.comtckmccoll.room.wsdepl finished on current cluster node for 9938 ms.#
    #1.5#00174212003F004C0000033D00000ADC00043341AB4F884D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:kernel.sda on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:kernel.sda#
    #1.5#00174212003F004C0000033E00000ADC00043341AB4F89A8#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader library:com.sap.engine.client.lib on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#library:com.sap.engine.client.lib#
    #1.5#00174212003F004C0000033F00000ADC00043341AB4F8A6D#1182257046878#/System/Server##com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.runtime.application.jcoclient on the system, but will register reference for furture usage.#2#sap.com/com.sapportals.supportplatform#sap.com/com.sap.portal.runtime.application.jcoclient#
    #1.5#00174212003F004C0000034700000ADC00043341AB96ACB5#1182257051534#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sapportals.supportplatform' application started successfully.#
    #1.5#00174212003F004C0000034800000ADC00043341AB96AD31#1182257051534#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sapportals.supportplatform] finished successfully on Web Container.#
    #1.5#00174212003F004C0000034900000ADC00043341AB96AFE4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library kernel.sda is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
    #1.5#00174212003F004C0000034A00000ADC00043341AB96B101#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Library com.sap.engine.client.lib is not deployed or loaded, but resolving of application sap.com/com.sapportals.supportplatform continues because it has weak reference to this library.#
    #1.5#00174212003F004C0000034B00000ADC00043341AB96B154#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.pcd.glservice and is starting it!#
    #1.5#00174212003F004C0000034C00000ADC00043341AB96B1B2#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.contentmigration.contentmigrationservice and is starting it!#
    #1.5#00174212003F004C0000034D00000ADC00043341AB96B1FF#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.httpconnectivity.urlfetcherservice and is starting it!#
    #1.5#00174212003F004C0000034E00000ADC00043341AB96B24C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.connectorservice and is starting it!#
    #1.5#00174212003F004C0000034F00000ADC00043341AB96B2A4#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.application.jcoclient and is starting it!#
    #1.5#00174212003F004C0000035000000ADC00043341AB96B2F1#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.systemlandscapeservice and is starting it!#
    #1.5#00174212003F004C0000035100000ADC00043341AB96B33B#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.ivs.iviewservice and is starting it!#
    #1.5#00174212003F004C0000035200000ADC00043341AB96B38C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.designservice and is starting it!#
    #1.5#00174212003F004C0000035300000ADC00043341AB96B3D7#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.themes.lafservice and is starting it!#
    #1.5#00174212003F004C0000035400000ADC00043341AB96B421#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.productivity.resolverservice and is starting it!#
    #1.5#00174212003F004C0000035500000ADC00043341AB96B46C#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has weak reference to application sap.com/com.sap.portal.runtime.config and is starting it!#
    #1.5#00174212003F004C0000035600000ADC00043341AB96B4B6#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sapportals.supportplatform : Application sap.com/com.sapportals.supportplatform has a weak reference to resource jdbc/Resource1 with type javax.sql.DataSource but the resource is not available and the application may not work correctly!#
    #1.5#00174212003F004C0000035700000ADC00043341AB96B510#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sapportals.supportplatform finished successfully on server 307377350#
    #1.5#00174212003F004C0000035800000ADC00043341AB96B557#1182257051534#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sapportals.supportplatform finished on current cluster node for 4813 ms.#
    #1.5#00174212003F004C0000036000000ADC00043341AB9A0CF9#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminclusteradminwd finished successfully on server 307377350#
    #1.5#00174212003F004C0000036100000ADC00043341AB9A0D67#1182257051753#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminclusteradminwd finished on current cluster node for 219 ms.#
    #1.5#00174212003F004C0000036900000ADC00043341AC476D74#1182257063114#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tc~workflowmodeler] finished successfully on Web Container.#
    #1.5#00174212003F004C0000036A00000ADC00043341AC4770C7#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tc~workflowmodeler finished successfully on server 307377350#
    #1.5#00174212003F004C0000036B00000ADC00043341AC47712A#1182257063114#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tc~workflowmodeler finished on current cluster node for 11361 ms.#
    #1.5#00174212003F004C0000037300000ADC00043341AD0C9DC4#1182257076037#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv] finished successfully on Web Container.#
    #1.5#00174212003F004C0000037400000ADC00043341AD0CA03B#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished successfully on server 307377350#
    #1.5#00174212003F004C0000037500000ADC00043341AD0CA099#1182257076037#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv finished on current cluster node for 12923 ms.#
    #1.5#00174212003F004C0000037D00000ADC00043341AD0D14D7#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.biloggingconfig finished successfully on server 307377350#
    #1.5#00174212003F004C0000037E00000ADC00043341AD0D1549#1182257076068#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.biloggingconfig finished on current cluster node for 31 ms.#
    #1.5#00174212003F004C0000038600000ADC00043341AD0FDBFC#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.netweaver.bc.uwl.logging finished successfully on server 307377350#
    #1.5#00174212003F004C0000038700000ADC00043341AD0FDC70#1182257076256#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.netweaver.bc.uwl.logging finished on current cluster node for 188 ms.#
    #1.5#00174212003F004C0000038F00000ADC00043341AD383B60#1182257078897#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/tcsldstartup~app] finished successfully on Web Container.#
    #1.5#00174212003F004C0000039000000ADC00043341AD383DD5#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tcsldstartup~app finished successfully on server 307377350#
    #1.5#00174212003F004C0000039100000ADC00043341AD383E2D#1182257078897#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tcsldstartup~app finished on current cluster node for 2641 ms.#
    #1.5#00174212003F004C0000039900000ADC00043341AD48B35C#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.ip.bi.sdk.datasource.sys finished successfully on server 307377350#
    #1.5#00174212003F004C0000039A00000ADC00043341AD48B3CE#1182257079975#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.ip.bi.sdk.datasource.sys finished on current cluster node for 1078 ms.#
    #1.5#00174212003F004C000003A200000ADC00043341AD619BAC#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/tclmwebadminmonitorcomplib~wd finished successfully on server 307377350#
    #1.5#00174212003F004C000003A300000ADC00043341AD619C1D#1182257081616#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/tclmwebadminmonitorcomplib~wd finished on current cluster node for 1641 ms.#
    #1.5#00174212003F004C000003A400000ADC00043341AD794D3C#1182257083163#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Start of application [sap.com/com.sap.workflow.j2eemoni] finished successfully on Web Container.#
    #1.5#00174212003F004C000003A500000ADC00043341AD795057#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 307377350 during startApp sap.com/com.sap.workflow.j2eemoni : Application sap.com/com.sap.workflow.j2eemoni has weak reference to application sap.com/com.sap.workflow.apps and is starting it!#
    #1.5#00174212003F004C000003A600000ADC00043341AD7950BD#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp over application sap.com/com.sap.workflow.j2eemoni finished successfully on server 307377350#
    #1.5#00174212003F004C000003A700000ADC00043341AD795105#1182257083163#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation startApp on application sap.com/com.sap.workflow.j2eemoni finished on current cluster node for 1547 ms.#
    #1.5#00174212003F004C000003A800000ADC00043341AD7AF3AE#1182257083272#/System/Server##com.sap.engine.services.deploy######0f1d31101e5f11dcbc7c00174212003f#SAPEngine_System_Thread[impl:5]_401##0#0#Info#1#com.sap.engine.services.deploy#Plain###The synchronization of applications with DB completed for 1631354 ms.#
    #1.5#00174212003F004D0000005B00000ADC00043341CABE84F0#1182257574096#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing HTTP request to servlet [jsp] finished with error.
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    Exception id: [00174212003F004D0000005A00000ADC00043341CABE8396]#
    #1.5#00174212003F004D0000005E00000ADC00043341CAD04526#1182257575252#/System/Server/WebRequests#sap.com/com.sap.security.core.admin#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####fedffd001e6311dcc5e900174212003f#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Plain###Processing an HTTP request by the error page [/error.jsp] finished with errors. Probably the exception [com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    ].] thrown by the requested servlet [/useradmin/error.jsp] cannot be processed.
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: [java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
    Exception in thread "main"
    Exception id: [00174212003F004D0000005D00000ADC00043341CAD04370]#
    I have JDK 1.4.2_014 installed on the system and WAS has its own JDK installed inside its own folder. I am having a similar problem with NWDS where it always picks up my JRE as default which is not installed inside my jdk 1.4._014. This remains the same even when I change the  jre path inside the NWDS preference from the Window->Preferences menu.
    This problem has stayed the same even after I uninstalled the jdk , NWDS, and WAS and reinstalled them from the scratch. Before that, I had actually got NWDS working when I added the tools.jar file from the jdk 1.4_014 to the jre my NWDS was pointing to. but this trick is not working with WAS.
    Also when I had deployed the web dynpro project, it did not show in the browser window which stayed blank.
    Please help me with it.

    I don't know. You would have to find people who pay attention to such things. Maybe try the developer forums at http://devforums.apple.com. From everything I have read, iAd is not one of the best advertising networks. Even the best advertising networks pay very, very little. I think it is much better to provide functionality that people are willing to pay for, probably via in-app purchases.

  • Unable to login to portal and any links in index.html page

    Hi,
    I am not able to login to portal. Only able to login to System information link.
    Whenever I try to login to other links, I have been taken to User input screen. After I enter the username and password, I am getting response as if Page is refreshed.
    Only log geting updated is default trace during this action.
    Few Error messages from default trace file during this action:
    #1.5 #00188B34FD3300590000002E000065BC0004620157F23D55#1233657817007#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#J2EE_GUEST#0##n/a##8310f2f3f1df11dda01a00188b34fd33#SAPEngine_Application_Thread[impl:3]_11##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: java.lang.NullPointerException: null)].
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
    Exception id: [00188B34FD3300590000002C000065BC0004620157F23ADA]#
    #1.5 #00188B34FD33006500000035000065BC00046201585A3EDE#1233657823820#com.sap.engine.services.security.authentication.logonapplication#sap.com/com.sap.security.core.admin#com.sap.engine.services.security.authentication.logonapplication.doLogon#J2EE_GUEST#0##n/a##8722f8c0f1df11dd933700188b34fd33#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Java###doLogon failed
    [EXCEPTION]
    #1#com.sap.security.core.logon.imp.UMELoginException
         at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.logon(SAPJ2EEAuthenticator.java:949)
         at com.sap.security.core.logonadmin.ServletAccessToLogic.logon(ServletAccessToLogic.java:208)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.doLogon(SAPMLogonLogic.java:914)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.uidPasswordLogon(SAPMLogonLogic.java:578)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:158)
         at com.sap.security.core.sapmimp.logon.SAPMLogonServlet.doPost(SAPMLogonServlet.java:60)
         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)
    Regards,
    Nallasivam.D

    Hi,
    have already read this thread:
    it´s nearly the same problem.
    Have you checked if the java guest account is enabled? Please check note 1231650.
    Best Regards,
    Jens

  • XSL Transformation error source

    I am using MII 12.0 and I am getting the following error in the log file:
    javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
    The problem is that I am not using and XSL transforms that I know of. What BLS action might generate this error other than the obvious XSL Transformation Action?
    Thanks.
    ...Sparks

    I found this thread:
    [Re: IDOC error|Re: IDOC error]
    Is your system set up to receive any idocs?
    Edited by: Christian Libich on Feb 8, 2010 10:00 PM

  • Error: Requested resource does not exist with SAP WebAS..deployed an ear

    hi,
    i deployed an application using SDM gui deployement manger.   the application is built using struts,spring etc. I have also created a datasource with Oracel 9i succesfully and hav associated it with the application.
    When i try to access the application using the struts based path i get an "<b>ERROR 404:- Error: Requested resource does not exist</b>". I also tried accessing the index.jsp page directly without struts paths but dont know why i get an error "<b>File [appContext/admin/index.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].</b>"
    The same ear is working perfectly fine with IBM WSAD but not in SAP Web AS ?? is there any configuration issues that i need to address ?? Kindly help me ASAP !!
    Regards,
    Vaibhav

    Hi,
    The Required server log contents are as follows:-
    #1.5#000CF1AFC124017A000000020000067000041B1D550F525C#1155712701853#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#sap.com/doculine#com.sap.engine.services.servlets_jsp.server.jsp.JSPParser#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server#Plain###Runtime error in compiling of the JSP file <C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp> !
    The error is: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [/WEB-INF/c.tld]: [
         com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)(:main:, row=739, col=23) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)
    Exception id: [000CF1AFC124017A000000000000067000041B1D550F4D94]#
    #1.5#000CF1AFC124017A000000030000067000041B1D550F5C88#1155712701868#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/doculine#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error##Plain###Processing HTTP request to servlet [action] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp].
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:117)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.getClassName(JSPServlet.java:238)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.compileAndGetClassName(JSPServlet.java:429)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:169)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
         at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:1001)
         at org.apache.struts.action.RequestProcessor.processForward(RequestProcessor.java:560)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:209)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
         at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:386)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:229)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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)
    Caused by: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.ParseException: TagLibValidator returns error(s) for taglib [/WEB-INF/c.tld]: [
         com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)(:main:, row=739, col=23) -> com.sap.engine.lib.xml.parser.ParserException: Unsupported character: a9(:main:, row:739, col:23)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.validate(JSPParser.java:243)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.initParser(JSPParser.java:348)
         at com.sap.engine.services.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:105)
         ... 37 more
    #1.5#000CF1AFC124017A000000050000067000041B1D550F5F94#1155712701868#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/doculine#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#2####661184d02cf711db80fa000cf1afc124#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [action] finished with error.
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/doculine/servlet_jsp/doculine/root/admin/login.jsp].
    Exception id: [000CF1AFC124017A000000030000067000041B1D550F5C88]#

Maybe you are looking for

  • CRM 5.0 - Middleware issues after Support Package installation

    Hi experts, after upgrading the support package (from version 11 to version 17) we are facing a lot of issues. 1. We need to synchronize custom tables from CRM to R/3. Can you give me an example on how to configure table SMOFQFIND/CRMMAPTAB for inbou

  • Some Virus Questions

    I have been trying to stay as safe as possible in my web life recently. I was getting a bit overconfident because of the Macs reputation. I have had only Macs going back to OS7. My questions are #1. When I finally get a Intel Mac and heaven only know

  • Looking for a way to monitor forums for a text string.

    Hi as the subject says I'm looking for a way to monitor various forums for a list of text strings and give me a link to the post. I'm have tried googling but cant find anything specific enough I've tried looking at methabot but am unsure as to if thi

  • Save Saver attached to Adobe Flash Player 11 or Adober Photoshop Elements 9 download

    In July 2013, I downloaded Adober Flash Player 11 after an upgrade of my Windows OS and Explorer software.  I have used Adobe Pro since 2009 and was using prior versions of Flash Player prior to my OS upgrade.  The download of Adobe Flash Player 11 c

  • Where can I get help for AE 5.0

    I only seem to get very confusing current CC help from the web and I need specific help for AE 5.0