JNDI Provider for wls 5.1 cluster

hi,
          how can I specify a JNDI provider URL for a WLS 5.1 cluster where the
          cluster nodes are different machines ? Is there a way to specify the
          URL without using a single servers IP address ?
          thx
          johannes

[att1.html]

Similar Messages

JAVA client JNDI lookup for EJB session in cluster in WLS 5.1

The documentation says :
          to obtain a Context for JNDI lookup do the following :
          Hashtable ht = new Hashtable();
          ht.put(Context.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
          ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
          try {
          Context ctx = new InitialContext(ht);
          // Do the client's work
          catch (NamingException ne) {
          // A failure occurred
          finally {
          try {ctx.close();}
          catch (Exception e) {
          // a failure occurred
          where "mycluster" is the DNS name of my cluster. My DNS server (Windows 200
          DNS server) use round robin
          to call alernatively all the wls server node in "mycluster" and it's OK. The
          two servers of my cluster
          are called alternatively for my EJB session stateless.
          Now I unplug one of the two nodes of my cluster and the remaining server is
          called only 2 times
          and not after.
          Questions :
          -is the load balancing between the nodes of mycluster only rely on DNS or
          is there an internal
          mecanism in EJB sub to try one server then an other ?
          - do I need to obtain a new reference on JNDI Context for each call ?
          Thank's a lot.
          Farid Bellameche.


          I too have the same problem. My scenario is :
          I have the web tier architecture away from cluster. All ejbs are in cluster
          running in two seperate machines. We have a factory class running in
          webtier(we use servlet in this tier) which obtains home interface only once
          and stores it for future reference. When ever we need the remoteobject stub,
          we ask the factory class and which in turn uses the stored home interface to
          get the same.
          In the webtier, I list all the servers in the cluster as a part of url as
          mentioned by you.
          I started the web tier as well as Object tier cluster. I could see the
          request coming in both the machines in the cluster for the ejb. But When I
          bring one the server in the cluster,
          1. Web tier throws an exception saying that it could not connect
          to server using t3.
          2. The other machine which is running the server, also says
          'failed to create socket to : -32323234324 sever name
          using protocol t3.
          It looks like I am able to get load balance. But I am not able to get the
          fail over to be working.
          In the weblogic-ejb-jar.xml, I added the following.
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          I compiled and added the .jar file. So the jar file now has replica aware
          stubs.
          Could any one of you help me for why the fail over is not working?
          Suersh
          "Giri Alwar" <[email protected]> wrote in message
          news:[email protected]...
          > Farid,
          > (1) Yes, the stub has the logic to perform load-balancing and
          fail-over.
          > (2) In almost all cases, no. You can get the context once, store it
          and
          > use it thereafter. Please refer to
          > http://www.weblogic.com/docs51/cluster/concepts.html#1025061 for more
          info.
          >
          > A couple of notes on your situation. From what you are describing, your
          > Windows DNS server is setup to serve only one IP from the cluster (using
          > round-robin) as opposed to a list of all IP's in the cluster. Hence, the
          > initial context you obtain is tied to a single server in the cluster (the
          > one returned by the DNS). The weblogic implementation on the client side
          has
          > no idea of the existence of the other servers in the cluster. This is not
          a
          > cluster aware context. To obtain a cluster aware context, either list all
          > the IP's in the URL like t3://server1,server2,server3:7001 or have
          > "mycluster" return a list of all servers in the cluster.
          >
          > Giri
          >
          >
          > "Farid Bellameche" <[email protected]> wrote in message
          > news:[email protected]...
          > > The documentation says :
          > >
          > > to obtain a Context for JNDI lookup do the following :
          > > Hashtable ht = new Hashtable();
          > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
          > > "weblogic.jndi.WLInitialContextFactory");
          > > ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
          > > try {
          > > Context ctx = new InitialContext(ht);
          > > // Do the client's work
          > > }
          > > catch (NamingException ne) {
          > > // A failure occurred
          > > }
          > > finally {
          > > try {ctx.close();}
          > > catch (Exception e) {
          > > // a failure occurred
          > > }
          > > }
          > >
          > > where "mycluster" is the DNS name of my cluster. My DNS server (Windows
          > 200
          > > DNS server) use round robin
          > > to call alernatively all the wls server node in "mycluster" and it's OK.
          > The
          > > two servers of my cluster
          > > are called alternatively for my EJB session stateless.
          > > Now I unplug one of the two nodes of my cluster and the remaining server
          > is
          > > called only 2 times
          > > and not after.
          > >
          > > Questions :
          > > -is the load balancing between the nodes of mycluster only rely on DNS
          > or
          > > is there an internal
          > > mecanism in EJB sub to try one server then an other ?
          > >
          > > - do I need to obtain a new reference on JNDI Context for each call ?
          > >
          > >
          > > Thank's a lot.
          > >
          > > Farid Bellameche.
          > >
          > >
          > >
          > >
          >
          >

Using JNDI Provider for Oracle JMS Queue

Hello,
I created a JMS Queue in Oracle 9.2.0.1 and would like
a Java client to receive events from the Queue. I am
not running Oracle9iAS. I have access to WebLogic server
7.0 which is also a JNDI provider. Is there a sample code
that shows the steps on how to go about this.
thanks very much for any pointers.

To define an Enterprise Message Source for AS JMS and OJMS in BAM, see Chapter 3 in the BAM Architect's User Guide.
Specifying Settings for Oracle (AS JMS and OJMS)
Settings for Oracle (AS JMS and OJMS) include:
■ Initial Context Factory.
For 10.1.3: oracle.j2ee.rmi.RMIInitialContextFactory
For 10.1.2: com.evermind.server.rmi.RMIInitialContextFactory
■ JNDI Service Provider URL. For standalone use oc4j: ormi://machine_name/
where machine_name is the OC4J installed host, and for production use Application Server: opmn:ormi://<machine_name>:<opmn request port>:home where machine_name is the application server installed host, opmn request port could be found from looking at opmn.xml in <App server install location>/opmn/conf
■ TopicConnectionFactory Name.
java:comp/resource/BAMTTT/TopicConnectionFactories/bam_ttq_tab
■ Topic Name. java:comp/resource/BAMTTT/Topics/bam_ttq
■ JMS Message Type. TextMessage.
■ Durable Subscriber Name. BAMFilteredSubscription
■ Message Selector. Message selector, for example, BAMFilter='true'
■ Client ID. ClientID
You can also refer to:
http://www.oracle.com/technology/products/integration/bam/10.1.3/TechNotes/TechNote_BAM_AQ_Configuration.pdf
Regards, Stephen

HP-UX Kernel Params for WLS 6.0SP2 Cluster to Avoid java.lang.outofmemory and/or thread death

          I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing heap and
          thread issues on start-up or invocation of my application as I deploy EJB's and create
          DB connection pools. These are fairly trivial tasks that don't give me any issues
          when starting the first node. It's only when I invoke the second node.
          I'm pretty sure that my issue is tied to the following kernel areas:
          1. Thread allocation
          2. Heap allocation
          3. Max Processes per user
          Can anyone make some kernel recommendations that might be beneficial to my deployment?
          My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I typically
          allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and allocate about
          1GB of RAM per node on a 4GB machine...
          Regards,
          Steve


I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing          heap and
          > thread issues on start-up or invocation of my application as I deploy
          EJB's and create
          > DB connection pools. These are fairly trivial tasks that don't give me any
          issues
          > when starting the first node. It's only when I invoke the second node.
          >
          > I'm pretty sure that my issue is tied to the following kernel areas:
          >
          > 1. Thread allocation
          > 2. Heap allocation
          > 3. Max Processes per user
          >
          > Can anyone make some kernel recommendations that might be beneficial to my
          deployment?
          > My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I
          typically
          > allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and
          allocate about
          > 1GB of RAM per node on a 4GB machine...
          HP has some kernel tuning guidelines for Java server apps on their web site,
          and BEA has some notes as well in their platform support page.
          What issues specifically are you seeing?
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "Steve Feldman" <[email protected]> wrote in message
          news:3cdc046e$[email protected]..
          >

Authentication problem by external ldap server for WLS 7.0

Hi all,
I have configured iPlanet directory Server to serve as authentication security
provider for WLS 7.0.While doing so I have created a Test security realm and made
it as default.I have also configured the other default settings for the remaining
security providers for the realm.
Now, while I start the WLS with the default username and password, boot-error
comes as given below. As a matter of fact I have also created groups with relevant
username and pwd in the ldap server as specified bu the Bea documentation.
I have tried to remove the problem since last 4 days but all in fiasco.
If anybody has any pointer to the problem - it will be a great help.
The error :
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea\weblogic700\samples\server\config\petstore>"D:\bea\jdk131_03\bin\java"
-h
otspot -Xms32m -Xmx200m -Dpet.mode= - Dweblogic.management.discover=false -Dweblo
gic.Name=petstoreServer -Dbea.home="D:\bea" -Dweblogic.management.username=weblo
gic -Dweblogic.management.password=weblogic -Dweblogic.ProductionModeEnabled=tru
e -Djava.security.manager -Djava.security.policy=="D:\bea\weblogic700\server\lib
\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Nov 19, 2002 10:08:04 AM IST> <Notice> <Management> <140005> <Loading configura
tion D:\bea\weblogic700\samples\server\config\petstore\.\config.xml>
<Nov 19, 2002 10:08:21 AM IST> <Notice> <Security> <090082> <Security initializi
ng using realm RitTestRealm.>
<Nov 19, 2002 10:08:22 AM IST> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: User weblogic
i
s not permitted to boot the server
java.lang.SecurityException: User weblogic is not permitted to boot the server
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1076)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
Regards,
Ritwik

Thanks Vijay - it has worked by creating the Administrator group in LDAP but Weblogic
documentation also states the creation of any group in Ldap server with the boot
username and pwd and then adding the group in the admin role of WLS7.0 - but this
did not work.
If there is any info regarding the same - pl. do let me know
Regards,
Ritwik
"Vijay" <[email protected]> wrote:
>
Ritwik,
I think WebLogic 7 requires a group called "Administrators" in the LDAP
server
and requires an user to be added to that group. I have this working in
one of
my projects. The group really doesnt need to be an LDAP administrative
group.
Can you provide any additional information. I might be able to help since
I got
this working only a coupla days back.
Vijay
"Ritwik Batabyal" <[email protected]> wrote:
Hi all,
I have configured iPlanet directory Server to serve as authentication
security
provider for WLS 7.0.While doing so I have created a Test security realm
and made
it as default.I have also configured the other default settings forthe
remaining
security providers for the realm.
Now, while I start the WLS with the default username and password, boot-error
comes as given below. As a matter of fact I have also created groups
with relevant
username and pwd in the ldap server as specified bu the Bea documentation.
I have tried to remove the problem since last 4 days but all in fiasco.
If anybody has any pointer to the problem - it will be a great help.
The error :
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea\weblogic700\samples\server\config\petstore>"D:\bea\jdk131_03\bin\java"
-h
otspot -Xms32m -Xmx200m -Dpet.mode= - Dweblogic.management.discover=false
-Dweblo
gic.Name=petstoreServer -Dbea.home="D:\bea" -Dweblogic.management.username=weblo
gic -Dweblogic.management.password=weblogic -Dweblogic.ProductionModeEnabled=tru
e -Djava.security.manager -Djava.security.policy=="D:\bea\weblogic700\server\lib
\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Nov 19, 2002 10:08:04 AM IST> <Notice> <Management> <140005> <Loading
configura
tion D:\bea\weblogic700\samples\server\config\petstore\.\config.xml>
<Nov 19, 2002 10:08:21 AM IST> <Notice> <Security> <090082> <Security
initializi
ng using realm RitTestRealm.>
<Nov 19, 2002 10:08:22 AM IST> <Critical> <WebLogicServer> <000364><Server
fail
ed during initialization. Exception:java.lang.SecurityException: User
weblogic
i
s not permitted to boot the server
java.lang.SecurityException: User weblogic is not permitted to bootthe
server
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1076)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
Regards,
Ritwik

Failed to lookup JNDI provider

Hi All,
I'm facing a problem sending Messages to a Queue within an OpenJMS server.
When I send the messages to a OpenJMS server runnin on my LocalHost, It is SUCCESSFUL.
then, I simply change the IP adress of the server (another machine on my local network) ... and here, I obtain the follwing exception :
Failed to lookup JNDI provider for URL: tcp://192.168.4.71:3035/
here is the code I'm using ( and where the exception is raised ):
Hashtable properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.jndi.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "tcp://192.168.4.71:3035/" );
context = new InitialContext(properties);Any help and suggestion please ?!
It's urgent

for more details :
this is the nested Exception I'm getting :
nested exception is:
java.io.InvalidClassException: org.exolab.jms.net.proxy.Proxy;
local class incompatible: stream classdesc serialVersionUID = -3335702252244367740, local class serialVersionUID = 1
?

JNDI conflict for WTC in cluster env

I found this error when starting more than one managed server in clustered environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.40 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.41 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
Please help.

Hi Salim,
Salim Djaffar wrote:
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
Salim Djaffar wrote:
I have a stateless ejb using this context to get the same JNDI namefrom tuxedo
connection factory. This ejb is deployed as clustered. I deployed thisejb into
many managed servers in the cluster. In other word every managed serverdeploys
this ejb.
I also have the web server configured with clustered plugin, but Iguess it has
nothing to do with it.
Isn't the wtc_config.xml stanza "WlsClusterName" a little misleadingsince it
does not support cluster at all ?Yes, it is kind of misleading. It is not used in WTC and will be removed
from dtd
(and document) in the future.
Besides in the admin console, I configured the WTC startup target to"cluster".
Is there any advise to overcome this problem ?I can't think of a good way to overcome this problem. One thing you
can do is to
target WTC to a WLS in the cluster. One drawback is that you have only
one WTC in
the cluster.
Honghsi
Does it mean I have to use RMI/IIOP to do the lookup to one particular server
for WTC ?No. The RMI/IIOP lookup is specific for CORBA NS lookup. It won't help you at
all.
>
Will WTC be available for clustered in the future ?There will be some changes to WTC that will make it possible for you to deploy WTC
instance on every WL server in the cluster. There are some administration (and
configuration) restrictions associate with it if you want to be able to do load
balancing and fail over.
Hong-Hsi :-)
>
>
Thanks.
Please help.
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
The current version of WTC will have this problem. Because the connection
factory is bound
to the same name in JNDI tre. However, the first WTC booted in the
WLS
cluster should
still be available to use.
BTW, I am interested in knowing how you use WTC currently, and howyou
plan to use in the
future.
Honghsi
Salim Djaffar wrote:
I found this error when starting more than one managed server in
clustered
environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.40 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.41 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
Please help.

How to change JNDI service provider for EJB's?

I need EJBean's home interface to be bound to another JNDI provider, not Weblogic.
How can I do it?
The most simple solution is not working: to specify <jndi-name> in weblogic-ejb-jar.xml
for bean as "xxx:bean_name".
By JNDI rules for such names context factory with name com.sun.jndi.url.xxx.xxxURLContextFactory
will be used. But for Weblogic this does not work. An exception is thrown during
bean deployment -
javax.management.MalformedObjectNameException: ObjectName: Invalid value -> xxx:bean_name
at javax.management.ObjectName.validateAndAdd(ObjectName.java:440) at javax.management.ObjectName.initObjectName(ObjectName.java:409)
at javax.management.ObjectName.<init>(ObjectName.java:254) at weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:196)
at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:90)
at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:83)
at weblogic.ejb20.internal.BaseEJBHomeMBean.<init>(BaseEJBHomeMBean.java:33) ......................

This is not an answer on my
question - My questions was: how to force a Welogic EJB Container to BIND EJBean's
home interface to another JNDI Service provider, not Weblogic.
But you wrote how to use JNDI in general - I already know how to use it :)))
Phil.
"VSK" <[email protected]> wrote:
Hi
Have a look at the code below
private Context getInitialContext () throws NamingException
String from = "CtxHelper::getInitialContext ";
String webLogicHostUrl = t3://SERVERNAME:9001
Logger.debug(from, "Begin Method", 3);
Hashtable h = System.getProperties();
h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory
h.put(Context.PROVIDER_URL, webLogicHostUrl);
return new InitialContext(h);
} //end getInitialContext
This way we will get the InitailContext and then do a jndi lookup using
the
Context object as follows
ctx.lookup..........
Now in the above code replace weblogic.jndi.WLInitialContextFactory by
ur
provider.
Hope this helps.
-VKS
"Phil Peshin" <[email protected]> wrote in message
news:[email protected]...
I need EJBean's home interface to be bound to another JNDI provider,not
Weblogic.
How can I do it?
The most simple solution is not working: to specify <jndi-name> inweblogic-ejb-jar.xml
for bean as "xxx:bean_name".
By JNDI rules for such names context factory with namecom.sun.jndi.url.xxx.xxxURLContextFactory
will be used. But for Weblogic this does not work. An exception isthrown
during
bean deployment -
javax.management.MalformedObjectNameException: ObjectName: Invalidvalue -> xxx:bean_name
at javax.management.ObjectName.validateAndAdd(ObjectName.java:440)at
javax.management.ObjectName.initObjectName(ObjectName.java:409)
at javax.management.ObjectName.<init>(ObjectName.java:254) atweblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:196)
atweblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelega
te.java:90)
atweblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate
..java:83)
atweblogic.ejb20.internal.BaseEJBHomeMBean.<init>(BaseEJBHomeMBean.java:33)

JNDI name for a JMB is not replicatet to other servers in the cluster

Hi,
          wl6.1sp7, two server cluster
          When I look at the JNDI Tree for a server I can't find JNDI names of JMB's from the other server in the cluster.
          I get an exception when trying to send to a destinaton on the other server. (Unable to resolve 'xlink.jms.service.report.biztalk-lab.Report' Resolved: 'xlink.jms.service.report' Unresolved:'biztalk-lab')
          Setting are same as explained in this thread...
          http://forums.bea.com/bea/thread.jspa?threadID=600003492&tstart=0
          And JNDINameReplicated is set to true....
          Why is the JNDI names not replicated?
          <JMSQueue JNDIName="xlink.jms.service.report.biztalk-lab.Report"
          JNDINameReplicated="true" Name="Report" StoreEnabled="default"/>
          This is the DD of a JMB:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          <connection-factory-jndi-name>xlink.jms.factory.commerceFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ~b

1. yes
          <JMSConnectionFactory AllowCloseInOnMessage="false"
          DefaultDeliveryMode="Persistent" DefaultPriority="4"
          DefaultTimeToLive="0"
          JNDIName="xlink.jms.factory.commerceFactory"
          MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
          OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
          2. No I am just using the jndi name of the queue.
          This is an example of how I send a message:
               Context ctx = new InitialContext();
          QueueConnectionFactory qconFactory;
          QueueConnection qcon;
          QueueSession qsession;
          QueueSender qsender;
          Queue queue;
          ObjectMessage msg;
          qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
          qcon = qconFactory.createQueueConnection();
          qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
          qsender = qsession.createSender(queue);
          msg = qsession.createObjectMessage(reportExecutorContainer);
          qcon.start();
          qsender.send(msg);
          qsender.close();
          qsession.close();
          qcon.close();
          3. I don't know those setting (wl 6.1sp7)

(268625273) Q WSI-29 Can you give any performance benchmarks for WLS web services?

Q<WSI-29> Can you give any performance benchmarks for WLS web services?
A<WSI-29>: It is very difficult to quantify performance aspects of web services
since they depend on so many variables including but not limited to: backend system
processing by stateless session beans and message driven beans, size of XML SOAP
message sent, system hardware (CPU speed, parallel processing, RAM speed) and
system software (JVM type and version of WebLogic server). However, let me point
out that the EJB backend processing of requests both have the best possible scalability
within the EJB2.0 specification (both stateless session and message driven beans
can be pooled) and servlets have a proven scalable track record. Thus it should
be possible to scale your web service deployment to meet demand. The overhead
in processing XML within the servlet can be significant depending on the size
of XML data (either as a parameter or a return type). While WLS6.1 does not have
any features to address this performance concern, WLS7.0 will feature Serializer
and Deserializer classes which can be dedicated to the XML to Java and Java to
XML translation (they can also be automatically be generated from a DTD, XML Schema
or regular JavaBean).
It is true that web services are not the fastest way to process client requests
but BEA is committed to making WebLogic server the fastest possible service provider.
Adam

see http://www.oracle.com/support/products/oas/sparc30/html/ows08811.html

JNDI lookup for UserTransaction

          Hi all,
          in Weblogic, in a typical scenario, do a client provide exactly
          one JNDI lookup for the UserTransaction object (interface) or do
          the client have to provide a JNDI lookup for each transaction?
          In some EJB implementations, a JNDI lookup for UserTransaction
          returns always the same reference. For example, in JOnAS, you can
          have one static reference which is set when the client starts.
          Then, more threads can simultaneously use the same static
          UserTransaction reference without any conflict, since the
          implementation of UserTransaction recognizes, which thread invoked
          a particular method.
          In other words, can I make an assumption that two different JNDI
          lookups for UserTransaction returns different references or not?
          Thanks a lot,
          Marek Prochazka
          Distributed Systems Research Group
          Department of Software Engineering
          Charles University, Faculty of Mathematics and Physics
          Malostranske namesti 25, 118 00 Prague 1, Czech Republic
          phone: +420-2-2191 4236
          http://nenya.ms.mff.cuni.cz/thegroup/


Actually, UserTransaction is a singleton and it's not a transaction. It's just
          very mis-named.
          It should be called UserTransactionManager or UserInterfaceToJTA.
          The actual transaction is javax.transaction.Transaction.
          -- Rob
          Cameron Purdy wrote:
          > Within a transaction, it is different instances? For example, if you call
          > it two times one right after another?
          >
          > A transaction is a unit of work. I understand why the transaction object
          > changes from transaction to transaction, since a single transaction object
          > (UserTransaction) represents exactly one transaction. Why would it be a
          > singleton? It is not a transaction manager.
          >
          > Peace,
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          > "Sarita" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > Hi Priscilla--
          > >
          > > This is not the behavior that I'm seeing, and I'm perplexed.
          > > Every time I request a UserTransaction from JNDI, I receive a
          > > a different instance. Should the value immediately returned by JNDI be
          > the singleton
          > > instance? If not, then how do I retrieve the singleton instance?
          > >
          > > I would like a session bean to start a transaction, and then call a method
          > on another
          > > session bean (which should operate under the same transaction). How does
          > the second
          > > session bean grab the correct transaction object? Is that possible?
          > >
          > > Thanks In Advance,
          > > Sarita
          > >
          > > "Priscilla Fung" <[email protected]> wrote:
          > > >
          > > >Hi Marek,
          > > >
          > > >In Weblogic 6.0, JNDI lookup of UserTransaction returns a reference to
          > the
          > > >singleton
          > > >Transaction Manager instance, which is thread-safe and can be used from
          > > >multiple
          > > >threads for transaction demarcations etc.
          > > >
          > > >-- Priscilla Fung, BEA Systems, Inc.
          > > >
          > > >"Marek Prochazka" <[email protected]> wrote:
          > > >>
          > > >>Hi all,
          > > >>
          > > >>in Weblogic, in a typical scenario, do a client provide exactly
          > > >>one JNDI lookup for the UserTransaction object (interface) or do
          > > >>the client have to provide a JNDI lookup for each transaction?
          > > >>
          > > >>In some EJB implementations, a JNDI lookup for UserTransaction
          > > >>returns always the same reference. For example, in JOnAS, you can
          > > >>have one static reference which is set when the client starts.
          > > >>Then, more threads can simultaneously use the same static
          > > >>UserTransaction reference without any conflict, since the
          > > >>implementation of UserTransaction recognizes, which thread invoked
          > > >>a particular method.
          > > >>
          > > >>In other words, can I make an assumption that two different JNDI
          > > >>lookups for UserTransaction returns different references or not?
          > > >>
          > > >>Thanks a lot,
          > > >>Marek Prochazka
          > > >>--------------------------------------------------------------
          > > >> Distributed Systems Research Group
          > > >> Department of Software Engineering
          > > >> Charles University, Faculty of Mathematics and Physics
          > > >> Malostranske namesti 25, 118 00 Prague 1, Czech Republic
          > > >> phone: +420-2-2191 4236
          > > >> http://nenya.ms.mff.cuni.cz/thegroup/
          > > >>--------------------------------------------------------------
          > > >>
          > > >
          > >

Looking up JNDI names for local client

Sir,
I have been trying to look up JNDI name for the local home interface in the client program.But I got only "javax.naming.NoInitialContextException".I want information about to give a JNDI name for EJB and its details.
Thanking you.
Yours,
R K Ramesh

It sounds like you are not specifying the right URL or username/credentials to get an initial context.
A typical example would be something like this:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, "t3://server:port");
InitialContext ic = new InitialContext(p);
(You can also use a properties file or system prpoerties to specify these.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Specifying JNDI Details for Controls (EJB/JMS) in Workshop

Hello,
I was running into some basic issues in using workshop for building applications. Any help is appreciated !
How do I point Controls (EJB/JMS) to JNDI where the Objects have been bound
In J2EE I will do this :
Context ctx = new InitialContext(ht); // ht has Provider URL etc.
Specifically in Design view of Workshop for (WLI) JMS Control how do you define PROVIDER_URL, SECURITY_PRINCIPAL, etc. My JMS Server is targeted to separate Managed Server that where Workshop Applications are deployed and I do not want to create Foriegn Destinations etc. on Managed Server where Applications get deployed.
For EJB Controls: How do you lookup remote EJBs that get deployed as a part of (EARs) on managed server (different from where Workshop Application and EJB Controls reside)
Basic Question: How do we distribute this "EJB Control" JAR to clients to call these EJBs using controls and specify the JNDI Environment for the control that surfaces the EJB resource deployed remotely?
I cannot import these as modules in an Workshop Application (=> EAR) and generate controls from these as they will get "deployed" in that application and we want only one deployment.
Thanks
Harish

Hi there,
In your GUI client you should consdier building a model that represents the data that you want the GUI to display. This model would contain the references to the EJB's that you need to use. If you want to avoid using some kid of model then it really depends on the complexity of your GUI. If your GUI consists of one JFrame then everything can be done inside the main class for the GUI. If you have lots of sub windows then you need to consider where the references will be used. If theyare used in more than one window then you could end up with lots of complex cross references which is why the model would be better in this situation.
JNDI lookups can be expensive and this depends on several factors particularly network latency, if your client is self contained then once you have a reference to a home interface then you may as well keep and use it for any future calls. The key to this is keeping references to home interfaces as instance variables rather than scoping them locally.
There should really be no bottleneck caused by using as single session bean as a Facade to your EJB tier. The Session Facade is a very common pattern and the one that is most espoused by the various authors writing EJB tech books. As far as coupling is concerned this is an ideal situation as your client can then make coarse grained calls to the single facade session bean instead of making lots of smaller fine-grained calls to several session beans. I'd say that this is a good general design.
Hope this helps
Amanda
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers

Need JNDI example for THIN CLIENT

I ned a JNDI example for a thin client (as opposed to a java program connecting on the same machine as the server).
1> Specifically, I need an example of a JNDI Provider URL
Would it be <b>corbaloc.iiop:<host>:5004 ???</b>
2> Also, how do I create a Queue Connection factory from within the GUI (Visual Administrator), so I can find out what to use on the THIN CLIENT Program?
Thanks

Hi,
Please find the answers below.
> I ned a JNDI example for a thin client (as opposed to
> a java program connecting on the same machine as the
> server).
>
> 1> Specifically, I need an example of a JNDI Provider
> URL
>
> Would it be <b>corbaloc.iiop:<host>:5004 ???</b>
Have a look at <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/8f633e0084e946e10000000a114084/frameset.htm">this</a> link.
> 2> Also, how do I create a Queue Connection factory
> from within the GUI (Visual Administrator), so I can
> find out what to use on the THIN CLIENT Program?
Have a look at <a href="http://help.sap.com/saphelp_nw04/helpdata/en/26/9b569f525445b0b3d66474b7569d39/frameset.htm">this</a> link.
> Thanks
Hope that helps,
Vladimir

JNDI Provider Connection With Weblogic 8.1

Hi all,
I am using SUN ONE Studio V 5.0 update 1 with weblogic 8.1 integrated with it.
Today I have added weblogic.jar in the classpath of the project.
Now I went to "runtime tab" and installed a jndi provider with factoryname and url successfully.
I tested the provider successfully :)
But when I tried to connect it to the service it failed.
IDE thrown a NPE and error message in dialog appears, says "TimeOut value is too short to connect".
There is no option for setting this timeout value.
Could any one pls help me regarding this. How can I get connected to JNDI service given by WL 8.1 ?
Has anyone also faced such problem ?
My server is up and smiling on me.
I am adding that error message fully....
java.lang.NullPointerException
     at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGenerator.java:785)
     at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:758)
     at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:803)
     at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
     at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
     at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
     at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
     at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
     at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
     at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
     at java.lang.Thread.run(Thread.java:534)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ] - with nested exception:
[java.lang.NullPointerException]
     at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:807)
     at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
     at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
     at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootServiceStub.java:50)
     at weblogic.security.acl.internal.Security.authenticate(Security.java:152)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:597)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:534)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:336)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:80)
     at org.netbeans.modules.jndi.JndiDirContext.<init>(JndiDirContext.java:47)
     at org.netbeans.modules.jndi.JndiDataType$1$Connector.checkContextValidity(JndiDataType.java:211)
     at org.netbeans.modules.jndi.JndiDataType$1$Connector.run(JndiDataType.java:169)
[catch] at java.lang.Thread.run(Thread.java:534)
one this more, if u see help then it is written that WL plugin will work only with jdk 1.3.1 and not with 1.4 but my plugin works successfully. What does it mean ?
My userdir is : C:\Utility\Dir4j, when I installed the provider for connecting to JNDI service of WL, then IDE created a dir C:\Utility\Dir4j\system\JNDI folder and created weblogic_jndi_WLInitialContextFactory.impl file under it.
Because I added that weblogic.jar file on my FSystem thats' why It created it under my userdir.
Pls Help
Sanjeev

Hi Sanjeev :
I am running into the same problem . Could you please be kind enough to tell me how you fixed the problem. I followed your solution but I am still running into the same problem.
Basically my WebStart application should be getting a connection from the Connection pool making a t3 call to a Weblogic server.
Thanks in advance .

JNDI Provider for wls 5.1 cluster

Similar Messages

Maybe you are looking for