Hi I am using JBoss-4.0.1 on Windows Xp and MySQL.
On starting up my Jboss, I get errors using/configuring DestinationManager and
I get the following to the console:
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\my_nueces\dist\jboss\jboss-4.0.1\bin\\..
.
JAVA: C:\java\j2sdk1.4.2_04\bin\java
.
JAVA_OPTS: -Xms128m -Xmx960m -Dprogram.name=run.bat -Xms128m -Xmx512m
.
CLASSPATH:
C:\java\j2sdk1.4.2_04\lib\tools.jar;C:\my_nueces\dist\jboss\jboss-4.0.1\bin\\run.jar
.
===============================================================================
.
17:01:23,845 INFO [Server] Starting JBoss (MX MicroKernel)...
17:01:23,845 INFO [Server] Release ID: JBoss [Zion] 4.0.1 (build:
CVSTag=JBoss_4_0_1 date=200412230944)
17:01:23,845 INFO [Server] Home Dir: C:\my_nueces\dist\jboss\jboss-4.0.1
17:01:23,845 INFO [Server] Home URL: file:/C:/my_nueces/dist/jboss/jboss-4.0.1/
17:01:23,845 INFO [Server] Library URL:
file:/C:/my_nueces/dist/jboss/jboss-4.0.1/lib/
17:01:23,845 INFO [Server] Patch URL: null
17:01:23,845 INFO [Server] Server Name: myapplication
17:01:23,845 INFO [Server] Server Home Dir:
C:\my_nueces\dist\jboss\jboss-4.0.1\server\myapplication
17:01:23,845 INFO [Server] Server Home URL:
file:/C:/my_nueces/dist/jboss/jboss-4.0.1/server/myapplication/
17:01:23,855 INFO [Server] Server Data Dir:
C:\my_nueces\dist\jboss\jboss-4.0.1\server\myapplication\data
17:01:23,855 INFO [Server] Server Temp Dir:
C:\my_nueces\dist\jboss\jboss-4.0.1\server\myapplication\tmp
17:01:23,855 INFO [Server] Server Config URL:
file:/C:/my_nueces/dist/jboss/jboss-4.0.1/server/myapplication/conf/
17:01:23,855 INFO [Server] Server Library URL:
file:/C:/my_nueces/dist/jboss/jboss-4.0.1/server/myapplication/lib/
17:01:23,855 INFO [Server] Root Deployment Filename: jboss-service.xml
17:01:23,855 INFO [Server] Starting General Purpose Architecture (GPA)...
17:01:24,225 INFO [ServerInfo] Java version: 1.4.2_04,Sun Microsystems Inc.
17:01:24,225 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM
1.4.2_04-b05,Sun Microsystems Inc.
17:01:24,225 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
17:01:24,476 INFO [Server] Core system initialized
17:01:27,901 INFO [Log4jService$URLWatchTimerTask] Configuring from URL:
resource:log4j.xml
17:01:30,184 ERROR [DestinationManager] Starting failed
jboss.mq:service=DestinationManager
RuntimeOperationsException: null Cause: java.lang.IllegalArgumentException:
null object name
at
org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:495)
at
org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:533)
at
org.jboss.mq.server.jmx.DestinationManager.startService(DestinationManager.java:345)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
..........
..........
...........
17:01:30,354 WARN [ServiceController] Problem starting service
jboss.mq:service=DestinationManager
java.lang.IllegalArgumentException: null object name
at
org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:495)
at
org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:533)
at
org.jboss.mq.server.jmx.DestinationManager.startService(DestinationManager.java:345)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
..........
..........
...........
Depends On Me:
ObjectName: jboss.mq:service=Invoker
state: CREATED
I Depend On: jboss.mq:service=TracingInterceptor
Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
ObjectName: jboss.mq:service=TracingInterceptor
state: CREATED
I Depend On: jboss.mq:service=DestinationManager
Depends On Me: jboss.mq:service=Invoker
ObjectName: jboss.mq:service=SecurityManager
state: CREATED
I Depend On: jboss.mq:service=DestinationManager
Depends On Me: jboss.mq.destination:name=com.myapplication.event,service=Topic
jboss.mq.destination:name=DLQ,service=Queue
ObjectName: jboss.mq:service=DestinationManager
state: FAILED
I Depend On: jboss.mq:service=StateManager
Depends On Me: jboss.mq.destination:name=com.myapplication.event,service=Topic
jboss.mq:service=TracingInterceptor
jboss.mq:service=SecurityManager
jboss.mq.destination:name=DLQ,service=Queue
java.lang.IllegalArgumentException: null object name
ObjectName: jboss.mq:service=PersistenceManager
state: CONFIGURED
I Depend On: jboss.jca:name=DefaultDS,service=LocalTxCM
Depends On Me:
ObjectName: jboss.mq.destination:name=DLQ,service=Queue
state: CREATED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
Depends On Me:
ObjectName: jboss.jca:name=MyDs,service=LocalTxCM
state: CONFIGURED
I Depend On: jboss.jca:name=MyDs,service=ManagedConnectionPool
jboss.jca:service=CachedConnectionManager
jboss:service=TransactionManager
Depends On Me: jboss.jca:name=MyDs,service=DataSourceBinding
ObjectName: jboss.jca:name=MyDs,service=ManagedConnectionPool
state: CONFIGURED
I Depend On: jboss.jca:name=MyDs,service=ManagedConnectionFactory
Depends On Me: jboss.jca:name=MyDs,service=LocalTxCM
ObjectName: jboss.jca:name=MyDs,service=ManagedConnectionFactory
state: CONFIGURED
I Depend On: jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment
Depends On Me: jboss.jca:name=MyDs,service=ManagedConnectionPool
ObjectName: jboss.jca:name=MyDs,service=DataSourceBinding
state: CONFIGURED
I Depend On: jboss.jca:name=MyDs,service=LocalTxCM
jboss:service=invoker,type=jrmp
Depends On Me:
ObjectName: jboss.jca:name=DefaultDS,service=LocalTxCM
state: CONFIGURED
I Depend On: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss:service=TransactionManager
Depends On Me: jboss.mq:service=PersistenceManager
jboss.jca:name=DefaultDS,service=DataSourceBinding
ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
state: CONFIGURED
I Depend On: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
Depends On Me: jboss.jca:name=DefaultDS,service=LocalTxCM
ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
state: CONFIGURED
I Depend On: jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment
Depends On Me: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
ObjectName: jboss.jca:name=DefaultDS,service=DataSourceBinding
state: CONFIGURED
I Depend On: jboss.jca:name=DefaultDS,service=LocalTxCM
jboss:service=invoker,type=jrmp
Depends On Me:
ObjectName: jboss.j2ee:jndiName=PackageBeanLocal,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: Error: can't find
data source: java:/MyDs; - nested throwable:
(javax.naming.NameNotFoundException: MyDs not bound
)
ObjectName: jboss.j2ee:jndiName=PackageBeanLocal,plugin=pool,service=EJB
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:jndiName=PackageMaintenanceHistoryBean,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: Error: can't find
data source: java:/MyDs; - nested throwable:
(javax.naming.NameNotFoundException: MyDs not bound
)
ObjectName:
jboss.j2ee:jndiName=PackageMaintenanceHistoryBean,plugin=pool,service=EJB
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:jndiName=FileBean,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: Error: can't find
data source: java:/MyDs; - nested throwable:
(javax.naming.NameNotFoundException: MyDs not bound
)
ObjectName: jboss.j2ee:jndiName=FileBean,plugin=pool,service=EJB
state: CREATED
I Depend On:
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.j2ee:jndiName=PackageMaintenanceHistoryBean,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: Error: can't find
data source: java:/MyDs; - nested throwable:
(javax.naming.NameNotFoundException: MyDs not bound
)
ObjectName: jboss.j2ee:jndiName=FileBean,plugin=pool,service=EJB
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:jndiName=PackageBeanLocal,plugin=pool,service=EJB
state: CREATED
**************************************************************
***********************
jbossmq-service.xml
--------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: jbossmq-service.xml,v 1.3 2003/12/09 15:18:00 dvalys Exp $ -->
<!-- ==================================================================== -->
<!-- JBossMQ -->
<!-- ==================================================================== -->
<!-- ==================================================================== -->
<!-- Invocation Layers -->
<!-- ==================================================================== -->
<!--
| InvocationLayers are the different transport methods that can
| be used to access the server.
-->
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
java:/ConnectionFactory
java:/XAConnectionFactory
0
<!--
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
RMIConnectionFactory
RMIXAConnectionFactory
60000
-->
<!--
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
ConnectionFactory
XAConnectionFactory
8090
60000
true
-->
<!--
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
UILConnectionFactory
UILXAConnectionFactory
8091
-->
<!-- FIXME: ping disabled because of deadlock problem -->
<!--
0
-->
<!-- 60000 -->
<!--
true
-->
<!--
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
OIL2ConnectionFactory
OIL2XAConnectionFactory
8092
60000
true
-->
<!--
New Unified Invocation Layer as of 3.0.7 - experimental
Synchronization moved to the message level to improve throughput
-->
<!--
<depends optional-attribute-name="Invoker">jboss.mq:service=Invoker
UIL2ConnectionFactory
UIL2XAConnectionFactory
8093
60000
true
-->
<!-- Used to disconnect the client if there is no activity -->
<!-- Ensure this is greater than the ping period -->
<!--
70000
-->
<!-- The size of the buffer (in bytes) wrapping the socket -->
<!-- The buffer is flushed after each request -->
<!--
2048
-->
<!-- Large messages may block the ping/pong -->
<!-- A pong is simulated after each chunk (in bytes) for both reading and
writing -->
<!-- It must be larger than the buffer size -->
<!--
1000000
-->
<!--
| The HTTP IL is configured in the deploy directory and available by
| default in both the "default" and "all" server configurations. To
customize
| its attributes please see the jboss-service.xml file included in
| the META-INF directory of jbossmq-httpil.sar directory. The rationale
| for not including its configuration here is due to the fact that it
| includes a required dependant web module which would have required
| a stand alone WAR file. It was elected, therefore, to put everything
| in the deploy directory.
-->
<!-- ==================================================================== -->
<!-- JBossMQ Interceptor chain configuration -->
<!-- ==================================================================== -->
<!-- To tune performance, you can have the Invoker skip over the
TracingInterceptor -->
<!-- and/or the SecurityManager, but then you loose the ability to trace
and/or enforce security. -->
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=TracingInterceptor
org.jboss.mq.server.TracingInterceptor
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager
<!--
| The ClientMonitorInterceptor disconnects clients that have been idle for
to long.
| This interceptor is not enabled by default since the server might
disconnect clients
| when the it is under high load.
-->
<!--
80000
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=ClientReconnectInterceptor
-->
<!--
| The ClientReconnectInterceptor is used to allow a client to connect to
the server even
| if it's clientID is allready being used by another client. This
interceptor will disconnect
| the previously connected client to allow the new connection to succeed.
This is not enabled
| by default since the JMS spec states that the 2nd client connecting to
the server with the same
| id should get an exception.
-->
<!--
org.jboss.mq.server.ClientReconnectInterceptor
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager
-->
<!-- Manne <depends
optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager
-->
<depends
optional-attribute-name="StateManager">jboss.mq:service=StateManager
<!-- ****** Manne -->
<!-- <depends
optional-attribute-name="MessageCache">jboss.mq:service=MessageCache -->
<!-- ****** Manne code ends -->
<!--
| The MessageCache decides where to put JBossMQ message that
| are sitting around waiting to be consumed by a client.
|
| The memory marks are in Megabytes. Once the JVM memory usage hits
| the high memory mark, the old messages in the cache will start getting
| stored in the DataDirectory. As memory usage gets closer to the
| Max memory mark, the amount of message kept in the memory cache
aproaches 0.
|
| ATTENTION: When the "file" or "rollinglogged" Persistence Manager is used
| you have to set the "CacheStore" to the CacheStore (the commented out
line)
| and not to the PM itself.
-->
500
600
<!-- <depends
optional-attribute-name="CacheStore">jboss.mq:service=CacheStore -->
jboss.mq:service=PersistenceManager
<!--
| The CacheStore decides where to store JBossMQ message that
| that the MessageCache has decided to move in secondary storage.
|
| Now you can specify a absolut path by using an ULR like:
| file:///c:/temp
| ATTENTION: the directory MUST exists because it will not be
| created.
-->
<!-- Manne
tmp/jbossmq
-->
<!--
| The StateManager is used to keep JMS persistent state data.
| For example: what durable subscriptions are active.
-->
<!-- This file is pulled from the configuration URL of the server -->
jbossmq-state.xml
<!--
| The PersistenceManager is used to store messages to disk.
|
| Now you can specify a absolut path by using an ULR like:
| file:///c:/temp
| ATTENTION: the directory MUST exists because it will not be
| created. Also for the "file" Persistance Manager the directory
| MUST be empty otherwise the startup fails ("rollinglogged" works
| fine.
-->
<!--
-->
<!-- Manne commented this data/jbossmq/file -->
<!-- <depends
optional-attribute-name="MessageCache">jboss.mq:service=MessageCache
-->
<!--
| The jdbc2 PersistenceManager is the new improved JDBC implementation.
| This implementation allows you to control how messages are stored in
| the database.
|
| Use this PM if you want the reliablity a relational database can offer
| you. The default configuration is known to work with hsqldb, other
databases
| will requrie teaking of the SqlProperties.
-->
<!-- Manne <depends
optional-attribute-name="MessageCache">jboss.mq:service=MessageCache -->
<depends
optional-attribute-name="ConnectionManager">jboss.jca:service=LocalTxCM,name=DefaultDS
BLOB_TYPE=OBJECT_BLOB
INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION,
MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES
WHERE DESTINATION=?
SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE
MESSAGEID=? AND DESTINATION=?
MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=?
AND DESTINATION=?
UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=?
AND DESTINATION=?
UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE
TXOP=?
UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=?
WHERE TXOP=? AND TXID=?
DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN
(SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?
DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND
DESTINATION=?
CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT
NULL, \
DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )
CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )
<!-- ==================================================================== -->
<!-- System Destinations -->
<!-- ==================================================================== -->
<!-- Dead Letter Queue -->
<depends
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends
optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
===========================================
Can anybody help me where I am wrong...
Thanks in Advance
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866721#3866721
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866721
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
