jboss 4.0.1sp1 to 5.1.0.GA migration issue.

[ppgandhi11]

Hi I am a newbie. I have java 1.6.0_26. with windows XP. I downloaded the jboss 5.1.0.GA as a full folder using winzip. stuff works on 4.0.1sp1 but doesnt work on new jboss. final goal is to upgrade jboss to 7.x. code is same. the generated dtu.ear file when kept in jboss' server/default/deploy directory works fine at 4.x jboss but doesnt work on 5.x. any help is appreciated. thank you.

for 4.x

set ANT_HOME=C:\apache-ant-1.9.0

set JBOSS_HOME=C:\jboss-4.0.1sp1

set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_26

set PATH=%PATH%;%ANT_HOME%\bin

set PATH=%PATH%;%JAVA_HOME%\bin

set PATH=%PATH%;%JBOSS_HOME%\bin

cd c:\jboss-4.0.1sp1

run

for 5.x

set ANT_HOME=C:\apache-ant-1.9.0

set JBOSS_HOME=C:\jboss-5.1.0.GA

set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_26

set PATH=%PATH%;%ANT_HOME%\bin

set PATH=%PATH%;%JAVA_HOME%\bin

set PATH=%PATH%;%JBOSS_HOME%\bin

cd c:\jboss-5.1.0.GA

run

12:41:15,023 ERROR [AbstractKernelController] Error installing to Real: name=vfs

zip:/C:/jboss-5.1.0.GA/server/default/deploy/dtu.ear/ state=PreReal mode=Manual

requiredState=Real

org.jboss.deployers.spi.DeploymentException: Failed to locate invoker: stateful-

rmi-invoker

        at org.jboss.ejb.deployers.EjbDeployer.deploy(EjbDeployer.java:383)

        at org.jboss.ejb.deployers.EjbDeployer.deploy(EjbDeployer.java:74)

        at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.de

ploy(AbstractSimpleVFSRealDeployer.java:56)

        at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.i

nternalDeploy(AbstractSimpleRealDeployer.java:62)

        at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(

AbstractRealDeployer.java:50)

        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(Deployer

Wrapper.java:171)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(Deployer

sImpl.java:1439)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi

rst(DeployersImpl.java:1157)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi

rst(DeployersImpl.java:1210)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(Deployers

Impl.java:1098)

        at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra

ctControllerContext.java:348)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractContr

oller.java:1631)

        at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra

ctController.java:934)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr

actController.java:1082)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr

actController.java:984)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractContro

ller.java:822)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractContro

ller.java:553)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.process(Deployers

Impl.java:781)

        at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeploye

rImpl.java:702)

        at org.jboss.system.server.profileservice.repository.MainDeployerAdapter

.process(MainDeployerAdapter.java:117)

        at org.jboss.system.server.profileservice.repository.ProfileDeployAction

.install(ProfileDeployAction.java:70)

        at org.jboss.system.server.profileservice.repository.AbstractProfileActi

on.install(AbstractProfileAction.java:53)

        at org.jboss.system.server.profileservice.repository.AbstractProfileServ

ice.install(AbstractProfileService.java:361)

        at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra

ctControllerContext.java:348)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractContr

oller.java:1631)

        at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra

ctController.java:934)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr

actController.java:1082)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr

actController.java:984)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractContro

ller.java:822)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractContro

ller.java:553)

        at org.jboss.system.server.profileservice.repository.AbstractProfileServ

ice.activateProfile(AbstractProfileService.java:306)

        at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(

ProfileServiceBootstrap.java:271)

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

461)

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

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

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

12:41:15,195 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of

incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS IN ERROR:

  Deployment "vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/dtu.ear/" is in er

ror due to the following reason(s): org.jboss.deployers.spi.DeploymentException:

Failed to locate invoker: stateful-rmi-invoker

12:41:15,210 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8

080

12:41:15,241 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

12:41:15,257 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=

JBoss_5_1_0_GA date=200905221053)] Started in 53s:54ms

[vishy_jboss]

The error clearly states its not able to find "stateful-rmi-invoker" - compare standardjboss.xml from both versions and you will see the difference.

[wdfink]

As it look like that there are special JBoss configurations inside the deployment descriptors it might be difficult to migrate to JBoss5 and further to JBoss7.

With EJB2 applications you might check whether the effort is higher than a migration to EJB3 together wit the AS migration.

It depends on the application which is the best way.

[ppgandhi11]

I am trying to take baby steps at a time. Instead of jumping from 4.x to 7.x i am trying to go 1 release at a time.

I resolved the first error by keeping stateless instead of stateful rmi invoker. But, I am getting below error for the java code that I am trying to compile now with the jboss 5.x  How do i resolve this? This code works fine with jboss 4.0.1sp1.

set JBOSS_HOME=C:\jboss-4.0.1sp1  -- code works.

set JBOSS_HOME=C:\jboss-5.1.0.GA -- code breaks.

for 5.x i had to create: server/default/deploy directory and had everything copied from 4.x directory from server level, otherwise it was failing stating: /server/default/deploy/jbossweb-tomcat50.sar does not exist

Any help is appreciated. Thanks.

...

compile-ejb:

    [javac] C:\DTU\DTU_FE\build.xml:243: warning: 'includeantruntime' was not se

t, defaulting to build.sysclasspath=last; set to false for repeatable builds

    [javac] Compiling 121 source files to C:\DTU\DTU_FE\build\classes

    [javac] C:\DTU\DTU_FE\src\com\acnielsen\dtu\common\MetaDataLookup.java:10: p

ackage javax.servlet does not exist

    [javac] import javax.servlet.*;

    [javac] ^

    [javac] C:\DTU\DTU_FE\src\com\acnielsen\dtu\common\MetaDataLookup.java:11: p

ackage javax.servlet.http does not exist

    [javac] import javax.servlet.http.*;

    [javac] ^

    [javac] Note: Some input files use unchecked or unsafe operations.

    [javac] Note: Recompile with -Xlint:unchecked for details.

    [javac] 2 errors

BUILD FAILED

[wdfink]

It looks like that you use JBoss libraries to compile your code. As the jars might be renamed or located in a different place you need to look for it (i.e. find the classes or packages inside the jars).

But in case of such standard libraries I would use the interfaces provided by oracle, in this case the build process in independent from JBoss.

[ppgandhi11]

Thanks a lot Wolf for pointing it out. I was able to fix it. Thanks.