Clustered Remote Object Bound To JNDI

Hello,
          I'd like to know if Weblogic 5.1 (service pack 10) supports
          clusterable remote objects.
          What I am trying to do is to implement a remote object that extends
          UnicastRemoteObject interface and bind it to JNDI. When the client
          needs the services, it will lookup that object in JNDI and call its
          methods remotely.
          What happens to my test implementation is that it all works well when
          I run Weblogic locally, but if it is run on the remote server, it
          gives me the exception to the extend that the stub for my remote
          object is not found (although it is in the classpath). I understand
          that this is because I should be using weblogic.rmic instead of
          regular rmic, is that right?
          Thanks,
          Eugene Kononov.

Similar Messages

Unable to retreive RMI object bound to JNDI

Hi
I am trying to retrieve an rmi object that appears to have been sucessfully
deployed to the weblogic server. Upon startup the nt command console shows
the message below and the class name appears in the Distributed objects/rmi
area in the Weblogic console.
Invoking main-style startup Guid xxxxxx.GuidImpl
However if I try to write a test client using either one of the following
calls I get a NameNotFoundException.
I have tried both the name Guid (which is what is in the startup entry) and
the fully qualified name. They all have the same results.
Sample calls:
Naming.lookup("Guid");
or
getInitialContext();
jndiContext.lookup("Guid");
In my weblogic properties files I have the following entry:
weblogic.system.startupClass.Guid=xxx.GuidImpl
in the main of GuidImpl class I have the following entry:
Naming.bind("xxx.Guid");
any ideas as to what might be wrong?
Thanks

Hi, all:
Currently I evaluate BEA Weblogic 6.1 server. I've read the "Programming
WebLogic JNDI" section of the documentation for Weblogic server 6.1.
However, I couldn't find the answer for my question. What problem I have
now is that
(1): How I can create a object in the Java VM when the Weblogic server
startup? Note:
This class need to read a property files and
store all of properties information into its instance for the
client program to lookup it later.
(2): How can the previous created object to be bound in the Weblogic
JDNI server and the bounded
object can be shown up in the JDNI tree in the Weblogic server's
console?
(3): How do I code my servlet to lookup that object I
just created in the step1? What configuration settings need to be
done before Weblogic server is started?
Because I am stopped by this problem, if anyone can give me the example
code or some explanation of the solution ASAP,
it would be very appreciated....Thanks in advance.......
Merry Christmas
Long

ClassCastException while looking up RMI objects bound to weblogic.JNDI under WLS 6.1

We deploy a servlet (in a single .war archive) establishing a RMI connection to
an external Java object bound into weblogic JNDI (WLS 6.1).
We get a ClassCastException on invoking JNDI lookup:
Servlet failed with Exception>
java.lang.ClassCastException: $Proxy67
     at com.thyssenkrupp.tks.tnt.admin.rmi.ClientServlet.init(ClientServlet.java:81)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:698)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:641)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:586)
     at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:366)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:240)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Curiously we don't observe these problems when we include all the classes of the
remote application in the classpath of the WebLogic Server. Actually we want to
avoid including external classes in weblogic.classpath for (hot) deployment reasons.
It also seems that problems don't occur when accessing the remote object from
an independent client application.
We expect this to be a classloader conflict within WLS 6.1
Does anybody know a solution to our problems?
Thanks for suggestions
Andreas Koerner

There was a similar bug that was supposedly fixed in WL 6.1 SP 2. I had
filed a bug on this myself, and was given a patch for SP1, you should be
able to ask for the patch for CR060416.
Peter Mularien
Deploy Solutions, Inc.
Andreas Koerner wrote:
>
We deploy a servlet (in a single .war archive) establishing a RMI connection to
an external Java object bound into weblogic JNDI (WLS 6.1).
We get a ClassCastException on invoking JNDI lookup:
Servlet failed with Exception>
java.lang.ClassCastException: $Proxy67
at com.thyssenkrupp.tks.tnt.admin.rmi.ClientServlet.init(ClientServlet.java:81)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:698)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:641)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:586)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:366)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:240)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Curiously we don't observe these problems when we include all the classes of the
remote application in the classpath of the WebLogic Server. Actually we want to
avoid including external classes in weblogic.classpath for (hot) deployment reasons.
It also seems that problems don't occur when accessing the remote object from
an independent client application.
We expect this to be a classloader conflict within WLS 6.1
Does anybody know a solution to our problems?
Thanks for suggestions
Andreas Koerner

Home Stub is bound or Home object is bound in JNDI

Hi,
When I lookup Home i get home stub at client side. My question is what is bound in JNDI tree Home stub or object of Home implementation class which is implemented by Server?
thanx

My understanding:
It is the stub that gets bound to the JNDI. From the client side, we look up the JNDI for the home stub. The stub knows how to communicate with it's corresponding server object(Home) thru the skeleteon(I think the concept of skeleton in RMI is deprecated now..)

Binding RMI-IIOP Remote Object in RMI Registry through JNDI

hi friends
I am writing RMI-IIOP Remote Object, both server program, and client program
are java programs. Through JNDI (with cosnaming name service), my program is working.
But what i want is, I want to use JNDI (with rmi registry name service) for my RMI-IIOP Remote Object ( and not RMI -JRMP Remote Object). Both my server
program and client programs are java(and not corba)
I am not getting this, while starting server its showing some error
Is it not possible to bind rmi-iiop remote object in rmi registry through jndi, why

because you are supposed to use the COSNaming service with IIOP. Even if you could bind an IIOP remote object into an RMIRegistry the clients wouldn't be able to use it because the RMI Registry doesn't do the extra processing that the COSNaming service does with IIOP references.

Bind remote object to JNDI tree

I want to create a JNDI tree in the same JVM with remote object, and then I have two problem:
1> Should I bind remote object or its stub to the JNDI tree?
2> How to look up the JNDI tree to get the binded stub from the client side? (Suppose server ip is 192.168.99.42)
I hope a gentleman would give me a piece of code, so i would be much clearer. Thanks a lot!

Hi,
Refer http://java.sun.com/products/jndi/tutorial/objects/storing/remote.html
-amol

Objects returned via JNDI Lookup

All,
I have had this nagging question in my head about JNDI lookups for some time
now, but haven't had the time to do the proper research. The question is
simple.
The setup is simple as well. Suppose that we have a typical WLS setup, with
WLS running in a JVM on a server host somewhere, with objects bound to its
JNDI tree (we'll leave clustering out of the picture for simplicity's sake),
and we also have a WLS client Java application. The client connects to WLS
and performs various JNDI lookups on the server. Some of these objects
implement java.io.Serializable, some do not.
The question is, if the client uses JNDI to lookup an object that exsts in a
separate JVM, and that object does not implement Serializable, how does this
object come to be instantiated on the client?
This leads to a second question: What exactly is getting returned from a
JNDI lookup? A reference to an object or a copy of it? I can see that
lookups within a single JVM would return a reference, but the cross-JVM
lookup is less clear to me.
Any and all help appreciated,
-jc

This leads to a second question: What exactly is getting returned from a
JNDI lookup?From how I understand it, only Serializable objects are returned such as RMI
stubs, which serve as proxies to EJB or other RMI servers registered in JNDI.
- Thomas
(ex-BONY too)
Jonathan Castellani wrote:
All,
I have had this nagging question in my head about JNDI lookups for some time
now, but haven't had the time to do the proper research. The question is
simple.
The setup is simple as well. Suppose that we have a typical WLS setup, with
WLS running in a JVM on a server host somewhere, with objects bound to its
JNDI tree (we'll leave clustering out of the picture for simplicity's sake),
and we also have a WLS client Java application. The client connects to WLS
and performs various JNDI lookups on the server. Some of these objects
implement java.io.Serializable, some do not.
The question is, if the client uses JNDI to lookup an object that exsts in a
separate JVM, and that object does not implement Serializable, how does this
object come to be instantiated on the client?
This leads to a second question: What exactly is getting returned from a
JNDI lookup? A reference to an object or a copy of it? I can see that
lookups within a single JVM would return a reference, but the cross-JVM
lookup is less clear to me.
Any and all help appreciated,
-jc

URGENT - javax.naming.NameNotFoundException No object bound to name

I'm working on a stateless EJB (JobDtlEJB) which calls another stateless EJB (FuncVSREJB). During runtime, the following message appear in application log:
[20/Feb/2006:00:16:56] INFO ( 2088): CORE3282: stdout: EJBGetter:getFuncVSRHome-to lookup[java:comp/env/ejb/funcvsr]
[20/Feb/2006:00:16:56] INFO ( 2088): CORE3282: stdout: [2006/02/21 00:16] {-VoiceSROut}
[20/Feb/2006:00:16:56] INFO ( 2088): CORE3282: stdout: JobDtlEJB exception FuncVSR:javax.naming.NameNotFoundException: No object bound to name java:comp/env/ejb/funcvsr
Would appreciate if anyone kind help!!!
Below is my portion of codes in JobDtlEJB:
import com.util.EJBGetter;
public class JobDtlEJB implements javax.ejb.SessionBean {
private transient javax.ejb.SessionContext m_ctx = null;
private FuncVSRHome myfuncvsrHome;
private FuncVSR myfuncvsrRemote;
public void ejbCreate() throws javax.ejb.CreateException {
System.out.println("ejbCreate() on obj " + this);
public String getConnect(String InjobID) {
try
myfuncvsrHome = EJBGetter.getFuncVSRHome("java:comp/env/ejb/funcvsr");
myfuncvsrRemote = myfuncvsrHome.create();
} catch(Exception ee) {
cFunction.NonIMErrLog("-VoiceSROut", "JobDtlEJB exception FuncVSR:"+ee.toString(), true);
ee.printStackTrace();
Coding inside EJBGetter:
package com.util;
import javax.rmi.PortableRemoteObject;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import com.ejb.*;
public final class EJBGetter {
public static FuncVSRHome getFuncVSRHome(String jndiName) throws NamingException
InitialContext initial = new InitialContext();
System.out.println("EJBGetter:getFuncVSRHome-to lookup["+jndiName+"]");
Object objref = initial.lookup( jndiName );
System.out.println("EJBGetter:getFuncVSRHome-narrow["+jndiName+"]");
FuncVSRHome ejb2Home = ( FuncVSRHome ) PortableRemoteObject.narrow( objref, FuncVSRHome.class );
System.out.println("EJBGetter:getFuncVSRHome-returning EJB Home for ["+jndiName+"]");
return ejb2Home;
} // EJBGetter
Below is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!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>
<session>
<display-name>TheFuncVSR</display-name>
<ejb-name>TheFuncVSR</ejb-name>
<home>com.ejb.FuncVSRHome</home>
<remote>com.ejb.FuncVSR</remote>
<ejb-class>com.ejb.FuncVSREJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
<session>
<display-name>TheJobDtl</display-name>
<ejb-name>TheJobDtl</ejb-name>
<home>com.ejb.JobDtlHome</home>
<remote>com.ejb.JobDtl</remote>
<ejb-class>com.ejb.JobDtlEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
THe following is my sun-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd'>

<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>TheJobDtl</ejb-name>
<jndi-name>jobdtl</jndi-name>
</ejb>
<ejb>
<ejb-name>TheFuncVSR</ejb-name>
<jndi-name>funcvsr</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
The web.xml file content:
<ejb-ref>
<ejb-ref-name>ejb/jobdtl</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ejb.JobDtlHome</home>
<remote>com.ejb.JobDtl</remote>
<ejb-link>TheJobDtl</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/funcvsr</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ejb.FuncVSRHome</home>
<remote>com.ejb.FuncVSR</remote>
<ejb-link>TheFuncVSR</ejb-link>
</ejb-ref>
</web-app>

I've solved this issue in ejb-jar.xml. This is because of <ejb-ref-name> in ejb-jar.xml is unmatched with that in web.xml
<ejb-ref-name>ejb/funcvsr</ejb-ref-name>
Jsut sharing to you all. :)

Re: replicating non-remote objects

I don't know if I would necesarily encourage this behavior, but I
          wonder if a SCOPE_CLUSTER workspace would work? At the very least,
          it's worth looking into.
          Jason
          On Thu, 16 Sep 1999 17:29:54 -0500, "Sam" <[email protected]> wrote:
          >I have a hastable storing references of remote objects and other hastables
          >for caching , Can anyone suggest a way to replicate the hastable in a
          >cluster of 2 WL4.5 servers.
          >Is it possible?
          >
          >thanks,
          >Sam Jacob
          >
          >


Alain is correct on both points.
          Alain Rogister wrote:
          > I believe SCOPE_CLUSTER in WorkspaceDef is only a placeholder for things
          > to come, since workspaces are not a clustered service yet.
          >
          > You might think of using JNDI as an alternative to workspaces, but it
          > won't be that easy. Quoting the clustering developer guide:
          >
          > <quote>
          > Note that you cannot reliably use the naming service to replicate
          > objects.
          > For example, if you bind an RMI object "myReplicatedObject" into a
          > cluster-wide JNDI tree, and "myReplicatedObject" from Server One
          > places a serializable -- but not Remote -- object "myDataObject" into
          > the
          > JNDI tree, that unRemoted object does not get replicated to other
          > servers in the cluster. If Server One fails and a client calls
          > "myReplicatedObject," the RMI service will be available, but its
          > "myDataObject" will not.
          >
          > If you need to guarantee access to some data that is produced or used
          > by a replicated object, you should store the data in a database so that
          > it
          > can be reached by any server in the cluster that is hosting the
          > replicated
          > service. An example of this is an entity EJBean.
          > </quote>
          >
          > Alain.
          > --
          > Alain Rogister
          > Ubiquity s.a.
          > http://www.ubiquity.be
          =====================================================
          Reply to the newsgroup. Don't reply to this mail
          alias. This is used only for answering posts on
          WebLogic Newsgroups.
          =====================================================

Client calling EJB + No object bound eror

Hi,
I am a newbie to oc4j. I have tried to get a client to call a stateless ejb using a bat file outside the server, with no luck. I get NamingException: No object bound for java:comp/env/EmployeeBean when doing a jndi lookup. I have read the doc's, tried the answers in the forum and I even used the example code provided from oracle, but I still get the same error message every time.
Has anyone come across this issue when calling an ejb from a client??
Any help would be greatly appreciated. Its driving me crazy.
Thanks
David

Hi,
I will check out the link, thank you. I am a newbie to java and oracle, so any help would be great. i wasnt sure which bits of code would be really helpfull, so i just put most of it in, sorry if it is too much info.
i am using oracle9ias release 1.0.2.2a (i dont know if this would make any difference). I deploy all my ears using the enterprise manager. The client-jar is within the ear. i use a bat to run the Client code.
I can get a servlet to call the same ejbs and that works fine.
#batfile
========
i set the classpath which including refernces to oc4j.jar and oc4jclient.jar and my ejb-jar
and then i use
set BigD=-Dorg.omg.CORBA.ORBInitialHost=localhost -Duser.timezone=ECT
java.exe %BigD% -classpath "%classpath%" com.test.client.Client
//Client Code
=============
public class Client {
     public static void main(String[] args) {
          System.out.println("Client started again...");
          try {
               Context context = new InitialContext();
               System.out.println("got context");
               Object homeObject = context.lookup("java:comp/env/ejb/ConsumerRequestSession");
               ConsumerRequestSessionHome home = (ConsumerRequestSessionHome) PortableRemoteObject.narrow(homeObject, ConsumerRequestSessionHome.class);
               System.out.println("got home");
               ConsumerRequestSession remote = (ConsumerRequestSession) PortableRemoteObject.narrow(home.create(), ConsumerRequestSession.class);
               System.out.println("got remote");
               String retValue = remote.getString();
               System.out.println("The retValue from client is : " + retValue);
          }catch(Exception e) {
               e.printStackTrace();
               System.out.println("ERROR in try block of client when creating jndi :" + e.getMessage());
#jndi
====
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
java.naming.provider.url=ormi://localhost/test
java.naming.security.principal=admin
java.naming.security.credentials=welcome
#application-client.xml
=======================
<application-client>
<display-name>ejb/ConsumerRequestSession</display-name>
     <ejb-ref>
          <ejb-ref-name>ejb/ConsumerRequestSession</ejb-ref-name>
          <ejb-ref-type>Session</ejb-ref-type>
          <home>com.test.ejb.ConsumerRequestSessionHome</home>
          <remote>com.test.ejb.ConsumerRequestSession</remote>
     </ejb-ref>

</application-client>
#orion-application-client.xml
=============================
<orion-application-client>
     <ejb-ref-mapping location="com/test/ejb/ConsumerRequestSession" name="ejb/ConsumerRequestSession"/>
     
</orion-application-client>
#ejb-jar.xml
<ejb-jar>
     <enterprise-beans>
          <session>
               <ejb-name>ejb/ConsumerRequestSession</ejb-name>
               <home>com.test.ejb.ConsumerRequestSessionHome</home>
               <remote>com.test.ejb.ConsumerRequestSession</remote>
               <ejb-class>com.test.ejb.ConsumerRequestSessionEJB</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
     <assembly-descriptor>
          <container-transaction>
               <method>
                    <ejb-name>ejb/ConsumerRequestSession</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>
#orion-ejb-jar.xml
==================
<orion-ejb-jar>
     <enterprise-beans>
          <session-deployment location="com/test/ejb/ConsumerRequestSession" name="ejb/ConsumerRequestSession"/>
     </enterprise-beans>
     <assembly-descriptor>
          <default-method-access>
               <security-role-mapping name="<default-ejb-caller-role>" impliesAll="true"/>
          </default-method-access>
     </assembly-descriptor>
</orion-ejb-jar>
thank you for your help
david.

Clustering rmi objects

Hi all,
I am looking for some information about clustering RMI objects. I have read as much
as I can find about it, not much seems to be in the wl docs.
I have read that if the server that bound the rmi object into jndi goes down, the
rmi server will no longer work. When I tested this out, the server seemed to continue
working and using the node in the cluster that was still running.
I am wondering what the difference between declaring the RMI object to be clusterable
and setting the WLContext.REPLICATE_BINDINGS flag to false when creating the context
to bind the RMI objects, and binding a seperate RMI object into the tree, one for
each node in the cluster.
is there some docs I can read about this? Thanks for any information you can give
me about this.
-chris

bwit <[email protected]> wrote:
In article <[email protected]>, [email protected]
says...
Hi all,Hi Chris.
I am looking for some information about clustering RMI objects. I haveread as much
as I can find about it, not much seems to be in the wl docs.
I have read that if the server that bound the rmi object into jndi goesdown, the
rmi server will no longer work. When I tested this out, the server seemedto continue
working and using the node in the cluster that was still running.If a server offering an RMI object via JNDI goes down the binding to
that object is removed from JNDI in all the other servers in the
cluster. Other replicas of that object may be available and will
continue to be used as you discovered.
I am wondering what the difference between declaring the RMI object tobe clusterable
and setting the WLContext.REPLICATE_BINDINGS flag to false when creatingthe context
to bind the RMI objects, and binding a seperate RMI object into the tree,one for
each node in the cluster.Marking the RMI object as clusterable causes WLS to generate a replica
aware stub for it. This stub is aware of all the replicas of the object
within the cluster and provides load balancing and failover. When you
bind a RMI object on multiple servers with REPLICATE_BINDINGS set to
false you have a bunch of individual, unrelated objects. Your clients
must contact the particular server running the objects and there will be
no load balancing or failover, all client calls will be serviced by the
object on the server which supplied the stub.
is there some docs I can read about this? Thanks for any informationyou can give
me about this.I thought the WLS RMI Programmer's Guide was pretty clear about how this
worked.
Well, you are right, the docs are clear on what they talk about, but as I mentioned,
when I marked the objects with REPLICATE_BINDINGS set to false, the client still
sent a comma delimited list of servers to create the InitialContext, and we still
observed load balancing, and what looked like failover. This is why we were confused,
we expected to see only one server do all the work (the first in the comma delimited
list), and for failures when that server was brought down. I will take a look at
our configuration and make sure we didnt make a mistake someplace in here.
Regards,
Bob
-chris

Two remote objects calls on the same php class

Hi to all,
I've encountered a strange issue while developing with remote objects.
I've a mxml component with an init() method inside which is called by a menu.
When the init() method is called it makes 7 remote object calls which are bound to some components' dataprovider.
Among this calls I've got 2 remote object which refer to the same remote class. This because I have to call the class twice and the bind the result to two different combobox. Below you find the code:
<mx:RemoteObject id="myFile" source="myRemoteClass" destination="amfphp" showBusyCursor="true" makeObjectsBindable="true" fault="traceFault(event)"/>
<mx:RemoteObject id="myXls" source="myRemoteClass" destination="amfphp" showBusyCursor="true" makeObjectsBindable="true" fault="traceFault(event)"/>
in the init function I make this calls:
myFile.listDir("dir_1")
myXls.listDir("dir_2")
then in the mxml code I bound the result of myFile to combobox1 and the result of myXls on combobox2.
The problem arise when I call the myXls' listDir method. When I call it I receive the following error:
code:
Client.Error.DeliveryInDoubt
Message:
Channel disconnected
Detail:
Channel disconnected before an acknowledgement was received
The strange thing is that not only the myXls object returns this error, but also all the other 6 remote object return the same error above.
I'm not sure, but I guess that the error could be caused by the two remote object which call the same php remote class. If I comment one of the two calls everything works fine.
Do you have any suggestion about?
Thanks!!
Bye
Luke

Hi Jan.
1) We have the 2 VO, each with 3 rows to fill in data. What I mean is that when i just fill in all the fields for the first row of the first VO, and the value of one of these fields is bigger than 50, then after the exception is thrown and the message is displayed, the fields for the first VO are duplicated and shown in the second VO as if the user had inserted them.
2) We tried yesterday the validateEntity and a Method and Atributte Validator approaches after reading that white paper with the same results.
The validation is correctly done using any of the those methods.
I will try to reproduce this issue with the HR schema.
Thanks in advance once again.

Error. Javamail. No object bound to name... Sun Java App. Server 9.0 updt 1

Hello,
I get this exception: No object bound to name java:comp/env/mail/SendSession
I am trying to build automatic mail sending in my application
I have configured my server with the next information and this code:
-Error, exception:
No object bound to name java:comp/env/mail/SendSession
-Code:
InitialContext ic = null;
Session session = null;
String snName = "";
// I HAVE TRIED WITH SEVERAL STRINGS
snName = "java:comp/env/mail/SendSession";
//snName = "/mail/SendSession";
//snName = "mail/SendSession";
//snName = "/SendSession";
//snName = "SendSession";
try {
ic = new InitialContext();
session = (Session) ic.lookup(snName);
} catch (NamingException ex) {
Logger.getLogger("org.xxxx").warning("Error:. " + ex.getLocalizedMessage());
-Server:
Sun Java System Application Server Platform Edition 9.0 update 1.
-Configuration in Sun\AppServer\domains\domain1\config\domain.xml:
<resources>
<mail-resource debug="true" enabled="true" from="[email protected]" host="yahoo.es" jndi-name="mail/SendSession" object-type="user" store-protocol="imap" store-protocol-class="com.sun.mail.imap.IMAPStore" transport-protocol="smtp" transport-protocol-class="com.sun.mail.smtp.SMTPTransport" user="xxxxx">
<description>sesion envio correo</description>
<property name="mail.transport.protocol" value="smtp"/>
<property name="mail.smtp.server" value="smtp.mail.yahoo.com"/>
<property name="mail.smtp.port" value="2473"/>
</mail-resource>
</resources>
<servers>
<server config-ref="server-config" lb-weight="100" name="server">
<resource-ref enabled="true" ref="mail/SendSession"/>
</server>
</servers>
I need your help.
Thanks in advance.
Pedro.

(This isn't really a JavaMail question...)
The JNDI name you use in your application
is a name that's local to your application.
The JNDI name that you configure in domain.xml
is a global JNDI name.
The two names can be different.
In the (e.g.) sun-web.xml file you need to
specify the mapping from the local JNDI
name you use in your application to the
global JNDI name you've configured in
the server.
If you use dependency injection to inject
the Session object, you can specify this
mapping in the @Resource annotation in
your source code.

Javax.naming.NameNotFoundException: No object bound for java:comp/env/...

Help, help! I have a problem:
javax.naming.NameNotFoundException: No object bound for java:comp/env/configuratorDataSource
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:127)
at javax.naming.InitialContext.lookup(InitialContext.java:355)
at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
at com.configurator.datasource.ToplinkClientSessionManager.<init>(ToplinkClientSessionManager.java:18)
at com.configurator.datasource.ToplinkClientSessionManager.getInstance(ToplinkClientSessionManager.java:33
at com.configurator.persistence.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:16)
at com.configurator.ConfiguratorServiceMediatorImpl.getModelsFromDB(ConfiguratorServiceMediatorImpl.java:3
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:384)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:281)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:285)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:653)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:301)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:595)
code:
initialContext = new InitialContext();
LocalStatelessREHome localHome = (LocalStatelessREHome)initialContext.lookup("java:comp/env/StatelessREBean");
in web.xml:
<ejb-local-ref>
<ejb-ref-name>StatelessREBean</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.re.stateless.ejb.LocalStatelessREHome</local-home>
<local>com.re.stateless.ejb.LocalStatelessRE</local>
<ejb-link>StatelessREBean</ejb-link>
</ejb-local-ref>
Any help will be appreciated! Thanks in advance.

Try removing the JNDI fully qualified name (i.e. java:comp\env\) Use the name of your bean to lookup.
It worked for me when i used to get a similar exception.

Remote object taking more time to respond

I am using live cycle data services to access my remote java object. Sometimes remote object is taking a lot of time to respond (even 15 minutes). Please give
me some solution.

Can you enable LCDS logging and see if you are seeing any errors? What client (Flex, JS, iOS, Java) are you using? In general, you can bound the timeout on request. Look at the documentation for client (Flex, JS, iOS, Java) are you using, for how to do it.
Rohit

Clustered Remote Object Bound To JNDI

Similar Messages

Maybe you are looking for