Ahh...just found the solution to this one. While mucking about with the old Tomcat integration, I noticed it complaining about missing a XMLParserFactory. I added Sun's jaxp.jar and parser.jar to my classpath, and everything is now magically working...
-Jason
| [EMAIL PROTECTED]
10/25/2000 08:53 AM
|
To: [EMAIL PROTECTED] cc: Subject: [jBoss-User] Is EmbeddedTomcat working? |
I'm using today's CVS snapshot (10/25), and have tried both the tomcat-service.jar that is packaged with it, and also compiled the EmbeddedTomcat module from the contrib CVS snapshot, both with the same result. I am running it against Tomcat 3.2b4. This is what I get at server startup:
[EmbeddedTomcat] Starting
[EmbeddedTomcat] Testing if Tomcat is present....
[EmbeddedTomcat] OK
[EmbeddedTomcat] ContextManager: Adding context Ctx( )
[Default] Error starting service 'DefaultDomain:service=EmbeddedTomcat': javax.management.RuntimeErrorException: Error thrown in operation start
[Default] Unable to start service 'EmbeddedTomcat'
The related MLET entries in jboss.conf looks like this:
<MLET CODE = "org.jboss.deployment.J2eeDeployer" ARCHIVE="jboss.jar,../xml.jar" CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="../tmp">
<ARG TYPE="java.lang.String" VALUE="EJB:service=ContainerFactory">
<ARG TYPE="java.lang.String" VALUE=":service=EmbeddedTomcat">
</MLET>
<MLET CODE = "org.jboss.tomcat.EmbeddedTomcatService" ARCHIVE="jboss.jar" CODEBASE="../lib/ext/">
<ARG TYPE="int" VALUE=8080>
</MLET>
Is there anyway to turn on some more verbose debugging? "Error thrown in operation start" doesn't help too much.. ;), or any ideas as to what might be wrong?
-Jason
