aspose file tools*
The moose likes BEA/Weblogic and the fly likes JNDI Lookup using T3 Protocol Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "JNDI Lookup using T3 Protocol" Watch "JNDI Lookup using T3 Protocol" New topic
Author

JNDI Lookup using T3 Protocol

Tushar Ojha
Greenhorn

Joined: Apr 14, 2007
Posts: 6
HI,

There are two managed servers(on port 9002 and 9003 respectively) and one proxy server(on port 9001) configured in single domain(named EJB-Domain) on BEA Weblogic Server 9.2. The EJB Module is deployed on both the managed servers.

I am trying to lookup EJB from a WAR module deployed on another domain (named WAR-Domain) running in a different machine using JNDI lookup by the EJB-Domain proxy server port no, which is giving the javax.naming.NameNotFoundException,

I guess the error is due to the fact that the proxy server do not contains the jndi names of ejbs in it's registry as the target is not set to proxy server

Is there a way to make some server configuration so that the lookup will be made through proxy server port to the managed server JNDI registry.

Code snippet is as below for EJB lookup from the WAR Module running in different domain and T3 protocol has been used.
---------------------------------------------------------------
String host="xxx.xxx.xxx.xxx"; // EJB-Domain IP address
String port="9001"; // proxy server Port

Object object =jndiMap.get(jndiName);
if(object==null) {
try {

Context context=getInitialContext("t3://" + host + ":" + port);
object = context.lookup(jndiName);

jndiMap.put(jndiName,object);
}catch(Exception ex){
ex.printStackTrace();
throw ex;
}
---------------------------------------------------------------


Thanks in Advance
 
Don't get me started about those stupid light bulbs.
 
subject: JNDI Lookup using T3 Protocol