EZ on the colloquialism, hard on the eyes and brain! WL has never been able to do JMS clustering, no matter what its sales docs say. Hence you've found out that you must pin a JMS destination to a single server. Furthermore, you also may have discovered that an admin may NOT be part of a cluster. So you're stuck between a rock and a hard place! :-) No, actually you just need to know how BEA's JNDI tree behaves. Basically if you pin a service to one node in a cluster, it will be discovered by any entry point into the cluster. So your choices are to:
1) deploy JMSServer/Destination to a dedicated server outside of the managed cluster; the Admin is typically a good choice (although many folks don't like to deploy anything in Admin). Then your MDB will have to create a InitialContext with the t3://host:port of your ADMIN. 2) pin JMSServer/Destination to a single node in your cluster, then you can look up with your cluster t3:// address. However this does not mean your JMS destination is clustered, fail-overable, etc... Gene --- SasiDharma Tharmarajah <[EMAIL PROTECTED]> wrote: > Hi gurus, > > It will be g8 if somebody can guide me on how to implement this scenario > > I'm having 2 MDB bean in a cluster. I have 2 managed server m1 and m2 and a admin > server. > admin and 1 managed is residing in same machine whereas m2 is in different machine. > I've configured all the JMS Topics,Queues and JMS Servers in admin machine. > > I've deployed my application in both the managed servers and not in admin server. > Just > using the admin server to reroute the request only. > Here only i'm facing the problem. When my application is deployed MDB's are > complaining > that there is no destination found for the Topic declared in weblogic-ejb-jar.xml. > I figured out that since my JMSServer is deployed in Admin server it is unable to > find > topic. When i changed my JMSServer to be deployed in one of the managed server then > there is no problem. > Wht i wanted to know is > 1) Is there a way in weblogic-ejb-jar.xml to specify the MDB's to lookup the Topic or > Queue in a particular JNDI tree... > 2) Y is the JNDI tree objects are not reflected in the managed servers when they are > available in the AdminServer. Is there a way to configure the JNDI tree to be > reflected > in the managed servers. If so cud somebody tell me how to do it. > > Looking for a +ve response > > Thankz in advance > > r > sasi > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
