JNDI Exception in Webgain 4.1

hi,
Was wondering if anyone had run into this issue: I have a relatively simple
RMI object held in BEA WLS 6.1 (its the RMI hello sample). The example
works fine in a DOS command window with the normal WLS examples environment
set.
When I try basically the same code under Visual Cafe 4.1, the exception
listed below occurs. The InitialContext is returned but the object lookup
fails. I do have the 6.1 weblogic jar in my classpath for Cafe.
TIA.
kwc
main (09:23:46): javax.naming.NameNotFoundException: Unable to resolve
HelloServer. Resolved: '' Unresolved:'HelloServer' ; remaining name ''
main (09:23:46): at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
quest.java:90)
main (09:23:46): at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:247)
main (09:23:46): at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:225)
main (09:23:46): at
weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(ServerNamingNode_WLStu
b.java:121)
main (09:23:46): at
weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
main (09:23:46): at
javax.naming.InitialContext.lookup(InitialContext.java:350)
main (09:23:47): at HelloClient.runHello(HelloClient.java:42)
main (09:23:47): at
TableExample3$DataUpdateThread.run(TableExample3.java:107)

Similar Messages

Jndi exception using weblogic.Admin

I was trying out the commands offered by weblogic.Admin to manage the packaged petstore server. I tried the following command and got jndi exception (null):
command:java weblogic.Admin -url petstoreServer.com:7001 GET -pretty -type Server
Error:Exception in thread "main" java.lang.IllegalArgumentException: JNDI naming exception: null
at weblogic.management.commandline.CommandLine.findMBeanHome(CommandLine.java:460)
at weblogic.management.commandline.CommandLine.doCommandline(CommandLine.java:86)
at weblogic.management.commandline.CommandLine.<init>(CommandLine.java:69)
at weblogic.Admin.main(Admin.java:689)
I checked in the console. A jndi name for petstoreServer does exist.

The current WebLogic 6.0 Beta-1 documentation incorrectly specifies the following in its example.
java weblogic.Admin -url xyz.com:7001 GET -pretty -type Server
This example falsely gives the impression that you must append ".com" to your host name. We will correct the document in the next revision to look like:
java weblogic.Admin -url hrserver:7001 GET -pretty -type Server
The -url petstoreServer.com:7001 parameter is incorrect. The command requires you to specify the <HostName>:<PortNumber> for the -url parameter.
Regards,
-Sachin
Helen Semus wrote:
I was trying out the commands offered by weblogic.Admin to manage the packaged petstore server. I tried the following command and got jndi exception (null):
command:java weblogic.Admin -url petstoreServer.com:7001 GET -pretty -type Server
Error:Exception in thread "main" java.lang.IllegalArgumentException: JNDI naming exception: null
at weblogic.management.commandline.CommandLine.findMBeanHome(CommandLine.java:460)
at weblogic.management.commandline.CommandLine.doCommandline(CommandLine.java:86)
at weblogic.management.commandline.CommandLine.<init>(CommandLine.java:69)
at weblogic.Admin.main(Admin.java:689)
I checked in the console. A jndi name for petstoreServer does exist.--
Sachin Thatte, Senior Software Engineer
BEA Systems, Inc
WWW: http://www.bea.com
[att1.html]

JNDI Exception : [System] not bound in naming services

Hi All,
Is there any way to resolve this JNDI exception "Invalid Path: [System/Launchers] not bound in naming service" ?
Thanks in Advance

This did not work dear. I assume when you say [Add ur datasource], you mean the name of the datasource, and I did as you told. I was wondering though that I have an independent java class which try to get data source from WSAD server, then how does web.xml help, may be I am not understanding the connection here.
Just to let you know, that same java class gets the datasource from 4.0 test server. I am running both servers now i.e. 4.0 test and 5.0 test server on different ports, and only data source from 4.0 workd good. Do you have any other solution, which I can try.
Is there any difference the way data source is accessed between 4.0 and 5.0 versions.
Thanks in advance.
Open web.xml, There will reference tab,, then take
Resource, Add ur datasourse on where the Cursor points
and then JNDI Name.
U need to restart ..

JNDI Exception while trying to create home object

Hi everyone,
I'm trying out a test application to create a home object in a remote computer. I'm using the SUN Ref-Impl v1.3 . I ran the small code below,
try {
Hashtable env= new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:1050");
env.put(Context.SECURITY_PRINCIPAL, "guest");
env.put(Context.SECURITY_CREDENTIALS, "guest123");
InitialContext ic= new InitialContext(env);
Object objRef= ic.lookup("jdbc/eVDB");
System.out.println("DB conn success!");
} catch (Exception ex) {
ex.printStackTrace();
System.out.println("Unable to conn DB... "+ ex.getMessage());
I successfully accessed this Database object wrapped in an entity bean through .jsp .
But when I ran the above code the follwing exception was emitted,
javax.naming.NameNotFoundException. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72)
     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:402)
     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at TestJNDI.main(TestJNDI.java:26)
Unable to conn DB... null
========================
If anybody can help me I would be most grateful. Thank you.

i added the j2ee.jar and the out put changed.
when i write,
ic.lookup("eV/CheckLogin");
it successfuly created the home object.
But when I added a database JNDI reference it failed,
when i wrote,
ic.lookup("java:comp/env/jdbc/eVDB");
the following exception occures,
javax.naming.NameNotFoundException: No object bound for java:comp/env/jdbc/eVDB
     at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at TestJNDI.main(TestJNDI.java:30)
and when i put,
ic.lookup("jdbc/eVDB")
the previous exception occures,
javax.naming.NameNotFoundException. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72)
     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:402)
     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at TestJNDI.main(TestJNDI.java:30)
===============
<sigh> I'm stumped...

JNDI Exception on Cluster Redeployment

"Does anyone know what was the resolution on the attached newsgroup posting? i am experiencing a similar


          Jerry Davis <[email protected]> wrote:
          >"Does anyone know what was the resolution on the attached newsgroup posting?
          > i am experiencing a similar
          This seems to have gotten chopped. I am seeing the following error when attempting
          to hot-deploy (through the admin console) a simple stateless EJB
          to the second managed server, and receive this exception. The first managed server
          receives the deployment no problem; it's only the second managed
          server that throws the exception.
          <Jun 14, 2001 4:56:39 PM CDT> <Error> <J2EE> <Error deploying application HelloWorld_EJB:
          Could not deploy: 'HelloWorld_EJB.jar': JNDI name in use
          >
          <Jun 14, 2001 4:56:39 PM CDT> <Error> <Management> <InvocationTargetException
          setting attribute Deployed on MBean wwt:Name=HelloWorld_EJB,Location=testlogic2Server,Type=ApplicationConfig
          to value true. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean)
          throws weblogic.management.DeploymentException,weblogic.management.UndeploymentException
          weblogic.management.DeploymentException: Could not deploy: 'HelloWorld_EJB.jar':
          JNDI name in use
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
          at weblogic.j2ee.Application.deploy(Application.java:167)
          at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
          at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:217)
          at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:187)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1136)
          at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:773)
          at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:750)
          at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:256)
          at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
          at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
          at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(RemoteMBeanServerImpl_WLSkel.java:1075)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
          at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Jun 14, 2001 4:56:39 PM CDT> <Error> <Cluster> <Conflict start: You tried to
          bind an object under the name HelloWorldBean_EO in the jndi tree. The object you
          have bound weblogic.rmi.cluster.ClusterableRemoteObject from prodlogic2 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.>

JNDI exception ..PLEASE HELP

hi
i am using the following expression to create a DataSource object
in my ejb application.
InitialContext ic=new InitialContext();
DataSource ds=(DataSource)ic.lookup("java:comp/env/jdbc/myAtmDB");
con=ds.getConnection();
When i deploy my app i am getting the following exception
javax.naming.Invalidname exception...real JNDI name cannot be empty
for jdbc/myAtmDB
thanks
bas

The 'java:comp/env/jdbc/myAtmDB' name you are referencing to is a name that you use in your code. In fact it is just an alias. Next thing to do is to use the deployment tool to point the alias to the 'real JNDI name' of the DataSource. You have probably left an empty spot somewhere in the resource reference tab.
regards,
Bert

Jndi exception

hi all,
i am getting this exception..I am using sun Application Sever 8.0
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory]
my code is here:
Properties prop = new Properties();
prop.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.fscontext.RefFSContextFactory");
prop.put(Context.PROVIDER_URL,"iiop://localhost:7676");
JndiTemplate jndi = new JndiTemplate(prop);
QueueConnectionFactory fabrika = (QueueConnectionFactory) jndi.lookup("qcf");
my factory and url is correct for sun application server 8.0?
thanks...

C:\JBuilderX\jdk1.4\bin\javaw -classpath "C:\HelloRMIIIOP\HelloRMIIIOP\classes;C:\JBuilderX\lib\cx.jar;C:\JBuilderX\jdk1.4\demo\jfc\Java2D\Java2Demo.jar;C:\JBuilderX\jdk1.4\demo\plugin\jfc\Java2D\Java2Demo.jar;C:\JBuilderX\jdk1.4\jre\javaws\javaws.jar;C:\JBuilderX\jdk1.4\jre\lib\applet\WMPNS.jar;C:\JBuilderX\jdk1.4\jre\lib\charsets.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\cosnaming.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\dnsns.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\ldapsec.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\localedata.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\providerutil.jar;C:\JBuilderX\jdk1.4\jre\lib\ext\sunjce_provider.jar;C:\JBuilderX\jdk1.4\jre\lib\im\indicim.jar;C:\JBuilderX\jdk1.4\jre\lib\im\thaiim.jar;C:\JBuilderX\jdk1.4\jre\lib\jce.jar;C:\JBuilderX\jdk1.4\jre\lib\jsse.jar;C:\JBuilderX\jdk1.4\jre\lib\plugin.jar;C:\JBuilderX\jdk1.4\jre\lib\rt.jar;C:\JBuilderX\jdk1.4\jre\lib\sunrsasign.jar;C:\JBuilderX\jdk1.4\lib\dt.jar;C:\JBuilderX\jdk1.4\lib\htmlconverter.jar;r" HelloServer
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.cosnaming.CNCtxFactory [Root exception is java.lang.ClassNotFoundException: com/sun/jndi/cosnaming/CNCtxFactory ]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)Trouble: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.cosnaming.CNCtxFactory [Root exception is java.lang.ClassNotFoundException: com/sun/jndi/cosnaming/CNCtxFactory ]
     at javax.naming.InitialContext.<init>(InitialContext.java:175)
     at HelloServer.main(HelloServer.java:13)
Caused by: java.lang.ClassNotFoundException: com/sun/jndi/cosnaming/CNCtxFactory
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
     ... 4 more
please help!!!i its driving me nuts!!!

JNDI Exception on re-deployment to a cluster

I'm getting an error that I have not seen in the newsgroups so far. It
          happens when I deploy what I believe to be a properly configured clusterable
          application (.ear file) to my cluster.
          Here's my setup:
          WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
          is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
          cluster). The 1st managed server (app1) is also on Stimpy bound to
          10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
          (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
          to deploy the app. (I turned auto-deploy off because the app was getting
          deployed to the admin server automatically and throwing an error because of
          the clustered HTTP session state)
          Here's what happens.
          I start up all of the instances with no apps deployed. Everything appears
          to be running fine. No errors. I then use the console to deploy my
          application (sample1.0.ear). I select only the cluster as the target for
          the EJB and the webapp. If I try to access the app at this point I just get
          404's. I then restart all of the servers and the app gets deployed across
          the cluster with no errors. I can access everything JSPs, servlets, and an
          EJB without issue.
          My problem comes when I try to re-deploy the application. I have tried this
          using the console, and by copying the new .ear file to the applications
          directory on the admin server. I always get the same error, and it only
          shows up on "app1" the first managed server in the cluster. Below is the
          output form the log:
          Undeploying EJB Component HelloWorldEJB
          <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
          <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
          HelloWorldEJB.j
          ar>
          <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
          : H
          elloWorldEJB
          weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
          exc
          eption is:
          javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          repl
          ica-aware stub to a name that is currently bound to a replica-aware stub;
          remain
          ing name ''
          javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          replica-awar
          e stub to a name that is currently bound to a replica-aware stub; remaining
          name
          <<no stack trace available>>
          >
          <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
          sampl
          e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
          >
          <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
          <InvocationTargetException s
          etting attribute Deployed on MBean
          me:Name=sample1.0,Location=app3,Type=Applicat
          ionConfig to value true. Method: public void
          weblogic.management.mbeans.custom.A
          pplication.setDeployed(boolean) throws
          weblogic.management.DeploymentException,w
          eblogic.management.UndeploymentException
          weblogic.management.DeploymentException: Could not deploy:
          'HelloWorldEJB.jar':
          JNDI name in use
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
          at weblogic.j2ee.Application.deploy(Application.java:167)
          at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
          at
          weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
          ation.java:217)
          at
          weblogic.management.mbeans.custom.Application.setDeployed(Application
          .java:187)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
          anImpl.java:1136)
          at
          weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
          anImpl.java:773)
          at
          weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
          anImpl.java:750)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
          igurationMBeanImpl.java:256)
          at
          com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
          ava:1356)
          at
          com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
          ava:1331)
          at
          weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
          teMBeanServerImpl_WLSkel.java:1075)
          at
          weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:373)
          at
          weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:237)
          at
          weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
          andler.java:118)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:17)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
          to b
          ind an object under the name HelloWorldHome_EO in the jndi tree. The object
          you
          have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 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.>
          <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
          to b
          ind an object under the name HelloWorldHome in the jndi tree. The object you
          hav
          e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
          clu
          sterable and you have tried to bind more than once from two or more servers.
          Suc
          h objects can only deployed from one server.>
          Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
          As far as I know, I have not installed the EJB2.0 container. Does this get
          installed by default with sp1? Also, I quite sure that my deployment
          descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
          EJB:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
          EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>HelloWorld</ejb-name>
          <caching-descriptor>
          <max-beans-in-free-pool>100</max-beans-in-free-pool>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
          potent>
          </clustering-descriptor>
          <jndi-name>HelloWorldHome</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
          going on here?


This seems like potential redeploy/undeploy bugs. COuld you follow up with
          [email protected]
          Viresh Garg
          Principal Developer Relations Engineer
          BEA Systems
          Paul Citarella wrote:
          > I'm getting an error that I have not seen in the newsgroups so far. It
          > happens when I deploy what I believe to be a properly configured clusterable
          > application (.ear file) to my cluster.
          >
          > Here's my setup:
          > WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
          > is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
          > cluster). The 1st managed server (app1) is also on Stimpy bound to
          > 10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
          > (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
          > to deploy the app. (I turned auto-deploy off because the app was getting
          > deployed to the admin server automatically and throwing an error because of
          > the clustered HTTP session state)
          >
          > Here's what happens.
          >
          > I start up all of the instances with no apps deployed. Everything appears
          > to be running fine. No errors. I then use the console to deploy my
          > application (sample1.0.ear). I select only the cluster as the target for
          > the EJB and the webapp. If I try to access the app at this point I just get
          > 404's. I then restart all of the servers and the app gets deployed across
          > the cluster with no errors. I can access everything JSPs, servlets, and an
          > EJB without issue.
          >
          > My problem comes when I try to re-deploy the application. I have tried this
          > using the console, and by copying the new .ear file to the applications
          > directory on the admin server. I always get the same error, and it only
          > shows up on "app1" the first managed server in the cluster. Below is the
          > output form the log:
          >
          > Undeploying EJB Component HelloWorldEJB
          > <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
          > <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
          > HelloWorldEJB.j
          > ar>
          > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
          > : H
          > elloWorldEJB
          > weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
          > exc
          > eption is:
          > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          > repl
          > ica-aware stub to a name that is currently bound to a replica-aware stub;
          > remain
          > ing name ''
          > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
          > replica-awar
          > e stub to a name that is currently bound to a replica-aware stub; remaining
          > name
          > ''
          > <<no stack trace available>>
          > >
          > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
          > sampl
          > e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
          > >
          > <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
          > <InvocationTargetException s
          > etting attribute Deployed on MBean
          > me:Name=sample1.0,Location=app3,Type=Applicat
          > ionConfig to value true. Method: public void
          > weblogic.management.mbeans.custom.A
          > pplication.setDeployed(boolean) throws
          > weblogic.management.DeploymentException,w
          > eblogic.management.UndeploymentException
          > weblogic.management.DeploymentException: Could not deploy:
          > 'HelloWorldEJB.jar':
          > JNDI name in use
          >
          > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
          > at weblogic.j2ee.Application.deploy(Application.java:167)
          > at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
          > at
          > weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
          > ation.java:217)
          > at
          > weblogic.management.mbeans.custom.Application.setDeployed(Application
          > .java:187)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
          > anImpl.java:1136)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
          > anImpl.java:773)
          > at
          > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
          > anImpl.java:750)
          > at
          > weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
          > igurationMBeanImpl.java:256)
          > at
          > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
          > ava:1356)
          > at
          > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
          > ava:1331)
          > at
          > weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
          > teMBeanServerImpl_WLSkel.java:1075)
          > at
          > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          > va:373)
          > at
          > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          > va:237)
          > at
          > weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
          > andler.java:118)
          > at
          > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > .java:17)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          > <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
          > to b
          > ind an object under the name HelloWorldHome_EO in the jndi tree. The object
          > you
          > have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 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.>
          > <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
          > to b
          > ind an object under the name HelloWorldHome in the jndi tree. The object you
          > hav
          > e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
          > clu
          > sterable and you have tried to bind more than once from two or more servers.
          > Suc
          > h objects can only deployed from one server.>
          >
          > Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
          > As far as I know, I have not installed the EJB2.0 container. Does this get
          > installed by default with sp1? Also, I quite sure that my deployment
          > descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
          > EJB:
          >
          > <?xml version="1.0"?>
          > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
          > EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
          > <weblogic-ejb-jar>
          > <weblogic-enterprise-bean>
          > <ejb-name>HelloWorld</ejb-name>
          > <caching-descriptor>
          > <max-beans-in-free-pool>100</max-beans-in-free-pool>
          > </caching-descriptor>
          > <clustering-descriptor>
          > <home-is-clusterable>true</home-is-clusterable>
          > <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          > <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
          > potent>
          > </clustering-descriptor>
          > <jndi-name>HelloWorldHome</jndi-name>
          > </weblogic-enterprise-bean>
          > </weblogic-ejb-jar>
          >
          > Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
          > going on here?

Jboss jndi exception

i deployed jca tuxedo in jboss and everything look good, the connexion is stablished, but when in my web appllication i try to do a lookup, the jndi dont get me the connection factory :
this is the log when im deploying de rar file :
2/13/12:2:30:44 PM:10:INFO[,registerClientSideResourceAdapter]TJA_0220:Tuxedo JCA Adapter, release 11gR1(11.1.1.2.1), resource archive version 1.1.0.0, build date: October 29 2010.
2/13/12:2:30:44 PM:10:TRACE[,TJAService]> ()
2/13/12:2:30:44 PM:10:DBG[,TJAService]xaAffinity = true
2/13/12:2:30:44 PM:10:TRACE[,TJAService]< return(10)
2/13/12:2:30:44 PM:10:TRACE[,][/TJAService/startTJAService/
2/13/12:2:30:44 PM:10:TRACE[,]create tuxedo subcontext
2/13/12:2:30:44 PM:10:TRACE[,]create tuxedo.services subcontext
2/13/12:2:30:44 PM:10:TRACE[,]/TJAService/startTJAService/110/TC Service started...
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Configuration Helper instantiated!
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Outbound routing service instantiated!
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Task Manager instantiated!
2/13/12:2:30:44 PM:10:TRACE[,TJASecurityService]> ()
2/13/12:2:30:44 PM:10:TRACE[,TJASecurityService]< return(10)
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC security service instantiated!
2/13/12:2:30:44 PM:10:INFO[,createRemoteAccessPoints#2]TJA_0201:INFO: RemoteAccessPoint Gdomtux created.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use Local to create default session profile property CredentialPolicy.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 0 to create default session profile property MinEncryptBits.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 128 to create default session profile property MaxEncryptBits.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use NONE to create default session profile property Security.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use ON_STARTUP to create default session profile property ConnectionPolicy.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 60,000 to create default session profile property BlockTime.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use false to create default session profile property Interoperate.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 3,600,000 to create default session profile property RetryInterval.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 7,208,000 to create default session profile property MaxRetries.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 2,147,483,647 to create default session profile property CompressionLimit.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 0 to create default session profile property KeepAlive.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 10,000 to create default session profile property KeepAliveWait.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0189:INFO: Default session profile created.
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Transaction service instantiated!
2/13/12:2:30:44 PM:10:INFO[,createDefaultSession]TJA_0193:INFO: Default session created between LocalAccessPoint jcaTux and RemoteAccessPoint Gdomtux.
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]> (QSPACETEST)
2/13/12:2:30:44 PM:10:INFO[,]factory = null
2/13/12:2:30:44 PM:10:INFO[,]name = QSPACETEST
2/13/12:2:30:44 PM:10:INFO[,]iname = QSPACETEST
2/13/12:2:30:44 PM:10:INFO[,]rsvc == null, create new ArrayList with key= QSPACETEST
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]< return(40) rtg com.oracle.tuxedo.adapter.config.RouteGroup@104e583
2/13/12:2:30:44 PM:10:INFO[,createImportFromProperty]TJA_0195:INFO: Imported resource QSPACETEST created.
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]> (STRING)
2/13/12:2:30:44 PM:10:INFO[,]factory = null
2/13/12:2:30:44 PM:10:INFO[,]name = STRING
2/13/12:2:30:44 PM:10:INFO[,]iname = STRING
2/13/12:2:30:44 PM:10:INFO[,]rsvc == null, create new ArrayList with key= STRING
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]< return(40) rtg com.oracle.tuxedo.adapter.config.RouteGroup@781bc7
2/13/12:2:30:44 PM:10:INFO[,createImportFromProperty]TJA_0195:INFO: Imported resource STRING created.
2/13/12:2:30:44 PM:17:TRACE[,][/ScheduledReconnect/run/Gdomtux
2/13/12:2:30:45 PM:17:TRACE[,]]/ScheduledReconnect/run/10/return
2/13/12:2:30:45 PM:18:TRACE[,][/CeInvoke/com.oracle.tuxedo.adapter.config.DMSession@1701ba3
2/13/12:2:30:45 PM:18:TRACE[,]]/CeInvoke/10
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/get_sess_sec/
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/get_sess_sec/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/set_dom_target_name/Gdomtux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/set_dom_target_name/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/set_local_domain_name/jcaTux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/set_local_domain_name/10
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setRemoteDomainId/Gdomtux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setRemoteDomainId/10
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]> () com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]disable keepalive
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kas = 0, kaExpTime = 0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kaws = -1, kawExpTime = 0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kaState = -1
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]< (10) return
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setKeepAliveWait/10000
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setKeepAliveWait/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setAppKey/1
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setAppKey/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setAllowAnonymous/true
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setAllowAnonymous/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setDfltAppKey/65536
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setDfltAppKey/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setEncryptionFlags/39
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setEncryptionFlags/10
2/13/12:2:30:45 PM:18:TRACE[,tpinit]>(weblogic.wtc.jatmi.TPINIT@baa0)
2/13/12:2:30:45 PM:18:TRACE[,tpinit]tpinfo.usrname: jcaTux
2/13/12:2:30:45 PM:18:TRACE[,do_connect]> (jcaTux) com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/alloc_TDOM/14/null
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/alloc_TDOM/10/TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null
2/13/12:2:30:45 PM:18:TRACE[,][/write_dom_65_tfmh/jcaTux/10/134217727
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/header calculated_size=524
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/opcode calculated_size=540
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/total calculated_size=540
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=10/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/writeTuxedoMessage/70/
2/13/12:2:30:45 PM:18:TRACE[,]/tfmh/write_dom_65_tfmh/TdomTcb=TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=540/myMark=540/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]*]/TpeOut/writeTuxedoMessage/40/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_dom_65_tfmh/110/0/
2/13/12:2:30:45 PM:18:TRACE[,][/read_dom_65_tfmh/10
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=32/myOffset=0/myMark=0/myProtocol=10/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=32
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=32/myMark=0
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/size=544
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=0/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/150/true
2/13/12:2:30:45 PM:18:TRACE[,]/tfmh/read_dom_65_tfmh/opcode=GWNW_XATMI_PRE_NW_ACALL1_RPLY
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/available/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=32/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/available/50/0
2/13/12:2:30:45 PM:18:TRACE[,]/read_dom_65_tfmh/bufsize=544 available=0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=32/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=512
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=544/myMark=32
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/120/true
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_security_type 0
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_security_type
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_tm_release 103
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_tm_release
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_dom_protocol 16
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_dom_protocol
2/13/12:2:30:45 PM:18:TRACE[,]]/read_dom_65_tfmh/70/0/0
2/13/12:2:30:45 PM:18:DBG[,do_connect]Remote gateway support features = 159
2/13/12:2:30:45 PM:18:DBG[,do_connect]dom_protocol = 16
2/13/12:2:30:45 PM:18:DBG[,do_connect]do LLE protocol
2/13/12:2:30:45 PM:18:DBG[,do_connect]lle buffer size = 2048
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/crypKeyeOne/eflags 4
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/crypKeyeOne/70/640
2/13/12:2:30:45 PM:18:TRACE[,][/write_tfmh/
2/13/12:2:30:45 PM:18:TRACE[,][/write_tcm/
2/13/12:2:30:45 PM:18:TRACE[,][/UserTcb/_tmpresend/java.io.DataOutputStream@12e3c04/weblogic.wtc.jatmi.tch@665e81
2/13/12:2:30:45 PM:18:TRACE[,]]/UserTcb/_tmpresend/60/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tcm/40/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/wrote user tcm/712
2/13/12:2:30:45 PM:18:TRACE[,][/write_tcm/
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/_tmpresend/weblogic.wtc.jatmi.tch@3fcce8
2/13/12:2:30:45 PM:18:TRACE[,]/TdomTcb/_tmpresend/opcode=20/reqid=1
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/_tmpresend/20
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tcm/40/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/wrote tdom tcm/792
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/Not compressed/calculated_size=792/
2/13/12:2:30:45 PM:18:TRACE[,][/write_metahdr/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=16/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/writeTuxedoMessage/70/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_metahdr/10/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/magic=-1862035368/ltype_idx=16/tmfmh_flag=65536
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/write(b)/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=792/myMark=792/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]*]/TpeOut/writeTuxedoMessage/40/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/write/30/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tfmh/100/0/
2/13/12:2:30:45 PM:18:DBG[,do_connect]...send LLE
2/13/12:2:30:45 PM:18:TRACE[,][/read_tfmh/
2/13/12:2:30:45 PM:18:TRACE[,][/read_metahdr/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=544/myMark=544/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/resetting mark for next Tuxedo buffer
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=32
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=32/myMark=0
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/size=384
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=352/myOffset=32/myMark=0/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/150/true
2/13/12:2:30:45 PM:18:TRACE[,]]/read_metahdr/10
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=352/myOffset=32/myMark=32/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=352
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=384/myMark=32
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/120/true
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/read(b)/232/0/232
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/read(b)/30/232
2/13/12:2:30:45 PM:18:TRACE[,]]/read_tfmh/80/0
2/13/12:2:30:45 PM:18:DBG[,do_connect]...recv LLE_RPLY
2/13/12:2:30:45 PM:18:DBG[,do_connect]recv size = 232
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/crypFinishOne/
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/decodeDH2/0
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/decodeDH2/10/224
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/generateFingerprint/
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/generateFingerprint/
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/crypFinishOne/130/LLE_DH2_128
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/setELevel(4)/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/setElevel/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/setLLE/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/setLLE/10/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/setElevel/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/setElevel/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/setLLE/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/setLLE/10/
2/13/12:2:30:45 PM:18:TRACE[,]/dsession(0)/do_connect/ready to use LLE
2/13/12:2:30:45 PM:18:DBG[,do_connect]ready to use LLE
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setUpTuxedoAAA/
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setUpTuxedoAAA/10/return 0
2/13/12:2:30:45 PM:18:DBG[,do_connect]chan = java.nio.channels.SocketChannel[connected local=192.168.19.156/192.168.19.156:36898 remote=/192.168.19.156:8888]
2/13/12:2:30:45 PM:18:DBG[,do_connect]myXidRplyObj = null
2/13/12:2:30:45 PM:18:DBG[,rdsession]myTimeService = java.util.Timer@797bc6
2/13/12:2:30:45 PM:18:TRACE[,dmqDecision]> () com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,dmqDecision]< (10) return
2/13/12:2:30:45 PM:18:INFO[,do_connect]TJA_0130:Established connection to remote domain Gdomtux.
2/13/12:2:30:45 PM:18:TRACE[,do_connect]< return(350) success
2/13/12:2:30:45 PM:18:TRACE[,tpinit]< return(50) success, uid = 0
2/13/12:2:30:45 PM:18:TRACE[,][/ScheduledReconnect/connectingSuccess/session = __sess_0_0
2/13/12:2:30:45 PM:18:TRACE[,]]/ScheduledReconnect/connectingSuccess/10/return
but since my web application try to do a look up, i cant get the connection factory by jndi , the descriptor is :
<resource-adapter>
<archive>
TuxedoAdapter.rar
</archive>
<transaction-support>
NoTransaction
</transaction-support>
<connection-definitions>
<connection-definition class-name="com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory"
     jndi-name="java:jboss/eis/TuxedoConnectionFactory" enabled="true" use-java-context="false"/>
</connection-definitions>
</resource-adapter>
ctx = new InitialContext();
          cf = (TuxedoConnectionFactory) ctx.lookup("java:jboss/eis/TuxedoConnectionFactory");
          c = cf.getConnection();
Edited by: 907185 on 13/02/2012 12:01

i deployed jca tuxedo in jboss and everything look good, the connexion is stablished, but when in my web appllication i try to do a lookup, the jndi dont get me the connection factory :
this is the log when im deploying de rar file :
2/13/12:2:30:44 PM:10:INFO[,registerClientSideResourceAdapter]TJA_0220:Tuxedo JCA Adapter, release 11gR1(11.1.1.2.1), resource archive version 1.1.0.0, build date: October 29 2010.
2/13/12:2:30:44 PM:10:TRACE[,TJAService]> ()
2/13/12:2:30:44 PM:10:DBG[,TJAService]xaAffinity = true
2/13/12:2:30:44 PM:10:TRACE[,TJAService]< return(10)
2/13/12:2:30:44 PM:10:TRACE[,][/TJAService/startTJAService/
2/13/12:2:30:44 PM:10:TRACE[,]create tuxedo subcontext
2/13/12:2:30:44 PM:10:TRACE[,]create tuxedo.services subcontext
2/13/12:2:30:44 PM:10:TRACE[,]/TJAService/startTJAService/110/TC Service started...
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Configuration Helper instantiated!
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Outbound routing service instantiated!
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Task Manager instantiated!
2/13/12:2:30:44 PM:10:TRACE[,TJASecurityService]> ()
2/13/12:2:30:44 PM:10:TRACE[,TJASecurityService]< return(10)
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC security service instantiated!
2/13/12:2:30:44 PM:10:INFO[,createRemoteAccessPoints#2]TJA_0201:INFO: RemoteAccessPoint Gdomtux created.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use Local to create default session profile property CredentialPolicy.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 0 to create default session profile property MinEncryptBits.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 128 to create default session profile property MaxEncryptBits.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use NONE to create default session profile property Security.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use ON_STARTUP to create default session profile property ConnectionPolicy.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 60,000 to create default session profile property BlockTime.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use false to create default session profile property Interoperate.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 3,600,000 to create default session profile property RetryInterval.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 7,208,000 to create default session profile property MaxRetries.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 2,147,483,647 to create default session profile property CompressionLimit.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 0 to create default session profile property KeepAlive.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0188:INFO: Use 10,000 to create default session profile property KeepAliveWait.
2/13/12:2:30:44 PM:10:INFO[,createDefaultSessionProfile]TJA_0189:INFO: Default session profile created.
2/13/12:2:30:44 PM:10:TRACE[,]INFO: TC Transaction service instantiated!
2/13/12:2:30:44 PM:10:INFO[,createDefaultSession]TJA_0193:INFO: Default session created between LocalAccessPoint jcaTux and RemoteAccessPoint Gdomtux.
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]> (QSPACETEST)
2/13/12:2:30:44 PM:10:INFO[,]factory = null
2/13/12:2:30:44 PM:10:INFO[,]name = QSPACETEST
2/13/12:2:30:44 PM:10:INFO[,]iname = QSPACETEST
2/13/12:2:30:44 PM:10:INFO[,]rsvc == null, create new ArrayList with key= QSPACETEST
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]< return(40) rtg com.oracle.tuxedo.adapter.config.RouteGroup@104e583
2/13/12:2:30:44 PM:10:INFO[,createImportFromProperty]TJA_0195:INFO: Imported resource QSPACETEST created.
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]> (STRING)
2/13/12:2:30:44 PM:10:INFO[,]factory = null
2/13/12:2:30:44 PM:10:INFO[,]name = STRING
2/13/12:2:30:44 PM:10:INFO[,]iname = STRING
2/13/12:2:30:44 PM:10:INFO[,]rsvc == null, create new ArrayList with key= STRING
2/13/12:2:30:44 PM:10:TRACE[,registerImportedService]< return(40) rtg com.oracle.tuxedo.adapter.config.RouteGroup@781bc7
2/13/12:2:30:44 PM:10:INFO[,createImportFromProperty]TJA_0195:INFO: Imported resource STRING created.
2/13/12:2:30:44 PM:17:TRACE[,][/ScheduledReconnect/run/Gdomtux
2/13/12:2:30:45 PM:17:TRACE[,]]/ScheduledReconnect/run/10/return
2/13/12:2:30:45 PM:18:TRACE[,][/CeInvoke/com.oracle.tuxedo.adapter.config.DMSession@1701ba3
2/13/12:2:30:45 PM:18:TRACE[,]]/CeInvoke/10
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/get_sess_sec/
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/get_sess_sec/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/set_dom_target_name/Gdomtux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/set_dom_target_name/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/set_local_domain_name/jcaTux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/set_local_domain_name/10
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setRemoteDomainId/Gdomtux
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setRemoteDomainId/10
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]> () com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]disable keepalive
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kas = 0, kaExpTime = 0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kaws = -1, kawExpTime = 0
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]kaState = -1
2/13/12:2:30:45 PM:18:TRACE[,setKeepAlive]< (10) return
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setKeepAliveWait/10000
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setKeepAliveWait/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setAppKey/1
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setAppKey/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setAllowAnonymous/true
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setAllowAnonymous/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession/setDfltAppKey/65536
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setDfltAppKey/10/
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setEncryptionFlags/39
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/setEncryptionFlags/10
2/13/12:2:30:45 PM:18:TRACE[,tpinit]>(weblogic.wtc.jatmi.TPINIT@baa0)
2/13/12:2:30:45 PM:18:TRACE[,tpinit]tpinfo.usrname: jcaTux
2/13/12:2:30:45 PM:18:TRACE[,do_connect]> (jcaTux) com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/alloc_TDOM/14/null
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession(0)/alloc_TDOM/10/TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null
2/13/12:2:30:45 PM:18:TRACE[,][/write_dom_65_tfmh/jcaTux/10/134217727
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/header calculated_size=524
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/opcode calculated_size=540
2/13/12:2:30:45 PM:18:TRACE[,]/write_dom_65_tfmh/total calculated_size=540
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=10/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/writeTuxedoMessage/70/
2/13/12:2:30:45 PM:18:TRACE[,]/tfmh/write_dom_65_tfmh/TdomTcb=TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=540/myMark=540/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]*]/TpeOut/writeTuxedoMessage/40/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_dom_65_tfmh/110/0/
2/13/12:2:30:45 PM:18:TRACE[,][/read_dom_65_tfmh/10
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=32/myOffset=0/myMark=0/myProtocol=10/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=32
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=32/myMark=0
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/size=544
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=0/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/150/true
2/13/12:2:30:45 PM:18:TRACE[,]/tfmh/read_dom_65_tfmh/opcode=GWNW_XATMI_PRE_NW_ACALL1_RPLY
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/available/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=32/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/available/50/0
2/13/12:2:30:45 PM:18:TRACE[,]/read_dom_65_tfmh/bufsize=544 available=0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=32/myProtocol=10/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=512
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=544/myMark=32
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/120/true
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_security_type 0
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_security_type
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_tm_release 103
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_tm_release
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/set_dom_protocol 16
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/set_dom_protocol
2/13/12:2:30:45 PM:18:TRACE[,]]/read_dom_65_tfmh/70/0/0
2/13/12:2:30:45 PM:18:DBG[,do_connect]Remote gateway support features = 159
2/13/12:2:30:45 PM:18:DBG[,do_connect]dom_protocol = 16
2/13/12:2:30:45 PM:18:DBG[,do_connect]do LLE protocol
2/13/12:2:30:45 PM:18:DBG[,do_connect]lle buffer size = 2048
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/crypKeyeOne/eflags 4
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/crypKeyeOne/70/640
2/13/12:2:30:45 PM:18:TRACE[,][/write_tfmh/
2/13/12:2:30:45 PM:18:TRACE[,][/write_tcm/
2/13/12:2:30:45 PM:18:TRACE[,][/UserTcb/_tmpresend/java.io.DataOutputStream@12e3c04/weblogic.wtc.jatmi.tch@665e81
2/13/12:2:30:45 PM:18:TRACE[,]]/UserTcb/_tmpresend/60/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tcm/40/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/wrote user tcm/712
2/13/12:2:30:45 PM:18:TRACE[,][/write_tcm/
2/13/12:2:30:45 PM:18:TRACE[,][/TdomTcb/_tmpresend/weblogic.wtc.jatmi.tch@3fcce8
2/13/12:2:30:45 PM:18:TRACE[,]/TdomTcb/_tmpresend/opcode=20/reqid=1
2/13/12:2:30:45 PM:18:TRACE[,]]/TdomTcb/_tmpresend/20
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tcm/40/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/wrote tdom tcm/792
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/Not compressed/calculated_size=792/
2/13/12:2:30:45 PM:18:TRACE[,][/write_metahdr/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=16/parsedMetahdr=false
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/writeTuxedoMessage/70/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_metahdr/10/
2/13/12:2:30:45 PM:18:TRACE[,]/write_tfmh/magic=-1862035368/ltype_idx=16/tmfmh_flag=65536
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/write(b)/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/writeTuxedoMessage/
2/13/12:2:30:45 PM:18:TRACE[,]/TpeOut/writeTuxedoMessage/myNeedToWrite=792/myMark=792/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]*]/TpeOut/writeTuxedoMessage/40/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/write/30/
2/13/12:2:30:45 PM:18:TRACE[,]]/write_tfmh/100/0/
2/13/12:2:30:45 PM:18:DBG[,do_connect]...send LLE
2/13/12:2:30:45 PM:18:TRACE[,][/read_tfmh/
2/13/12:2:30:45 PM:18:TRACE[,][/read_metahdr/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=544/myMark=544/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/resetting mark for next Tuxedo buffer
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=32
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=32/myMark=0
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/size=384
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/false
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=352/myOffset=32/myMark=0/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/50/true
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/150/true
2/13/12:2:30:45 PM:18:TRACE[,]]/read_metahdr/10
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/readTuxedoMessage/true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=352/myOffset=32/myMark=32/myProtocol=16/parsedMetahdr=true
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/toRead=352
2/13/12:2:30:45 PM:18:TRACE[,]/TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=384/myMark=32
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/readTuxedoMessage/120/true
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/read(b)/232/0/232
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/read(b)/30/232
2/13/12:2:30:45 PM:18:TRACE[,]]/read_tfmh/80/0
2/13/12:2:30:45 PM:18:DBG[,do_connect]...recv LLE_RPLY
2/13/12:2:30:45 PM:18:DBG[,do_connect]recv size = 232
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/crypFinishOne/
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/decodeDH2/0
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/decodeDH2/10/224
2/13/12:2:30:45 PM:18:TRACE[,][/tplle/generateFingerprint/
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/generateFingerprint/
2/13/12:2:30:45 PM:18:TRACE[,]]/tplle/crypFinishOne/130/LLE_DH2_128
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/setELevel(4)/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/setElevel/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeIn/setLLE/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeIn/setLLE/10/
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/setElevel/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/setElevel/10/0
2/13/12:2:30:45 PM:18:TRACE[,][/TpeOut/setLLE/
2/13/12:2:30:45 PM:18:TRACE[,]]/TpeOut/setLLE/10/
2/13/12:2:30:45 PM:18:TRACE[,]/dsession(0)/do_connect/ready to use LLE
2/13/12:2:30:45 PM:18:DBG[,do_connect]ready to use LLE
2/13/12:2:30:45 PM:18:TRACE[,][/dsession(0)/setUpTuxedoAAA/
2/13/12:2:30:45 PM:18:TRACE[,]]/dsession/setUpTuxedoAAA/10/return 0
2/13/12:2:30:45 PM:18:DBG[,do_connect]chan = java.nio.channels.SocketChannel[connected local=192.168.19.156/192.168.19.156:36898 remote=/192.168.19.156:8888]
2/13/12:2:30:45 PM:18:DBG[,do_connect]myXidRplyObj = null
2/13/12:2:30:45 PM:18:DBG[,rdsession]myTimeService = java.util.Timer@797bc6
2/13/12:2:30:45 PM:18:TRACE[,dmqDecision]> () com.oracle.tuxedo.adapter.tdom.ResponderSession@0
2/13/12:2:30:45 PM:18:TRACE[,dmqDecision]< (10) return
2/13/12:2:30:45 PM:18:INFO[,do_connect]TJA_0130:Established connection to remote domain Gdomtux.
2/13/12:2:30:45 PM:18:TRACE[,do_connect]< return(350) success
2/13/12:2:30:45 PM:18:TRACE[,tpinit]< return(50) success, uid = 0
2/13/12:2:30:45 PM:18:TRACE[,][/ScheduledReconnect/connectingSuccess/session = __sess_0_0
2/13/12:2:30:45 PM:18:TRACE[,]]/ScheduledReconnect/connectingSuccess/10/return
but since my web application try to do a look up, i cant get the connection factory by jndi , the descriptor is :
<resource-adapter>
<archive>
TuxedoAdapter.rar
</archive>
<transaction-support>
NoTransaction
</transaction-support>
<connection-definitions>
<connection-definition class-name="com.oracle.tuxedo.adapter.spi.TuxedoManagedConnectionFactory"
     jndi-name="java:jboss/eis/TuxedoConnectionFactory" enabled="true" use-java-context="false"/>
</connection-definitions>
</resource-adapter>
ctx = new InitialContext();
          cf = (TuxedoConnectionFactory) ctx.lookup("java:jboss/eis/TuxedoConnectionFactory");
          c = cf.getConnection();
Edited by: 907185 on 13/02/2012 12:01

Reg. JNDI error when starting monitor server

Hi all,
I am installing CCMS for our CRM4.0 Server. At one point of the installation, it asks to start the monitor server. When I start the monitor.bat it throws a error saying "<b>Cannot Connect to Cluster , beacuse of null. ID003814 : JNDI exception in getinitialContext of InitialContextFactoryImpl</b>".
Can anyone please throw some light on this?
Thanks in advance,
Krishna Karthik P

Stop the existing IS & AS as root or kill the (ois_server,aaa_server) process manually since the pid, pid_watchdog process are catch hold by root user. Logon as normal oracle user and issue the command start_ois_sever_nptl.

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

JMS Server JNDI not being replicated? (clustered environment)

Hello,
First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
My current production and test environments consist, each one of them, of
clusters with one admin server (ProdAdmin) and two managed servers (Prod1
and Prod2). One of the managed servers (Prod1) is the server to which the
JMS server is deployed and everything works fine.
Now I'm trying to add another managed server to the cluster. The idea is to
target the JMS Server (and nothing else) to this node. We don't want the JMS
server to be running in Prod1 and the new server, named ProdJMS, won't even
have any deployed beans or the startup class targeted to it. Just the JMS
server. Here our problems start.
I'm able to start this ProdJMS node with no problems. However, when I start
Prod1 it seems that the JMS server is not binded. This is the exception
we're getting when a message-driven bean is being deployed (I get the same
exception trying to create other):
------- snip -------------
<May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
CacheUpdateBean is unable to connect to the JMS
destination: securityChanges. The EJB container will automatically attempt
to re-establish the connection with the JMS s
erver. This warning may occur during WebLogic Cluster start-up if the JMS
destination is located on another WebLogic Ser
ver instance. When the JMS server connection is re-established, the
Message-Driven EJB will again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Error creating session
Start server side stack trace:
weblogic.jms.common.JMSException: Error creating session
at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------- Linked Exception -----------
weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
Prod1, javax.naming.NameNotFoundException: Un
able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
Unresolved:'S:Prod1' ; remaining name ''
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
.java:260)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
anager.java:307)
at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
------- snip -------------
If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
actually able to see "weblogic.jms.S:Prod1", which is the name that seems
not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
everything works fine. If I deploy the JMS server to a server with only the
JMS server I get the mentioned JNDI exception.
I would appreciate if you could give me help me solving this problem.
Thanks in a dvance for any help.
Andre Mendonca

First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
My current production and test environments consist, each one of them, of
clusters with one admin server (ProdAdmin) and two managed servers (Prod1
and Prod2). One of the managed servers (Prod1) is the server to which the
JMS server is deployed and everything works fine.
Now I'm trying to add another managed server to the cluster. The idea isto
target the JMS Server (and nothing else) to this node. We don't want theJMS
server to be running in Prod1 and the new server, named ProdJMS, won'teven
have any deployed beans or the startup class targeted to it. Just the JMS
server. Here our problems start.
I'm able to start this ProdJMS node with no problems. However, when Istart
Prod1 it seems that the JMS server is not binded. This is the exception
we're getting when a message-driven bean is being deployed (I get the same
exception trying to create other):1. Make sure that you are using a dif multicast address for each cluster
2. Remove the JMS from Prod1 -- double check this!
3. Stop Prod1 and Prod2
4. Start the ProdJMS
5. Restart Prod1 and Prod2
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/
"Andre Mendonca" <[email protected]> wrote in message
news:[email protected]...
Hello,
------- snip -------------
<May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
CacheUpdateBean is unable to connect to the JMS
destination: securityChanges. The EJB container will automatically attempt
to re-establish the connection with the JMS s
erver. This warning may occur during WebLogic Cluster start-up if the JMS
destination is located on another WebLogic Ser
ver instance. When the JMS server connection is re-established, the
Message-Driven EJB will again receive JMS messages.
The Error was:
weblogic.jms.common.JMSException: Error creating session
Start server side stack trace:
weblogic.jms.common.JMSException: Error creating session
atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------- Linked Exception -----------
weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
Prod1, javax.naming.NameNotFoundException: Un
able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
Unresolved:'S:Prod1' ; remaining name ''
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
.java:260)
at
weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
anager.java:307)
atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
a:300)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
------- snip -------------
If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
actually able to see "weblogic.jms.S:Prod1", which is the name that seems
not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
everything works fine. If I deploy the JMS server to a server with onlythe
JMS server I get the mentioned JNDI exception.
I would appreciate if you could give me help me solving this problem.
Thanks in a dvance for any help.
Andre Mendonca

Missing beans for BI/Portal integration configuration

I've configured BI/Portal configuration but when executing the tests or when using BEX I have an errors:
com.sap.engine.services.rfcengine.RFCException: Bean RSWR_TEMPLATE_PROCESS_PROXY not found
Caused by: .jndi.exceptions.NameNotFoundException: Object not found in lookup of RSWR_TEMPLATE_PROCESS_PROXY.
same error for other RSWR beans (RSWR_RFC_SERVICE_TEST etc.).
It seems I am missing some component(s), in my installation (the SSO, auth, etc seems configured correctly according the configuration guides).
Does anybody knows what component I should re-deploy in order to have missing beans? Any other possibility to fix this error?
Thanks,
Evgeni.

Which versions of EP and BW are you using?
The attached link provides steps for EP BW integration.
http://help.sap.com/saphelp_nw04/helpdata/en/60/1c0340dcf41e07e10000000a1550b0/content.htm

ACL problem in 6 and 5.1 sp9? Bug?!

Hi all gurus:
I got this problem for several days, and still cannot solve it. Can
anyone help me?
My design is to put all my beans and connection pool under one "kbf"
acl. And "guest" servlet/jsp accesses these beans by using this "kbf"
account. And it works in 5.1 sp8.
Then i tried to use sp9. The very first time when jsp is compiling
by WLS, all the jsps work correctly! After that, immediately click the
link again, it throws jndi exception. Saying "guest" no permission to
access "kbf" jndi. But my "guest" actually is a servlet/jsp running
inside the server.
So then we tried to use 6 sp2, to see whether we can solve the
problem. And the funny things come out as follows.
I just click my URL link in browser, first time everything is fine,
my data is shown correctly. second time it throws ACL exception ,saying
guest no right to look up my JDBC pool. Click again, the data comes out
again. Clieck again throws same exception. It is a "toggle".
And, for another jsp page/link, (it gets data from two tables),
first time both two tables data are shown. Click some other link, then
come back to click this link, only one table data is shown, then click
this link again, both are shown. It is also a "toggle", slightly
different.
Something really funny going on for this ACL!
Can anyone in BEA tell me more about this ACL issue? Why always
nobody cares to answer these ACL questions? Both in ejb group and
security group?
Or simply nobody is using ACL in their project?
Or i missed out something important? or i am abusing ACL?
Or is it a bug?
Since we are going to production very soon, i need the solution
ASAP. Right now i only have two solutions:
1. stick to 5.1 sp8.
2. grant "guest" permission to all my beans, connection pool, which
means no use for the ACL at all.
Hope someone at least give me an hint. And sorry for the crossing
post.
Thanks.
minjiang

Thanks a lot!
The problem is that i cached the ejb homes and connection pool. So now i use
your first solution, create context everytime, although the performance may be
slow down.
But strange, it works in 5.1 sp6-8.
Thanks again, Dimitri!
minjiang
Dimitri Rakitine wrote:
The security context is associated with thread so, for example:
in a servlet, you create InitialContext as "user" and save it.
Next request which will be "guest" anyway.
So, if you want authentication, you can either
- create InitialContext everytime
- use j2ee security so container will do this automatically:
http://e-docs.bea.com/wls/docs61/webapp/security.html
Dimitri
On Fri, 13 Jul 2001, minjiang wrote:
Hi Dimitri:
Sorry to mail you directly.
I have this question for quite some time. And not receive any
response for my posting, cross posting.
Do you have any idea why my deployment works on 5.1 sp8, but not on
sp9 and 6 sp2?
I noticed bea changed the weblogic.ejb.interal.StatefulEJBObejct,
and StatefulEJBCache in sp9, and this is part of why my application
cannot work. (for one facade session bean looking up other beans in
another acl)
Another part is i described in the forward posting, for my "guest"
jsp/servelt cannot access other acl?
For my understanding, since my facade bean and jsp/servlet only run
inside the WLS server, so as long as the correct credential is supplied
while constructing the jndi context, they should be allowed, right? It
shoud not be only one credential in one thread, which seems WLS is doing
now.
Thanks for help, and any hint or document is appreciated.
minjiang

Problem Connecting to J2ee engine for EP6.o

Hello Gurus,
Help needed..I tried my best in searching several OSS notes but none helped me.
We installed EP6.0 on HPUX 11.1/Oracle 9.2.04
I upgrades J2ee Engine to patchlevel 17.
WHen trying to apply SP2 using SDM, it is erroring out : unable to connect to J2ee with Administrator!!
I launched j2ee admin console and trying to connect(port 50104), user: Administrator, Password none, but in vain.The folowing error is coming:
javax.naming.NamingException:Connection lost
ID003814: !UNSOLICITED! JNDI Exception in getInitialContext of initialCOntextFactoryImpl [Root exception is com.inqmy.services.rmi_p4.P4IOException:Connect
I am able to connect to j2ee engine using telnet to 50108 port with user: Administrator withoout any password.
When I do lsc..it is listing dispatcher (port 50110) and Server (port 50120).
I started the portal (system # 01) and the element joined ...(Element 628068834 joined)
But when I try to connect to the portal using explorer
(http:/myserver:80100 or http:/myserver:80100/irj) , I am getting the following error:
Dispatcher running, but no server connected!
Earlier to applying J2ee ENgine patch 17, I was able to connect to the portal.
Please help me understand what is going on with our EP installation and any experiences/guidance to bring life to EP6.0
thank in advance.
paparaju buddhavarap

Paparaju -
1. How are you starting the portal (i.e. go scripts or unixdaemon)?
2. Is the R/3 startup service set to Manual?
If it is not, I'd recommend setting to manual and shutting down all portal processes before restarting.
Regards,
Kyle

JNDI Exception in Webgain 4.1

Similar Messages

Maybe you are looking for