WL 4.5.1 JNDI defaults,JNDI lookup with multiple environments etc..

The WL4.5 docs, state that if "java.naming.provider.url" is not
explicitly provided
(either during the JVM start or in the InitialContext), the WL will
default to
"t3://localhost:7001".
Q1) If server is listening on a different port, shouldn't we explicitly
specify the
"-Djava.naming.provider.url=t3://theServerIP:theServerPort" during the
WL JVM
start-up. If we don't, how would the naming lookup work, when there is
no naming
service on the "localhost:7001"
In the real life, usually there are several (usually identical) copies
of the WL server
instances running in (DEV/TEST/QUAL environments. Assume that all
servers are
on the same network and have the same EJBs deployed (using the same home
names).
Q2) Does each WL instance have its own naming service running? (assume
yes)
Q3) If no WL instances listen on 7001, what happens with Q1?
Q4) If client specifically sets the TEST server IP:port for the
"java.naming.provider.url", would TEST naming service first lookup its
own tree and
then, if object does not exist ask other naming services (assume yes ...
how is this
set-up, how do the WL naming services discover each other)
Q5) How many naming services would run if all WL instances are running
on the
same machine using different listen ports? (assume N)
Darko Bohinc
Consultant - Synergy International Limited
Level 7, Synergy House, 131 Queen Street, PO Box 7445 Wellesley Street,
Auckland, NZ
Phone: +64 9 3772400
Fax: +64 9 3772444
URL: http://www.synergy.co.nz

No,version 4.5 is built to the 1.1 API.
Version 1.5 is updated to JNDI 1.2.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
<[email protected]> wrote in message news:[email protected]..
Hi All
I have been using WL 4.5.1 for a while with JNDI 1.1.2 which are
included in weblogicaux.jar.
Can I use JNDI 1.2.1 with WL 4.5.1 by overriding the default 1.1.2 ?
If so, how do I do it?
Thanks
Madhu

Similar Messages

Anyone knows how to do JNDI lookup with OracleAQ?

Hi all;
Can anybody point me some guide/idea on how to implement JNDI lookup with OracleAQ?
(Creating connectionFacotry , parameters for "java.naming.factory.initial", java.naming.provider.url etc..)
Thanks
-Ratha
Edited by: Ratha on Sep 27, 2011 3:50 AM

import javax.naming.*;
import javax.naming.directory.*;
import java.util.Properties;
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, PROVIDER_URL);
env.put(Context.SECURITY_PRINCIPAL, JNDI_USER);
env.put(Context.SECURITY_CREDENTIALS, JNDI_PWD);
InitialContext = new InitialDirContext(env);
where JNDI_USER is the userid If ACL is configured at the JNDI server
where JNDI_PWD is the password If ACL is configured at the JNDI server
Context.INITIAL_CONTEXT_FACTORY is the initial Context factory and depends on ur JNDI service provider.
PROVIDER_URL is the url of the JNDI server containing protocol/ip/port
Hope it helps
-aseem

JNDI lookup with DNS

Hi all,
we are using 2 weblogic 5.1 servers (not clustered) for
our load balancing solution. In our client applications,
we use a hostname against a DNS for the JNDI lookups for our
RMI objects deployed on the 2 weblogic servers.
Ideally, a round-robin load balancing is expected.
But in reality, all the lookups are sticking to one of our
servers until we restart our client applications. The
lookups may switch to another. In our applications,
we are making many subsequent RMI lookup using JNDI.
We would like to spread the remote method invocation
between our 2 servers. How can we integrate with the
DNS? We have proved that the DNS will return the
IP addresses of the 2 weblogic in round-robin manner.
thanks!
cheers,
Kenneth
[email protected]

Ken,
What client are you using? We had the same problem when we switched from
Windows NT to Windows 2000 clients. Round-robin worked fine in NT and by
default got "stuck" when we tried it from Win 2000 client. There is a
setting in the network properties on Win 2000 to "unstick" that will fix the
problem, if this is the setup you have?
Bart Jenkins, Globeflow SA
[email protected]
"Kenneth Yue" <[email protected]> wrote in message
news:3bb09863$[email protected]..
>
>
Hi all,
we are using 2 weblogic 5.1 servers (not clustered) for
our load balancing solution. In our client applications,
we use a hostname against a DNS for the JNDI lookups for our
RMI objects deployed on the 2 weblogic servers.
Ideally, a round-robin load balancing is expected.
But in reality, all the lookups are sticking to one of our
servers until we restart our client applications. The
lookups may switch to another. In our applications,
we are making many subsequent RMI lookup using JNDI.
We would like to spread the remote method invocation
between our 2 servers. How can we integrate with the
DNS? We have proved that the DNS will return the
IP addresses of the 2 weblogic in round-robin manner.
thanks!
cheers,
Kenneth
[email protected]

Problem in JNDI lookup with Jdev JDEVADF_MAIN_GENERIC_061111.1900.4245

I have a JMS topic defined in a standalone oc4j (11g) and I am doing a JNDI lookup on that from an application that runs in embedded oc4j of jdev. Look up fails but if I add the same topic in jms.xml of embedded oc4j, it starts to work fine. My point is topic name shouldn't be needed in jms.xml of embedded oc4j i.e. client side (topic is present in remote oc4j and rightly defined in jms.xml of that oc4j). I verified that by creating a command line java application and that one is able to do lookup on the same topic available in the standalone oc4j.
I guess this problem is not specific to the label JDEVADF_MAIN_GENERIC_061111.1900.4245, it was there before also.
Any pointers on what could be wrong when I run in JDev?
Thanks,
Vishal

Please use the internal email distribution list jdev_us for 11 related questions.

JNDI Lookup for multiple server instances with multiple cluster nodes

Hi Experts,
I need help with retreiving log files for multiple server instances with multiple cluster nodes. The system is Netweaver 7.01.
There are 3 server instances all instances with 3 cluster nodes.
There are EJB session beans deployed on them to retreive the log information for each server node.
In the session bean there is a method:
public List getServers() {
List servers = new ArrayList();
ClassLoader saveLoader = Thread.currentThread().getContextClassLoader();
try {
   Properties prop = new Properties();
   prop.setProperty(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
   prop.put(Context.SECURITY_AUTHENTICATION, "none");
   Thread.currentThread().setContextClassLoader((com.sap.engine.services.adminadapter.interfaces.RemoteAdminInterface.class).getClassLoader());
   InitialContext mInitialContext = new InitialContext(prop);
   RemoteAdminInterface rai = (RemoteAdminInterface) mInitialContext.lookup("adminadapter");
   ClusterAdministrator cadm = rai.getClusterAdministrator();
   ConvenienceEngineAdministrator cea = rai.getConvenienceEngineAdministrator();
   int nodeId[] = cea.getClusterNodeIds();
   int dispatcherId = 0;
   String dispatcherIP = null;
   String p4Port = null;
   for (int i = 0; i < nodeId.length; i++) {
    if (cea.getClusterNodeType(nodeId[i]) != 1)
     continue;
    Properties dispatcherProp = cadm.getNodeInfo(nodeId[i]);
    dispatcherIP = dispatcherProp.getProperty("Host", "localhost");
    p4Port = cea.getServiceProperty(nodeId[i], "p4", "port");
    String[] loc = new String[3];
    loc[0] = dispatcherIP;
    loc[1] = p4Port;
    loc[2] = null;
    servers.add(loc);
   mInitialContext.close();
} catch (NamingException e) {
} catch (RemoteException e) {
} finally {
   Thread.currentThread().setContextClassLoader(saveLoader);
return servers;
and the retreived server information used here in another class:
public void run() {
ReadLogsSession readLogsSession;
int total = servers.size();
for (Iterator iter = servers.iterator(); iter.hasNext();) {
   if (keepAlive) {
    try {
     Thread.sleep(500);
    } catch (InterruptedException e) {
     status = status + e.getMessage();
     System.err.println("LogReader Thread Exception" + e.toString());
     e.printStackTrace();
    String[] serverLocs = (String[]) iter.next();
    searchFilter.setDetails("[" + serverLocs[1] + "]");
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    prop.put(Context.PROVIDER_URL, serverLocs[0] + ":" + serverLocs[1]);
    System.err.println("LogReader run [" + serverLocs[0] + ":" + serverLocs[1] + "]");
    status = " Reading :[" + serverLocs[0] + ":" + serverLocs[1] + "] servers :[" + currentIndex + "/" + total + " ] ";
    prop.put("force_remote", "true");
    prop.put(Context.SECURITY_AUTHENTICATION, "none");
    try {
     Context ctx = new InitialContext(prop);
     Object ob = ctx.lookup("com.xom.sia.ReadLogsSession");
     ReadLogsSessionHome readLogsSessionHome = (ReadLogsSessionHome) PortableRemoteObject.narrow(ob, ReadLogsSessionHome.class);
     status = status + "Found ReadLogsSessionHome ["+readLogsSessionHome+"]";
     readLogsSession = readLogsSessionHome.create();
     if(readLogsSession!=null){
      status = status + " Created ["+readLogsSession+"]";
      List l = readLogsSession.getAuditLogs(searchFilter);
      serverLocs[2] = String.valueOf(l.size());
      status = status + serverLocs[2];
      allRecords.addAll(l);
     }else{
      status = status + " unable to create readLogsSession ";
     ctx.close();
    } catch (NamingException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (CreateException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (IOException e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
    } catch (Exception e) {
     status = status + e.getMessage();
     System.err.println(e.getMessage());
     e.printStackTrace();
   currentIndex++;
jobComplete = true;
The application is working for multiple server instances with a single cluster node but not working for multiple cusltered environment.
Anybody knows what should be changed to handle more cluster nodes?
Thanks,
Gergely

Thanks for the response.
I was afraid that it would be something like that although
was hoping for
something closer to the application pools we use with IIS to
isolate sites
and limit the impact one badly behaving one can have on
another.
mmr
"Ian Skinner" <[email protected]> wrote in message
news:fe5u5v$pue$[email protected]..
> Run CF with one instance. Look at your processes and see
how much memory
> the "JRun" process is using, multiply this by number of
other CF
> instances.
>
> You are most likely going to end up on implementing a
"handful" of
> instances versus "dozens" of instance on all but the
beefiest of servers.
>
> This can be affected by how much memory each instance
uses. An
> application that puts major amounts of data into
persistent scopes such as
> application and|or session will have a larger foot print
then a leaner
> application that does not put much data into memory
and|or leave it there
> for a very long time.
>
> I know the first time we made use of CF in it's
multi-home flavor, we went
> a bit overboard and created way too many. After nearly
bringing a
> moderate server to its knees, we consolidated until we
had three or four
> or so IIRC. A couple dedicated to to each of our largest
and most
> critical applications and a couple general instances
that ran many smaller
> applications each.
>
>
>
>
>

Calling BRM from UDF using JNDI lookup with @EJB annotation

Hi Experts
I am trying to implement a UDF to invoke my BRM Rules set via JNDI Lookup instead of a SOAP Channel lookup.
I have had a look at the following links/docs:
Calling BRM from UDF using Public API
http://www.gleanster.com/system/resources/W1siZiIsIjIwMTIvMDgvMDcvMjAvNDcvNTAvNDMvVGhpbmdzX1lvdV9TaG91bGRfS25vd19hYm91dF9TQVBfTmV0V2VhdmVyX0JSTS5wZGYiXV0/Things%20You%20Should%20Know%20about%20SAP%20NetWeaver%20BRM.pdf
For item 1 above, the example looks really good, but it doesnt explain how I get access to the following required imports from my UDF:
import com.sap.brms.qrules.ejb.*;
import com.sap.brms.qrules.engine.AbstractProject;
import com.sap.brms.qrules.engine.RuleEngine;
import com.sap.brms.qrules.engine.RulesetContext;
import javax.ejb.EJB;
The second document is really good as well, but I could not figure out how to get it to work from my UDF.
So, can anyone help me to understand specifically what is required to get this to work?
Is is possible to invoke the rule set from my UDF?
How do I give my UDF access to all the required jars/imports?
I have manage to create a new DC (Development Component) with a public part and this enables me to get my code to compile on my local PC but I am not able to activate it due to the server not having access to the same java packages as my local copy.
Any help would be greatly appreciated.

You resolve the dependency by importing the required jars with using the dependency tab for the mapping program.
As stipulated before, I have managed to resolve the dependency issue but I have now getting the same error as in the forum: Calling BRM from UDF using Public API
The specific error is:
com.sap.engine.services.cross.PortableRemoteObjectContainer.narrow(PortableRemoteObjectContainer.java:238)
Has anyome manage to get invoke a BRM Ruleset using JNDI?

Best way to do a lookup with multiple tables

Hello,
I am looking for an example or how to do a lookup through ESB XSL transformation. What I am wanting to accomplish is something like below:
I am reading in a flat file and then want to use a field in that file to do a lookup in multiple tables.
i.e.
Select c.customer_name
from customers c, order_lines ol, order_headers oh
where ol.customer_id = c.customer_id
and ol.header_id = oh.header_id
and oh.order_number = p_order_num;
I know that there is the lookup-table function but didnt know if that would work with this scenario. Any suggestions are appreciated.
Thanks,
Jason
Edited by: Colby J on Oct 21, 2008 11:13 AM

Hello,
I am looking for an example or how to do a lookup through ESB XSL transformation. What I am wanting to accomplish is something like below:
I am reading in a flat file and then want to use a field in that file to do a lookup in multiple tables.
i.e.
Select c.customer_name
from customers c, order_lines ol, order_headers oh
where ol.customer_id = c.customer_id
and ol.header_id = oh.header_id
and oh.order_number = p_order_num;
I know that there is the lookup-table function but didnt know if that would work with this scenario. Any suggestions are appreciated.
Thanks,
Jason
Edited by: Colby J on Oct 21, 2008 11:13 AM

EJB 3 JNDI lookup with WL 12c (12.1.1) Exception

Hi all,
I'm trying to lookup an EJB inside my application with the following code :
Context ctx = new InitialContext();
ctx.lookup("java:module/MyEJB");
it throws this Exception :
javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
     at javax.faces.component.UICommand.broadcast(UICommand.java:315)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
     Truncated. see log file for complete stacktrace
Caused By: javax.faces.el.EvaluationException: javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at javax.faces.component.UICommand.broadcast(UICommand.java:315)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
     Truncated. see log file for complete stacktrace
Caused By: javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:86)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:466)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:256)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:170)
     Truncated. see log file for complete stacktrace
Caused By: java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject
     at weblogic.jndi.internal.WLEventContextImpl.copyObject(WLEventContextImpl.java:384)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:251)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:170)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     Truncated. see log file for complete stacktrace
Caused By: java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     Truncated. see log file for complete stacktrace
i'm using WL 12c, JDK 1.6.29.
regards.

I can't upload all the project, but i will upload the [required files|http://dl.dropbox.com/u/79750638/WLForum.7z] .
inform me if you need more info.
thanks

Weblogic JNDI lookup with JDK1.2

Hi,
I've written JMS client that sends message to weblogic 8.1,
and I use "weblogic.jndi.WLInitialContextFactory" to get access to resources.
Now the problem is that my client can run only on JDK 1.2 and
so when I send message I get exceptions about some security classes which
webligic's JNDI is implementing looks like:
java.lang.NoClassDefFoundError: javax/security/auth/callback/CallbackHandler
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
I was wondering if there is any way to a client running on JDK 1.2
to get access to weblogic's JNDI, other than using WLInitialContextFactory,
or I have to go to Weblogic 6?
Any help is appreciated!
Thanks,
Ann

Hi,
I've written JMS client that sends message to weblogic 8.1,
and I use "weblogic.jndi.WLInitialContextFactory" to get access to resources.
Now the problem is that my client can run only on JDK 1.2 and
so when I send message I get exceptions about some security classes which
webligic's JNDI is implementing looks like:
java.lang.NoClassDefFoundError: javax/security/auth/callback/CallbackHandler
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
I was wondering if there is any way to a client running on JDK 1.2
to get access to weblogic's JNDI, other than using WLInitialContextFactory,
or I have to go to Weblogic 6?
Any help is appreciated!
Thanks,
Ann

AD Site lookup with multiple IP

Hey all,
If I have the following setup:
Servername: IP Subnet Gateway
Server1: 192.168.1.10 255.255.255.0 192.168.1.1
Server2: 192.168.1.20 255.255.255.0 192.168.1.1
AD site definitions:
192.168.1.0/24: Site1
192.168.1.20/32: Site2
This means that Server1 would report Site1 as a result to a nltest site lookup and server2 would report Site2. Up to that point everything is ok.
However, when setting up a windows cluster, the cluster IP would also be in the 192.168.1.0/24 range. If the Server2 has the cluster IP address, what site would this server be in? Will the Server2 base its site location based on the 192.168.1.20 interface?
In general, if a server has two NICs and each NIC uses a subnet that is allocated to another AD site: how is this site selection performed.
Thanks for the responses! And if you have pointers to technet, these are also welcome!

In addition, see this.
DNS and Subnet Priortization & DNS Round Robin
Subnet priortization works by default. No other action is required. If you have multiple identical A records, then Round Robin will supercede.
If Round Robin is not needed, it can be disabled in order to take full advantage of Subnet Priortization, otherwise, Round Robin will superceded.
http://blogs.msmvps.com/acefekay/2010/05/29/dns-and-subnet-priortization-amp-dns-round-robin/
Regards,
Biswajit
MCTS, MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, Enterprise Admin, ITIL F 2011
Blog:
Script Gallary:
LinkedIn:
Note: Disclaimer: This posting is provided & with no warranties or guarantees and confers no rights..

Setting Default Indesign program with multiple versions installed Snow Leopard

Hi,
when having 2 versions of Indesign installed (CS4 and CS5), Snow Leopard uses CS5 as the default application to open INDD files.
Typically if you want to set a particular program as the default program, you right-click on the file, go to "get Info", then "open with" and pick the applications from the pulldown menu and then click right below it "Change All". Typically now that program has become the default program. This has worked all the time except in this case. When trying to set Indesign CS4 as the default program for all INDD files (use CS4 99% of the time and all INDD files on the system were created using CS4) it will not let me use the "change all" button. It automatically goes back to CS5. I want Indesign CS4 to be the default program.
Any suggestion is greatly appreciated.
Thanks.

Change file associations manually or have this freebie jewel do it for you. Most likely CS5 will take over again. Otherwise you can go fish on http://hints.macworld.com/ for another way.
Rubicode - RCDefaultApp

Problem in JNDI lookup.

Hi,
I have a JSP running on tomcat. And it accesses an EJB running on weblogic thru a local bean. When the following JNDI lookup code is executed, I get errors. Errors follow the code. Please Help.
Thanks!
public InitialContext getInitialContext() throws NamingException
// Utils.Trace("****** in getInitialContext ******");
// web logic server and jsp engine NOT weblogic
if (url != null && url.length() > 0)
//Hashtable env = new Hashtable();
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
// assumes that JSP and EJB container are on the same box,
// otherwise EJB hostname should be specified
//env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.PROVIDER_URL, url);
System.out.println("Using t3 services");
return new InitialContext(env);
// weblogic server and weblogic jsp, or inprise server (JBuilder's default JSP)
else
System.out.println("Not Using t3 services");
return new InitialContext();
The ERRORS are
=====================================================================
org.apache.jasper.JasperException: weblogic/common/T3Services
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:248)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
     at java.lang.Thread.run(Thread.java:479)
root cause
javax.servlet.ServletException: weblogic/common/T3Services
     at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:497)
     at org.apache.jsp.login_jsp._jspService(login_jsp.java:276)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
     at java.lang.Thread.run(Thread.java:479)

Your JSP trying to load the weblogic context factory to perform the lookup, but can't find it. Your servlet engine must have access to the weblogic.jndi.WLInitialContextFactory class (in weblogic.jar).

Queue JNDI lookup in a clustered environment

Hey all,
          I know in a 6.1 cluster, the queues/JMS servers can only reside on one
          server.
          How can i lookup a queue from internal code from one of the off servers? The
          JNDI lookup doesn't grab it, throws an object not found exception. Do I need
          to
          be using the createQueue() method in the QueueSession class?
          It's fairly critical to know this to get our app up on the cluster, so
          any help would
          be very appreciated!
          Thanks,
          Greg


          A dumb question - how do I specify JNDINameReplicated=false? I am using WLS 6.1
          SP3 and in my config.xml I have
          <JMSTopic Name="topicA" JNDIName="topicA" JNDINameReplicated="false" />
          but WebLogic does not like it.
          Eric Ma
          Tom Barnes <[email protected]> wrote:
          >The parameter name "JNDINameReplicated" parameter is only available in
          >a patch
          >on top
          >of SP2 or SP3, and is "true" by default. I doubt that you are using
          >it.
          >
          >Greg Kaestle wrote:
          >
          >> Thanks much,
          >> Where is this parameter set in config.xml?
          >>
          >> Greg
          >>
          >> "Shean-Guang Chang" <[email protected]> wrote in message
          >> news:[email protected]...
          >> > If you want the queue to be found from other server in the same cluster
          >> then
          >> > you should not set "JNDINameReplicated" to false. This
          >> > will make the JNDI name of the queue known to the local server which
          >is
          >> > hosting the JMS queue. The purpose to use "JNDINameReplicated=false"
          >> > is to have multiple queues with the same JNDI name and then use some
          >sort
          >> of
          >> > load balancer to spread load among different JMS servers in the cluster.
          >> >
          >> >
          >> > "Greg Kaestle" <[email protected]> wrote in message
          >> > news:[email protected]...
          >> > > Hey all,
          >> > >
          >> > > I know in a 6.1 cluster, the queues/JMS servers can only reside
          >on
          >> one
          >> > > server.
          >> > > How can i lookup a queue from internal code from one of the off
          >servers?
          >> > The
          >> > > JNDI lookup doesn't grab it, throws an object not found exception.
          >Do I
          >> > need
          >> > > to
          >> > > be using the createQueue() method in the QueueSession class?
          >> > >
          >> > > It's fairly critical to know this to get our app up on the cluster,
          >> so
          >> > > any help would
          >> > > be very appreciated!
          >> > >
          >> > > Thanks,
          >> > > Greg
          >> > >
          >> > >
          >> >
          >> >
          >

XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
    SAP XI: 7.0 SP8 , Sun JDK 1.4.2
    IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
   JMS Providers: Default Messaging Provider
   Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
   Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
<b>Variant 1.</b>
    Adapter type: JMS
    Type: Receiver
    JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
    JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
    JNDI Lookup Name of JMS Queue: jms/Queue
    Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
    JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
    "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
<b>Variant 2</b>
    The same settings as in Variant 1 above, were used and additionally the following settings were done:
    - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
    - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
    - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
    As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
   "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

Distributed Queue/JMX - JNDI lookup on startup fails

Hi,
I have a problem starting up Camel routes on a cluster via JMX. Although I have a NotificationListener registered that tries to startup the routes when the server sends a STATE=RUNNING lifecycle event, I cannot start the all Camel routes due to a "JMSException, Destination not found".
But, when I remote debug the application and put a breakpoint in, wait let's say 5 secs, then the JNDI lookup works and everything is fine.
I have unsuccessfully tried to play with the deployment order or my ear (by default the JMSServer is started with a priority of 1000), no luck. I have also put a poll method in, that waits until the JMSServer and the Destinations (=queues) are available, again no luck.
Anyone able to assist with that issue?
Best Regards,
Sebastian

I found the reason for the late binding. We are using "migratable target" in our cluster. When I remove the migratable target I have no issue whatsoever. Is there a way to either tweak the config or configure the Migratable targets in a way to by-pass this issue?
Regards,
Seb

WL 4.5.1 JNDI defaults,JNDI lookup with multiple environments etc..

Similar Messages

Maybe you are looking for