Weblogic 8.1 SP2 + Struts + Internal Servlet Session Process Error Found!

Hi,
          I have developed a struts 1.1 based webapplication which runs fine on
          weblogic 7 (for one year in production), tomcat 4.1,5 and others but
          refuses to function in weblogic 8.1 sp2!
          This is the stacktrace I get when I try to call an action via the browser:
          java.lang.IllegalStateException: Internal Servlet Session Process Error
          Found!
               at
               weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
               at
               weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
               at
               org.apache.struts.action.RequestProcessor.processLocale(RequestProcessor.java:638)
               at
               org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:230)
               at
               org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
               at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:502)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at
               javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
               weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at
               weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at
               weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at
               weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at
               weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at
               weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at
               weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at
               weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
               weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Just out of curiosity I deployed the struts-examples webapplication from
          the apache jakarta struts distribution and it also fails to run with the
          same error!
          Can anybody help me out with this one? Does anybody experience the same
          thing?
          regards,
          oliver
          p.s. I will also post this message on the struts user list.
          

Hi,
          I have developed a struts 1.1 based webapplication which runs fine on
          weblogic 7 (for one year in production), tomcat 4.1,5 and others but
          refuses to function in weblogic 8.1 sp2!
          This is the stacktrace I get when I try to call an action via the browser:
          java.lang.IllegalStateException: Internal Servlet Session Process Error
          Found!
               at
               weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
               at
               weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
               at
               org.apache.struts.action.RequestProcessor.processLocale(RequestProcessor.java:638)
               at
               org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:230)
               at
               org.apache.struts.action.ActionServlet.process(ActionServlet.java:1420)
               at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:502)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at
               javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
               weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at
               weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at
               weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at
               weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at
               weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at
               weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at
               weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at
               weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
               weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Just out of curiosity I deployed the struts-examples webapplication from
          the apache jakarta struts distribution and it also fails to run with the
          same error!
          Can anybody help me out with this one? Does anybody experience the same
          thing?
          regards,
          oliver
          p.s. I will also post this message on the struts user list.
          

Similar Messages

  • IllegalStateException: Internal Servlet Session Process Error Found!

              I keep getting the annoying error as listed, and the server also keeps reporting
              that I can only connect from 0 unique ip addresses. Has anybody else seen these
              type of frustrations on 8.1 sp2, or can explain them.
              With as much detail omitted for simplicity;
              Frustration 1.
              I have a 8sp2 server running all ok, occasionally after a redeploy of an ear file
              I attempt to load a jsp file, and the error below is thrown.
              The JSP has a bean which is session based, and as from following the stack trace
              it is around some weblogic code which tests if my license allows access to the
              http session (on a developer license). I then have to start another server instance
              and do a deployment of a v.simple war, and access this, then deploy the same war
              to the broken server and access that, then the initial jsp works fine. no code
              changes just environment stops, starts and redeploys!
              Frustration 2
              Server runs ok, tray and connect from two machines (I have an ldap server that
              wants to 'broadcast' messages to my server), error of too many connections.
              The ip connection issues can in most cases be removed with a server restart.
              EXCEPTION TRACE
              java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
              With the following stack trace:
              java.lang.IllegalStateException: Internal Servlet Session Process Error Found!
                   at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
                   at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
                   at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
                   at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

              I have the same problem. Could any one help us?
              "David" <[email protected]> wrote:
              >
              >I keep getting the annoying error as listed, and the server also keeps
              >reporting
              >that I can only connect from 0 unique ip addresses. Has anybody else
              >seen these
              >type of frustrations on 8.1 sp2, or can explain them.
              >
              >With as much detail omitted for simplicity;
              >
              >Frustration 1.
              >I have a 8sp2 server running all ok, occasionally after a redeploy of
              >an ear file
              >I attempt to load a jsp file, and the error below is thrown.
              >
              >The JSP has a bean which is session based, and as from following the
              >stack trace
              >it is around some weblogic code which tests if my license allows access
              >to the
              >http session (on a developer license). I then have to start another
              >server instance
              >and do a deployment of a v.simple war, and access this, then deploy the
              >same war
              >to the broken server and access that, then the initial jsp works fine.
              > no code
              >changes just environment stops, starts and redeploys!
              >
              >Frustration 2
              >Server runs ok, tray and connect from two machines (I have an ldap server
              >that
              >wants to 'broadcast' messages to my server), error of too many connections.
              >The ip connection issues can in most cases be removed with a server restart.
              >
              >
              >EXCEPTION TRACE
              >
              >java.lang.IllegalStateException: Internal Servlet Session Process Error
              >Found!
              >
              >With the following stack trace:
              >
              >java.lang.IllegalStateException: Internal Servlet Session Process Error
              >Found!
              >     at weblogic.servlet.internal.session.SessionData.checkProcess(SessionData.java:1148)
              >     at weblogic.servlet.internal.session.SessionData.setAttribute(SessionData.java:501)
              >     at jsp_servlet._security.__changeprofile._jspService(__changeprofile.java:135)
              >     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
              >     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
              >     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
              >     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              >     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
              >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              >
              

  • Error in weblogic 7.0 SP2  Monitoring WebApplication servlets.

    Hi,
    I am facing an error screen at WebApplication Monitoring section. it is showing error at monitoring table.
    please find error bellow:-(.
    Error :
    [Lweblogic.management.WebLogicObjectName;
    java.lang.reflect.InvocationTargetException: java.lang.ClassCastException: [Lweblogic.management.WebLogicObjectName;
         at $Proxy102.getServlets(Unknown Source)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.console.info.ReflectingAttribute.doGet(ReflectingAttribute.java:110)
         at weblogic.management.console.tags.table.AttributeCellPrinter.doCellContents(AttributeCellPrinter.java:57)
         at weblogic.management.console.tags.table.TableTag.printTable(TableTag.java:553)
         at weblogic.management.console.tags.table.TableTag.doEndTag(TableTag.java:342)
         at weblogic.management.console.webapp._domain.__webappcomponentruntimetable._jspService(__webappcomponentruntimetable.java:357)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
         at weblogic.servlet.internal.RequestDispatcherImpl$ForwardAction.run(RequestDispatcherImpl.java:342)
         at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:252)
         at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:132)
         at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
         at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5445)
         at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    Console Release Build7.0.2.0Server Release Build7.0.2.0Server BuildWebLogic Temporary Patch for CR105443 07/15/2003 12:30:49All Server Product VersionsWebLogic Temporary Patch for CR105443 07/15/2003 12:30:49 WebLogic Temporary Patch for CR099307 04/21/2003 10:54:50 WebLogic Server 7.0 SP2 Sun Jan 26 23:09:32 PST 2003 234192
    please help me to rectify the above error message.
    Thanks in Advance:)

              Modify the <cewolf:param> tag.
              <cewolf:chart id="confchart" title="Reports" type="bar3d" yaxislabel="Time"> <cewolf:data>
              <cewolf:producer id="report"> <cewolf:param name="type" value="all" > </cewolf:param>
              </cewolf:producer> </cewolf:data> </cewolf:chart>
              "Balakrishnan" <[email protected]> wrote:
              >
              >We are using cewolf charting library in weblogic 7.0. The charting library
              >is implemented
              >as custom jsp tag library module.
              >
              >However, when the use the tag for displaying the chart, weblogic is producing
              >this compiler error.
              >
              >/reports/reportsView.jsp(108): no corresponding open tag for tag extension
              >close:
              >//[ null; Line: 108]
              >
              >Here's the corresponding source of the jsp file:
              >
              > <cewolf:chart id="confchart" title="Reports" type="bar3d" yaxislabel="Time">
              > <cewolf:data>
              > <cewolf:producer id="report">
              > <cewolf:param name="type" value="all" /> (<-- Error occurs
              >here.
              >Line no: 108)
              > </cewolf:producer>
              > </cewolf:data>
              > </cewolf:chart>
              >
              >I've also checked the corresponding tld file and it is in place.
              >
              >The same code without any modifications is working fine in tomcat. Can
              >you please
              >let me know what needs to be corrected to make this work?
              

  • Error deploying Struts 1.1 on weblogic 6.1 sp2

    Hello,
    I am trying to deploy the struts-documentation.war that comes with struts 1.1
    on weblogic 6.1 sp2.
    I already have xerces.jar , xalan.jar and crimson.jar in WEB-INF/lib. I have also
    tired giving the files in the weblogic classpath.
    It does not deploy the application and it gives the following error:
    ####<Jul 13, 2004 2:26:44 PM IST> <Debug> <HTTP> <phinwo-w00206>
    <myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
    <system> <> <101158> <Exception thrown while loading struts-documentation:
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1>
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1
    at java.lang.String.substring(String.java:1525)
    at
    weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
    at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
    at
    weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
    at
    weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
    at
    weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
    at
    weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
    at
    weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
    at
    weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
    at
    weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at
    weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy29.addWebDeployment(Unknown Source)
    at
    weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
    at
    weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
    at
    weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy64.addTarget(Unknown Source)
    at
    weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
    at
    weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
    at
    weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
    at
    weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at
    weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy5.update(Unknown Source)
    at
    weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
    at
    weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at
    weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
    at
    weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at
    weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ####<Jul 13, 2004 2:26:44 PM IST> <Error> <J2EE> <phinwo-w00206>
    <myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
    <system> <> <160001> <Error deploying application struts-documentation:
    Could not load struts-documentation>
    ####<Jul 13, 2004 2:26:44 PM IST> <Error> <Management> <phinwo-w00206>
    <myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
    <system> <> <141042> <Error deploying application
    .\config\mydomain\applications\struts-documentation.war:
    java.lang.reflect.UndeclaredThrowableException>
    Any help in this regard will be highly appreciated.

    I'm also running Weblogic 6.1 SP2 and getting a very similar error during startup when trying to deploy JSTL (Apache's version 1.0.6 from here http://jakarta.apache.org/taglibs/) in an exploded application that starts up fine if I remove the JSTL jars from WEB-INF/lib.
    The exact stack trace in my case is this:
    java.lang.StringIndexOutOfBoundsException: String index out of range: -1
    at java.lang.String.substring(String.java:1525)
    at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
    at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
    at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
    at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:234)
    at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3407)
    at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
    at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
    at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy31.addWebDeployment(Unknown Source)
    at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy30.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy41.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)

  • Problem with Weblogic 8.1 Sp2 and Struts 1.1 + tiles

    I am using weblogic 8.1 sp2 with struts and tiles.
    I am getting the follwing error in my web pages, which is not consistent.
    The error stack trace is as below.
    [java] <Oct 6, 2005 12:23:53 PM GMT+05:30> <Error> <HTTP> <BEA-101309> <[ServletContext(id=3212
    195,name=awmweb,context-path=/awm)] could not deserialize the context attribute "org.apache.struts.
    iles.DEFINITIONS_FACTORY"
    [java] java.io.NotSerializableException: com.awm.awm.controllers.layout.BaseLayoutControll
    r
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    [java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    [java] at java.util.HashMap.writeObject(HashMap.java:978)
    [java] at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
    25)
    [java] at java.lang.reflect.Method.invoke(Method.java:324)
    [java] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    [java] at java.util.HashMap.writeObject(HashMap.java:978)
    [java] at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
    25)
    [java] at java.lang.reflect.Method.invoke(Method.java:324)
    [java] at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    [java] at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    [java] at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    [java] at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    [java] at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    [java] at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.
    ava:136)
    [java] at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
    [java] at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
    [java] at weblogic.servlet.internal.WebAppServletContext.getAttribute(WebAppServletContext.
    ava:619)
    [java] at org.apache.struts.tiles.TilesUtilStrutsModulesImpl.getDefinitionsFactory(TilesUti
    StrutsModulesImpl.java:145)
    [java] at org.apache.struts.tiles.TilesUtilStrutsModulesImpl.getDefinitionsFactory(TilesUti
    StrutsModulesImpl.java:133)
    [java] at org.apache.struts.tiles.TilesUtil.getDefinitionsFactory(TilesUtil.java:186)
    [java] at org.apache.struts.tiles.TilesUtil.getDefinition(TilesUtil.java:224)
    [java] at org.apache.struts.taglib.tiles.util.TagUtils.getComponentDefinition(TagUtils.java
    339)
    [java] at org.apache.struts.taglib.tiles.DefinitionTag.doStartTag(DefinitionTag.java:261)
    [java] at com.awm.awm.jsp._errors.__500_45_servererror._jspService(__500_45_servererro
    .java:208)
    [java] at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
    [java] at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStub
    mpl.java:971)
    [java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
    [java] at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
    [java] at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.filters.AWMBaseFilter.doFilter(AWMBaseFilter.java:97)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.quote.QuoteUsageFilter.doFilter(QuoteUsageFilter.java:70)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.filters.AWMBaseFilter.doFilter(AWMBaseFilter.java:97)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.filters.FrontFilter.doFilter(FrontFilter.java:160)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.filters.JTidyFilter.doFilter(JTidyFilter.java:152)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at com.awm.awm.filters.PerfLogFilter.doFilter(PerfLogFilter.java:211)
    [java] at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    [java] at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.jav
    :305)
    [java] at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:
    23)
    [java] at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletConte
    t.java:3908)
    [java] at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext
    java:3683)
    [java] at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [java] >
    Can any one comment on why I am getting this error? Is it related to the hot deployment issue? Please comment.
    Thanks in advance,
    K

    Hi,
    Generally this type of exception raised by a class or the serialization runtime when a class may not be serialized.The argument should be the name of the class.
    You might be forgot to implement the serializable interface for the class in struts frame work.
    check it properly.
    Regards
    Anilkumar kari

  • How to use call back and user session id based conversation with web service in weblogic 6.1 sp2 ?????????

    Hi, every one:
    Here's my question of my day - >>>
    I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K, and
    I got a web service up and running called Price Update web service through
    which user can pick up a price and push a deal to another web service
    called: deal service, the deal service will take the user deal and book the
    deal ( sending a JMS message to a Queue, a MD will pick up and do the work,
    then send the confirmation to another JMS Queue ), then the confirmation
    will be picked up and sent to another web service , called: User Deal
    Confirmation Service, here's the question:
    1. Since the client application is only allowed to see its own confirmed
    deals, how I can make the confirmed deal encrypted based on a server
    generated key or the session id that client application provides
    2. Now, I have 3 webservices: update, deal and confirm, each of them has a
    client.jar file available - from the client application point of view, do I
    need all these 3 client.jar, or I just need one of them ?????
    3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
    beta, you can do this easily in the workshop, in the second question above,
    I think I need some how relate the confirmation to the client conversation
    id ??
    thanks a lot for the input, have a nice day.
    regards,
    mark.

    Any comments ?
    mark
    "markhu" <[email protected]> wrote in message
    news:[email protected]..
    Hi, every one:
    Here's my question of my day - >>>
    I am using weblogic 6.1 SP2 right now - running on Unix and Win 2K,and
    I got a web service up and running called Price Update web service through
    which user can pick up a price and push a deal to another web service
    called: deal service, the deal service will take the user deal and bookthe
    deal ( sending a JMS message to a Queue, a MD will pick up and do thework,
    then send the confirmation to another JMS Queue ), then the confirmation
    will be picked up and sent to another web service , called: User Deal
    Confirmation Service, here's the question:
    1. Since the client application is only allowed to see its own confirmed
    deals, how I can make the confirmed deal encrypted based on a server
    generated key or the session id that client application provides
    2. Now, I have 3 webservices: update, deal and confirm, each of them has a
    client.jar file available - from the client application point of view, doI
    need all these 3 client.jar, or I just need one of them ?????
    3. How can I use web service call back in wls 6.1 sp2 ?????? - in the 7.0
    beta, you can do this easily in the workshop, in the second questionabove,
    I think I need some how relate the confirmation to the client conversation
    id ??
    thanks a lot for the input, have a nice day.
    regards,
    mark.

  • Wls 8.1 sp2: weblogic.jspc complains about struts-html tags

              Hi,
              I am trying to compile jsps with weblogic.jspc, which use struts' html tags. However,
              the compilation fails with the following message:
              [java] Translation of /views/viewPageBody.jsp failed: (line 3): Error in using
              tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
              has no setter method corresponding to TLD declared attribute 'server', (JSP 1.1
              spec, 5.4.1)
              I opened the BaseTag class from the struts jar and found the setter exists for
              the attribute 'server' of html tld. So does the property 'server'. The property
              'server' is a string and the parameter in the setter is a string. I read about
              the jspc errors in wls 8.1 about the setter parameter being of different type
              than the property. However, that is not the case here. I tried using both Sun's
              and BEA's jdk. None of them help. Btw, there is another attribute mentioned in
              the html tld, which is 'target'. The compiler doesn't complain yet about this.:(
              Also, I happened to compile other apps which have struts logic tags.
              My environment:
              OS: Win2k sp3
              WLS: 8.1 sp2
              JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
              Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
              without any mention supports only ant 1.5.3.)
              I would appreciate any help in this regard.
              Thanks,
              Abbas
              

              What version of Struts are you trying to use?
              Are you certain you're not encountering a different instance of that class in
              an unexpected location in your classpath?
              "Abbas" <[email protected]> wrote:
              >
              >Hi,
              >I am trying to compile jsps with weblogic.jspc, which use struts' html
              >tags. However,
              >the compilation fails with the following message:
              >
              >[java] Translation of /views/viewPageBody.jsp failed: (line 3): Error
              >in using
              >tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
              >has no setter method corresponding to TLD declared attribute 'server',
              >(JSP 1.1
              >spec, 5.4.1)
              >
              >I opened the BaseTag class from the struts jar and found the setter exists
              >for
              >the attribute 'server' of html tld. So does the property 'server'. The
              >property
              >'server' is a string and the parameter in the setter is a string. I read
              >about
              >the jspc errors in wls 8.1 about the setter parameter being of different
              >type
              >than the property. However, that is not the case here. I tried using
              >both Sun's
              >and BEA's jdk. None of them help. Btw, there is another attribute mentioned
              >in
              >the html tld, which is 'target'. The compiler doesn't complain yet about
              >this.:(
              >Also, I happened to compile other apps which have struts logic tags.
              >
              >
              >My environment:
              >OS: Win2k sp3
              >WLS: 8.1 sp2
              >JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
              >Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
              >without any mention supports only ant 1.5.3.)
              >
              >I would appreciate any help in this regard.
              >
              >Thanks,
              >
              >Abbas
              

  • Double submission problem in J2EE application under Weblogic 8.1 SP2 server

    Hi,
    We are facing double submission problem in our J2EE application which is running under Weblogic 8.1 SP2 and for the same we already implemented or added the below preventive solutions.
    1. We disable the SUBMIT button once the user clicks it.
    2. We preventated pressing 'F5' button and clicking 'Refresh' button in the browser.
    3. Also we tried to prevent by declaring the idempotent is 'true' under weblogic-ejb-jar.xml as below.
    <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempotent>
    So please somebody help us on this issue like how to prevent in some other way.
    Regards,
    Dinesh.

    I have no idea why you would think changing your EJB configuration would have anything to do with preventing double submission at your servlet layer.
    One technique I've seen for preventing double submission was first used in the Struts framework several years ago. When a page is "prepared" for display, a token value is created and stored in the session. The page is displayed with a hidden field containing that value. When the page is submitted, the value of the hidden field is compared with the value stored in the session. If they're not equal, the submission is ignored.

  • Deployment problem - Weblogic 8.1 SP2

    I've created a simple, one-page project to test deployment to Weblogic 8.1 SP2.
    I followed the instructions in http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/weblogicdeploy.html except for the database related parts (my project does not access a database).
    On startup, Weblogic fails to proload the FacesServlet for my app:
    ####<May 18, 2006 2:45:42 PM PDT> <Error> <HTTP> <hqp-vs-hypdev01> <ProtivitiServer> <main> <<WLS Kernel>> <> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "HelloTest".
    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)
    and when I try to access my Page1.jsp, Weblogic throws another (related?) exception:
    <BEA-101017> <[ServletContext(id=1830320,name=HelloTest,context-path=/HelloTest)] Root cause of ServletException.
    java.lang.NullPointerException
         at javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
         at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:993)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:869)
    Any help with this? Do I need Weblogic 8.1 SP4?

    hi,
    0. Check WLS classpath in startWeblogic.{cmd.sh} for JSF jars
    1. Check your web.xml with section conserning FacesServlet
    it shoul look like:
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    2. Try to find any other servlet and look at its <load-on-startup> section.
    Final Java Servlet Specification Ver. 2.4 page 127:
    " The load-on-startup element indicates that this
    servlet should be loaded (instantiated and have
    its init() called) on the startup of the web
    application. The optional contents of these
    element must be an integer indicating the order in
    which the servlet should be loaded. If the value
    is a negative integer, or the element is not
    present, the container is free to load the servlet
    whenever it chooses. If the value is a positive
    integer or 0, the container must load and
    initialize the servlet as the application is
    deployed. The container must guarantee that
    servlets marked with lower integers are loaded
    before servlets marked with higher integers. The
    container may choose the order of loading of
    servlets with the same load-on-start-up value "
    Kind regards,
    Alex
    Message was edited by:
    AKlimenko

  • Using JSTL on Weblogic 8.1 SP2

              I'm trying to create a web app running on Weblogic 8.1 SP2 that uses JSTL tags.
              I've downloaded the Apache 1.0.5 Reference Implementation of the JSTL 1.0 spec,
              but I can't get the sample web-app (standard-examples.war) to work correctly.
              When I go to the "General Purpose Tag Examples" and try to view the Out example
              JSP, I get a large exception saying that java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
              (full stack trace at bottom). This also happens when I try to view the JSP source
              and pretty much any other example. I found that the German example in "I18N &
              Formatting" works, but running the Italian example gives a new exception:
              Parsing of JSP File '/format/ItalianLocale.jsp' failed:
              /format/ItalianLocale.jsp(12): for tag 'message', property 'bundle' of tag handler
              class 'org.apache.taglibs.standard.tag.rt.fmt.MessageTag', the value must be a
              runtime expression "<%=...%>", since we cannot do an automatic conversion from
              "${itBundle}" to type 'javax.servlet.jsp.jstl.fmt.LocalizationContext' and there
              is no custom property editor for that type
              probably occurred due to an error in /format/ItalianLocale.jsp line 12:
              <fmt:message key="greetingMorning" bundle="${itBundle}"/>
              I can, however, get this to work on Tomcat 5.0. Has any else had this problem?
              Is there something that I'm doing incorrectly?
              Thanks in advance.
              -Kelvin
              ===========================================================
              java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
                   at java.lang.Class.getDeclaredMethods0(Native Method)
                   at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)
                   at java.lang.Class.getDeclaredMethods(Class.java:1114)
                   at java.beans.Introspector$1.run(Introspector.java:1103)
                   at java.security.AccessController.doPrivileged(Native Method)
                   at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1101)
                   at java.beans.Introspector.getTargetMethodInfo(Introspector.java:966)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:370)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:207)
                   at java.beans.Introspector.(Introspector.java:351)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:207)
                   at java.beans.Introspector.getBeanInfo(Introspector.java:193)
                   at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
                   at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
                   at weblogic.servlet.jsp.StandardTagLib.(StandardTagLib.java:292)
                   at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
                   at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
                   at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
                   at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
                   at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
                   at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
                   at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
                   at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
                   at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
                   at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
                   at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
                   at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
                   at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:367)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:223)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:172)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:518)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:362)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
                   at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              

              I'm having the same problem, did you find a solution?
              "Kelvin" <[email protected]> wrote:
              >
              >I'm trying to create a web app running on Weblogic 8.1 SP2 that uses
              >JSTL tags.
              > I've downloaded the Apache 1.0.5 Reference Implementation of the JSTL
              >1.0 spec,
              >but I can't get the sample web-app (standard-examples.war) to work correctly.
              >
              >When I go to the "General Purpose Tag Examples" and try to view the Out
              >example
              >JSP, I get a large exception saying that java.lang.NoClassDefFoundError:
              >javax/servlet/jsp/el/ELException
              >(full stack trace at bottom). This also happens when I try to view the
              >JSP source
              >and pretty much any other example. I found that the German example in
              >"I18N &
              >Formatting" works, but running the Italian example gives a new exception:
              >
              >Parsing of JSP File '/format/ItalianLocale.jsp' failed:
              >--------------------------------------------------------------------------------
              > /format/ItalianLocale.jsp(12): for tag 'message', property 'bundle'
              >of tag handler
              >class 'org.apache.taglibs.standard.tag.rt.fmt.MessageTag', the value
              >must be a
              >runtime expression "<%=...%>", since we cannot do an automatic conversion
              >from
              >"${itBundle}" to type 'javax.servlet.jsp.jstl.fmt.LocalizationContext'
              >and there
              >is no custom property editor for that type
              >probably occurred due to an error in /format/ItalianLocale.jsp line 12:
              ><fmt:message key="greetingMorning" bundle="${itBundle}"/>
              >
              >
              >I can, however, get this to work on Tomcat 5.0. Has any else had this
              >problem?
              > Is there something that I'm doing incorrectly?
              >
              >
              >Thanks in advance.
              >-Kelvin
              >
              >===========================================================
              >java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
              >     at java.lang.Class.getDeclaredMethods0(Native Method)
              >     at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)
              >     at java.lang.Class.getDeclaredMethods(Class.java:1114)
              >     at java.beans.Introspector$1.run(Introspector.java:1103)
              >     at java.security.AccessController.doPrivileged(Native Method)
              >     at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1101)
              >     at java.beans.Introspector.getTargetMethodInfo(Introspector.java:966)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:370)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:207)
              >     at java.beans.Introspector.(Introspector.java:351)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:207)
              >     at java.beans.Introspector.getBeanInfo(Introspector.java:193)
              >     at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
              >     at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
              >     at weblogic.servlet.jsp.StandardTagLib.(StandardTagLib.java:292)
              >     at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
              >     at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
              >     at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
              >     at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
              >     at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
              >     at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
              >     at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
              >     at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
              >     at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
              >     at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
              >     at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
              >     at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
              >     at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
              >     at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:367)
              >     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:223)
              >     at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:172)
              >     at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:518)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:362)
              >     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
              >     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
              >     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              >     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              >     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
              >     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              

  • Weblogic 6.0 sp2: War deployment not working !!

    Hi,
    I'm using weblogic 6.0 sp2, and it seems as though the war deployment is not
    working. My war consists of jsps, images, and under the WEB-INF/classes
    directory, Struts classes (i.e. Form and Action classes). When I try to run
    a jsp, i get the following error :
    <Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
    <[WebAppServletContext(4655498,ati
    nera)] Root cause of ServletException
    javax.servlet.jsp.JspException: Exception creating bean of class
    com.atinera.log
    in.web.LoginForm: java.lang.ClassNotFoundException:
    com.atinera.login.web.LoginF
    orm
    But if you look in the war, that class is in there.
    What gives ?
    Thanks,
    Jamie

    That's right - ActionServlet does Class.forName(actionClass) to load action
    class, and this uses ClassLoader which loaded the current class (ActionServlet)
    ClassLoaders always delegate to their parent before attempting to load
    the class themselves, so it wasn't working until you moved struts.jar to your
    WEB-INF/lib.
    BTW, Struts doc mentions this problem:
    lib/struts.jar - This JAR file contains all of the Java classes included
    in Struts. It should be copied into the WEB-INF/lib directory of your web
    application. WARNING - If you are going to be hosting multiple Struts based
    applications on the same servlet container, you will be tempted to place the
    struts.jar file into the shared repository supported by your container. Be
    advised that this will like cause you to encounter ClassNotFoundException
    problems unless all of your application classes are stored in the shared
    repository.
    Jamie Tsao <[email protected]> wrote:
    So I found the solution to this problem, but it doesn't really make sense to
    me.
    I originally had struts.jar outside of the WAR file, but in my CLASSPATH.
    Weblogic was able to load Strut's ActionServlet (controller), but when the
    ActionServlet was looking for the LoginForm (which was inside the WAR), it
    couldn't find it.
    I solved the problem by putting struts.jar inside the WAR (under
    WEB-INF/lib) instead that other directory. Now it works cause apparently
    ActionServlet is now in the same classloader as LoginForm, the classloader
    which loaded the WAR.
    I'm confused because original way should have worked since the classloader
    that loaded struts.jar from outside the war is the parent classloader for
    the classloader that loaded the WAR. did that make any sense ?
    anyone know why ?
    thanks,
    jamie
    "Jamie Tsao" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I'm using weblogic 6.0 sp2, and it seems as though the war deployment isnot
    working. My war consists of jsps, images, and under the WEB-INF/classes
    directory, Struts classes (i.e. Form and Action classes). When I try torun
    a jsp, i get the following error :
    <Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
    <[WebAppServletContext(4655498,ati
    nera)] Root cause of ServletException
    javax.servlet.jsp.JspException: Exception creating bean of class
    com.atinera.log
    in.web.LoginForm: java.lang.ClassNotFoundException:
    com.atinera.login.web.LoginF
    orm
    But if you look in the war, that class is in there.
    What gives ?
    Thanks,
    Jamie
    Dimitri

  • Servlet Session Monitoring via MBeans turns up no MBeans

    Hi,
    I discovered more about why I'm not seeing any Servlet Session Runtime
    MBeans when I enable session monitoring. It looks like each time my
    managed server creates a new session, two errors get written to my
    WebLogic log:
    "####<Sep 22, 2002 6:46:43 PM EDT> <Warning> <Dispatcher>
    <chile.iso-ne.com> <adminserver> <ExecuteThread: '7' for queue:
    '__weblogic_admin_rmi_queue'> <> <> <000000> <RuntimeException thrown
    by rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid:
    '7074298665992588400S:10.145.220.82:[7001,7001,7002,7002,7001,7002,-1]:smsdomain:adminserver',
    oid: '267', implementation:
    'weblogic.management.internal.AdminMBeanHomeImpl@3c7b65''>
    weblogic.management.NoAccessRuntimeException: User guest does not have
    access permission on weblogic.admin.mbean.MBeanHome
    at weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1637)
    and
    "####<Sep 22, 2002 6:46:43 PM EDT> <Error> <HTTP Session>
    <chile.iso-ne.com> <webuiserver> <ExecuteThread: '0' for queue:
    'default'> <> <> <100032> <Error creating servlet session runtime>
    weblogic.management.NoAccessRuntimeException: User guest does not have
    access permission on weblogic.admin.mbean.MBeanHome
    at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy7.getMBeanServer(Unknown Source)
    at weblogic.management.internal.MBeanHomeImpl.isAdminHome(MBeanHomeImpl.java:93)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:118)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:590)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:568)
    at weblogic.servlet.internal.session.SessionData$1.run(SessionData.java:185)
    at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
    at weblogic.servlet.internal.session.SessionData.getRuntimeMBean(SessionData.java:179)
    at weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:166)
    Looks like the managed server is making a request of the admin server
    and propagating the "guest" principal instead of "system".
    These principal propagation errors from managed-to-admin seem to
    happen all over the place with different MBeans, and get patched one
    place at a time in various BEA service packs. For instance, there's
    another issue with accessing the XML Entity Cache from a managed
    server, and I'm sure I've read about others. Isn't there a way to
    make sure these errors no longer occur with any MBean requests from
    the managed server?
    Jim

    Add
    acl.access.weblogic.admin.mbean.MBeanHome=guest
    in the filerealm.properties file.
    Jim Doyle wrote:
    Hi,
    I discovered more about why I'm not seeing any Servlet Session Runtime
    MBeans when I enable session monitoring. It looks like each time my
    managed server creates a new session, two errors get written to my
    WebLogic log:
    "####<Sep 22, 2002 6:46:43 PM EDT> <Warning> <Dispatcher>
    <chile.iso-ne.com> <adminserver> <ExecuteThread: '7' for queue:
    '__weblogic_admin_rmi_queue'> <> <> <000000> <RuntimeException thrown
    by rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid:
    '7074298665992588400S:10.145.220.82:[7001,7001,7002,7002,7001,7002,-1]:smsdomain:adminserver',
    oid: '267', implementation:
    'weblogic.management.internal.AdminMBeanHomeImpl@3c7b65''>
    weblogic.management.NoAccessRuntimeException: User guest does not have
    access permission on weblogic.admin.mbean.MBeanHome
    at weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1637)
    and
    "####<Sep 22, 2002 6:46:43 PM EDT> <Error> <HTTP Session>
    <chile.iso-ne.com> <webuiserver> <ExecuteThread: '0' for queue:
    'default'> <> <> <100032> <Error creating servlet session runtime>
    weblogic.management.NoAccessRuntimeException: User guest does not have
    access permission on weblogic.admin.mbean.MBeanHome
    at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy7.getMBeanServer(Unknown Source)
    at weblogic.management.internal.MBeanHomeImpl.isAdminHome(MBeanHomeImpl.java:93)
    at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:118)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:590)
    at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:568)
    at weblogic.servlet.internal.session.SessionData$1.run(SessionData.java:185)
    at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
    at weblogic.servlet.internal.session.SessionData.getRuntimeMBean(SessionData.java:179)
    at weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:166)
    Looks like the managed server is making a request of the admin server
    and propagating the "guest" principal instead of "system".
    These principal propagation errors from managed-to-admin seem to
    happen all over the place with different MBeans, and get patched one
    place at a time in various BEA service packs. For instance, there's
    another issue with accessing the XML Entity Cache from a managed
    server, and I'm sure I've read about others. Isn't there a way to
    make sure these errors no longer occur with any MBean requests from
    the managed server?
    Jim--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • WebLogic 6.1 SP2 stateful EJB handle serialization problem

    I try to serialize and later deserialize the handle of a stateful
    session bean in WebLogic 6.1 SP2. This works on the client, but not on
    the server. In WebLogic 6.1 SP1, it worked on both server and client.
    The test code:
    try {
    InitialContext context = new InitialContext();
    InfSessionHome sessionHome = (InfSessionHome)
    InfEJBUtil.getInfEJBHome
    (context, InfJNDINames.INFSESSION_EJBHOME,
    InfSessionHome.class);
    infSession1 = sessionHome.create();
    // serialize
    ObjectOutputStream objector = new ObjectOutputStream(byteStream);
    objector.writeObject(infSession1.getHandle());
    objector.flush();
    objector.close();
    byte[] ejbKeyBytes = byteStream.toByteArray();
    // deserialize
    ByteArrayInputStream byteInStream = new
    ByteArrayInputStream(ejbKeyBytes);
    ObjectInputStream objStream = new ObjectInputStream(byteInStream);
    Handle ejbHandle = (Handle) objStream.readObject();
    objStream.close();
    InfSession infSession2 = (InfSession) ejbHandle.getEJBObject();
    if (!infSession2.equals(infSession1)) {
    throw new IllegalStateException("not equal: " + infSession2);
    } catch (Exception e) {
    e.printStackTrace();
    I get the following stack trace in the readObject() call:
    java.io.InvalidClassException:
    weblogic.rmi.internal.LocalServerRefMissing no-arg constructor for
    class
    at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1221)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263)
    at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
    at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:73)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2214)
    at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
    at weblogic.ejb20.internal.HandleImpl.readExternal(HandleImpl.java:89)
    at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
    I suppose that WebLogic uses a different handle on the server
    (LocalServerRef class, handle local to it's EJB) than on the client.
    I took the routine from Apache SOAP 2.2 StatefulEJBProvider. So I
    suppose that more people are running into the same problem.
    Does anybody know of a workaround?
    Tom

    Just a small addition/clarification to what Cameron said on serialization.
    - The no argument constructor is required in the first non-serializable class in the object hierarchy for de-serialization process. If your class extends form Object class(which has a no arg constructor), you need not have a no-arg constructor. refere to http://64.49.216.133/faq/view.jsp?EID=251942 for more details.
    - Also I suggest using the api
    isIdentical(...)
    instead of equals method in the code if you are trying to establish whether the two objects represent the same EJBObject or not
    - Rajeev
    Cameron Purdy <[email protected]> wrote in message news:[email protected]...
    A no-argument constructor is required for a class to be deserialized. It
    sounds like a BEA bug from the stack trace, but make sure you don't have
    something extra that you are serializing on something of yours that should
    be transient. (It's hard to imagine how, but you never know ...)
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Tom Gerber" <[email protected]> wrote in message
    news:[email protected]...
    I try to serialize and later deserialize the handle of a stateful
    session bean in WebLogic 6.1 SP2. This works on the client, but not on
    the server. In WebLogic 6.1 SP1, it worked on both server and client.
    The test code:
    try {
    InitialContext context = new InitialContext();
    InfSessionHome sessionHome = (InfSessionHome)
    InfEJBUtil.getInfEJBHome
    (context, InfJNDINames.INFSESSION_EJBHOME,
    InfSessionHome.class);
    infSession1 = sessionHome.create();
    // serialize
    ObjectOutputStream objector = new ObjectOutputStream(byteStream);
    objector.writeObject(infSession1.getHandle());
    objector.flush();
    objector.close();
    byte[] ejbKeyBytes = byteStream.toByteArray();
    // deserialize
    ByteArrayInputStream byteInStream = new
    ByteArrayInputStream(ejbKeyBytes);
    ObjectInputStream objStream = new ObjectInputStream(byteInStream);
    Handle ejbHandle = (Handle) objStream.readObject();
    objStream.close();
    InfSession infSession2 = (InfSession) ejbHandle.getEJBObject();
    if (!infSession2.equals(infSession1)) {
    throw new IllegalStateException("not equal: " + infSession2);
    } catch (Exception e) {
    e.printStackTrace();
    I get the following stack trace in the readObject() call:
    java.io.InvalidClassException:
    weblogic.rmi.internal.LocalServerRefMissing no-arg constructor for
    class
    atjava.io.ObjectInputStream.inputObject(ObjectInputStream.java:1221)
    atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    atjava.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263)
    atjava.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519)
    at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:73)
    at java.lang.reflect.Method.invoke(Native Method)
    atjava.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2214)
    atjava.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411)
    atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
    atweblogic.ejb20.internal.HandleImpl.readExternal(HandleImpl.java:89)
    atjava.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
    atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
    atjava.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
    I suppose that WebLogic uses a different handle on the server
    (LocalServerRef class, handle local to it's EJB) than on the client.
    I took the routine from Apache SOAP 2.2 StatefulEJBProvider. So I
    suppose that more people are running into the same problem.
    Does anybody know of a workaround?
    Tom
    [att1.html]

  • JSF and weblogic 8.1 sp2??  Please help!

    Hello All -
    We are part of a small team here in SF at a biotech company... they have given us the green light to use JSF on a small project.
    Only problem is that we must deploy to Weblogic 8.1 SP2 & I can't get JSF to work on Weblogic 8.1 SP2.
    I get strange errors -- an inability to control navigation. The simple "hello world" app that comes with the Manning book "Javaserver faces in Action" does not work on WL 8.1 SP2. It does however work on Tomcat.
    I have even written a hack servlet that starts the listener manually that is needed for JSF to work. (http://forum.java.sun.com/thread.jspa?threadID=499690&start=15&tstart=30)
    Any ideas on this? We are getting desperate with a deadline looming Thursday. Want to make this work & not have to go back to Struts.
    One blog I saw said that what is needed is a Weblogic patch. Anyone know anything about this? (http://jroller.com/page/RickHigh/20040929)
    Thank you-
    Matt

    I'm trying to get a JSF web app I have working on
    tomcat ported to weblogic 8.1 sp2.
    When I deploy the webapp I get the following
    exception.
    I get the same exception when I try to deploy the JSF
    sample cardemo.war. (I've tried both JSF1.0 and JSF
    1.1, both result in the same error).Hello Kieth,
    Have you considered this content from the README:
    * Some web containers (Notably BEA WebLogic Server) don't follow the
    JSP 1.2 Spec rule of calling ServletContextListeners listeners defined
    in tld files in the META-INF directory of a jar. Running a faces
    webapp in such a container requires you to manually declare the
    ServletContextListener. The listener-class you need to specify is
    com.sun.faces.config.ConfigureListener
    Ed (EG Member)

  • Can't deploy a SINGLE bean in weblogic 6.1 SP2 w/o application reload

    Anyone know how to update a single bean in an application without
    redeploying the entire application?
    We have a project containing 101 beans (session and entity) and 372
    jsps which we are deploying on weblogic 6.1, SP2 as a single
    application. The project is deployed in an exploded directory format
    as follows:
    trader/
    META-INF/application.xml
    lib/
    third-party.jar
    third-party.jar (etc.)
    SessionBean.jar
    EntityBean.jar (etc.)
    trader/
    WEB-INF/web.xml
    META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
    jsp/html/gif's reside below this point.
    Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
    library dependencies through the use of the Class-Path entry.
    When we we try to update a single bean's implementation, the
    entire application reloads, which can take between 10 - 30 minutes.
    We have tried using the weblogic.deploy tool as well as undeploying
    and redeploying the bean from the console. In both cases, the
    entire application reloads.
    When we use weblogic.deploy, we've tried the following:
    weblogic.deploy
    -url T3://localhost:7001
    update weblogicpwd trader ~/trader/build/SessionBean.jar
    and
    weblogic.deploy
    -url T3://localhost:7001
    -component SessionBean:srvr1
    update weblogicpwd trader ~/trader/build/SessionBean.jar

    Anyone know how to update a single bean in an application without
    redeploying the entire application?
    We have a project containing 101 beans (session and entity) and 372
    jsps which we are deploying on weblogic 6.1, SP2 as a single
    application. The project is deployed in an exploded directory format
    as follows:
    trader/
    META-INF/application.xml
    lib/
    third-party.jar
    third-party.jar (etc.)
    SessionBean.jar
    EntityBean.jar (etc.)
    trader/
    WEB-INF/web.xml
    META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
    jsp/html/gif's reside below this point.
    Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
    library dependencies through the use of the Class-Path entry.
    When we we try to update a single bean's implementation, the
    entire application reloads, which can take between 10 - 30 minutes.
    We have tried using the weblogic.deploy tool as well as undeploying
    and redeploying the bean from the console. In both cases, the
    entire application reloads.
    When we use weblogic.deploy, we've tried the following:
    weblogic.deploy
    -url T3://localhost:7001
    update weblogicpwd trader ~/trader/build/SessionBean.jar
    and
    weblogic.deploy
    -url T3://localhost:7001
    -component SessionBean:srvr1
    update weblogicpwd trader ~/trader/build/SessionBean.jar

Maybe you are looking for