Binding RMI object at startup in cluster

Hi
While I have seen similar postings perhaps someone could provide clarity. I have
two nodes in a WL 6.1 cluster. I have a class that implements the ServletContextListener
interface and is invoked on deployment of my app. This class binds checks for
the existence of a bound object and if not found binds one. The first node binds
correctly. When I start the managed server it does not find the bound object.
Is this because the replication was not quick enough? The bound object is n clusterable
RMI object. The idea here is that should the first node fail the second node,
which keeps checking in the interim, will find no bound object and bind one.

Does xyzImpl extend UnicastRemoteObject by any chance? If so, delete the exportObject() call, it is already exported by its constructor (i.e. when its constructor calls super()).

Similar Messages

RMI Objects running on single cluster memb. only avail on that

          Hi,
          My setup:
          An RMI object shall be bound to a single cluster member.
          Only one cluster member has therefore the startup entry. The
          RMI Object is thus instantiated only in this one cluster member.
          I now expected to have the weblogic.rmi.myclass JNDI entry
          replicated into all cluster member's jndi context (thus having
          a simple way for implementing a singleton? does this work??).
          All clients, which are loadbalanced to a cluster-member
          that does not the startup entry will fail to lookup the rmi object's
          entry
          with the following.
          Why is the entry not replicated into the other machines naming context?
          javax.naming.NameNotFoundException: 'mybindname'; remaining name
          'mybindname'
          at
          weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
          at
          weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
          at
          weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
          at mypackage.MyClass.lookup(...);
          Thank you for any help on this & happy new year
          Toby


We too are looking to achieve the same thing. Anyone know the answer to
          Tobias's question?
          david
          Tobias Christen wrote:
          > Hi,
          >
          > My setup:
          > An RMI object shall be bound to a single cluster member.
          > Only one cluster member has therefore the startup entry. The
          > RMI Object is thus instantiated only in this one cluster member.
          > I now expected to have the weblogic.rmi.myclass JNDI entry
          > replicated into all cluster member's jndi context (thus having
          > a simple way for implementing a singleton? does this work??).
          >
          > All clients, which are loadbalanced to a cluster-member
          > that does not the startup entry will fail to lookup the rmi object's
          > entry
          > with the following.
          >
          > Why is the entry not replicated into the other machines naming context?
          >
          > javax.naming.NameNotFoundException: 'mybindname'; remaining name
          > 'mybindname'
          > at
          > weblogic.rmi.extensions.BasicRequest.sendReceive(BasicRequest.java:44)
          > at
          > weblogic.jndi.WLContext_WLStub.lookup(WLContext_WLStub.java:192)
          > at
          > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
          > at mypackage.MyClass.lookup(...);
          >
          > Thank you for any help on this & happy new year
          > Toby
          David Michaels <[email protected]>
          Director of Technology
          ShockMarket Corporation (650) 330-4665
          [david.vcf]

Bind RMI object to JNDI

InitialContext ctx = new InitialContext ();
ctx.rebind ("wwlhp", remoteObject);Does the JNDI tree and remoteObject reside in the same JVM?
Can i use JNDI without J2EE platform?
Can some one give me a piece of code illustrating rebinding in server side and looking up in client side.

import javax.naming.*;
import java.util.*;
public class Server{
public static void main(String[]args){
try{
Hashtable env=new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.rmi.registry.RegistryContextFactory");
env.put(Context.PROVIDER_URL,"rmi://servername");
Context ctx=new InitialContext(env);
//create an instance of remote object
RemoteIF i=new RemoteImpl();
ctx.rebind("common name",ri);
}catch(Exception ex){}
The client needs to create a context as well, as above, the lookup
RemoteIF ri=(RemoteIF)ctx.lookup("common name");
The Stub classes must be available to the client as well
start rmiregistry
start the server
off you go with the client

How to register a regular rmi object in the class which is not setted as startup classes?

hi:
it seems the rmi object can only be registed in a startup class,
is there any way to do this in an nostartup class?
Thanks for any clue.
Reno hu
TCSI

Yes.
It is possible to export an RMI object from a servlet's init() method. You
will have to specify a <load-on-startup> tag in the web.xml deployment
descriptor, but otherwise, it's pretty straightforward to bind/unbind an RMI
object when an application is deployed/undeployed.
-Don
Andy Piper wrote:
"Reno hu" <[email protected]> writes:
No
hi:
it seems the rmi object can only be registed in a startup class,
is there any way to do this in an nostartup class?
Thanks for any clue.
Reno hu
TCSI
" .sigs are like your face - rarely seen by you and uglier than you think"
mail: [email protected]

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.

How can we determine exactly what server an RMI object is bound to?

We have RMI objects that bind to a server in a cluster. How can we determine for
monitoring purposes what server a RMI object is currently bound to /executing
on?
We have tried the most of the Mbeans but can't find one that returns runtime info
for startup classes or RMI objects.
We have a new monitoring requirement we are trying to satisfy.

try get the value of PKEY_OfflineAvailability using shell property system APIs (SHGetPropertyStoreFromParsingName or ShellFolderItem.ExtendedProperty)
Visual C++ MVP

RMI object bindings bot being replicated

          I have a two node cluster setup for testing. I am creating an RMI
          object on one server and binding it into the JNDI tree. I can see the
          binding on the server where the object was bound but I never see
          anything in the JNDI tree of the other server in the cluster.
          I have tried adding WLContext.REPLICATE_BINDINGS=true to my
          InitialContext. I've also tried compiling the RMI object with
          weblogic.rmic as clusterable. Neither seems to have made any
          difference.
          Any assistance will be appreciated.
          Thanks and regards,
          Bob


          Thanks for the reply. Please see my responses inline:
          In article <[email protected]>, [email protected]
          says...
          > Bob,
          >
          > A couple of questions
          > 1> Whether your multicast address is working properly? Perform the
          > multicast test and verify this.
          What is the multicast test? The console cluster monitor screen shows
          both servers sending and receiving message fragments. Both servers show
          zero for Lost Multicast Messages.
          > 2> How are you deploying the RMI object (to the cluster or individual
          > servers)?
          I'm not sure what you mean by "deploying the RMI object". The RMI
          object is created by a startup class and bound to the JNDI tree on one
          server in the cluster. It appears in the tree it where it was bound but
          not the tree on the other server.
          > 3> What version of WLS and Service pack are you using?
          WLS 6.1 SP1 Load3
          > 4> Could you try our sample example in the \cluster\rmi folder?
          This exhibits the same behavior I'm seeing in my app.
          Thanks for your help.
          Regards,
          Bob
          >
          >
          > Bob Withers wrote:
          >
          > > I have a two node cluster setup for testing. I am creating an RMI
          > > object on one server and binding it into the JNDI tree. I can see the
          > > binding on the server where the object was bound but I never see
          > > anything in the JNDI tree of the other server in the cluster.
          > >
          > > I have tried adding WLContext.REPLICATE_BINDINGS=true to my
          > > InitialContext. I've also tried compiling the RMI object with
          > > weblogic.rmic as clusterable. Neither seems to have made any
          > > difference.
          > >
          > > Any assistance will be appreciated.
          > >
          > > Thanks and regards,
          > > Bob
          >
          >

Javax.naming.NameAlreadyBoundException: Failed to bind remote object

I am getting an error while deploying wli-ejbs.ear file. This ear uses oracle thin drivers to connect to database. But while deploying i am receiving an error as below. Can anyone please help me to solve this problem?
Deployer:149033]preparing application wli-ejbs on managed2_cvf01
[Deployer:149033]preparing application wli-ejbs on managed1_cvf01
[Deployer:149033]prepared application wli-ejbs on managed1_cvf01
[Deployer:149033]prepared application wli-ejbs on managed2_cvf01
[Deployer:149033]activating application wli-ejbs on managed1_cvf01
[Deployer:149033]activating application wli-ejbs on managed2_cvf01
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application wli-ejbs on cvf01_cluster.: weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for calendar/oracle
Module: calendar/oracle Error: Exception activating module: EJBModule(calendar/oracle,status=PREPARED)
Unable to deploy EJB: RemoteCalendarBean from calendar/oracle:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: RemoteCalendarBean.
javax.naming.NameAlreadyBoundException: Failed to bind remote object (ClusterableRemoteRef(704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01 null)/948 [com.bea.wli.calendar.api.BusinessCalendarHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]) to replica aware stub at RemoteCalendarBean(ClusterableRemoteRef(704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01 [704752282736664516S:172.24.206.163:[7003,7003,7004,7004,7003,7004,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed1_cvf01/944, -8505871579836432025S:172.24.206.163:[7005,7005,7006,7006,7005,7006,-1,0,0]:172.24.206.163:7003,172.24.206.163:7003:cvf01:managed2_cvf01/1008])/944 [com.bea.wli.calendar.api.BusinessCalendarHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]); remaining name ''
at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:177)
at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:347)
at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:124)
at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:279)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:386)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1141)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1385)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3315)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2194)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2167)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2503)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2421)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2138)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:676)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

run the sync.bat file as mentioned in the instructions...
or through EBCC(select sampleportal-project dir, app name "sampleportal")...
good luck
Vijay
"ellen" <[email protected]> wrote:
>
I installed sampleportal and did all the changes according to the documents,
when
the server started, there is this error:
Unable to deploy EJB: CatalogWebService from catalogwe.jar:
Unable to bind EJB Home Interface to the JNDI name: sampleportal.BEA_commerce.CatalogWebService.
The error was: javax.naming.nameAlreadyBoundException: Failed to bind remote
object...to
replica aware stub at CatalogWebService; remaining name'sampleportal.BEA_commerce'
After the server started with the above error, I tried to run the app, here
is what
occured:
PortalPersistenceManager: portal'sampleportal/sampleportal' not found.
Has anybody seen this before?
Ellen

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

Binding huge object to the jndi tree.

Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. This same thing is working with about 4MB object in Sun One but takes about 45 Mins to 1 Hour to finish the serialization etc for jndi .Kindly provide some guidance.Thanks in advance.

True. At the end I configured the value as a "server property". The cool thing about configuring the jndi tree is that it is replicated in a cluster.
Obviously the values that I inserted affected all the applications, like the url of our SOA server.

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

How to use RMI objects in a servlet

Hi,
I have just run the example RMI program in the java tutorial in my linux pc. Also I have another method to just echo a string back. It works fine when calling from command line.
Now I want to write a servlet that get a string when POSTed and call the RMI objects echo method and display the returned string.
I use Tomcat-5.0 which is installed in /usr/local. I moved the remote object interface jar to the common/lib folder and import the interface in my Servlet. I use the following statements inside the servlet to get the RMI object reference.
            Registry registry = LocateRegistry.getRegistry("localhost");
            Rser comp = (Rser) registry.lookup("rmiser");When i use this in my servlet the tomcat stops working.
Also I don't know how to specify the code base and security policy which I use in command prompt when calling RMI object.
Pls suggest me what to do and also specify any resources that explain this task step by step.
Thanks.

restarted the system and caught the following exception while calling the servlet.
Apr 30, 2009 12:24:15 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3861 ms
java.security.AccessControlException: access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
     at java.security.AccessController.checkPermission(AccessController.java:546)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     at java.lang.SecurityManager.checkConnect(SecurityManager.java:1034)
     at java.net.Socket.connect(Socket.java:513)
     at java.net.Socket.connect(Socket.java:469)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:180)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at RequestParamExample1.doGet(RequestParamExample1.java:94)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at filters.ExampleFilter.doFilter(ExampleFilter.java:101)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:619)
Apr 30, 2009 12:25:19 PM org.apache.coyote.tomcat5.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
     at java.security.AccessController.checkPermission(AccessController.java:546)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     at java.lang.Thread.setContextClassLoader(Thread.java:1351)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:619)
Exception in thread "ContainerBackgroundProcessor[StandardEngine[Catalina]]" java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
     at java.security.AccessController.checkPermission(AccessController.java:546)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     at java.lang.Thread.setContextClassLoader(Thread.java:1351)
     at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1623)
     at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1608)
     at java.lang.Thread.run(Thread.java:619)
Hope u can find it now.
the line
at RequestParamExample1.doGet(RequestParamExample1.java:94)
is the file I am editing and using to call RMI.
Edited by: itsraja on Apr 30, 2009 12:06 AM

Trouble in storing and retrieving RMI object in Weblogic 7 JNDI tree.

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

I have created a simple server (BankImpl), implementing a RMI interface
called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
class using
"rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
in Weblogic
server 7 under the name of "PeopleBank".
After the binding, I can see the stub class in the JNDI tree, but with a
different name: BankImpl_WLStub.class). when a
client program is trying to lookup the stub associated with "PeopleBank", it
failed with a puzzling message:
java.io.NotSerializableException: BankImpl_WLStub
Why a stub of a RMI object is not serializable? Does Weblogic needs a
different rmic to generate RMI stubs?
Thanks,
Lian

Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster

Unable to connect to MQ7.0 in BIND mode from Weblogic10.3.4 Cluster (Managed Servers)
Issue in brief is we are able to connect to MQ7.0 from Weblogic10.0 admin server but not able to connect to MQ7.0 from Weblogic Cluster (Managed Servers).
Below are the details:-
Environment:-
1) Weblogic 10.3.4
MQ Version: 7.0.1.4
Admin Server :- adminserver
Managed Server:- ms1
Managed Server:- ms2
Cluster:- cluster_1 (ms1,ms2)
a) Admin Server (adminserver)
When deployed the application on Admin Server (adminserver) its working fine, able to connect to MQ 7.0
b) Cluster:- cluster_1 (ms1,ms2)
When deployed the application on cluster_1(ms1,ms2) its failing with the error message:-
Error:-
####<Jan 4, 2012 3:27:39 PM CET> <Warning> <EJB> <ahuoms30> <ms2> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <guest> <> <> <1325687259034> <BEA-010061> <The Message-Driven EJB: TestMDBean is unable to connect to the JMS destination: jms/queue/external/TestResponseQueue. The Error was:
com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI. The Java(tm) MQI has thrown an exception describing the problem. See the linked exception for further information.
Nested exception: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
Nested exception: java.lang.UnsatisfiedLinkError: no mqjbnd in java.library.path>
Analysis:-
Error Occurs because it is not able to find the mqjbnd in java.library.path.
The JAVA_LIB_PATH="/opt/mqm/java/lib64" valus is set in the startup script for both the Admin Server (adminserver) and cluster_1 (ms1,ms2),
working fine for Admin Server (adminserver) but not for cluster_1 (ms1,ms2).
Connection towards MQ is not working for the clusters(ms1,ms2) when compared with the Admin Server (adminserver) as all the settings in scripts are same.
Does anyone have experience similar issue and solved this issue, please let me know.

In case this happens to anyone in the future, you may also need to add '/opt/mqm/java/lib64' to the LD_LIBRARY_PATH env variable.

Primary Server went down going to get a fresh object elsewhere in the clust

C:\>java -cp c:/oc4j_extended/j2ee/home/oc4j.jar;c:/how-to-ejb-clustering/lib/st
ackClient.jar cluster.client.ClusterClient
[One]
[One, Two]
[One, Two, Three]
Kill current server and press Enter to continue.
Primary Server went down going to get a fresh object elsewhere in the cluster
Exception in thread "main" com.evermind.server.rmi.RMIConnectionException: Serve
r shutdown
at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocati
onHandler.java:50)
at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(Rec
overableRemoteInvocationHandler.java:22)
at com.evermind.server.ejb.StatefulSessionRemoteInvocationHandler.invoke
(StatefulSessionRemoteInvocationHandler.java:40)
at __Proxy2.push(Unknown Source)
at cluster.client.ClusterClient.main(ClusterClient.java:45)

Upss,i forgot to inform :
i have my BC4J deployed ( +- 10 Entity objects/View objects ) , 1 Application Module
i also developed java client to access this BC4J component,and calculate the average process time.
Thanks
Regards,
Ricky HP

Binding RMI object at startup in cluster

Similar Messages

Maybe you are looking for