JBoss 3.2.3 installation with standalone Tomcat

[manollo]

Hi!

I've installed JBoss 3.2.3 and it works perfectly with the embedded Tomcat. But now I've tried to run JBoss 3.2.3 with a standalone Tomcat.

For example, some of our clients that have installed a Tomcat version and wish to use the JBoss, but when I start the Tomcat and the JBoss I've got some exceptions. Exists there a workaround or is it impossible? Thanks in advance.

Manollo

[juha]

I don't understand how you would expect anyone to be able to help you with an error description of "I've got some exceptions."....

[manollo]

thanks for your fast reply. I'm not so familar with the jboss, but should I deploy those war's in the tomcat? And if so how could the web-console connect to jboss? okay here's a snippet from jboss log.

Thanks, Manollo

13:26:05,818 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@4f4825ba { url=file:/C:/jboss-3.2.3/server/default/deploy/http-invoker.sar/invoker.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/http-invoker.sar/invoker.war/
lastDeployed: 1084965959419
lastModified: 1084958351089
mbeans:
, org.jboss.deployment.DeploymentInfo@ea7d0fbb { url=file:/C:/jboss-3.2.3/server/default/deploy/jboss-net.sar/jboss-net.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/jboss-net.sar/jboss-net.war/
lastDeployed: 1084965959419
lastModified: 1084958319053
mbeans:
, org.jboss.deployment.DeploymentInfo@4afbafb6 { url=file:/C:/jboss-3.2.3/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
lastDeployed: 1084965959439
lastModified: 1084958351920
mbeans:
, org.jboss.deployment.DeploymentInfo@a164e411 { url=file:/C:/jboss-3.2.3/server/default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/jmx-console.war/
lastDeployed: 1084965965618
lastModified: 1084958357919
mbeans:
, org.jboss.deployment.DeploymentInfo@c3d4767 { url=file:/C:/jboss-3.2.3/server/default/deploy/management/web-console.war }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/management/web-console.war
lastDeployed: 1084965965808
lastModified: 1084965965788
mbeans:
]Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@a164e411 { url=file:/C:/jboss-3.2.3/server/default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/jmx-console.war/
lastDeployed: 1084965965618
lastModified: 1084958357919
mbeans:
, org.jboss.deployment.DeploymentInfo@c3d4767 { url=file:/C:/jboss-3.2.3/server/default/deploy/management/web-console.war }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.3/server/default/deploy/management/web-console.war
lastDeployed: 1084965965808
lastModified: 1084965965788
mbeans:
]MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
state: CONFIGURED
I Depend On: jboss.mq:service=Invoker
jboss.web:service=WebServer

Depends On Me: ]
13:26:06,159 INFO [URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL
13:26:06,269 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.3/server/default/conf/jboss-service.xml
13:26:06,279 INFO [Server] JBoss (MX MicroKernel) [3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)] Started in 28s:271ms

[juha]

If you've removed the servlet container from JBoss then you need to remove these WARs as well. The web-console only connects to the local server, so deploying it on tomcat won't help you.