4 Replies Latest reply on Mar 17, 2009 2:05 AM by jaikiran pai

    Upgrading to JBoss 5.0 GA

    Muthukumaran Manickavasagam Newbie

      Hi,

      I'm trying to upgrade my ejb application to Jboss 5.0. With the blind start i copied the EAR into the deploy folder and started my Jboss server. However it failed with the following exception. I tried to get some solution through web (google) but so far there is no luck in this regard. I will do search more but if you get any suggestion please let me know. From the log i think it failed to parse my jboss.xml with latest DTD however i do not want to uprade my XML as it will be a huge effort for me. How i can use this EAR as if i used it in jboss 4.x. Please find the error log below,

      ---------------------
      17:18:56,858 INFO [WebService] Using RMI server codebase: http://IN-LENOR28:8083/

      17:19:44,198 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/D:/views/mmuthu/software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear state=Not Installed mod

      e=Manual requiredState=Parse

      org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/D:/views/mmuthu/software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear/yodleemdb.jar

      at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)

      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)

      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)

      at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:95)

      at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)

      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)

      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

      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:781)

      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)

      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)

      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)

      at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)

      at org.jboss.Main.boot(Main.java:209)

      at org.jboss.Main$1.run(Main.java:547)

      at java.lang.Thread.run(Thread.java:595)

      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: The content of element type "jboss" must match "(loader-repository?,jmx-name?,enforce-ejb-restrictions?,security-domain?,missi

      ng-method-permissions-excluded-mode?,unauthenticated-principal?,exception-on-rollback?,webservices?,enterprise-beans?,assembly-descriptor?,resource-managers?,invoker-proxy-bindings?,container-configur

      ations?)". @ vfszip:/D:/views/mmuthu/software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear/yodleemdb.jar/META-INF/jboss.xml[149,9]

      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:323)

      ... 24 more

      Caused by: org.xml.sax.SAXException: The content of element type "jboss" must match "(loader-repository?,jmx-name?,enforce-ejb-restrictions?,security-domain?,missing-method-permissions-excluded-mode?,

      unauthenticated-principal?,exception-on-rollback?,webservices?,enterprise-beans?,assembly-descriptor?,resource-managers?,invoker-proxy-bindings?,container-configurations?)". @ vfszip:/D:/views/mmuthu/

      software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear/yodleemdb.jar/META-INF/jboss.xml[149,9]

      at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426)

      at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)

      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

      at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

      at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)

      at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)

      at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(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)

      ... 32 more

      17:19:48,252 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent

      17:19:49,076 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.

      17:19:49,076 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer

      17:19:49,915 INFO [TransactionManagerService] Initializing recovery manager

      17:19:51,150 INFO [TransactionManagerService] Recovery manager configured

      17:19:51,166 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference

      17:19:51,230 INFO [TransactionManagerService] Starting transaction recovery manager

      17:19:52,528 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080

      17:19:52,544 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009

      17:19:52,544 INFO [StandardService] Starting service jboss.web

      17:19:52,560 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.1.GA

      17:19:52,718 INFO [Catalina] Server startup in 427 ms

      17:19:53,067 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):



      *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}



      jboss.ejb:persistencePolicy=database,service=EJBTimerService

      -> jboss.jca:name=DefaultDS,service=DataSourceBinding{Create:** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **}

      -> jboss.jdbc:datasource=DefaultDS,service=metadata{Create:** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **}



      jboss.ejb:service=EJBTimerService

      -> jboss.ejb:persistencePolicy=database,service=EJBTimerService{Create:Configured}





      *** CONTEXTS IN ERROR: Name -> Error



      jboss.jdbc:datasource=DefaultDS,service=metadata -> ** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **



      vfszip:/D:/views/mmuthu/software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear -> org.xml.sax.SAXException: The content of element type "jboss" must match "(loader-repository?,jmx-

      name?,enforce-ejb-restrictions?,security-domain?,missing-method-permissions-excluded-mode?,unauthenticated-principal?,exception-on-rollback?,webservices?,enterprise-beans?,assembly-descriptor?,resourc

      e-managers?,invoker-proxy-bindings?,container-configurations?)". @ vfszip:/D:/views/mmuthu/software/jboss/jboss-5.0.0.GA/server/messaging/deploy/2_yodlee.ms.mdbs.ear/yodleemdb.jar/META-INF/jboss.xml[1

      49,9]



      jboss.jca:name=DefaultDS,service=DataSourceBinding -> ** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **

      --------------------------

        • 1. Re: Upgrading to JBoss 5.0 GA
          jaikiran pai Master

           


          Caused by: org.xml.sax.SAXException: The content of element type "jboss" must match "(loader-repository?,jmx-name?,enforce-ejb-restrictions?,security-domain?,missing-method-permissions-excluded-mode?,

          unauthenticated-principal?,exception-on-rollback?,webservices?,enterprise-beans?,assembly-descriptor?,resource-managers?,invoker-proxy-bindings?,container-configurations?


          I guess, the order of the elements in the jboss.xml is incorrect or maybe some unexpected element is present in the jboss.xml.
          Please post the contents of that file.

          While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.


          • 2. Re: Upgrading to JBoss 5.0 GA
            Muthukumaran Manickavasagam Newbie

            Please find my jboss.xml XML code below...

            <?xml version="1.0"?>
            <!DOCTYPE jboss
             PUBLIC "-//JBoss//DTD MBean Service 4.0//EN"
             "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
            <jboss>
             <enterprise-beans>
             <message-driven>
             <ejb-name>...</ejb-name>
             <destination-jndi-name>....</destination-jndi-name>
             <mdb-user>...</mdb-user>
             <mdb-passwd>...</mdb-passwd>
             <mdb-client-id>...</mdb-client-id>
             <mdb-subscription-id>...</mdb-subscription-id>
             <configuration-name>...</configuration-name>
             </message-driven>
             </enterprise-beans>
            
             <!-- container configuration for WSMQ -->
            
             <container-configurations>
             <container-configuration extends="Standard Message Driven Bean">
             <container-name>...</container-name>
             <invoker-proxy-binding-name>
             wsmq-message-driven-bean</invoker-proxy-binding-name>
             </container-configuration>
             </container-configurations>
            
            
             <!-- The JmsProviderAdapterJNDI must match the ProviderName in SERVER_HOME/deploy/jms/wsmq-ds.xml file. -->
             <invoker-proxy-bindings>
             <invoker-proxy-binding>
             <name>wsmq-message-driven-bean</name>
             <invoker-mbean>default</invoker-mbean>
             <proxy-factory>
             org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
             <proxy-factory-config>
             <JMSProviderAdapterJNDI>JBOSSMQJMSProvider</JMSProviderAdapterJNDI>
             <ServerSessionPoolFactoryJNDI>
             StdJMSPool</ServerSessionPoolFactoryJNDI>
             <CreateJBossMQDestination>true</CreateJBossMQDestination>
             <MinimumSize>10</MinimumSize>
             <MaximumSize>10</MaximumSize>
             <KeepAliveMillis>30000</KeepAliveMillis>
             <MaxMessages>1</MaxMessages>
             <MDBConfig>
             <ReconnectIntervalSec>10</ReconnectIntervalSec>
             <DLQConfig>
             <DestinationQueue>MDBDeadLetterQueue</DestinationQueue>
             <MaxTimesRedelivered>3</MaxTimesRedelivered>
             <TimeToLive>0</TimeToLive>
             <DLQUser>...</DLQUser>
             <DLQPassword>...</DLQPassword>
             </DLQConfig>
             </MDBConfig>
             </proxy-factory-config>
             </invoker-proxy-binding>
             </invoker-proxy-bindings>
            </jboss>
            


            • 3. Re: Upgrading to JBoss 5.0 GA
              Muthukumaran Manickavasagam Newbie

              Hi, I brought down the container-configuration lower in the order which is ultimately resolving my problem. Should i need to open each and every configuration and match it with DTD to resolve these kind of issues? Can't i fall back with old way of XML validation in JBOSS which is my originial interest of the post. Did i miss something here?

              • 4. Re: Upgrading to JBoss 5.0 GA
                jaikiran pai Master

                 

                "mmuthu" wrote:
                Hi, I brought down the container-configuration lower in the order which is ultimately resolving my problem. Should i need to open each and every configuration and match it with DTD to resolve these kind of issues? Can't i fall back with old way of XML validation in JBOSS which is my originial interest of the post.


                I think for that you will have to upgrade to 5.1.0-Beta which was recently released. Here's a thread in the jboss-dev forum which discussed this http://www.nabble.com/changes-in-parsing-with-xb-td22478176.html