9 Replies Latest reply on Jun 11, 2007 1:19 PM by Ronald van Kuijk

    problem accessing jbpm-console (jbpm 3.2.1 GA) on weblogic s

    Naseem Khan Newbie

      Hi,

      I am using jBPM version 3.2.1 GA. I tried to deploy the jbpm-console.war on weblogic server 8.1.

      I managed to deploy it on weblogic. I resolved all the issues which are coming on weblogic like problem of antlr related to hibernate 3.1 and weblogic 8.1. Secondly I faced problem in query parser class that I changed to ASTQueryTranslatorFactory from ClassicQueryTransactionFactory as I am using hibernate verion 3.1.

      There is no error on the console at the time of deployment. weblogic console shows successful deployment message.

      Now when I tried to access the URL: http://localhost:7001/jbpm-console/search/tasks.html, I got exception on the browser.

      java.lang.ExceptionInInitializerError
      at org.jbpm.webapp.tag.jbpm.JbpmLibrary.(JbpmLibrary.java:59)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
      at java.lang.Class.newInstance0(Class.java:308)
      at java.lang.Class.newInstance(Class.java:261)
      ..........................
      Caused by: java.lang.NullPointerException
      at java.util.Hashtable.get(Hashtable.java:333)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:233)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
      at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
      at org.jbpm.webapp.tag.jbpm.renderer.ButtonRenderer.(Unknown Source)
      ... 46 more


      Please help. What could be the cause of this exception?


      Warm Regards,
      Naseem

        • 1. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
          Ronald van Kuijk Master

          isn't there more info in the logs? this is to little to be helpful

          • 2. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
            Naseem Khan Newbie

             

            "kukeltje" wrote:
            isn't there more info in the logs? this is to little to be helpful


            Exactly. I have gone through the source code of org.jbpm.webapp.tag.jbpm.JbpmLibrary as well. Line where it?s showing exception is written in a constructor of the JbpmLibrary class.

            I seems like exception has something to do with the SAXParser, but I am not very sure.

            Log file too is not very helpful.


            <[ServletContext(id=13797435,name=traveldesk,context-path=/traveldesk)] Root cause of ServletException.
            java.lang.Throwable
            at org.jbpm.webapp.tag.jbpm.JbpmLibrary.<init>(JbpmLibrary.java:59)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
            at java.lang.Class.newInstance0(Class.java:308)
            at java.lang.Class.newInstance(Class.java:261)
            at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.processLibraryClass(TagLibraryConfig.java:327)
            at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:166)
            at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:585)
            at weblogic.apache.xerces.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:710)
            at weblogic.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:647)
            at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:1937)
            at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:851)
            at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1008)
            at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1469)
            at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
            at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
            at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
            at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
            at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
            at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
            at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
            at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
            at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
            at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:394)
            at com.sun.facelets.FaceletViewHandler.initializeCompiler(FaceletViewHandler.java:275)
            at com.sun.facelets.FaceletViewHandler.initialize(FaceletViewHandler.java:161)
            at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:523)
            at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
            at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
            at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
            at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
            at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
            at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
            at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
            at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
            at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
            >




            • 3. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
              Martin Weiler Apprentice

              It looks like WL is using it's own SAXParser implementation instead of the apache one (which is bundled in <jboss-4.0.x>/lib/endorsed/xercesImpl.jar btw). Have a look at this docu, it's referring to an older WL version but I guess one of the ways to get around this issue described there should still work:
              http://ws.apache.org/soap/faq/faq-for-WL6.1beta.html

              • 4. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
                Naseem Khan Newbie

                 

                "mputz" wrote:
                It looks like WL is using it's own SAXParser implementation instead of the apache one (which is bundled in <jboss-4.0.x>/lib/endorsed/xercesImpl.jar btw). Have a look at this docu, it's referring to an older WL version but I guess one of the ways to get around this issue described there should still work:
                http://ws.apache.org/soap/faq/faq-for-WL6.1beta.html



                Hi,

                I have tried using my own parser for jbpm-console application. From weblogic console, I have created new XML Registry. My web application is also using the same newly created XML Registry, but no luck, same exception I get.

                It is really becoming nightmare for me.

                I did some more RnD on it. I have created a simple test.xhtml file. Its content is as below:

                <ui:composition
                 xmlns="http://www.w3.org/1999/xhtml"
                 xmlns:h="http://java.sun.com/jsf/html"
                 xmlns:f="http://java.sun.com/jsf/core"
                 xmlns:ui="http://java.sun.com/jsf/facelets"
                 xmlns:jbpm="http://jbpm.org/jsf"
                 template="../common/template.xhtml">
                 <b>hello World</b>
                </ui:composition>


                Now when I access the same from the browser:

                http://localhost:7001/jbpm-console/test.xhtml. I get output hello World in bold.

                But when I access the following url: http://localhost:7001/jbpm-console/test.jsf

                I get the same exception.



                • 5. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
                  Ronald van Kuijk Master

                  The difference between case one and two is no wonder.. in case one the jsf tags are not interpreted and it is just plain xhtml. In the second case the parser comes in.

                  I have no idea about the cause though. I (myself) quit trying to use weblogic at all because of many similar issues with hibernate, soap, ws, xml, .....

                  • 6. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
                    Edward Staub Expert

                    You need to include the jars you require in your ear file, and then tell WebLogic to use them in favor of its built-in jars.

                    Sorry, I (frustratingly) don't remember where you tell WebLogic to prefer the ear's jars over its own.

                    -Ed Staub

                    • 7. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
                      Edward Staub Expert

                      Found it!

                      In your WEB-INF for the console, insert this "weblogic.xml" file:

                      <?xml version='1.0' encoding='UTF-8'?>
                      <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                      
                      <container-descriptor>
                      <prefer-web-inf-classes>true</prefer-web-inf-classes>
                      </container-descriptor>
                      </weblogic-web-app>


                      -Ed Staub

                      • 8. Re: problem accessing jbpm-console (jbpm 3.2.1 GA) on weblog
                        Jean-Louis Rastapoc Newbie

                        Sorry I'm totally out topic but... Is 3.2.1 GA out? Where can I see if it is out or not? How can I get it?

                        I see the 3.2 GA release on SourceForge because I went there before looking here... If I didn't I would have been stuck with 3.1.4 since it appears to be the last usable release from here...