JBoss doesn't start: jboss-4.0.0DR1_tomcat-4.1.24 on Linux

[amartinr]

Hi guys, I need your help. Somebody has installed jboss4.0+tomcat without errors?

I have intalled it on OS-System: Linux 2.4.21-0.13mdk,i386; and Java version: 1.4.1_01.

I'm using a copy of configuration default renamed 'myjboss', and I have change the port of Tomcat (jboss-4.0.0DR1_tomcat-4.1.24/server/myjboss/deploy/tomcat41-service.xml) to 8079 in order to solve incompatibilities with JBoss port.

The services of JBoss don't deploy, obtaining this error:


13:10:07,268 INFO [MainDeployer] Starting deployment of package: file:/opt/jboss-4.0.0DR1_tomcat-4.1.24/server/myjboss/deploy/jboss-net.sar/jboss-net.war/
13:10:09,343 INFO [EmbeddedCatalinaService41] deploy, ctxPath=/jboss-net, warUrl=file:/opt/jboss-4.0.0DR1_tomcat-4.1.24/server/myjboss/deploy/jboss-net.sar/jboss-net.war/
13:10:10,669 WARN [ServiceController] Problem starting service jboss.deployment:name=file%3a/opt/jboss-4.0.0DR1_tomcat-4.1.24/server/myjboss/deploy/jboss-net.sar/jboss-net.war/,service=DeploymentInfo
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException; remaining name 'env')
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:408)
at org.jboss.deployment.DeploymentInfo.start(DeploymentInfo.java:254)


I look in URL:
(1) http://tomcat:8079/jmx-console
HTTP Status 500 - No Context configured to process this request
(2) http://tomcat:8080/ doesn't connect

I'm thinking if it is a version problem. Is JBoss 4.0 running well with tomcat?

Thanks in advance,

Ana

[amartinr]

I've found next lines in server.log:

2003-06-25 13:10:26,332 INFO [org.jboss.ejb.StatelessSessionContainer] Starting
2003-06-25 13:10:26,334 DEBUG [org.jboss.ejb.StatelessSessionContainer] Begin java:comp/env for EJB: MEJB
2003-06-25 13:10:26,336 DEBUG [org.jboss.ejb.StatelessSessionContainer] TCL: java.net.URLClassLoader@94b318
2003-06-25 13:10:26,363 DEBUG [org.jboss.ejb.StatelessSessionContainer] Binding env-entry: Server-Name of type: java.lang.String to value:null
2003-06-25 13:10:26,369 DEBUG [org.jboss.ejb.StatelessSessionContainer] End java:comp/env for EJB: MEJB

Maybe it has some relationship. Someone knows how this value must configure diferent to null?

thanks alot,

Ana

[amartinr]

well, I've found why web-console didn't work. I have not starting with the files jboss,go.sh in JBossQuickStart30-1.pdf.
Know I can see the console at: http://tomcat:8080/web-console/index.html

The error is still appearing:

2003-06-26 13:40:52,361 WARN [org.jboss.system.ServiceController] Problem starting service jboss.deployment:name=file%3a/opt/jboss_tomcat/server/myjboss/deploy/jboss-net.sar/jboss-net.war/,service=DeploymentInfo
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException; remaining name 'env')
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:408)
at org.jboss.deployment.DeploymentInfo.start(DeploymentInfo.java:254)
at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
...
Caused by: javax.naming.NameAlreadyBoundException; remaining name 'env'
at org.jnp.server.NamingServer.createSubcontext(NamingServer.java:446)
at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:819)
at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:805)
at org.jboss.web.AbstractWebContainer.parseWebAppDescriptors(AbstractWebContainer.java:567)
...
MBeans waiting for classes:

MBeans waiting for other MBeans:

{ objectName: jboss.deployment:name=file%3a/opt/jboss_tomcat/server/myjboss/deploy/jboss-net.sar/jboss-net.war/,service=DeploymentInfo
state: NOTSTARTABLE
problem: org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException; remaining name 'env')
} org.jboss.system.ServiceContext@fd6f5e54,


I don't know what important jboss-net is. Is it?

thanks,

Ana

[jonlee]

go.sh isn't the normal start method - at least not any more. It has apparently caused some angst for other people.

Since 3.2.x, it has been run.sh. You just need to set JAVA_HOME beforehand and ensure that CLASSPATH is blank (or not set).

So to start your special configuration:
./run.sh -c myjboss

JBoss.NET is not an essential service if you do not use Web services. It is the Apache Axis-based Web service. If you don't know what it is, you can remove the jboss-net.sar from your deployment.

Hope it helps.

[nollario]

Hi!

I posted the same topic in the Jboss user mailing list...

Scott Stark replied that there will be a new DR this week... This one will fix our problem! :)

Christian

[amartinr]

Well :D I've installed jboss-4.0.0DR2 and It has solved all the problems with startup. web-console works fine.

I think the problem with 'env' was JBOSS_HOME. I had a lot of version installed and it's possible JBOSS_HOME was pointing through another version when I was started one version.

I realise there's no version jboss-4.0.0DR2_tomcat-4.1.24

Is JBoss supportting JSP-servlet?

If it's true, why we need tomcat?

Thanks in advance,

Ana