Migrating 5.1 to AS7

[pete.haidinyak]

I've been tasked with migrating our EJB 2.x application from JBoss 5.1 to AS7 and ran into some problems.

First, I just dropped our existing EAR into the standalone deployments directory and hoped that it would just work.

This gave me some WARN messages in the log regarding our DB2 JDBC Driver JAR

08:42:37,255 WARN  [org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor] (MSC service thread 1-4) Could not index class COM/ibm/db2os390/sqlj/custom/DB2SQLJCustomizer.class in archive '"/C:/software/JBoss/jboss-as-7.0.1.Final/bin/content/XXXX.ear/db2jcc.jar"': java.lang.RuntimeException: Invalid Magic

        at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:389)

        at org.jboss.jandex.Indexer.index(Indexer.java:628)

        at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:121)

        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)

        at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_16]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_16]

        at java.lang.Thread.run(Thread.java:619) [:1.6.0_16]

After the WARN Messages I then received a couple of ERROR Messages

08:42:39,627 ERROR [org.jboss.as] (MSC service thread 1-11) JBoss AS 7.0.1.Final "Zap" started (with errors) in 15307ms - Started 102 of 160 services (3 services failed or missing dependencies, 55 services are passive or on-demand)

and

08:42:47,769 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.subunit.\"TcsEnterpriseApplication.ear\".\"TcsEnterpriseApplicationWeb.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"TcsEnterpriseApplication.ear\".\"TcsEnterpriseApplicationWeb.war\".PARSE: Failed to process phase PARSE

of subdeployment \"TcsEnterpriseApplicationWeb.war\" of deployment \"TcsEnterpriseApplication.ear\""}}}}

I've Googled these error and warn messages to look for a solution without success.

My question: Is there a better way to diagnose and fix these problems?

Thanks

-Pete

[sgilda]

Pete,

Datasource configuration has changed in AS7. Did you define the datasource in your server configuration file?

Here are a few helpful links:

https://docs.jboss.org/author/display/AS7/DataSource+configuration

https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7 (look for: Update the DataSource Configuration).

-Sande

[pete.haidinyak]

Hi Sande,

    Turns out we create the Data Source's programmatically using JMX so the Data Sources are not defined in any configuration file.

Any other ideas?

Thanks

-Pete

[pete.haidinyak]

Unless I miss my guess, the magic number warning means that the jandex Indexer thinks the class in the DB2 JDBC Driver in not a valid Java Class file. Would this warning be causing the deployment failure I am seeing?

Thanks

-Pete

[sgilda]

Pete, this is way beyond my expertise. I only know the basics.

Can anyone else help him?

[smarlow]

No, the warning doesn't cause the deployment to fail (involved code is here https://github.com/jbossas/jboss-as/blob/master/server/src/main/java/org/jboss/as/server/deployment/annotation/AnnotationIndexProcessor.java#L123). 

[smarlow]

Try attaching your server.log, perhaps there are other hints that would help us understand the reason for the deployment failure.  From what you said, that probably won't be the case, but may as well try...

[pete.haidinyak]

Turns out when I remove the offending DB2 jar files and any reference to them those errors went away and now I'm left with the expected ClassNotFound problems. I don't know why the processor didn't like the DB2 classes.

Thanks