[stephanenicoll]

Can you AT LEAST read the log file before posting? You'll see that the JMS is not started properly. Don't you think it's useless to check your client if the server is not ready to receiver your requests?

Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@ac42209b{ url=file:/E:/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/hsqldb-ds.xml, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: exception in init of file:/E:/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/hsqldb-ds.xml; - nested throwable: (org.jboss.deployment.DeploymentException: Problem with xsl transformation; - nested throwable: (javax.xml.transform.TransformerException: XSL-1103: (Fatal Error) DOMResult can not be this kind of node.))

check the server/default/deploy/hsqldb-ds.xml which contains the HSQL configuration. This file seems to be broken.

By default JMS uses HSQL as persistence manager, that's why it's not deployed correctly

Regards,

Stephane

[basem_musa]

Dear Stephane,
I removed the coflict and the hsqldb-ds.xml is no longer gives any error messages. but now when I start the jboss server this error appears in the server log :

Cause: Incomplete Deployment listing:
Packages waiting for a deployer:

Incompletely deployed packages:

MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.mq.destination:service=Queue,name=HomesEmailQueue
state: FAILED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: javax.management.InstanceNotFoundException: null object name]

for the my-service.xml:

jboss.mq:service=DestinationManager


yours...

[basem_musa]

hi stephane,
I replace the above with the following and it works successfully...


<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



thax alot stephane... but one last question, when I put a message in a queue, how can I review it. is there any tool for jms which can help me out in tracing purposes...

Yours....

[stephanenicoll]

Review, meaning browse it? The JMS Specification has a QueueBrowser notion. With that you can browse a queue and see (read only) the messages which are on a queue.

At JBoss level, the JMX console can tell you how many messages are pending in a specific destination.

Regards,

Stephane

[basem_musa]

Hi stephane,
I saw the jmx console, there I can see my queue and see how many messages are there, but I still can't reach my messages to view them...

Yours...

[stephanenicoll]

You can't. I never told you it was possible through the JMX console. As far as I know you have to write your own components for this.

A colleague writes an MBean which is able to read Text and Object message. I can ask him if he aggress to post his code

Regards,

Stephane

[basem_musa]

thax Stepane...
I like you....

Yourse....