jQuery in Action, 2nd edition*
The moose likes JBoss/WildFly and the fly likes jboss 4.0.1sp1 to 5.1.0.GA migration issue. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "jboss 4.0.1sp1 to 5.1.0.GA migration issue." Watch "jboss 4.0.1sp1 to 5.1.0.GA migration issue." New topic
Author

jboss 4.0.1sp1 to 5.1.0.GA migration issue.

prashant gandhi
Greenhorn

Joined: May 21, 2013
Posts: 18
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
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5812
    
    7

Where is your EAR file is there a reference to stateful-rmi-invoker? Apparently, that is missing (I searched in 4.0.1.SP1 and 5.1.0.GA and didn't find anything by that name).

By the way, if you final objective is to run on JBoss AS 7.x, why are you porting to 5.1.0? You will just have to go through yet another port to get to 7.x.


JBoss In Action
prashant gandhi
Greenhorn

Joined: May 21, 2013
Posts: 18
thanks for the response.

my dtu.ear file is in C:\jboss 5.1.0.GA\server\default\deploy directory. That is where I had kept my ear file for 4.0.1sp1 version (at: C:\jboss4.0.1sp1\server\default\deploy - and it works alright).
how do i see what reference is missing? sorry, i am new to this.

i am trying to upgrade to 5.x first so that we can take baby steps at a time, to make it simplified. if i go from 4.x to 5.x only 1 release difference is what i need to worry about, is it not?
prashant gandhi
Greenhorn

Joined: May 21, 2013
Posts: 18
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
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5812
    
    7

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.

This is a fallacy. JBoss AS 7 is a complete rewrite, different architecture, different configuration mechanism. None of the changes that you make to get from 4.0.x to 5.1.0 will help you in getting to 7.x - you will have to start your port from scratch.

Regarding the error you posted, where is jbossweb-tomcat50.sar referenced in your code/config? That file no longer exists, the closest to it is deploy/jbossweb.sar
prashant gandhi
Greenhorn

Joined: May 21, 2013
Posts: 18
Thanks for the reply.

I am a newbie to Java and Jboss world. Could you please tell me what would be a good starting point? Any direction/help/assistance would be much appreciated.

Is Jboss 6.1.1 also a rewrite? from which version, the component re-write became necessity post 4.x version of jboss? Without changing any source code, I tried compiling my existing Java source code using <ant> at jboss 5.x and it compiled fine and gave the exe. from 5.x to 6.x - i get lots of errors. Thanks again.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5812
    
    7

When you move from one version of JBoss AS to another, there is always some amount of rewrite/reconfiguration necessary because things change from release to release. And newer versions of AS support newer versions of Java EE (and while the newer versions are supposed to support older J2EE technologies, sometimes they don't do a very good job of it and older J2EE stuff just doesn't work). While there were refinements in the AS core (5.x move from a JMX core to a microkernel with still a lot of JMX support), 7.x was the first complete rewrite - the directory structure changed, how you manage it changed. All versions up to then appeared very similar with a similar directory structure and familiar XML configuration files.

I tried compiling my existing Java source code using <ant> at jboss 5.x and it compiled fine and gave the exe.

I don't see how that is possible, exe's have nothing to do with Java

from 5.x to 6.x - i get lots of errors

Didn't you just say that it compiled with 5.x? Or do you mean that it doesn't compile against 6.x? (By the way, without seeing the error messages I couldn't even guess at the problem.)

If you really are new to JBoss AS, and you really want to eventually port your app to AS 7.x, then you really should ignore all versions before 7.x and concentrate on the latest version of 7.x. There are docs and tutorials online, and I know of at least one book on 7.x that will come out soon.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: jboss 4.0.1sp1 to 5.1.0.GA migration issue.
 
Similar Threads
moved from jboss-4.0.3 to jboss-5.1.0 where do I put my war files
BRMS on JBOSS 4.0.2
EJB 3 deployment Error
JBOSS 5.0.0.Beta4 Statup problem
Deployment Failed on JBoss 5.0.1 GA