-
1. Re: JBoss Without Tomcat
asack Apr 15, 2006 12:47 PM (in response to mglause)"mglause" wrote:
Is it possible to setup jboss to run without apache tomcat? I know the minimal configuration does this but I can't figure out how to deploy my application without hot deployment. Thanks.
I'm not sure what you mean. The jbossweb-tomcat.sar is the JMX Service Archive that I believe encompasses Tomcat. If you remove that, you remove Tomcat. -
2. Re: JBoss Without Tomcat
mglause Apr 15, 2006 1:11 PM (in response to mglause)I've tried removing it and when I do it breaks everything. I basically just want jboss to run the ejb's.
-
3. Re: JBoss Without Tomcat
asack Apr 15, 2006 4:43 PM (in response to mglause)"mglause" wrote:
I've tried removing it and when I do it breaks everything. I basically just want jboss to run the ejb's.
What breaks? (you may have tgo edit a config file for a clean removal) -
4. Re: JBoss Without Tomcat
mglause Apr 16, 2006 12:10 PM (in response to mglause)If I just delete the tomcat directory within the deploy area I get an output like this:
C:\jboss-3.2.8.SP1\bin>run -c test =============================================================================== . JBoss Bootstrap Environment . JBOSS_HOME: C:\jboss-3.2.8.SP1\bin\\.. . JAVA: C:\j2sdk1.4.2_11\bin\java . JAVA_OPTS: -Dprogram.name=run.bat . CLASSPATH: C:\j2sdk1.4.2_11\lib\tools.jar;C:\jboss-3.2.8.SP1\bin\\run.jar . =============================================================================== . 12:08:16,602 INFO [Server] Starting JBoss (MX MicroKernel)... 12:08:16,602 INFO [Server] Release ID: JBoss [WonderLand] 3.2.8.SP1 (build: CVS Tag=JBoss_3_2_8_SP1 date=200603031235) 12:08:16,602 INFO [Server] Home Dir: C:\jboss-3.2.8.SP1 12:08:16,602 INFO [Server] Home URL: file:/C:/jboss-3.2.8.SP1/ 12:08:16,602 INFO [Server] Patch URL: null 12:08:16,602 INFO [Server] Server Name: test 12:08:16,602 INFO [Server] Server Home Dir: C:\jboss-3.2.8.SP1\server\test 12:08:16,602 INFO [Server] Server Home URL: file:/C:/jboss-3.2.8.SP1/server/tes t/ 12:08:16,602 INFO [Server] Server Temp Dir: C:\jboss-3.2.8.SP1\server\test\tmp 12:08:16,602 INFO [Server] Root Deployment Filename: jboss-service.xml 12:08:16,792 INFO [ServerInfo] Java version: 1.4.2_11,Sun Microsystems Inc. 12:08:16,792 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_11-b06 ,Sun Microsystems Inc. 12:08:16,792 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 12:08:17,183 INFO [Server] Core system initialized 12:08:18,665 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:log4j.xml 12:08:18,735 INFO [WebService] Using RMI server codebase: http://vaio:8083/ 12:08:18,845 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0. 0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jbos s.net.sockets.DefaultSocketFactory 12:08:20,187 INFO [RARMetaData] Required license terms present. See deployment descriptor. 12:08:20,237 INFO [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA dr ivers 12:08:20,237 INFO [RARMetaData] Required license terms present. See deployment descriptor. 12:08:20,267 INFO [RARMetaData] Required license terms present. See deployment descriptor. 12:08:21,790 INFO [MailService] Mail Service bound to java:/Mail 12:08:21,990 INFO [DefaultDS] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'jav a:/DefaultDS' 12:08:22,160 INFO [A] Bound to JNDI name: queue/A 12:08:22,160 INFO [B] Bound to JNDI name: queue/B 12:08:22,170 INFO [C] Bound to JNDI name: queue/C 12:08:22,170 INFO [D] Bound to JNDI name: queue/D 12:08:22,170 INFO [ex] Bound to JNDI name: queue/ex 12:08:22,200 INFO [testTopic] Bound to JNDI name: topic/testTopic 12:08:22,200 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 12:08:22,200 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 12:08:22,200 INFO [testQueue] Bound to JNDI name: queue/testQueue 12:08:22,220 INFO [UILServerILService] JBossMQ UIL service available at : /0.0. 0.0:8093 12:08:22,260 INFO [DLQ] Bound to JNDI name: queue/DLQ 12:08:22,280 INFO [JmsXA] Bound connection factory for resource adapter for Con nectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA' 12:08:22,471 INFO [EjbModule] Deploying Fibo 12:08:22,531 INFO [EjbModule] Deploying Hello 12:08:22,591 INFO [EJBDeployer] Deployed: file:/C:/jboss-3.2.8.SP1/server/test/ deploy/FiboEJB.jar 12:08:22,631 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Packages waiting for a deployer --- org.jboss.deployment.DeploymentInfo@78b61faa { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/http-invoker.sar/invoker.war/ } deployer: null status: Starting state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/http-invoker.sar/invoker.wa r/ lastDeployed: 1145203701059 lastModified: 1145203574336 mbeans: org.jboss.deployment.DeploymentInfo@13b75bc6 { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ } deployer: null status: Starting state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/jms/jbossmq-httpil.sar/jbos smq-httpil.war/ lastDeployed: 1145203701059 lastModified: 1145203570631 mbeans: org.jboss.deployment.DeploymentInfo@45178421 { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/jmx-console.war/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/jmx-console.war/ lastDeployed: 1145203702631 lastModified: 1145203570050 mbeans: org.jboss.deployment.DeploymentInfo@7150972e { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/management/web-console.war/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/management/web-console.war/ lastDeployed: 1145203702631 lastModified: 1145203569039 mbeans: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@45178421 { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/jmx-console.war/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/jmx-console.war/ lastDeployed: 1145203702631 lastModified: 1145203570050 mbeans: org.jboss.deployment.DeploymentInfo@7150972e { url=file:/C:/jboss-3.2.8.SP1/serv er/test/deploy/management/web-console.war/ } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/C:/jboss-3.2.8.SP1/server/test/deploy/management/web-console.war/ lastDeployed: 1145203702631 lastModified: 1145203569039 mbeans: --- 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 --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.web:service=WebServer State: NOTYETINSTALLED Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP 12:08:22,871 INFO [Server] JBoss (MX MicroKernel) [3.2.8.SP1 (build: CVSTag=JBo ss_3_2_8_SP1 date=200603031235)] Started in 6s:259ms
-
5. Re: JBoss Without Tomcat
asack Apr 16, 2006 1:21 PM (in response to mglause)So why don't you remove the pertinent modules then?
I don't understand what your really trying to do. If you create stripped down version at install time and add what you need, it should be a cleaner appraoch. -
6. Re: JBoss Without Tomcat
mglause Apr 16, 2006 2:28 PM (in response to mglause)If I'm not mistaken the URLDeploymentScanner is what is failing and if I remove that then my test EJB will note get deployed. This wouldn't be a problem if I knew how to manually deploy but I'm pretty new to JBoss and haven't been able to find out how to do that.
12:08:22,471 INFO [EjbModule] Deploying Fibo 12:08:22,531 INFO [EjbModule] Deploying Hello 12:08:22,591 INFO [EJBDeployer] Deployed: file:/C:/jboss-3.2.8.SP1/server/test/ deploy/FiboEJB.jar 12:08:22,631 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
-
7. Re: JBoss Without Tomcat
mglause Apr 16, 2006 3:01 PM (in response to mglause)You were right. Upon making my previous post I realized what I said didn't make sense so I started deleting files until I got down to a barebone setup. Then I had to modify the service file in jboss-ws4ee.sar/. Thanks for your help.