Toyan Harvey

Thank You

Alrighty, so this problem appears to be a configuring issue in the weblogic server. The server the MDB is on has to know where the queues are. You can configure this throught the admin console ->system mod->foreign server. Now to figure out how to configure this correctly...

Any experts out there in this area? I'm confused on what goes in the JNDI Properties and JNDI Properties Credentials.

Any help would be appreciated.

Thanks

Hey guys,
I'm trying to find some documentation on how to set up an MDB to listen to a remote queue. The following is a snippet from my mdb:

@MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue="QCF"), @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue="inQueue"), @ActivationConfigProperty(propertyName = "addressList", propertyValue="t3://localhost:9001") //didn't work :( }, mappedName = "inQueue")

Any help would be appreciated
Thanks

Hey guys, I've seen posts about this error but it appears I'm doing everything correct. The url i'm sending to get the context of the server is "t3://xxx.xxxx.xxxx.xxxx:7001".

I may be confused on what I'm doing. I have 2 weblogic servers (2 different machines). A web app on one and a MDB on the other. In the webapp I want to send a message to one of the mdb server jms queues. When I send the url to my get context method I get the following exception

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://172.16.85.37:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination]

Anyone have any ideas on what I should check out to debug this problem.

Thanks