1 2 Previous Next 15 Replies Latest reply on Sep 22, 2008 11:56 AM by Peter Johnson

    Migrate from 4.2.2 GA to JBoss 5 CR2 fails

    Nicole Schweighardt Novice

      Hello,

      I have got some example-projects that run on 4.2.2 GA but not on JBoss 5 CR2.

      The first is a simple facelets project.
      Now I tried to migrate it to JBoss 5 CR2 but I get this error:

      11:28:09,656 ERROR [compiler] Missing Built-in Tag Libraries! Make sure they are included within the META-INF directory of Facelets' Jar
      11:28:09,734 ERROR [viewhandler] Error Rendering View[/pages/inputname.xhtml]
      java.lang.NullPointerException
       at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
       at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
       at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
       at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:510)
       at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:553)
       at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:109)
       at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
       at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
       at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
       at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
       at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
       at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
       at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:696)
       at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:667)
       at org.apache.jsp.index_jsp._jspService(index_jsp.java:59)
       at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
       at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
       at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
       at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
       at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91)
       at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:92)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:595)


      If I understand it in the right way the built-in libs from jboss have changed.Can you please tell me exactly which libs I need to include now?

      Another problem I have got with my sample jpa project. (runs on 4.2.2GA too)
      public @Stateless class ProductTestBean implements ProductTest {
      
       @PersistenceContext(unitName="firstJPA")
       EntityManager em;
      
       public static final String RemoteJNDIName = ProductTestBean.class.getSimpleName() + "/remote";
      
       public void createProduct() {
       Product product = new Product("EJB-Buch","24,99","Fachbuch", "Einsteigerbuch in EJB3");
       em.persist(product);
       }
      }


      @Entity
      public class Product {
      
       private Integer id;
       private String name;
       private String price;
       private String category;
       private String shortDescription;
      //... getters and setters
      
      



      public class TestClient {
      
       public static void main(String[] args) {
       Context context;
       try
       {
       context = new InitialContext();
      
       ProductTest beanRemote = (ProductTest)context.lookup(ProductTestBean.RemoteJNDIName);
       beanRemote.createProduct();
       } catch (NamingException e)
      ...
       {



      Following error occurs:
      11:42:37,281 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/C:/jboss-5.0.0.CR2/server/default/deploy/FirstJPA.jar/ state=Not Installed mode=Manual requiredState=Parse
      org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/jboss-5.0.0.CR2/server/default/deploy/FirstJPA.jar/
       at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
       at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
       at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
       at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
       at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
       at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
       at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
       at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
       at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
       at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
       at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
       at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
       at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
       ... 27 more
      Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
       at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
       at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
       at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
       at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
       ... 35 more
      11:42:37,312 WARN [HDScanner] Failed to process changes
      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      vfsfile:/C:/jboss-5.0.0.CR2/server/default/deploy/FirstJPA.jar/ -> org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
      
      
       at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)


      I have got some more projects that do not work anymore. Is it possible that something basic is wrong or missing?
      If you need some more code or logs please tell me.
      Any help would be great.
      Thanks,
      Nicole


        • 1. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
          Ales Justin Master

          Quick reply.

          In order to make facelets work,
          you need the release that includes my patch - it understands VFS.
          Check this forum for existing such issues,
          as they should include url to that release.

          For jpa issue.
          I think you need to provide full namespace in your persistence.xml file.
          Check any of our testsuite files for exact content.

          • 2. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
            jaikiran pai Master

            Not sure about the facelets error. But for the JPA related exception

            Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence


            You have to fix your persistence.xml. See this for details http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138438

            • 3. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
              Nicole Schweighardt Novice

              Hi,

              thanks for your answers.

              In the jpa-example I corrected the persistence.xml.

              Now I get a new error I had in another application too:

              javax.naming.NameNotFoundException: ProductTestBean not bound
               at org.jnp.server.NamingServer.getBinding(NamingServer.java:564)
               at org.jnp.server.NamingServer.getBinding(NamingServer.java:572)
               at org.jnp.server.NamingServer.getObject(NamingServer.java:578)
               at org.jnp.server.NamingServer.lookup(NamingServer.java:288)
               at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
               at sun.rmi.transport.Transport$1.run(Transport.java:153)
               at java.security.AccessController.doPrivileged(Native Method)
               at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
               at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
               at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
               at java.lang.Thread.run(Thread.java:595)
               at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
               at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
               at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
               at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
               at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
               at $Proxy0.lookup(Unknown Source)
               at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
               at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
               at javax.naming.InitialContext.lookup(InitialContext.java:351)
               at de.test.TestClient.main(TestClient.java:18)
              Exception in thread "main" java.lang.RuntimeException: javax.naming.NameNotFoundException: ProductTestBean not bound
               at de.test.TestClient.main(TestClient.java:23)
              Caused by: javax.naming.NameNotFoundException: ProductTestBean not bound
               at org.jnp.server.NamingServer.getBinding(NamingServer.java:564)
               at org.jnp.server.NamingServer.getBinding(NamingServer.java:572)
               at org.jnp.server.NamingServer.getObject(NamingServer.java:578)
               at org.jnp.server.NamingServer.lookup(NamingServer.java:288)
               at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
               at java.lang.reflect.Method.invoke(Method.java:585)
               at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
               at sun.rmi.transport.Transport$1.run(Transport.java:153)
               at java.security.AccessController.doPrivileged(Native Method)
               at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
               at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
               at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
               at java.lang.Thread.run(Thread.java:595)
               at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
               at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
               at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
               at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
               at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
               at $Proxy0.lookup(Unknown Source)
               at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
               at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
               at javax.naming.InitialContext.lookup(InitialContext.java:351)
               at de.test.TestClient.main(TestClient.java:18)


              The project is working in 4.2.2, so I think JNDI-Names are right.

              Facelets Issue: I do not really understand what you mean with "version with my patch"? Version from JBoss or built-in facelets-libs? I could not find an url in the forum.

              Thank you for other ideas.
              Nicole

              • 4. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                jaikiran pai Master

                For the JNDI issue, look at the jmx-console to see the jndi-name to which the bean is bound. Then use that jndi-name in your code for the lookup string. Follow the steps here to display the jndi tree http://wiki.jboss.org/wiki/DisplayTheJDNITreeWithTheJMXConsole

                • 5. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                  jaikiran pai Master

                   

                  "NSchweig" wrote:

                  Facelets Issue: I do not really understand what you mean with "version with my patch"? Version from JBoss or built-in facelets-libs? I could not find an url in the forum.




                  Ales is referring to the issue he fixed in facelets. See his blog http://blogs.jboss.com/blog/alesj/?permalink=JBoss5_CR1_SpringDeployer_and_VFS.txt for details. Here's the relevant part from that blog:

                  We first encountered this with Facelets while deploying Seam apps. So here is the fix:

                  https://facelets.dev.java.net/files/documents/3448/99102/facelets-1.1.15.B1.zip

                  https://facelets.dev.java.net/issues/show_bug.cgi?id=315


                  • 6. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                    Nicole Schweighardt Novice

                    HI,

                    I think the jndi issue solution was that jboss as could not start jndi-service on 1099; firefox blocked this port.

                    I know it from 4.2.2 that I could put for example 1095 in <in jboss-service.xml.

                    <attribute name="BindAddress">${jboss.bind.address}</attribute>
                     <!-- The port of the RMI naming service, 0 == anonymous -->
                     <attribute name="RmiPort">1095</attribute>
                    


                    But I do not know if it is a good solution?


                    • 7. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                      Nicole Schweighardt Novice

                      ... oh and my new exception now is:

                      Exception in thread "main" java.lang.ClassCastException: javax.naming.Reference
                       at de.test.TestClient.main(TestClient.java:18)


                      TestClient.java Line 18:

                      ProductTest beanRemote = (ProductTest)context.lookup(ProductTestBean.RemoteJNDIName);


                      Any ideas?

                      • 8. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                        Nicole Schweighardt Novice

                        Thanks for the facelets-issue-solution, it works now!

                        • 9. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                          jaikiran pai Master

                           

                          "NSchweig" wrote:
                          ... oh and my new exception now is:
                          Exception in thread "main" java.lang.ClassCastException: javax.naming.Reference
                           at de.test.TestClient.main(TestClient.java:18)


                          TestClient.java Line 18:

                          ProductTest beanRemote = (ProductTest)context.lookup(ProductTestBean.RemoteJNDIName);


                          Any ideas?


                          See my previous reply about using the jmx-console to figure out the jndi name. If you could not find the jndi name of the bean then post the jndi tree output here.

                          • 10. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                            Nicole Schweighardt Novice

                            Hi,

                            I am totally confused.

                            In the jmx-console there is the right name:

                            Other components with java:comp namespace
                            
                            java:comp namespace of the component
                            jboss.j2ee:ear=FirstJPA.jar,jar=FirstJPA.jar,name=ProductTestBean,service=EJB3 :
                             +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef)
                             +- env (class: org.jnp.interfaces.NamingContext)
                             | +- em (class: org.jboss.ejb3.entity.TransactionScopedEntityManager)
                             | +- de.beans.ProductTestBean (class: org.jnp.interfaces.NamingContext)
                             ...
                            


                            and:

                            Global JNDI Namespace
                            
                             +- UserTransactionSessionFactory (proxy: $Proxy134 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
                             +- jmx (class: org.jnp.interfaces.NamingContext)
                             | +- rmi (class: org.jnp.interfaces.NamingContext)
                             | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
                             | +- invoker (class: org.jnp.interfaces.NamingContext)
                             | | +- RMIAdaptor (proxy: $Proxy139 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
                             +- queue (class: org.jnp.interfaces.NamingContext)
                             | +- DLQ (class: org.jboss.jms.destination.JBossQueue)
                             | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue)
                             +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
                             +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
                             +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
                             +- persistence.unit:unitName=#firstJPA (class: org.hibernate.impl.SessionFactoryImpl)
                             +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
                             +- console (class: org.jnp.interfaces.NamingContext)
                             | +- PluginManager (proxy: $Proxy142 implements org.jboss.console.manager.PluginManagerMBean (no security manager: RMI class loader disabled))
                             +- topic (class: org.jnp.interfaces.NamingContext)
                             +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
                             +- ProductTestBean (class: org.jnp.interfaces.NamingContext)
                             | +- remote (class: Proxy for: de.beans.ProductTest)
                             | +- remote-de.beans.ProductTest (class: Proxy for: de.beans.ProductTest)
                             +- TomcatAuthenticators (class: java.util.Properties)
                             +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
                             +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
                            
                            


                            Thanks and greetz,
                            Nicole

                            • 11. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                              Andrew Rubinger Master

                              The CCE to javax.naming.Reference is a good sign that you don't have the proper ObjectFactory classes on your client ClassPath. Check that you've got either jbossall-client.jar or jboss-ejb3-proxy-client.jar defined there (relative to $JBOSS_HOME/client/).

                              S,
                              ALR

                              • 12. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                                Nicole Schweighardt Novice

                                Hi,

                                I thought it is enough to start the project with JBoss AS 5.0. I forgot to change "Runtime 4.2.2" in the build path to "Runtime 5.0"....
                                arrg.

                                Thank you all so much for your help!
                                It is not easy as beginner to handle all these things and without people like you it would be much more frustrating.

                                Thanks and bye.
                                Nicole

                                PS.: Perhaps anyone can tell me sth. about the port-issue?
                                (Change the jboss port:

                                <attribute name="BindAddress">${jboss.bind.address}</attribute>
                                 <!-- The port of the RMI naming service, 0 == anonymous -->
                                 <attribute name="RmiPort">1095</attribute>

                                Is this okay to handle this problem? Is the port 1095 okay?)


                                • 13. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                                  jaikiran pai Master

                                   

                                  "NSchweig" wrote:


                                  PS.: Perhaps anyone can tell me sth. about the port-issue?
                                  (Change the jboss port:
                                  <attribute name="BindAddress">${jboss.bind.address}</attribute>
                                   <!-- The port of the RMI naming service, 0 == anonymous -->
                                   <attribute name="RmiPort">1095</attribute>

                                  Is this okay to handle this problem? Is the port 1095 okay?)


                                  The ports that JBoss binds to can be changed. Its upto you to decide which ports JBoss binds to. You only have to ensure that no other application uses this port. The best way to manage ports in JBoss is through the ServiceBindingManager http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta422/html/Additional_Services-Services_Binding_Management.html

                                  • 14. Re: Migrate from 4.2.2 GA to JBoss 5 CR2 fails
                                    jaikiran pai Master

                                     

                                    "jaikiran" wrote:


                                    The ports that JBoss binds to can be changed. Its upto you to decide which ports JBoss binds to. You only have to ensure that no other application uses this port. The best way to manage ports in JBoss is through the ServiceBindingManager http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta422/html/Additional_Services-Services_Binding_Management.html


                                    I just noticed that there's been a change in the way ServiceBindingManager is configured in JBoss-5 CR2. See this thread for details http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142572

                                    1 2 Previous Next