What is "Replicate JNDI Name In Cluster" equivalent in Weblogic 10.3

Hi,
We are migrating one of our application from WL8 and WL10.3 where the existing setup using a non-distributed queue with "Replicate JNDI Name In Cluster" enabled. The cluster has 2 instances Ex: M1 and M2, both of these instances are using the aforesaid non-distributed queue which is tragetted only to M1 instance.
However the queue is targetted to M1, JNDI name associated to this Queue is available in M2 server so the MDB and Initial Context lookups are able to obtain the queue instance.
Now the issue is, we are unable to setup this feature in WL10.
1. We have created a UDQ and targetted to only M1.
2. MDBs and Intial context lookups from M2 is failing with NameNotFoundException.
Ultimatey the requirement is, the application deployed on cluster should consume/publish message only to/from queues available in M1. There is business reason behind this.
Please help.

Hi,
If your MDB is io version 3.0 then u can make use of the following Annotations to define the "*providerUrl*" of the server from where ur MDB wants to listen the messages.
Example: http://weblogic-wonders.com/weblogic/2010/06/09/mdb-with-non-container-specific-annotations/
initial-context-factory (Equivalent Property: initialContextFactory)
provider-url (Equivalent Property: providerURL)
ActivationConfigProperty(propertyName = “providerURL”, propertyValue = “your_MS1_Address”)
If you are using MDB2.0 then the same thing u need to do with "weblogic-ejb-jar.xml" file using <provider-url > Tag.
Thanks
Jay SenSharma

Similar Messages

JNDI-name and ejb-name

Hi,
I know 'ejb-name' should be the name used in ejb-jar.xml. what should be JNDI-name?
can I assign it to "xyz" or there is some strict rule? Is there any relation betn
'ejb-name' and 'JNDI-name'
Thanks a lot.
Vishal

Vishal,
ejb-name - name of the ejb
jndi-name- name by which remote components identify a particular bean.
it's name is unique. for naming policies
http://java.sun.com/products/jndi/tutorial/beyond/misc/policy.html
/Venki..
vishal patel wrote:
Hi,
I know 'ejb-name' should be the name used in ejb-jar.xml. what should be JNDI-name?
can I assign it to "xyz" or there is some strict rule? Is there any relation betn
'ejb-name' and 'JNDI-name'
Thanks a lot.
Vishal

Unable to bind EJB Home Interface to the JNDI name

Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Slava,
In case I change the name of the jndi name to a unique name. I still get the same
problem. I checked for multiple occurences, but there aren't any.
My web.xml file is:
<ejb-local-ref>
<description>
Reference EJB resources in Weblogic Resources
</description>
<ejb-ref-name>GangsterEJB</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
</ejb-local-ref>
My weblogic-ejb-jar.xml file is:
<weblogic-enterprise-bean>
<ejb-name>GangsterEJB</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/GangsterDB</res-ref-name>
<jndi-name>oraclePool</jndi-name>
</resource-description>
</reference-descriptor>
<local-jndi-name>Gangster_test</local-jndi-name>
</weblogic-enterprise-bean>
I do not get the problem.
Thank you
Ronak Parekh
"Slava Imeshev" <[email protected]> wrote:
Hi Ronak,
This exception means that you already have a bean
with the same JNDI name. Search your weblogic-ejb-jar.xml files
for multiple occurrences of the name and fix the problem.
Regards,
Slava Imeshev
"Ronak Parekh" <[email protected]> wrote in message
news:[email protected]...
Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

How the ejb is bound to JNDI name

I am very new to Oracle App server. In weblogic, we declare the jndi-name of an EJB in weblogic-ejb-jar.xml file.
I did not see this in OC4J.
Actualli I have written a simple stateful session bean and trying to access it through a standalone java client. But don't know what to look up in JNDI.
HELP PLEASE!!!!!!!!!

Hi Vinay,
Your question has been asked (and answered) many times previously in this forum. (However, when I tried searching the forum archives, I only got three results!?!)
The below code shows how to perform a lookup of the "home" interface of an EJB from a stand-alone, non-deployed java client:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
"com.evermind.server.rmi.RMIInitialContextFactory");
props.put(Context.PROVIDER_URL,"ormi://<host>/<app_name>");
props.put(Context.SECURITY_PRINCIPAL,"admin");
props.put(Context.SECURITY_CREDENTIALS,"<admin_password>");
new InitialContext(props).lookup("<home_name>");where "<host>" is the name of the machine where OC4J is running;
"<app_name>" is the name you gave to the application when you deployed it;
"<admin_password>" is the password for the "admin" user (that you supplied when you installed OC4J);
"<home_name>" is the value of the "<ejb-name>" element from your "ejb-jar.xml" file.
I have assumed that you have not set up any special security for your application -- otherwise you need to change the values for the SECURITY_PRINCIPAL and SECURITY_CREDENTIALS properties.
I have also assumed that you are using the stand-alone version of OC4J.
Good Luck,
Avi.

JNDI name for TransactionManager?

What is the JNDI name for TransactionManager on Oracle9ias? I thought
it was "java:comp/UserTransaction" but everytime I try to get the
TransactionManager I get a javax.naming.NamingTransaction, root exception is java.lang.NullPointerException. Any help would be appreciated. :-)
TransactionManager trans = null;
String name = null;
try {
InitialContext ctx = new javax.naming.InitialContext();
name = "java:comp/UserTransaction";
trans = (TransactionManager) ctx.lookup( name );
out.println("<p>*** class of TransactionManager is: " + trans);
trans.begin();

Srini,
You mention EJB client -> is the EJB an entity bean? Is it BMT or CMT? If its an entity bean with CMT then you cannot (and should not) be starting the transactions. If however this is BMT then you can use a Sesssion Bean to start and commit the transaction.
I have a feeling that you are using a remote client to access the EJB and then would like to start and commit a transaction. I would like to point out that this kind of transaction demarcation is not supported in OC4J. Here is quote from the OC4J documentation:
"Client-side transaction demarcation is not supported in the application client container: OC4J does not support client-side transaction demarcation. This form of transaction demarcation is not required by the J2EE specification, and is not recommended for performance and latency reasons."
I would recommend that you start using SLSB instead of remote clients.
Hope this helps.
Deepak

Ejb - jndi name

You do not specify JNDI name at console but in deployment descriptors.
"Ronak Parekh" <[email protected]> wrote in message
news:[email protected]..
what is the jndi name for the EJB? Where do you specify the EJB jndi namein
the console?/
Ronak

A prefix can be included in the EJB JNDI name dynamically?

In the Stateless annotation, we can specify the mappedName attribute to the EJB JNDI name bind.
Can we specify a prefix to the mappedName separately?
For example: We have this:
@Stateless(mappedName="myEJB")And don't want to do this:
@Stateless(mappedName="prefix/myEJB")We want to include the prefix in another place in the code dynamically.
Can we do that??

jtahlborn wrote:
eudesf wrote:
Hello! Thanks for reply!
As I can't configure programatically, there is any way to configure in an application descriptor, or in another place of the application server?
The idea is to publish two applications that use the same EJB classes, but in different JNDI namespaces, because we don't want to share the resources. Otherwise, it will result in JNDI name conflicts. The applications works in different contexts and we want to reuse the existing EJB definitions.
Any suggestion?yes you can do this. ejb 3.0 keeps the features from 2.1, namely all the xml based configuration (although it is now optional). and, the annotations are always overriden by the xml configuration. thus, you can create different deployments with different the same compiled class files. you just need to override the annotation configuration with xml configuration (via ejb-jar.xml or whatever).Yes, we can do that. I've tested here, and it works. But, can we do better?
The configuration via XML implies maintenance, and it's not good, because we have so many EJBs to maintain.
And there is another problem... The EJB classes are in JARs, and these JARs are shared across the applications.
Pretend that you have to maintain two versions of each EJB JAR. One with XML configured and other without. If we change one, the another must be changed too. How can it be productive?
I have seen some EJB implementations that are more flexible with JNDI naming.
See:
- [http://openejb.apache.org/jndi-names.html|http://openejb.apache.org/jndi-names.html]
- [http://fixunix.com/weblogic/221782-dynamic-jndi-name-weblogic-ejb-jar-xml.html|http://fixunix.com/weblogic/221782-dynamic-jndi-name-weblogic-ejb-jar-xml.html]
Does it have a better solution in Glassfish?

The DataSource with the JNDI name: MyDataSource could not be located.

hi,
I created a connection pool myconnectionpool and i create a data source MyDataSource with jndi name as mydsn.
in my weblogic-cmp-rdbms-jar.xml i gave
<data-source-name>MyDataSource</data-source-name> and
When i deploy the bean i am getting following exception.
Unable to deploy EJB: containerManaged from cmp7.jar:
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:128)
     at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:213)
     at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:185)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:160)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:928)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1216)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:850)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:70)
     at weblogic.j2ee.Application.addComponent(Application.java:253)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:144)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:301)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:255)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:206)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:716)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:698)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:380)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:902)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:480)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:208)
     at $Proxy34.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:3724)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1584)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:337)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:233)
     at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:852)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:273)
     at weblogic.Server.main(Server.java:33)
Where i went wrong?
Thanks in advance
phani

Hi ,
I have the same problem .when i look into JNDI tree view the jndi name is listed. but it saying error below listed.
my
ejb-name:=containerManaged
datasourcename=EX_DataSource
jndi-name=EX_JNDI
<Feb 14, 2005 3:10:08 PM IST> <Error> <Deployer> <149231> <The slave deployer was unable to set the activatio
true for the application EX_Container
weblogic.management.ApplicationException: activate failed forEX_Container
Module Name: EX_Container, Error: Exception activating module: EJBModule(EX_Container,status=PREPARED)
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
TargetException:
Unable to deploy EJB: containerManaged from EX_Container.jar:
The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1093)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1022)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLife
ava:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
my weblogic-ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>containerManaged</ejb-name>
<entity-descriptor>
<persistence>
     <persistence-use>
     <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
     <type-version>7.0</type-version>
     <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
     </persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>EX_JNDI</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
weblogic-cmp-rdbms-jar.xml file
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>containerManaged</ejb-name>
<data-source-name>EX_DataSource</data-source-name>
<table-map>
<table-name>ejbAccounts</table-name>
<field-map>
<cmp-field>accountId</cmp-field>
<dbms-column>id</dbms-column>
</field-map>
<field-map>
<cmp-field>balance</cmp-field>
<dbms-column>bal</dbms-column>
</field-map>
<field-map>
<cmp-field>accountType</cmp-field>
<dbms-column>type</dbms-column>
</field-map>
</table-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>DropAndCreateAlways</create-default-dbms-tables>
</weblogic-rdbms-jar>
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>containerManaged</ejb-name>
<home>containerBN.EX.AccountHome</home>
<remote>containerBN.EX.Account</remote>
<ejb-class>containerBN.EX.AccountBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>AccountBean</abstract-schema-name>
<cmp-field>
<field-name>accountId</field-name>
</cmp-field>
<cmp-field>
<field-name>balance</field-name>
</cmp-field>
<cmp-field>
<field-name>accountType</field-name>
</cmp-field>
<primkey-field>accountId</primkey-field>
<query>
<query-method>
<method-name>findBigAccounts</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance > ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findAccount</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance = ?1]]>
</ejb-ql>
</query>
<query>
<query-method>
<method-name>findNullAccounts</method-name>
<method-params>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.accountType IS NULL]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>containerManaged</ejb-name>
     <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EX_Container.jar</ejb-client-jar>
</ejb-jar>
pls lhelp me .
my email id: [email protected]
thanks in advance.
Sudhakar.M

WLS10.3.1 : How to overload the jndi name of a stateless EJB

Hi,
I am trying to overload the jndi name of a stateless bean defined in an application by using a weblogic-ejb-jar.xml descriptor file.
This does not work.
The ear contains a jar that have a weblogic-ejb-jar.xml file in its META-INF directory. The file is :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>TOTO</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
This is the code of my bean :
package test;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless( name = "HelloWorldBean", mappedName="HWBean")
@Local( IHelloWorldLocal.class)
@Remote( IHelloWorldRemote.class)
public class HelloWorldBean implements IHelloWorldLocal, IHelloWorldRemote
public void sayHello(String name) {
System.out.println( "Hello " + name + "!!!!");
The bean implements the following interfaces :
package test;
public interface IHelloWorldRemote extends IHelloWorld {
package test;
public interface IHelloWorldLocal extends IHelloWorld {
package test;
public interface IHelloWorld {
public void sayHello( String name);
When i browse the JNDI tree, i see the bean registered with the mapped name attribute (HWBean#test.IHelloWorldRemote) but i don't see any bean registered with the name provided by the weblogic-ejb-jar.xml (TOTO)
My standalone client can't perform a lookup using the JNDI name 'TOTO' but reaches the bean when using 'HWBean#test.IHelloWorldRemote'
It seem's that the overload of the Jndi name using the weblogic-ejb-jar file descriptor doesn't work.
Can you help me to solve the problem.
Thanks.

Thank you, my sample works fine with the following weblogic-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloWorldBean</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>test.IHelloWorldRemote</business-remote>
<jndi-name>TOTO</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

Weblogic 10.3 - changing jndi-name with deployment plan fails

I was trying to alter the global jndi name of a stateless ejb by using a deployment plan, but can't get it to work.
- to be able to replace it later on with a deployment plan, I specify a jndi-name in weblogic-ejb-jar.xml (so I do not use the @mappedName)
e.g.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
     <weblogic-enterprise-bean>
          <ejb-name>ExampleService</ejb-name>
          <enable-call-by-reference>true</enable-call-by-reference>
          <stateless-session-descriptor>
               <business-interface-jndi-name-map>
                    <business-remote>com.example.ExampleServiceRemote</business-remote>
                    <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
               </business-interface-jndi-name-map>
          </stateless-session-descriptor>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
- during deployment I specify a deploymentPlan with following content:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="true">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/stateless-session-descriptor/business-interface-jndi-name-map/\[business-remote="com.example.ExampleServiceRemote"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
- after deployment, the original jndi-name ("com.example.ExampleService#com.example.ExampleServiceRemote") is active in the jndi tree instead of "ExampleService"
p.s. When I specified the jndi-name in weblogic-ejb.jar.xml as
     <weblogic-enterprise-bean>
          <ejb-name>ExampleService</ejb-name>
          <enable-call-by-reference>true</enable-call-by-reference>
          <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
     </weblogic-enterprise-bean>
and the replace in the deployment plan as
<variable-assignment>
<name>ejb_jndiname_SecurityService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
the replacement does work (checked by verifying the jndi-name within the deployed ear using the console), but the problem then is that the jndi-name does not appear in the jndi tree (that's why I tried the <business-interface-jndi-name-map>)
Any ideas?
Kind regards,
Ben
Edited by: user11230128 on 4-jun-2009 7:42

After a Service Request and some trial and error, I got it to work after adding the following part in each 'jar module override' section of the deployment plan:
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
Apparantly this is needed even though there is no ejb-jar.xml in the jar.
So the deployment plan has to be something like:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name="ExampleService"]/stateless-session-descriptor/business-interface-jndi-name-map/[business-remote="com.example.ExampleServiceRemote"]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
</module-override>
...

Weblogic 12c ignores jndi-name definition. Why ?

Hi all!
I have a Stateless Bean which has a custom JNDI name defined in weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>CompanySFSB</ejb-name>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>model.logic.Company</business-remote>
<jndi-name>ejb/Company</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
However looking at the JNDI tree the bean is stored as "WLSEARWLSEJB_jarCompanySFSB_Company"
Therefore injecting the EJB as
@EJB(name = "CompanySFSB", mappedName = "ejb/Company")
Is there a way to store the EJB with the JNDI declared in weblogic-ejb-jar.xml ? or by using an annotation in the EJB ?
Thanks
Frank

Hi Frank,
Try this option in your startup script.
-Dweblogic.jndi.retainenvironment=true
Regards,
Kal

JNDI Names of JMS server's queue not replicating to cluster

          Am having some trouble configuring a JMS Server and Queues in a clustered development
          environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
          a single machine.
          The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
          names for the Queues appear in the JNDI tree of Server1, but not in Server2.
          When the sending of a message is attempted on Server2, the following occurs:
          javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
          didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
          This may be a problem with the cluster configuration, but I haven't been able
          to see anything wrong with it.
          Any and all help will be appreciated.
          There is the Config.xml file:
          <?xml version="1.0" encoding="UTF-8"?>
          <Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
          <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
          ListenPort="7001" Name="myserver" NativeIOEnabled="true"
          ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <SSL Enabled="false" HostnameVerificationIgnored="false"
          IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
          <Log Name="myserver" NumberOfFilesLimited="true"/>
          </Server>
          <Security Name="mydomain"
          PasswordPolicy="wl_default_password_policy"
          Realm="wl_default_realm" RealmSetup="true">
          <weblogic.security.providers.authentication.DefaultAuthenticator
          Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authentication.DefaultIdentityAsserter
          ActiveTypes="AuthenticatedUser"
          Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultRoleMapper
          Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultAuthorizer
          Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
          <weblogic.security.providers.authorization.DefaultAdjudicator
          Name="Security:Name=myrealmDefaultAdjudicator"
          Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
          <weblogic.security.providers.credentials.DefaultCredentialMapper
          Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
          <weblogic.management.security.authentication.UserLockoutManager
          Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
          <weblogic.management.security.Realm
          Adjudicator="Security:Name=myrealmDefaultAdjudicator"
          Auditors="Security:Name=myrealmSTARSIIAuditor"
          AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
          Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
          CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
          DefaultRealm="true" DisplayName="myrealm"
          FullyDelegateAuthorization="true"
          Name="Security:Name=myrealm"
          RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
          <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
          ControlFlag="SUFFICIENT"
          Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
          <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
          ExemptUri="/common/,/images/,/warning.do,/login.do"
          Name="Security:Name=myrealmSTARSIIAuthorizer"
          PolicyDeploymentEnabled="false"
          Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
          <gov.fns.starsii.common.security.audit.STARSIIAuditor
          Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
          </Security>
          <EmbeddedLDAP
          Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
          <SecurityConfiguration
          Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
          Name="mydomain" RealmBootStrapVersion="1"/>
          <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          <FileRealm Name="wl_default_file_realm"/>
          <PasswordPolicy Name="wl_default_password_policy"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII BRSB Pool"
          Password="{3DES}9pslRpr051lR9/NEKdanag=="
          Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
          PoolName="STARSII Store Pool" Targets="MyCluster"/>
          <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
          PoolName="STARSII Store Pool" Targets="MyCluster"/>
          
          <MailSession JNDIName="mail/STARSIIMailSession"
          Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Store Pool"
          Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          Targets="MyCluster"
          TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="AffTest" Password=""
          Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
          PoolName="AffTest" Targets=""/>
          <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
          Name="Spy STARSII BRSB Pool"
          Password="{3DES}9pslRpr051lR9/NEKdanag=="
          Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Store Pool 2"
          Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
          PoolName="STARSII Store Pool" Targets=""/>
          <JDBCConnectionPool
          DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          Name="STARSII Stars Pool"
          Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
          Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
          Targets="MyCluster"
          TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          <Machine Name="MachineA">
          <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
          </Machine>
          <Server Cluster="MyCluster" ExpectedToRun="false"
          ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
          ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
          Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <ServerDebug Name="Server1"/>
          <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
          <KernelDebug Name="Server1"/>
          <Log Name="Server1"/>
          <ServerStart Name="Server1"
          OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
          Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          <WebServer Name="Server1"/>
          <COM Name="Server1"/>
          <IIOP Name="Server1"/>
          <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
          <JTARecoveryService Name="Server1"/>
          </Server>
          <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
          MulticastAddress="226.0.0.244" Name="MyCluster"/>
          <Server Cluster="MyCluster" ExpectedToRun="false"
          ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
          ListenPort="7002" Machine="MachineB" Name="Server2"
          ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          <ServerDebug Name="Server2"/>
          <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
          <KernelDebug Name="Server2"/>
          <Log Name="Server2"/>
          <ServerStart Name="Server2"
          Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          <WebServer Name="Server2"/>
          <COM Name="Server2"/>
          <IIOP Name="Server2"/>
          <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
          <JTARecoveryService Name="Server2"/>
          </Server>
          <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
          Notes="This is a system generated default migratable target for a server.
          Do not delete manually." UserPreferredServer="Server1"/>
          <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
          Notes="This is a system generated default migratable target for a server.
          Do not delete manually." UserPreferredServer="Server2"/>
          <Application Deployed="true" Name="STARSII"
          Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
          <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
          <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
          <EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
          <EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
          <EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
          <EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
          <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
          <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
          <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
          <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
          <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
          </Application>
          <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
          StagingMode="nostage" TwoPhase="true">
          <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
          </Application>
          <Application Name="activeportal"
          Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
          StagingMode="nostage" TwoPhase="true">
          <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
          </Application>
          <JTA Name="mydomain" TimeoutSeconds="300"/>
          <JMSServer Name="JobServer" Targets="Server1 (migratable)">
          <JMSQueue CreationTime="1072820642598"
          JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
          <JMSQueue CreationTime="1072820669345"
          JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
          <JMSQueue CreationTime="1088000795852"
          JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
          <JMSQueue CreationTime="1072820687125"
          JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
          <JMSQueue CreationTime="1072820687125"
          JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
          <JMSQueue CreationTime="1072820687225"
          JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
          <JMSQueue CreationTime="1072820687325"
          JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
          <JMSQueue CreationTime="1072820687425"
          JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
          <JMSQueue CreationTime="1072820687525"
          JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
          <JMSQueue CreationTime="1072820687625"
          JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
          <JMSQueue CreationTime="1072820687725"
          JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
          <JMSQueue CreationTime="1072820687825"
          JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
          <JMSQueue CreationTime="1072820687925"
          JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
          <JMSQueue CreationTime="1072820688025"
          JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
          <JMSQueue CreationTime="1072820688125"
          JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
          <JMSQueue CreationTime="1072820688225"
          JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
          <JMSQueue CreationTime="1072820688325"
          JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
          </JMSServer>
          <Machine Name="MachineB">
          <NodeManager DebugEnabled="true" Name="MachineB"/>
          </Machine>
          </Domain>


Internally, many BEA developers and testers use various versions
          of XP with clustering on a daily basis. I don't know what
          is unique about your machine. I suggest raising the issue
          with customer support and/or posting to the clustering newsgroup...
          Andy Frank wrote:
          > It would seems that my OS and the MultiCast config are to blame. The MultiCast
          > test utility worked fine the Win2K machines I tried. Think I will take another
          > look at MS KB article 827536 and/or think about another dev OS.
          >
          > "Andy Frank" <[email protected]> wrote:
          >
          >>Tom,
          >>Thanks for this info.
          >>
          >>My servers don't look like they are running in different subnets (had
          >>a friend
          >>look this over and he concurs).
          >>
          >>My network admin says he hasn't blocked multicast traffic.
          >>
          >>I think the MultiCast test utility is telling me that I have some kind
          >>of multicast
          >>config problem. Output follows:
          >>
          >>------ Begin MultiCast test utility output: ------
          >>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
          >>237.155.15
          >>5.1 -t 15
          >>***** WARNING ***** WARNING ***** WARNING *****
          >>Do NOT use the same multicast address as a running WLS cluster.
          >>
          >>
          >>Starting test. Hit any key to abort
          >>
          >>
          >>Using multicast address 237.155.155.1:7001
          >>Will send messages under the name server200 every 2 seconds
          >>Will print warning every 15 seconds if no messages are received
          >>
          >> I (server200) sent message num 1
          >> I (server200) sent message num 2
          >> I (server200) sent message num 3
          >> I (server200) sent message num 4
          >> I (server200) sent message num 5
          >> I (server200) sent message num 6
          >> I (server200) sent message num 7
          >>java.net.SocketTimeoutException: Receive timed out
          >> at java.net.PlainDatagramSocketImpl.receive(Native Method)
          >> at java.net.DatagramSocket.receive(DatagramSocket.java:680)
          >> at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
          >> I (server200) sent message num 8
          >> I (server200) sent message num 9
          >> I (server200) sent message num 10
          >> I (server200) sent message num 11
          >> I (server200) sent message num 12
          >>------ End MultiCast test utility output: ------
          >>
          >>No "Received message X from server200" messages. I think I need to look
          >>into
          >>configuring multicast communications on my OK (Windows XP Pro, ver 2002
          >>SP1).
          >>I did see MS KB article 827536 about "An IP multicast may not be sent
          >>correctly
          >
          >>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
          >
          >>but
          >>the resolution scared me some.
          >>
          >>Think I will try some things out on another OS and see what that gets
          >>me.
          >>
          >>Any other thoughts on this will be appreciated.
          >>
          >>
          >>Tom Barnes wrote:
          >>
          >>>I too suspect something is going wrong with clustering, I wonder
          >>>if the servers are running in different subnets (even though
          >>>they are on the same box) and/or your network admin has
          >>>blocked multicast traffic.
          >>>
          >>>The MultiCast test utility should help narrow things down:
          >>>
          >>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
          >>>
          >>>Tom
          >>>
          >>>Andy Frank wrote:
          >>>
          >>>
          >>>>Am having some trouble configuring a JMS Server and Queues in a clustered
          >>>
          >>>development
          >>>
          >>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
          >>>
          >>>both on
          >>>
          >>>>a single machine.
          >>>>
          >>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
          >>
          >>>All the JNDI
          >>>
          >>>>names for the Queues appear in the JNDI tree of Server1, but not in
          >>>
          >>>Server2.
          >>>
          >>>>When the sending of a message is attempted on Server2, the following
          >>>
          >>>occurs:
          >>>
          >>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
          >>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
          >>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
          >>>>
          >>>>This may be a problem with the cluster configuration, but I haven't
          >>>
          >>>been able
          >>>
          >>>>to see anything wrong with it.
          >>>>
          >>>>Any and all help will be appreciated.
          >>>>
          >>>>There is the Config.xml file:
          >>>><?xml version="1.0" encoding="UTF-8"?>
          >>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
          >>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
          >>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
          >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          >>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
          >>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
          >>>
          >>>Name="myserver"/>
          >>>
          >>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
          >>>> </Server>
          >>>> <Security Name="mydomain"
          >>>> PasswordPolicy="wl_default_password_policy"
          >>>> Realm="wl_default_realm" RealmSetup="true">
          >>>> <weblogic.security.providers.authentication.DefaultAuthenticator
          >>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
          >>>>
          >>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
          >>>> ActiveTypes="AuthenticatedUser"
          >>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultRoleMapper
          >>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultAuthorizer
          >>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.security.providers.authorization.DefaultAdjudicator
          >>>> Name="Security:Name=myrealmDefaultAdjudicator"
          >>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
          >>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
          >>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.management.security.authentication.UserLockoutManager
          >>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
          >>>> <weblogic.management.security.Realm
          >>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
          >>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
          >>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
          >>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
          >>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
          >>>> DefaultRealm="true" DisplayName="myrealm"
          >>>> FullyDelegateAuthorization="true"
          >>>> Name="Security:Name=myrealm"
          >>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
          >>>>
          >>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
          >>>> ControlFlag="SUFFICIENT"
          >>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
          >>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
          >>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
          >>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
          >>>> PolicyDeploymentEnabled="false"
          >>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
          >>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
          >>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
          >>>> </Security>
          >>>> <EmbeddedLDAP
          >>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
          >>>
          >>>Name="mydomain"/>
          >>>
          >>>> <SecurityConfiguration
          >>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
          >>>> Name="mydomain" RealmBootStrapVersion="1"/>
          >>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          >>>> <FileRealm Name="wl_default_file_realm"/>
          >>>> <PasswordPolicy Name="wl_default_password_policy"/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII BRSB Pool"
          >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
          >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
          >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
          >>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
          >>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
          >>>> 
          >>>> <MailSession JNDIName="mail/STARSIIMailSession"
          >>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
          >>>
          >>>Targets="myserver"/>
          >>>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Store Pool"
          >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          >>>> Targets="MyCluster"
          >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="AffTest" Password=""
          >>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
          >>>> PoolName="AffTest" Targets=""/>
          >>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
          >>>> Name="Spy STARSII BRSB Pool"
          >>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
          >>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
          >>>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Store Pool 2"
          >>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
          >>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
          >>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
          >>>
          >>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>
          >>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
          >>>> PoolName="STARSII Store Pool" Targets=""/>
          >>>> <JDBCConnectionPool
          >>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
          >>>> Name="STARSII Stars Pool"
          >>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
          >>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
          >>>> Targets="MyCluster"
          >>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
          >>>> <Machine Name="MachineA">
          >>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
          >>>> </Machine>
          >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
          >>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
          >>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
          >>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
          >>>
          >>>StdoutSeverityLevel="64">
          >>>
          >>>> <ServerDebug Name="Server1"/>
          >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
          >>>> <KernelDebug Name="Server1"/>
          >>>> <Log Name="Server1"/>
          >>>> <ServerStart Name="Server1"
          >>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
          >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          >>>> <WebServer Name="Server1"/>
          >>>> <COM Name="Server1"/>
          >>>> <IIOP Name="Server1"/>
          >>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
          >>>> <JTARecoveryService Name="Server1"/>
          >>>> </Server>
          >>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
          >>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
          >>>> <Server Cluster="MyCluster" ExpectedToRun="false"
          >>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
          >>>> ListenPort="7002" Machine="MachineB" Name="Server2"
          >>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
          >>>> <ServerDebug Name="Server2"/>
          >>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
          >>>> <KernelDebug Name="Server2"/>
          >>>> <Log Name="Server2"/>
          >>>> <ServerStart Name="Server2"
          >>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
          >>>> <WebServer Name="Server2"/>
          >>>> <COM Name="Server2"/>
          >>>> <IIOP Name="Server2"/>
          >>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
          >>>> <JTARecoveryService Name="Server2"/>
          >>>> </Server>
          >>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
          >>>> Notes="This is a system generated default migratable target
          >>>
          >>>for a server.
          >>>
          >>>>Do not delete manually." UserPreferredServer="Server1"/>
          >>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
          >>>> Notes="This is a system generated default migratable target
          >>>
          >>>for a server.
          >>>
          >>>>Do not delete manually." UserPreferredServer="Server2"/>
          >>>> <Application Deployed="true" Name="STARSII"
          >>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
          >>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
          >>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
          >>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
          >>
          >>URI="../commonSession"/>
          >>
          >>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
          >>>
          >>>URI="../complianceMessage"/>
          >>>
          >>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
          >>>
          >>>URI="../complianceSession"/>
          >>>
          >>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
          >>
          >>URI="../starsiiEntity"/>
          >>
          >>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
          >>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
          >>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
          >>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
          >>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
          >>>> </Application>
          >>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
          >>>> StagingMode="nostage" TwoPhase="true">
          >>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
          >>>> </Application>
          >>>> <Application Name="activeportal"
          >>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
          >>>> StagingMode="nostage" TwoPhase="true">
          >>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
          >>>> </Application>
          >>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
          >>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
          >>>> <JMSQueue CreationTime="1072820642598"
          >>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
          >>>> <JMSQueue CreationTime="1072820669345"
          >>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
          >>>> <JMSQueue CreationTime="1088000795852"
          >>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
          >>>> <JMSQueue CreationTime="1072820687125"
          >>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
          >>>> <JMSQueue CreationTime="1072820687125"
          >>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
          >>>> <JMSQueue CreationTime="1072820687225"
          >>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
          >>>> <JMSQueue CreationTime="1072820687325"
          >>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
          >>>> <JMSQueue CreationTime="1072820687425"
          >>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
          >>>> <JMSQueue CreationTime="1072820687525"
          >>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
          >>>> <JMSQueue CreationTime="1072820687625"
          >>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
          >>>> <JMSQueue CreationTime="1072820687725"
          >>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
          >>>> <JMSQueue CreationTime="1072820687825"
          >>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820687925"
          >>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
          >>>> <JMSQueue CreationTime="1072820688025"
          >>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
          >>>> <JMSQueue CreationTime="1072820688125"
          >>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820688225"
          >>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
          >>>> <JMSQueue CreationTime="1072820688325"
          >>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
          >>>> </JMSServer>
          >>>> <Machine Name="MachineB">
          >>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
          >>>> </Machine>
          >>>></Domain>
          >>>
          >

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)

Jndi-name javax.naming.NameAlreadyBoundException:

Hi,
I am getting the following error while deploying a CMP Bean. Initially
this started to deploy, but later when I recompiled the source files
and tried to deploy again, I get the following errors.
In fact I am tired of trying to see what's actually happening.
Your immediate response is highly appreciated.
thanks and regards,
F S Joseph
Unable to deploy EJB: country from Country.jar:
weblogic.ejb20.WLDeploymentException: Unable to bind EJB Home
Interface to the JNDI name: ejb.CountryHome. The error was:
javax.naming.NameAlreadyBoundException: Failed to bind remote object
(ClusterableRemoteRef(127.0.0.1
null)/292     [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome])
to replica aware stub at CountryHome(ClusterableRemoteRef(127.0.0.1
[127.0.0.1/291])/291     [cashnet.ejb.CountryHome+javax.ejb.EJBHome+weblogic.ejb.QueryHome+weblogic.ejb20.interfaces.QueryHandler+weblogic.ejb20.interfaces.RemoteHome]);
remaining name 'ejb'
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
     at weblogic.jndi.internal.ServerNamingNode_WLStub.bind(Unknown
Source)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
     at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:353)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:951)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
     at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:956)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1302)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:342)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1509)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:970)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:957)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1074)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:700)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
failed application Country on cashnetserver

there is already an ejb with this name!
this is set in weblogic-ejb-jar.xml
Ronak Parekh wrote:
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name: Organization. The error
was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

How to setup JNDI Name for Oracle Apps adapter?

Hello,
I am learning Oracle SOA 11g and trying to do some tutorial on Oracle Application Adapter. I know how to configure JNDI for DBadapter and I did that successfully. I followed same steps to create New JNDI for Oracle Apps Adapter.
1. I Created new data source using Path Services->Data Sources -> New Genric Data Source. Connection to database was successful and created new JNDI Name: jdbc/PKDTAPPS.
2. Then Deployment-> OracleApps Adapter-> Configuration-> Outbound Connection Pools -> New and created JNDI Name eis/Apps/PKDTAPPS.
However I did not find newly created JNDI Name in step 2 under Deployment-> OracleApps Adapter-> Configuration-> Outbound Connection Pools -> javax.resource.cci.ConnectionFactory.
Please let me know if am I following correct steps to create new Oracle Apps Adapter JNDI Name or not.
Since above approch did not work I created new JNDI for DBAdapter with same database connection details. And then latter on use that JNDI Name while creating Oracle Application Adapter in JDeveloper composite. And it allowed me to access Oracel Apps open interface. However while deploying the application it gave me following error.
<Feb 16, 2015 10:50:59 AM CST> <Error> <oracle.integration.platform.blocks.deploy.servlet> <SOA-21537> <Sending back error message: There was an error deploying the composite on AdminServer: [JCABinding]
[adapter-Apps-101-JournalImport.InsertJournal/1.0]Unable to complete unload due to: Cannot locate Java class oracle.tip.adapter.apps.AppsTableWriteInteractionSpec: Cannot locate Java class
oracle.tip.adapter.apps.AppsTableWriteInteractionSpec..>
Since I have no past experience kindly suggest me what is right way to do this.
Thanks,
Shri

Hi shri,
Can you check the targets of oracle apps adapter that is it deployed on both cluster and admin server both.
Deployment-> OracleApps Adapter-> Targets
Regards,
Anshul

What is "Replicate JNDI Name In Cluster" equivalent in Weblogic 10.3

Similar Messages

Maybe you are looking for