Cannot process an HTTP request to servlet [Faces Servlet] in [wcb] web application

Hi All
l am working on a Wcem 3.0 with Trex with ERP and WAS 7.3.
When I logon to http://<host>:<port>/wcb/index.html url I am able to see wcbuilder_erp & wcbuilder_erp_ume application ids.
But suddenly I am getting The website cannot display the page error message when I access the above mentioned URL.
When I verify the developer log trace it showing as 500 Internal sever error issue.[EXCEPTION] java.lang.VerifyError: Bad return type
In defaultTrace.trc file it is showing as Cannot process an HTTP request to servlet [Faces Servlet] in [wcb] web application exception.
09 10 18:08:56:098#+0530#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
com.sap.ASJ.web.000137#WEC-APP-BF#sap.com/wec~comm~wcb~leanapp#C0000A229CA7094A0000000000001188#2392750000000004#sap.com/wec~comm~wcb~leanapp#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##CFAFBF4C38E411E4B4750000002482AE#ffbcbcdd38e611e49d020000002482ae#ffbcbcdd38e611e49d020000002482ae#0#Thread[HTTP Worker [@455349581],5,Dedicated_Application_Thread]#Plain##
Cannot process an HTTP request to servlet [Faces Servlet] in [wcb] web application.
[EXCEPTION] java.lang.VerifyError: Bad return type
Exception Details:
Location: com/sap/wec/tc/core/runtime/jsf/resource/WecExternalContextFactory.getExternalContext(Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)Ljavax/faces/context/ExternalContext; @17: areturn
Reason: Type 'com/sap/wec/tc/core/runtime/jsf/resource/WecExternalContext' (current frame, stack[0]) is not assignable to 'javax/faces/context/ExternalContext' (from method signature)
Current Frame:
    locals: { 'com/sap/wec/tc/core/runtime/jsf/resource/WecExternalContextFactory', 'java/lang/Object', 'java/lang/Object', 'java/lang/Object' }
    stack: { 'com/sap/wec/tc/core/runtime/jsf/resource/WecExternalContext' }
  Bytecode:
    0000000: bb00 0359 2ab6 0004 2b2c 2db6 0005 b700
    0000010: 06b0                                
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2446)
    at java.lang.Class.getConstructor0(Class.java:2756)
    at java.lang.Class.getConstructor(Class.java:1693)
Any help?
Regards
Rami Reddy

Hi Steffen,
Thanks for promt response.
But when I checked with Basis team as of now there are not yet configured TREX, only WCEM components has been configured in WAS 7.3. When they are configuring WCEM components HTTPS protocol not configured.
But for past 2 weeks I am able to see the below screen using http://<host>:<port>/wcb/index.html url.
But now I am getting The website cannot display the page error.
Please clarify me if anything is wrong from my side. And also pl let us know which configurations I have to check for fixing the issue.
Regards,
Rami Reddy

Similar Messages

  • Cannot process an HTTP request to servlet [DialogServlet] in [manufacturing] web application.

    Hi all,
    Now I can't open any new search help that use with the dialogservlet .
    And the log have the following error message :
    500 Internal Server Error is returned for HTTP request
    [http://xxxx:xxxxxx/manufacturing/com/sap/me/system/common/client/ErrorPage.jsp]:
      component [DialogServlet],
      web module [manufacturing],
    application [sap.com/me~ear],
      DC name [sap.com/me~ear],
      CSN
    component[],
      problem categorization [com.sap.ASJ.web.000137],
    internal categorization [254340799].
    [EXCEPTION]
    java.lang.NullPointerException: while trying to invoke
    the method java.lang.Throwable.printStackTrace(java.io.PrintWriter) of an object
    loaded from local variable 'e'
    at
    com.sap.me.frame.Utils.getStackTrace(Utils.java:764)
    at
    JEE_jsp_com_sap_me_system_common_client_ErrorPage_1410450_1404183172000_1404185122991._jspService(JEE_jsp_com_sap_me_system_common_client_ErrorPage_1410450_1404183172000_1404185122991.java:137)
    at
    com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
    at
    com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at
    com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:428)
    at
    com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:147)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at
    com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at
    com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doCached(RequestDispatcherImpl.java:655)
    at
    com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:488)
    at
    com.vatti.mes.common.web.BaseServlet.doError(BaseServlet.java:61)
    at
    com.vatti.mes.common.dialog.web.DialogServlet.doPost(DialogServlet.java:125)
    at
    com.vatti.mes.common.dialog.web.DialogServlet.doGet(DialogServlet.java:53)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at
    com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at
    com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at
    com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
    at
    com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at
    com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    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.SessionSizeFilter.process(SessionSizeFilter.java:26)
    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:57)
    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: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.server.Processor.chainedRequest(Processor.java:475)
    at
    com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at
    com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    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:328)

    Hi Ivan!
    The fact the this code worked fine yesterday or is working fine in Dev but not in another system proves nothing. On the contrary, the stack trace confirms that the problem stems from your custom code com.vatti.mes.common.web.BaseServlet.doError(BaseServlet.java:61). The obvious thing is that the method here is called "doError" that likely means you either face some error there or intentionally generate error message. After that the system tries to log the error message but it looks as if com.sap.me.frame.Utils.getStackTrace method gets null as an input parameter e. How does it get triggered and what is passed into - this is a question to your developers.
    Regards,
    Sergiy

  • Cannot process an HTTP request to servlet [DTRServlet]

    Hi NWDI experts,
    I just installed a completely new NWDI 7.4 SR1 (SP05) on Windows 2012 R2 and Oracle 11.2.0.4.
    When I try to access DTR I receive error "500 Internal Server Error". In defaultTrace the system reports problems with initialization of DTR. Multiple entries exists in the various log-files and traces, which concerns the problem. I've therefore attached logs and traces to this discussion. After downloading the file rename it to .zip instead of .txt.
    The error seems to be caused by a NullPointerException in oracle.jdbc.driver.OracleStatement.m_batchItems.
    I've searched extensively on SCN, Notes and Google, but have not been able to find any answers to what the problem is. Also I've looked at note 774339 - Internal Server Error in DTR, but have not been able to find a useful solution.
    Has anyone experienced the same error and how where you able to solve it?
    Best regards,
    Jacob

    Good morning Ervin,
    Thank you very much for your answer. I had a suspicion that the error was deeper in the belly of the system and not caused by DTR.
    In the note you mention, it says that a new version of Oracle Client software will be delivered, which should fix the error, but do you have an idea on when it will be available for SAP customers to download?
    Just as a temporary workaround I've replaced the ojdbc6.jar for 11.2.0.4 with the one from 11.2.0.3 and I'm now able to access and browse the DTR.
    Best regards,
    Jacob

  • Exception thrown by servlet Faces Servlet in WAS ND 6.1.0.13

    Hi,<br>
    I'm using WebSphere Application Server Network Deployment (WAS ND) v. 6.1.0.13.<br><br>
    I'm getting this error when I try to launch my application:<br><br>
    [1/24/08 11:41:44:100 WET] 0000003c ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet Faces Servlet: java.lang.NullPointerException<br>
    at javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)<br>
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:190)<br>
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:317)<br>
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:346)<br>
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)<br>
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3276)<br>
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)<br>
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)<br>
    at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)<br>
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)<br>
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)<br>
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)<br>
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)<br>
    at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)<br>
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:556)<br>
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:606)<br>
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:979)<br>
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1064)<br>
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)<br>
    <br><br><br>
    After doing a search I tried this following steps:<br>
    � Delete the entry in web.xml:<br>
    <listener><br>
    <listener-class><br>
    com.sun.faces.config.ConfigureListener<br>
    </listener-class><br>
    </listener><br><br>
    � Update my log4j version<br><br>
    � Delete the commons-logging.jar from WEB-INF directory<br>
    These are the jar files included in WEB-INF directory:<br>
    commons-beanutils.jar<br>
    commons-collections.jar<br>
    commons-digester.jar<br>
    commons-javaflow-20060411.jar<br>
    commons-logging.jar<br>
    FglConnectorClient.jar<br>
    itext-1.4.2.jar<br>
    jasperreports-1.2.3.jar<br>
    jcommon-1.0.0.jar<br>
    jfreechart-1.0.1.jar<br>
    jsf-api.jar<br>
    jsf-ibm.jar<br>
    jsf-impl.jar<br>
    jstl.jar<br>
    log4j-1.2.14.jar<br>
    standard.jar<br>
    struts.jar<br>
    <br><br>
    <br>
    None of the suggestions worked.<br><br>
    Then I tried to deploy my application in another WAS ND 6.1.0.13 and it worked!!! <br>
    What can I do so solve this problem in my WAS ND 6.1.0.13? What could be the problem?<br><br>
    Thanks,<br>
    Nuno

    Did you find a solution to this problem
    please help
    Thanks & Regards
    Nasir

  • Servlet Faces Servlet is currently unavailable

    Hi,
    I get the following error when deploying my webapp to Tomcat 4.0:
    [Thu Dec 18 12:03:16 EST 2003] stdout: StandardWrapper[DeployApp:Faces Servlet]: Marking servlet Faces Servlet as unavailable
    [Thu Dec 18 12:03:16 EST 2003] stdout: StandardContext[DeployApp]: Servlet /BULDeployApp threw load() exception: javax.servlet.ServletException: Wrapper cannot find servlet class javax.faces.webapp.FacesServlet or a class it depends on
    [Thu Dec 18 12:03:16 EST 2003] stdout: javax.servlet.ServletException: Wrapper cannot find servlet class javax.faces.webapp.FacesServlet or a class it depends on
    The jsf-ri.jar is copied in $tomcat_home/common/lib (to solve the ConfigListener error) and following libraries are a part of web-inf/lib:
    commons-beanutils.jar, commons-collections.jar, commons-digester.jar, commons-logging.jar, jsf-api.jar, jstl.jar, standard.jar.
    Please help.

    The jsf-ri.jar is copied in $tomcat_home/common/lib
    (to solve the ConfigListener error) and following
    libraries are a part of web-inf/lib:
    commons-beanutils.jar, commons-collections.jar,
    commons-digester.jar, commons-logging.jar,
    jsf-api.jar, jstl.jar, standard.jar.
    If you copy jsf-ri.jar into common/lib, you should copy all of the others as well (and remove them from your web application). However, you should also know that if you are really using Tomcat 4.0.x there are several class loader problems that will make it virtually impossible for this to run correctly. I would strongly recommend updating to Tomcat 5.0.16 (recently released stable implementation of Servlet 2.4 and JSP 2.0).
    It's also possible to get the beta release of JSF to work on Tomcat 4.1.29 (see the release notes for details) but you will need to be sure you're using JSTL 1.0 instead of 1.1.
    >
    Please help.Craig

  • How to transfer the http request from applet to servlet/jsp

    I use the JTree component to create a navigation of a website,but i don't
    know how to connect the tree's nodes with the jsp/servlet.
    I mean how to transfer the http request from the applet to a jsp.
    I use the "<frameset>" mark which will divide the web browse into 2 blocks.
    The left side is Applet,and the right side is the linked jsp page.
    what I say is as the weblogic console layout.
    who can help me!!!
    Thank You!

    I use the JTree component to create a navigation of a website,but i don't
    know how to connect the tree's nodes with the jsp/servlet.
    I mean how to transfer the http request from the applet to a jsp.
    I use the "<frameset>" mark which will divide the web browse into 2 blocks.
    The left side is Applet,and the right side is the linked jsp page.
    what I say is as the weblogic console layout.
    who can help me!!!
    Thank You!

  • Detect server node processing a http request

    Is there any way to detect which server node is answering a http request? For debug purposes I would like to add the cluster element to the output of a jsp. Maybe it is also possible to force a jsp being processed by a given node?
    Thanks in advance for your answers!
    Best regards,
    Frank

    Hi Violeta,
    Thanks for your answer! This has been very helpful indeed.
    However, I´m still a bit puzzled. Replacing the saplb cookie forces the load balancer to use the given server, but the JSESSIONID does not change. Looking at the application data I know that I´m talking to a different server, but I still don´t seem to have a way to tell which server ansered - except my expectation that the saplb cookie might have been taken into account by the server.
    Isn´t there a more sophisticated way to access this kind of information? Escpecially, getting a list of all available servers would be great, as this would allow to choose the server having a look at.
    Best regards,
    Frank

  • DTRServlet - 500 Internal Server Error is returned for HTTP request

    Hi everybody,
    I've got a Problem with my DTR.
    Recently we've set up the new CE 7.2 System.
    The DTR has run until about 3 hours ago.
    I don't know what I've done that this error occurs, but I'm nearly shure that I haven't done anything that depends on the dtr.
    I went through the set up wizzard of "Connect Design Time for Visual Composer with NWDI" again, but nothing changed.
    Can you please help me with this issue?!
    Thank you and best regards
    julian
    This is the text from the application log:
    #2.0 #2010 08 20 15:02:47:398#+0200#Info#/Applications/DTR/Lifecycle#
    lifecycle.startApplicationInitialisation#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE050000000000000010D8#1694250000000004#sap.com/tcdtrenter
    priseapp#com.tssap.dtr.server.servlet.WebdavServlet#Guest#0##F30581C3AC5A11DFCAED00000019DA2A#f30581c3ac5
    a11dfcaed00000019da2a#f30581c3ac5a11dfcaed00000019da2a#0#Thread[HTTP Worker [@1902689675],5,Dedicated_Application_Thread]#Plain#com.tssap.dtr.server.deltav.resources.log_messages#
    Starting initialisation of DTR application.#
    #2.0 #2010 08 20 15:02:47:405#+0200#Fatal#/Applications/DTR/Lifecycle#
    com.sap.DI.dtr.090009#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE050000000001000010D8#1694250000000004#sap.com/tcdtrente
    rpriseapp#com.tssap.dtr.server.servlet.WebdavServlet#Guest#0##F30581C3AC5A11DFCAED00000019DA2A#f30581c3ac5
    a11dfcaed00000019da2a#f30581c3ac5a11dfcaed00000019da2a#0#Thread[HTTP Worker [@1902689675],5,Dedicated_Application_Thread]#Plain#com.tssap.dtr.server.deltav.resources.log_messages#
    Initialisation of DTR application failed. Please refer to SAP note 774339 for more details on how to analyze the error condition.#
    And this is the message from the Default Trace: (not all, that didn't fit in this thread)
    #2.0 #2010 08 20 15:13:49:744#+0200#Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#
    com.sap.ASJ.web.000137#BC-CTS-DTR-SRV#sap.com/tcdtrenterpriseapp#005056BA56AE05D600000002000010D8#1694250000000004#sap.com/tcdtrent
    erpriseapp#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##7F3F3C0AAC5A11DF869E00000019D
    A2A#7db05704ac5c11dfa28500000019da2a#7db05704ac5c11dfa28500000019da2a#0#Thread[HTTP Worker [@236433360],5,Dedicated_Application_Thread]#Plain##
    Cannot process an HTTP request to servlet [DTRServlet] in [dtr] web application.
    [EXCEPTION]
    javax.servlet.ServletException: WebdavServlet.init() failed : com.tssap.dtr.pvc.basics.cluster.TaskFailedException: Connection is invalid.
         at com.tssap.dtr.server.servlet.WebdavServlet.init(WebdavServlet.java:471)
         at javax.servlet.GenericServlet.init(GenericServlet.java:270)
         at com.sap.engine.services.servlets_jsp.server.application.WebComponents.getServlet(WebComponents.java:864)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:326)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
         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:328)
    Caused by: com.tssap.dtr.pvc.basics.cluster.TaskFailedException: Connection is invalid.
         at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.start(ClusterExclusiveTaskRunner.java:54)
         at com.tssap.dtr.server.deltav.impl.Repository.initialize(Repository.java:643)
         at com.tssap.dtr.server.deltav.impl.Repository.initialize(Repository.java:613)
         at com.tssap.dtr.server.servlet.WebdavServlet.initializeDeltaV(WebdavServlet.java:556)
         at com.tssap.dtr.server.servlet.WebdavServlet.init(WebdavServlet.java:462)
         ... 36 more
    Caused by: com.tssap.dtr.pvc.util.sql.SQLRuntimeException: Connection is invalid.
         at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.prepareStatement(GenericStatementProvider.java:75)
         at com.tssap.dtr.pvc.util.sql.GenericStatementProvider._getPreparedStatement(GenericStatementProvider.java:62)
         at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.getPreparedStatement(GenericStatementProvider.java:44)
         at com.tssap.dtr.pvc.basics.persistence.PersistentClass.getPreparedStatement(PersistentClass.java:148)
         at com.tssap.dtr.pvc.repository.TaggedValuePersistentClass.loadTaggedValue(TaggedValuePersistentClass.java:113)
         at com.tssap.dtr.pvc.repository.TaggedValueTransientClass.loadTaggedValue(TaggedValueTransientClass.java:51)
         at com.tssap.dtr.pvc.repository.RepositoryManager._checkDbInitialization(RepositoryManager.java:288)
         at com.tssap.dtr.pvc.repository.RepositoryManager.isDbInitialized(RepositoryManager.java:1128)
         at com.tssap.dtr.server.deltav.impl.Repository.initializeDeltaV(Repository.java:558)
         at com.tssap.dtr.server.deltav.impl.Repository$1.run(Repository.java:645)
         at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.startTask(ClusterExclusiveTaskRunner.java:65)
         at com.tssap.dtr.pvc.basics.cluster.ClusterExclusiveTaskRunner.start(ClusterExclusiveTaskRunner.java:51)
         ... 40 more
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: Connection is invalid.
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfInvalid(ConnectionHandle.java:652)
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfValid(ConnectionHandle.java:639)
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:113)
         at com.tssap.dtr.pvc.basics.transaction.SharedConnection.prepareStatement(SharedConnection.java:131)
         at com.tssap.dtr.pvc.util.sql.GenericStatementProvider.prepareStatement(GenericStatementProvider.java:73)
         ... 51 more

    Hello Julian
    This is a known problem.
    Cause
    - A user may have been added to a group in another ldap tree with a name, that is already existing.
    - When DTR retrieves the group from UME, we get 2 similar group names, but the groups may be different.
    - DTR cannot handle this and throws "Internal Server error"
    Resolution
    If you change parameter "ume.ldap.unigue_grup_attribute" to 'uid', DTR doesn't use the groupname,
    but the group-uid, therefore the group is unique.
    1. open Visual Administrator
    2. choose Services
    3. choose UME Provider
    4. Reset "ume.ldap.unigue_grup_attribute" with 'uid'
    5. restart the system
    Thanks
    Kenny.

  • How to send a HTTP request to servlet in java application

    I'm new in Java. I need to send a HTTP request with parameters to servlet in a java aplication. Here is my code. It can be compiled but always threw an exceptions when I ran it. Can anyone help?
    package coreservlets;
    import java.io.*;
    import java.net.*;
    public class PostHTTP
         public static void main(String args[])
              throws IOException, UnknownHostException {
              try
              // URL and servlet
                   URL myURL = new URL("http://pc076/servlet/coreservlets.OffHold");
                   URLConnection c = myURL.openConnection();
                   c.setUseCaches(false);
                   c.setDoOutput(true);
                   ByteArrayOutputStream byteStream = new ByteArrayOutputStream(512);
                   PrintWriter out = new PrintWriter(byteStream, true);
    //parameters
                   String postData = "REASON_CODE=3B&RSPCODE=JSmith&CASENUM=NA795401&REPLY=123&SOURCE=XYZ&REPLYLINK=http://pc076/servlet/coreservlets.ShowParameters";
                   out.print(postData);
                   out.flush();
                   String lengthString = String.valueOf(byteStream.size());
                   c.setRequestProperty("Content-Length", lengthString);
                   c.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
                   byteStream.writeTo(c.getOutputStream());
                   BufferedReader in =     new BufferedReader(new InputStreamReader
                                                 (c.getInputStream()));
                   String line;
                   //String linefeed = "\n";
                   //resultsArea.setText("");
                   while((line = in.readLine()) != null) {
                        System.out.println(line);
                        //resultsArea.append(linefeed);
              catch(IOException ioe) {
              // Print debug info in Java Console
              System.out.println("IOException: " + ioe);

    here are some updates to your code I haven't tested it running
    post again if you still have trouble
    URL myURL = new URL("http://pc076/servlet/coreservlets.OffHold");
    HttpURLConnection c = (HttpURLConnection)myURL.openConnection();
    c.setDoInput(true);
    c.setDoOutput(true);
    ByteArrayOutputStream byteStream = new ByteArrayOutputStream(512);
    String lengthString = String.valueOf(byteStream.size());
    c.setRequestProperty("Content-Length", lengthString);
    c.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
    PrintWriter out = new PrintWriter(byteStream, true);
    //parameters
    String postData = "REASON_CODE=3B&RSPCODE=JSmith&CASENUM=NA795401&REPLY=123&SOURCE=XYZ&REPLYLINK=http://pc076/servlet/coreservlets.ShowParameters";
    out.print(postData);
    out.flush();
    byteStream.writeTo(c.getOutputStream());
    // connect
    c.connect();
    BufferedReader in = new BufferedReader(new InputStreamReader
    (c.getInputStream()));
    String line;
    while((line = in.readLine()) != null)
        System.out.println(line);

  • WLS8.1 & JSF 1.0 Final: "Faces Servlet" failed to preload

    Ok, this i what I've done. Modified the samples proprties file so everythings gets build without problems with the 1.0.x taglib.
    <copy todir="${build}/${example}/WEB-INF/lib" file="${jstl.jar}"/>
    <copy todir="${build}/${example}/WEB-INF/lib" file="${standard.jar}"/>
    <copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/jaxen-full.jar"/>
    <copy todir="${build}/${example}/WEB-INF/lib" file="/jakarta-taglibs-standard-1.0.5/lib/saxpath.jar"/>
    The jst.jar, standard.jar also point to /jakarta-taglibs-standard-1.0.5/lib
    I updated the web.xml for the listener
    <listener>
         <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
    </listener>     
    ant the web.cml validated against http://java.sun.com/dtd/web-app_2_3.dtd
    If I deploy the cardemo I see:
    <5/03/2004 10:28:30 PM CET> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "jsf-cardemo".
    javax.servlet.ServletException
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
    at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:688)
    at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
    at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    >
    5/03/2004 22:28:32 com.sun.faces.config.rules.NavigationRuleRule end
    WARNING: [NavigationRuleRule]{faces-config/navigation-rule} Merge(/confirmChoices.jsp)
    What am I still missing here? I really want to start using JSF!
    Regards,
    Peter

    I believe I have found the issue to the problem. The issue seems to be Weblogic is not respecting part of the Servlet 2.3 spec. It states that all ServletContextListener implementations should be called before the Servlet's init method is called. Tomcat respects this and that's why JSF works when deployed in Tomcat. Weblogic 8.1 calls this instance AFTER the Servlet's init's methods are called. This results in a NullPointerException being thrown.
         You can see how the ordering changes between Weblogic and Tomcat for yourself by editing the log4j.properties file and add the following:
    log4j.category.com.sun.faces.config = DEBUG, config log4j.additivity.com.sun.faces.config=false
    log4j.appender.config = org.apache.log4j.ConsoleAppender log4j.appender.config.layout = org.apache.log4j.PatternLayout log4j.appender.config.layout.ConversionPattern = ...
         Deploy the example application to both Weblogic and Tomcat and observe the order.
         I've developed a work around for this issue. Weblogic seems to respect the <load-on-startup> element in the web.xml file. I have written a Servlet which manually loads the ServletContextListener for JSF. The code below:
    import org.apache.commons.logging.Log;
    import org.apache.commons.logging.LogFactory;
    import javax.faces.FactoryFinder;
    import javax.faces.lifecycle.LifecycleFactory;
    import javax.servlet.ServletConfig;
    import javax.servlet.ServletContextEvent;
    import javax.servlet.ServletContextListener;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    public class WeblogicHackServlet extends HttpServlet {
    public static final String CONFIGURE_LISTENER_KEY = "CONFIGURE_LISTENER"; public static final transient Log logger = LogFactory.getLog(WeblogicHackServlet.class);
    public void init(ServletConfig servletConfig) throws ServletException {
    LifecycleFactory factory =(LifecycleFactory)      
    FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
    if (factory != null)
    return;
    String className = servletConfig.getInitParameter(CONFIGURE_LISTENER_KEY);
    if (className == null) {
    logger.fatal("Did not find the init parameter " + CONFIGURE_LISTENER_KEY);
    return;
    try {
    Class aClass = Class.forName(className);
    ServletContextListener listener = (ServletContextListener)
                   aClass.newInstance();
    listener.contextInitialized(
         new ServletContextEvent(servletConfig.getServletContext()));
    } catch (Exception e) {
    logger.fatal("The ConfigureListener could not be triggered", e);
         The web.xml file also needs to be changed to the following:
    <servlet>
    <servlet-name>WeblogicHackServlet</servlet-name>
    <servlet-class>WeblogicHackServlet</servlet-class>
    <init-param>
    <param-name>CONFIGURE_LISTENER</param-name>
    <param-value>com.sun.faces.config.ConfigureListener</param-value>
    </init-param>
    <load-on-startup> 1 </load-on-startup>
    </servlet>
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup> 2 </load-on-startup>
    </servlet>
    This causes JSF to load properly. Hopefully, BEA can resolve this issue so my hack can be removed.
    Thanks,
    Louis Calisi
    Applications Architect

  • Simultaneous remote object calls in one http request?

    I am noticing when I have two remote object calls happen at the same time they are being bundled into one http request.  This is causing problems in my application becuase the result is not coming back until both have finished.
    So basically I have to calls that happen at the sametime.  One does not take anytime and the other is a long running task.  I will not get the result for the first until the long running task completes.
    Has anyone else seen this?
    Any help would be appreciated.

    "suspend the main thread, pending a remote call.." No. Can't
    be done.
    ..."pass arguments into the resultHandler..." Yes, this is
    done using the AsyncToken. (ACT pattern)
    The send() methods returns an AsyncToken object. You can use
    this dynamic object to add almost anything you want to the token,
    including strings, and functions (google the term "closure").
    As I am still not comfortable with anonymous functions, I
    like to pass strings. I pass an identifier, which I can use in a
    switch statement to determine the next step. Sometimes I pass a
    "nextStep" string to define finer grain conditionality.
    I use a single dataService object and result handler function
    for all calls.
    Tracy

  • Possible to get runtime info (Http request, response) from a WD4A Appl.?

    Hey,
    In a BSP / JSP application, it is possible to retrieve and set the runtime data (http request and response). For Example:
    response.setContentType("application/x-suvaagent;charset=iso-8859-1");
    response.setHeader("Cache-Control", "public");
    response.getWriter().print("<Request>");
    response.getWriter().print("</Request>");
    Is it possible to do this in a WebDynpro (ABAP) Application?
    The requirement is to construct a file using http response method. This file contains parameters like business data etc. The file type is already registered as a MIME type which is associated with a standalone program.
    When sending the http response, the file will be filled out with needed data and the associated program will be called using the data in the file.
    I haven't found out how to do this in web dynpro application, since we use WD4A in our project.
    Thanks and Regards,
    Liang

    In Web Dynpro you do not have direct access to the Request or Response object. This is part of the design of the abstracted rendering and makes things like the SmartClient and the AJAX based Delta Rendering possible.
    In Web Dynpro you should use the FileDownload UI element or the CL_WD_RUNTIME_SERVICES=>ATTACH_FILE_TO_RESPONSE
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/a8d95673b12fe2e10000000a42189d/frameset.htm
    If you want more control over the response object for a download then I might suggest that you can create a cached response object, place it into the ICM cache and generate a unique URL for it.  You can then fire a navigation plug or a LinkToURL to go to that cached response object.

  • Timeouts during http requests

    Hi,
    We have noticed that long HTTP requests from the IP phones to a web server are terminated with a timeout (timeout varies according to the phone model).
    Where is these timeout being set? and is it editable?

    this confusion occurrs commonly. Frankly, the StringTokenizer class is not documented well: the delimited Stirng is not treated as a single delimiter. Instead, it is treated as a list of character delimiters. Thus, when you create your StringTokenizer, you are actually defining '%', '2', and '0' as your delimiters. Any of those characters would be treated as a delimiter.

  • Instantiating a eInsight business process through web application

    Hi all,
    Has anybody ever tried instantiating a eInsight business process involving user activities by clicking a link on a web application? All the tutorials I have seen so far are all based on input files. Could anybody please refer me to some sample where a eInsight process is started by clicking a link or rather interactively.
    Thanks & Regards,
    Sujoy

    An eInsight Business Process is instantated when a message for its initial Receive Activity becomes available for delivery. If you contrive to deliver a message to eInsight's BP from a Web Applicatin you will achieve the result you seek. The receive activity can be associated with a File eWay, a JMS Client end-point or any numer of other end points/adapters/connectors capable of receiving a message. You could, for example, use the JMS API Kit in a JSP in your web application to send a message to a JMS Receive activity that starts the BP. That presupposes that your web application is external to the Java CAPS solution. You could also build your web application using the eVision product, which is specifically designed to allow you to build Java CAPS-based web applications/composite applications. Have a look at eVision to see if you can use that to achieve what you need to achieve.

  • How to construct a faces request from a http request?

    I wonder how FacesServlet.service determines whether it should be calling LifecycleImpl.execute in oppose to calling LifecycleImpl.render?
    Basically, I'm trying to construct a http request that would go through the decode method of my UIComponent. However, it seems that my request has always been treated as a non-faces request, where it goes to the render face directly.
    Does anyone know how do I need to construct my http request so that it'll be recgonized as a faces request?
    Anyone knows where i can download the source code for FacesServlet?
    thanks!

    Sorry, are you saying that FacesServlet ALWAYS call execute before render even if it's the first request?
    What I experienced is that for the first request, execute isn't called, and it goes directly to render.
    And if I use the html form submit on the 2nd request, it does go to execute, then render.
    However, if i construct another http request, it'll act like a first request, where it doesn't go through the execute, but striaght to render.
    This is what I set in web.xml:
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup> 1 </load-on-startup>
    </servlet>
    <!-- Faces Servlet Mapping -->
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    I call my jsp using http://server:8080/faces/my.jsp, and I'm using tomcat 5. Any help would be appreciated.

Maybe you are looking for