10 Replies Latest reply on Jan 31, 2006 8:28 AM by farooqrashed

JBoss4.0.2 + Oracle9i configration problem (Any successful p

ourai Jun 10, 2005 4:28 AM

I am challenging to build a JBoss4.0.2 + Oracle9i Application server, all of my *.war and *.ear files can be deployed in my configration and everything LOOKS like running well but,,, some error message of MBeans comes everytime when I start the JBoss server. Here is my server starting log :

==============================================
JBoss Bootstrap Environment
JBOSS_HOME: /export/home/jdev/develop/MASS/jboss
JAVA: /usr/java/bin/java
JAVA_OPTS: -server -Xms256M -Xmx512M -Dprogram.name=run.sh -Dmegabatch.home=/export/home/jdev/develop/MASS/projects/Mega
CLASSPATH: /export/home/jdev/develop/MASS/jboss/bin/run.jar:/usr/java/lib/tools.jar
==============================================
16:52:32,845 INFO [Server] Starting JBoss (MX MicroKernel)...
16:52:32,852 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
16:52:32,854 INFO [Server] Home Dir: /space/jdev/app-3/jboss-4.0.2
16:52:32,855 INFO [Server] Home URL: file:/space/jdev/app-3/jboss-4.0.2/
16:52:32,856 INFO [Server] Library URL: file:/space/jdev/app-3/jboss-4.0.2/lib/
16:52:32,861 INFO [Server] Patch URL: null
16:52:32,862 INFO [Server] Server Name: default
16:52:32,863 INFO [Server] Server Home Dir: /space/jdev/app-3/jboss-4.0.2/server/default
16:52:32,865 INFO [Server] Server Home URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/
16:52:32,866 INFO [Server] Server Data Dir: /space/jdev/app-3/jboss-4.0.2/server/default/data
16:52:32,867 INFO [Server] Server Temp Dir: /space/jdev/app-3/jboss-4.0.2/server/default/tmp
16:52:32,868 INFO [Server] Server Config URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/conf/
16:52:32,869 INFO [Server] Server Library URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/lib/
16:52:32,870 INFO [Server] Root Deployment Filename: jboss-service.xml
16:52:32,885 INFO [Server] Starting General Purpose Architecture (GPA)...
16:52:35,629 INFO [ServerInfo] Java version: 1.5.0_03,Sun Microsystems Inc.
16:52:35,630 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_03-b07,Sun Microsystems Inc.
16:52:35,632 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
16:52:41,153 INFO [Server] Core system initialized
16:53:01,304 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
16:53:02,201 INFO [WebService] Using RMI server codebase: http://jakky:8083/
16:53:03,760 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0
, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
16:53:48,379 INFO [Embedded] Catalina naming disabled
16:53:53,795 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
16:53:53,807 INFO [Catalina] Initialization processed in 4327 ms
16:53:53,898 INFO [StandardService] Starting service jboss.web
16:53:53,920 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
16:53:54,254 INFO [StandardHost] XML validation disabled
16:53:54,815 INFO [Catalina] Server startup in 1007 ms
16:53:56,228 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default
/deploy/http-invoker.sar/invoker.war/
16:53:58,762 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
16:54:04,407 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default/t
mp/deploy/tmp35308jboss-ws4ee.war/
16:54:07,249 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default/deploy
/jbossweb-tomcat55.sar/ROOT.war/
16:54:13,128 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/
default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
16:54:45,304 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/def
ault/deploy/management/console-mgr.sar/web-console.war/
16:54:52,773 INFO [MailService] Mail Service bound to java:/Mail
16:54:58,893 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-ha-local-jdbc.rar
16:55:01,263 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-ha-xa-jdbc.rar
16:55:03,484 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-local-jdbc.rar
16:55:05,654 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-xa-jdbc.rar
16:55:08,192 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jms/jms-ra.rar
16:55:10,121 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/mail-ra.rar
16:55:17,320 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManag
er 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
16:55:18,627 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jbo
ss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
16:55:28,680 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/def
ault/deploy/jmx-console.war/
16:55:30,920 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

 --- 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

 ObjectName: jboss.mq.destination:service=Topic,name=testTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Queue,name=testQueue
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Queue,name=A
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=B
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=C
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=D
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=ex
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq:service=Invoker
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=TracingInterceptor
 Depends On Me:
 jboss.mq:service=InvocationLayer,type=HTTP
 jboss.mq:service=InvocationLayer,type=JVM
 jboss.mq:service=InvocationLayer,type=UIL2

 ObjectName: jboss.mq:service=TracingInterceptor
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=SecurityManager
 Depends On Me:
 jboss.mq:service=Invoker

 ObjectName: jboss.mq:service=SecurityManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq:service=TracingInterceptor
 jboss.mq.destination:service=Queue,name=DLQ

 ObjectName: jboss.mq.destination:service=Queue,name=DLQ
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq:service=InvocationLayer,type=JVM
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

 ObjectName: jboss.mq:service=DestinationManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=MessageCache
 jboss.mq:service=PersistenceManager
 jboss.mq:service=StateManager
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq.destination:service=Queue,name=A
 jboss.mq.destination:service=Queue,name=B
 jboss.mq.destination:service=Queue,name=C
 jboss.mq.destination:service=Queue,name=D
 jboss.mq.destination:service=Queue,name=ex
 jboss.mq:service=SecurityManager
 jboss.mq.destination:service=Queue,name=DLQ

 ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

 --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
 ObjectName: jboss.mq:service=StateManager
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.mq:service=DestinationManager

16:55:32,581 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
16:55:33,431 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
16:55:33,488 INFO [JkMain] Jk running ID=0 time=0/149 config=null
16:55:33,545 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 3m:659ms

1. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

ourai Jun 10, 2005 5:07 AM (in response to ourai)

I will share my configration below, if anybody know some information about the error messages, plese response me.

1. remove the default hsqldb.
$ cd JBOSS_HOME/server/default/deploy
$ rm hsqldb-ds.xml
$ cd ./jms
$ rm hsqldb-jdbc*
$ cd ../../lib
$ rm hsqldb-plugin.jar hsqldb.jar

2. add the oracle9i datasource.
$ cd default/deploy
$ cp JBOSS_HOME/docs/examples/jca/oracle-ds.xml ./
$ emacs oracle-ds.xml

<datasources>
 <local-tx-datasource>
 <jndi-name>DefaultDS</jndi-name>
 <connection-url>jdbc:oracle:thin:@xxx.xxx.xxx.xxx:1521:ORCL9i</connection-url>
 <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
 <user-name>testid</user-name>
 <password>testpassword</password>
.....................

$ cd ./jms
$ cp JBOSS_HOME/docs/examples/jms/oracle-jdbc2-service.xml ./

3. copy the oracle9i jdbc driver
$ cd JBOSS_HOME/server/default/lib
$ cp xxxxxxxxxxx/classes12.zip ./

4. change the data type mapping
$ cd JBOSS_HOME/server/default/conf
$ emacs standardjaws.xml

<jaws>
 <datasource>java:/DefaultDS</datasource>
 <type-mapping>Oracle8</type-mapping>
 <debug>false</debug>
.......................

$ emacs standardjbosscmp-jdbc.xml

<jbosscmp-jdbc>
 <defaults>
 <datasource>java:/DefaultDS</datasource>
 <datasource-mapping>Oracle9i</datasource-mapping>
..................

5. other setting for j2ee(maybe it is not necessary.)
$ cd JBOSS_HOME/server/default/conf
$ emacs jboss-service.xml

.................

 <mbean code="org.jboss.naming.NamingService"
 name="jboss:service=Naming"
 xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
 <!-- The call by value mode. true if all lookups are unmarshalled using the caller's TCL, false if in VM lookups return the value by reference.
 -->
 <attribute name="CallByValue">true</attribute>

.................

 <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
 <mbean code="org.jboss.tm.XidFactory"
 name="jboss:service=XidFactory">
 <attribute name="Pad">true</attribute>
 </mbean>

.................

$ cd ../deploy
$ emacs ear-deployer.xml

<server>
 <!-- EAR deployer, remove if you are not using ear deployments -->
 <mbean code="org.jboss.deployment.EARDeployer"
 name="jboss.j2ee:service=EARDeployer">
 <!-- A flag indicating if ear deployments should have their own scoped
 class loader to isolate their classes from other deployments.
 -->
 <attribute name="Isolated">true</attribute>
 <!-- A flag indicating if the ear components should have in VM call
 optimization disabled.
 -->
 <attribute name="CallByValue">true</attribute>
 </mbean>
</server>

This is all of my configrations. waitting for your response.

2. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

ourai Jun 15, 2005 12:20 AM (in response to ourai)

I fixed it by added the HSQLDB setting back.
It seems that I can not remove all of the HSQLDB setting so I ADD the oracle data source in the default hsqldb setting.
Actions
3. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jun 30, 2005 4:37 PM (in response to ourai)

How do you do it?
You set the Oracle tags in the hsqldb-service.xml file?
Actions
4. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

nusa Jun 30, 2005 6:39 PM (in response to ourai)

Leave the DefaultDS used by HSQL.
If your datasource is Oracle, just deploy oracle-ds.xml or oracle-xa-ds.xml, AND set the <jndi-name> to OracleDS, for example.
If your datasource is Sybase, deploy sybase-ds.xml AND set the <jndi-name> to SybaseDS, for example.

In anycase, DO NOT play around with DefaultDS/HSQL. You'll have trouble !
Actions
5. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jul 1, 2005 11:03 AM (in response to ourai)

I'll try and report!
Actions
6. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jul 1, 2005 11:20 AM (in response to ourai)

Sorry, but oracle-ds.xml?
Not oracle-service.xml?
Actions
7. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jul 1, 2005 11:25 AM (in response to ourai)

In which archive do I alter the DefaultDS?
Actions
8. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jul 1, 2005 11:30 AM (in response to ourai)

I have changed the archives, but I'm having this new error:
12:29:09,244 ERROR [LocalTxConnectionManager] Starting failed
org.jboss.deployment.DeploymentException: Could not bind ConnectionFactory into jndi: java:/OracleDS

What can it mean?
Actions
9. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

fechotecho Jul 1, 2005 11:47 AM (in response to ourai)

All resolved.
You need to delete hsqldb-service.xml, use oracle-service.xml and change all the DefaultDS to OracleDS, while changing drivers.

Thanks!
Actions

10. Re: JBoss4.0.2 + Oracle9i configration problem (Any successf

farooqrashed Jan 31, 2006 8:28 AM (in response to ourai)

Dear!!!

kindly send me the detailed document for setting data source and connection pooling in JBoss Appication server 4.0.3
it a great faviour for me, as soon as possible
waiting for reply
Thanks

"ourai" wrote:
I am challenging to build a JBoss4.0.2 + Oracle9i Application server, all of my *.war and *.ear files can be deployed in my configration and everything LOOKS like running well but,,, some error message of MBeans comes everytime when I start the JBoss server. Here is my server starting log :


==============================================
JBoss Bootstrap Environment
JBOSS_HOME: /export/home/jdev/develop/MASS/jboss
JAVA: /usr/java/bin/java
JAVA_OPTS: -server -Xms256M -Xmx512M -Dprogram.name=run.sh -Dmegabatch.home=/export/home/jdev/develop/MASS/projects/Mega
CLASSPATH: /export/home/jdev/develop/MASS/jboss/bin/run.jar:/usr/java/lib/tools.jar
==============================================
16:52:32,845 INFO [Server] Starting JBoss (MX MicroKernel)...
16:52:32,852 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
16:52:32,854 INFO [Server] Home Dir: /space/jdev/app-3/jboss-4.0.2
16:52:32,855 INFO [Server] Home URL: file:/space/jdev/app-3/jboss-4.0.2/
16:52:32,856 INFO [Server] Library URL: file:/space/jdev/app-3/jboss-4.0.2/lib/
16:52:32,861 INFO [Server] Patch URL: null
16:52:32,862 INFO [Server] Server Name: default
16:52:32,863 INFO [Server] Server Home Dir: /space/jdev/app-3/jboss-4.0.2/server/default
16:52:32,865 INFO [Server] Server Home URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/
16:52:32,866 INFO [Server] Server Data Dir: /space/jdev/app-3/jboss-4.0.2/server/default/data
16:52:32,867 INFO [Server] Server Temp Dir: /space/jdev/app-3/jboss-4.0.2/server/default/tmp
16:52:32,868 INFO [Server] Server Config URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/conf/
16:52:32,869 INFO [Server] Server Library URL: file:/space/jdev/app-3/jboss-4.0.2/server/default/lib/
16:52:32,870 INFO [Server] Root Deployment Filename: jboss-service.xml
16:52:32,885 INFO [Server] Starting General Purpose Architecture (GPA)...
16:52:35,629 INFO [ServerInfo] Java version: 1.5.0_03,Sun Microsystems Inc.
16:52:35,630 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_03-b07,Sun Microsystems Inc.
16:52:35,632 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
16:52:41,153 INFO [Server] Core system initialized
16:53:01,304 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
16:53:02,201 INFO [WebService] Using RMI server codebase: http://jakky:8083/
16:53:03,760 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0
, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
16:53:48,379 INFO [Embedded] Catalina naming disabled
16:53:53,795 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
16:53:53,807 INFO [Catalina] Initialization processed in 4327 ms
16:53:53,898 INFO [StandardService] Starting service jboss.web
16:53:53,920 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
16:53:54,254 INFO [StandardHost] XML validation disabled
16:53:54,815 INFO [Catalina] Server startup in 1007 ms
16:53:56,228 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default
/deploy/http-invoker.sar/invoker.war/
16:53:58,762 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
16:54:04,407 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default/t
mp/deploy/tmp35308jboss-ws4ee.war/
16:54:07,249 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/default/deploy
/jbossweb-tomcat55.sar/ROOT.war/
16:54:13,128 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/
default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
16:54:45,304 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/def
ault/deploy/management/console-mgr.sar/web-console.war/
16:54:52,773 INFO [MailService] Mail Service bound to java:/Mail
16:54:58,893 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-ha-local-jdbc.rar
16:55:01,263 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-ha-xa-jdbc.rar
16:55:03,484 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-local-jdbc.rar
16:55:05,654 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jboss-xa-jdbc.rar
16:55:08,192 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/jms/jms-ra.rar
16:55:10,121 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/space/jdev/app-3/jboss
-4.0.2/server/default/deploy/mail-ra.rar
16:55:17,320 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManag
er 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
16:55:18,627 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jbo
ss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
16:55:28,680 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/space/jdev/app-3/jboss-4.0.2/server/def
ault/deploy/jmx-console.war/
16:55:30,920 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

 --- 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

 ObjectName: jboss.mq.destination:service=Topic,name=testTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Queue,name=testQueue
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq.destination:service=Queue,name=A
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=B
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=C
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=D
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq.destination:service=Queue,name=ex
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager

 ObjectName: jboss.mq:service=Invoker
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=TracingInterceptor
 Depends On Me:
 jboss.mq:service=InvocationLayer,type=HTTP
 jboss.mq:service=InvocationLayer,type=JVM
 jboss.mq:service=InvocationLayer,type=UIL2

 ObjectName: jboss.mq:service=TracingInterceptor
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=SecurityManager
 Depends On Me:
 jboss.mq:service=Invoker

 ObjectName: jboss.mq:service=SecurityManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq:service=TracingInterceptor
 jboss.mq.destination:service=Queue,name=DLQ

 ObjectName: jboss.mq.destination:service=Queue,name=DLQ
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=DestinationManager
 jboss.mq:service=SecurityManager

 ObjectName: jboss.mq:service=InvocationLayer,type=JVM
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

 ObjectName: jboss.mq:service=DestinationManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=MessageCache
 jboss.mq:service=PersistenceManager
 jboss.mq:service=StateManager
 Depends On Me:
 jboss.mq.destination:service=Topic,name=testTopic
 jboss.mq.destination:service=Topic,name=securedTopic
 jboss.mq.destination:service=Topic,name=testDurableTopic
 jboss.mq.destination:service=Queue,name=testQueue
 jboss.mq.destination:service=Queue,name=A
 jboss.mq.destination:service=Queue,name=B
 jboss.mq.destination:service=Queue,name=C
 jboss.mq.destination:service=Queue,name=D
 jboss.mq.destination:service=Queue,name=ex
 jboss.mq:service=SecurityManager
 jboss.mq.destination:service=Queue,name=DLQ

 ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=Invoker

 --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
 ObjectName: jboss.mq:service=StateManager
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.mq:service=DestinationManager

16:55:32,581 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
16:55:33,431 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
16:55:33,488 INFO [JkMain] Jk running ID=0 time=0/149 config=null
16:55:33,545 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 3m:659ms

Go to original post