aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Help on Topic in JMS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Help on Topic in JMS " Watch "Help on Topic in JMS " New topic
Author

Help on Topic in JMS

Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
Hi All,

I need a little advise from you people, regarding Topic in JMS. I have a requirement where the publisher and the subscribers are on different servers.

The scenario is like this; the publisher is on one server and then there are three subscribers for that topic; these subscribers are on three different servers.

I have written three MDB for these 3 subscribers , Now my concern is how do i bound these MDBs to the Topic which is on some other server.


I am using JBOSS as my application server.

Thanks in advance
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Have a look at HowDoIConfigureAnMDBToTalkToARemoteQueue. Though the steps mentioned there are for a queue, it's going to be the same for a topic too.


[My Blog] [JavaRanch Journal]
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
Thanks jaikiran; but when i try doing what is mentioned on the web page i am getting javax.naming.NameNotFoundException.


Besides can anybody explain why do require this


Thanks in advance
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Originally posted by Neha Mohit:
but when i try doing what is mentioned on the web page i am getting javax.naming.NameNotFoundException.

Can you post the stacktrace? When does this exception occur?

Originally posted by Neha Mohit:
Besides can anybody explain why do require this




That's a configuration for the DeadLetterQueues
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
hello jaikiran,


I am pasting logs ; hope it is of some use


2007-10-09 17:21:50,307 INFO [org.jboss.ejb.EjbModule] Deploying TheRemoteQueue
2007-10-09 17:21:50,307 DEBUG [org.jboss.ejb.EjbModule] Creating WebClassLoader of class org.jboss.web.WebClassLoader
2007-10-09 17:21:50,323 DEBUG [org.jboss.ejb.EjbModule] creating binding for TheRemoteQueue:message-driven-bean
2007-10-09 17:21:50,338 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:jndiName=local/NewRequestQueue@21758581,service=EJB
2007-10-09 17:21:50,338 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: []
2007-10-09 17:21:50,495 DEBUG [org.jboss.ejb.MessageDrivenContainer] Creating jboss.j2ee:jndiName=local/TheRemoteQueue@6527406,service=EJB
2007-10-09 17:21:50,541 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying mdb.jar
2007-10-09 17:21:50,541 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.0.4.GA/server/other-instance/deploy/mdb.jar
2007-10-09 17:21:50,541 DEBUG [org.jboss.ws.server.WebServiceDeployerEJB21] start: file:/C:/jboss-4.0.4.GA/server/other-instance/deploy/mdb.jar
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.EJBDeployer] start application, deploymentInfo: org.jboss.deployment.DeploymentInfo@9a27c500 { url=file:/C:/jboss-4.0.4.GA/server/other-instance/deploy/mdb.jar }
deployer: MBeanProxyExt[jboss.ejb:service=EJBDeployer]
status: Starting
state: START_DEPLOYER
watch: file:/C:/jboss-4.0.4.GA/server/other-instance/deploy/mdb.jar
altDD: null
lastDeployed: 1191930709276
lastModified: 1191930709260
mbeans:
jboss.j2ee:jndiName=local/NewRequestQueue@21758581,service=EJB state: Created
jboss.j2ee:jndiName=local/SubmitRequestNotifyQueue@86176,service=EJB state: Created
jboss.j2ee:jndiName=local/SubmitRequestTransformQueue@9246537,service=EJB state: Created
jboss.j2ee:jndiName=local/TheRemoteQueue@6527406,service=EJB state: Created
, short name: mdb.jar, parent short name: null
2007-10-09 17:21:50,541 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EjbModule,module=mdb.jar
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.EjbModule] Starting jboss.j2ee:service=EjbModule,module=mdb.jar
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.EjbModule] startService, starting container: NewRequestQueue
2007-10-09 17:21:50,541 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:jndiName=local/NewRequestQueue@21758581,service=EJB
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.MessageDrivenContainer] Starting jboss.j2ee:jndiName=local/NewRequestQueue@21758581,service=EJB
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.MessageDrivenContainer] Begin java:comp/env for EJB: NewRequestQueue
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.MessageDrivenContainer] TCL: org.jboss.util.loading.DelegatingClassLoader@94a28e
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.MessageDrivenContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.MessageDrivenContainer] End java:comp/env for EJB: NewRequestQueue
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.plugins.local.BaseLocalProxyFactory] NewRequestQueue cannot be Bound, doesn't have local and local home interfaces
2007-10-09 17:21:50,541 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EJB,plugin=pool,jndiName=local/NewRequestQueue@21758581
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.plugins.MessageDrivenInstancePool] Starting jboss.j2ee:service=EJB,plugin=pool,jndiName=local/NewRequestQueue@21758581
2007-10-09 17:21:50,541 DEBUG [org.jboss.ejb.plugins.MessageDrivenInstancePool] Started jboss.j2ee:service=EJB,plugin=pool,jndiName=local/NewRequestQueue@21758581
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/DefaultJMSProvider
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@18b492
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@c4cee
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection: Connection@21506279[token=ConnectionToken:null/4463e685287780f3c2282912a708be9c rcvstate=STOPPED]
2007-10-09 17:21:50,901 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: QUEUE.DLQ
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@755866
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: SubmitRequestNotifyQueue
2007-10-09 17:21:50,901 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for SubmitRequestNotifyQueue
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX): org.jboss.jms.asf.StdServerSessionPool@554189, SpySession@17095030[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], SpySession@17095030[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], true
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] added server session to the pool: org.jboss.jms.asf.StdServerSession@161100c
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] initializing with connection: Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX): org.jboss.jms.asf.StdServerSessionPool@554189, SpySession@23370522[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], SpySession@23370522[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], true
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] added server session to the pool: org.jboss.jms.asf.StdServerSession@2e879
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] initializing with connection: Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX): org.jboss.jms.asf.StdServerSessionPool@554189, SpySession@15504449[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], SpySession@15504449[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], true
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] added server session to the pool: org.jboss.jms.asf.StdServerSession@1f95cce
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSessionPool] initializing with connection: Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]
2007-10-09 17:21:50,916 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX): org.jboss.jms.asf.StdServerSessionPool@554189, SpySession@3926741[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], SpySession@3926741[tx=true txid=null XA RUNNING connection=Connection@33469350[token=ConnectionToken:ID:3/279545f0fd26a218a108e98909825859 rcvstate=STOPPED]], true
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.MessageDrivenContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.MessageDrivenContainer] End java:comp/env for EJB: TheRemoteQueue
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.local.BaseLocalProxyFactory] TheRemoteQueue cannot be Bound, doesn't have local and local home interfaces
2007-10-09 17:21:50,948 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EJB,plugin=pool,jndiName=local/TheRemoteQueue@6527406
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.MessageDrivenInstancePool] Starting jboss.j2ee:service=EJB,plugin=pool,jndiName=local/TheRemoteQueue@6527406
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.MessageDrivenInstancePool] Started jboss.j2ee:service=EJB,plugin=pool,jndiName=local/TheRemoteQueue@6527406
2007-10-09 17:21:50,948 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.j2ee:service=EJB,plugin=pool,jndiName=local/TheRemoteQueue@6527406 dependent components: []
2007-10-09 17:21:50,948 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionInterceptor] start called in CachedConnectionInterceptor
2007-10-09 17:21:50,948 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EJB,plugin=invoker,binding=message-driven-bean,jndiName=local/TheRemoteQueue@6527406
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Starting jboss.j2ee:service=EJB,plugin=invoker,binding=message-driven-bean,jndiName=local/TheRemoteQueue@6527406
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/DefaultJMSProvider
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@18b492
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@c4cee
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection: Connection@15701285[token=ConnectionToken:null/03c62d2c8f4035914daa4ac0cedc89ad rcvstate=STOPPED]
2007-10-09 17:21:50,948 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: QUEUE.DLQ
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@128e909
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: TheRemoteQueue
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for TheRemoteQueue
2007-10-09 17:21:50,948 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory: org.jboss.mq.SpyXAConnectionFactory@c4cee
2007-10-09 17:21:50,948 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/-- not shown --
2007-10-09 17:21:50,948 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created XAQueueConnection: Connection@5680378[token=ConnectionToken:null/85c6675bd818c227c0347925642373fb rcvstate=STOPPED]
2007-10-09 17:21:50,948 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
2007-10-09 17:21:50,963 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destination not found: queue/TheRemoteQueue reason: javax.naming.NameNotFoundException: TheRemoteQueue not bound




Thanks in advance
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
I am pasting the code so you can have a better picture




[B]The JMSMessageSender is on default instance of Jboss running on port 8080
The Deployment Descriptor for mdb is on an other instance of JBOSS on the same system[/B]







Regards

[ October 09, 2007: Message edited by: Neha Mohit ]
[ October 09, 2007: Message edited by: Neha Mohit ]
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Havent yet gone through the code completely, but the contents of jms-ds.xml dont look right:

The entry in jms-ds.xml



The server (=anyName) and the localhost (both marked in bold) should point to the remote JBoss server which has the remote queue deployed.
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
As told by you; now they both point to default




still on the console i get the error

INFO [EjbModule] Deploying TheRemoteQueue
WARN [JMSContainerInvoker] destination not found: queue/TheRemoteQueue reason: javax.naming.NameNotFoundException: TheRemoteQueue not bound
WARN [JMSContainerInvoker] creating a new temporary destination: queue/TheRemoteQueue
[TheRemoteQueue] Bound to JNDI name: queue/TheRemoteQueue

Actually the MDB and the Sender are not on two servers; rather they are on two instances of the same jboss.

Sender with provider url as jnp://localhost:1099 on default instance
and
MDB on provider URL as jnp://localhost:11099 other-instance .

Hope this makes sense Thanks in advance
[ October 09, 2007: Message edited by: Neha Mohit ]
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Originally posted by Neha Mohit:
As told by you; now they both point to default



I guess i should have been more clear Sorry about that.


Originally posted by Jaikiran Pai:
The server (=anyName) and the localhost (both marked in bold) should point to the remote JBoss server which has the remote queue deployed.


What i meant was you should change those values to the machine name/IP address of the remote JBoss server on which the queue is deployed. Let's take an example. Let's say i have the remote queue deployed on a machine named ps1123 and the MDB is deployed on a machine(within the same network) named ps1190. So my jms-ds.xml should look like(see the values marked in bold, replace them with the machinename/IP address of the remote JBoss server):

Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Furthermore, make these changes to the files ONLY on ps1190 (the system on which MDB is deployed).
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
No; its not working. I tried with my system's IP as well as by its name. As asked by you.


Regards
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Have you deployed the queue/TheRemoteQueue on the remote system? How have you done that? Can you post the configuration file for that? Also, some snippet of logs from the remote server which says that TheRemoteQueue is bound.
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
Originally posted by Jaikiran Pai:
Have you deployed the queue/TheRemoteQueue on the remote system? How have you done that? Can you post the configuration file for that? .



Sorry if i am not wrong; i think the remoteQueue will be on the system which has the sender and not on the system which has the mdb.

please find the logs below ; if it is



The entry in jboss-mq-destinations-service.xml is

<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=MyRemoteQueue">
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
</mbean>


Hope this is what you asked for


Regards

[ October 09, 2007: Message edited by: Neha Mohit ]
[ October 09, 2007: Message edited by: Neha Mohit ]
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Sorry if i am not wrong; i think the remoteQueue will be on the system which has the sender and not on the system which has the mdb.


You are correct.

2007-10-09 19:44:15,309 INFO [org.jboss.mq.server.jmx.Queue.MyRemoteQueue] Bound to JNDI name: queue/MyRemoteQueue


The logs also show that the queue is bound to "queue/MyRemoteQueue". However, i am confused as to why we see the log:

WARN [JMSContainerInvoker] destination not found: queue/TheRemoteQueue reason: javax.naming.NameNotFoundException: TheRemoteQueue not bound


Had you modified the log to change MyRemoteQueue to TheRemoteQueue? Or is this the actual log?
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
no i have not modified the logs if you look my previous posts the deployment descriptor for mdb ; i have given as



Is this wrong
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

INFO [EjbModule] Deploying TheRemoteQueue
WARN [JMSContainerInvoker] destination not found: queue/TheRemoteQueue reason: javax.naming.NameNotFoundException: TheRemoteQueue not bound
WARN [JMSContainerInvoker] creating a new temporary destination: queue/TheRemoteQueue
[TheRemoteQueue] Bound to JNDI name: queue/TheRemoteQueue


These logs are strange because the MDB is being made to listen to queue/TheRemoteQueue instead of queue/MyRemoteQueue.

But, i guess, i got what the problem is. The jboss.xml file present in the META-INF folder of your application is being ignored (a sample test on my local setup proved that when this file is ignored, the MDB will be bound to a queue whose name will be the same as the ejb-name).
Few reasons why the jboss.xml is being ignored:
1) The jboss.xml file is not present in the META-INF folder of the ejb jar (it should be at the same place as ejb-jar.xml)
2) The contents of the file are incorrect (may not be following the dtd). Can you post the entire contents of this file?
[ October 09, 2007: Message edited by: Jaikiran Pai ]
Shailesh Kini
Ranch Hand

Joined: Oct 17, 2001
Posts: 153
Hi Neha,

Are you using annotations by any chance?


Shailesh Kini.
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
Originally posted by Jaikiran Pai:


1) The jboss.xml file is not present in the META-INF folder of the ejb jar (it should be at the same place as ejb-jar.xml)


yes it is not present ; i have not written that file only.


Have modified my deployment descriptor

Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Neha,

The queue name and some of the other stuff for the MDB should be specified in a jboss.xml file and not ejb-jar.xml. This is shown in step "3. Configure the MDB" in the wiki entry that i posted in my first reply. Here's an extract from the wiki:

Finally use the invoker proxy binding for your MDB in jboss.xml.
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
Sorry,

I will make sure; i dont repeat this again; but first let me test ; how things goes now.


Thanks
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Originally posted by Neha Mohit:
Sorry,

I will make sure; i dont repeat this again;


No problem
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
I know it is most stupid thing to paste the full logs ; but i am completely lost Whats wrong now

All i can understand it it still doing the jndi lookup on the local machine , but again why




regards
[ October 10, 2007: Message edited by: Neha Mohit ]
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10048
    
163

Neha,

Before going through the log file, i would help if you post the exact contents of your ejb-jar.xml and the jboss.xml.
Neha Mohit
Ranch Hand

Joined: Apr 25, 2006
Posts: 87
sorry for being late; here what you asked for

Entry in jboss-ds.xml


where this 16.19.138.273 is my server ip

Entry in standardjboss.xml



Entry in ejb-jar.xml




Entry in jbossmq-destinations-service.xml on remote system


Even after doing this ; why the MDB is getting bound to the local system rather than remote

Thanks in advance
neha
[ October 23, 2007: Message edited by: Neha Mohit ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Help on Topic in JMS