RMI Clustering in Weblogic 7.0

Hi !
I am trying to use RMI Clustering in Weblogic 7.0. I followed the samples in the
documentation and it doesnt work for me. I could successfully bing my RMi Server
object to the JNDI tree and could view it via the weblogic JNDI tree. Even the
lookup is fine, but when I invoke a method on the remote object via the client,
I get the following error. Clearly there is something wrong with the Dynamic stub
downloaded from the JNDI tree.
Any Clues please...
Thanks
Sanjay
class examples.rmi.hello.HelloImpl_WLStub
java.rmi.ConnectException: Couldn't connect to weblogic.rjvm.RJVMImpl@3a0ab1 -
id: '6003776402499002017C:15.10.45.93R:12
46860412257523095S:15.10.45.93:[7001,7001,7002,7002,7001,7002,-1]:examples:examplesServer'
connect time: 'Fri Sep 06 08:
42:01 IST 2002'
at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1559)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:363)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:88)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:116)
at examples.rmi.hello.HelloImpl_WLStub.sayHello(Unknown Source)
at examples.rmi.hello.HelloClient.main(HelloClient.java:42)

Similar Messages

RMI Clustering

Hi All,
We have developed a Spring RMI application and we developed business logic in spring POJO's. Using this RMI technology I exposed my business components to client. Here I have developed userinterface with swings.
It is a client server application. Here I didn't use any EJB kind of technology because spring provides
some of the services like security and Transaction Management.
But I have some questions regarding RMI based implementation.
1) How can I put my application in clusturing environment?.
2) Is there any application server providing clustering for SpringRMI/RMI application?.
3) Is application server necessary for implementing clustering for Spring RMI based application?.
4) Whether this approach is correct or not?
Suggest me the currect approach and Spring RMI clustering.
Thanks in Advance
Mohan Reddy. M

If you want reliable cluster-wide state replication, there's only one
          option: http://www.tangosol.com/products-clustering.jsp
          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/
          "Stone Cold Steve Austin" <[email protected]> wrote in
          message news:3cce62c9$[email protected]..
          >
          > What v understood from Failover for RMI Objects (RMI Clustering) is
          weblogic load
          > balances the method calls across servers in the cluster & doesn't
          implement fail-over
          > / replication.If our understanding is wrong can anyone guide us for
          replicating RMI
          > Objects like Http Session State Replication.

Registering standalone RMI server in WebLogic JNDI

Hi,
I need to register a standalone RMI server in WebLogic JNDI. I'm sure I've done this before, but now I'm having problems!
I have a standalone program which creates a remote object (implements Remote and extends UnicastRemoteObject). I am compiling my stubs with the Sun rmic compiler. I then create a JNDI InitialContext using wlclient.jar and a t3 url, and attempt to bind my remote object. It fails with the following exception:
javax.naming.NamingException: Unhandled exception in rebind() [Root exception is org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code
: 0 completed: No]I am using WLS 8.1sp4 and Sun JDK 1.4.2_05 (as shipped with WLS).
If I use the RMI registry (Naming.bind(), etc.) it works fine.
Thanks
Dan.

Danny Yates <> writes:
You should use PortableRemoteObject and generate iiop ties for your
impl. wlclient.jar runs on top of iiop.
andy
Hi,
I need to register a standalone RMI server in WebLogic JNDI. I'm sure I've done this before, but now I'm having problems!
I have a standalone program which creates a remote object (implements Remote and extends UnicastRemoteObject). I am compiling my stubs with the Sun rmic compiler. I then create a JNDI InitialContext using wlclient.jar and a t3 url, and attempt to bind my remote object. It fails with the following exception:
javax.naming.NamingException: Unhandled exception in rebind() [Root exception is org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code
: 0 completed: No]I am using WLS 8.1sp4 and Sun JDK 1.4.2_05 (as shipped with WLS).
If I use the RMI registry (Naming.bind(), etc.) it works fine.
Thanks
Dan.

RMI Through Apache-Weblogic Bridge

Hi,
How to use RMI in apache-weblogic bridge
Thanks,
Siva E.

[email protected] (srinivasa reddy) wrote in
<39bb039e$[email protected]>:
>
hi,
I have a basic question, does webloigc support apache-weblogic
bridge with mod_ssl/any ssl installed on apache.
thanks & regards
[email protected]
There is a mod_wl_ssl.so in sp4 (i believe). mod_ssl extends Apaches API
and thereby breaks the WebLogic bridge. For raven installations you need
mod_wl_ssl_rave.so because raven extends the API even further.
Joel
E-Mail: (jbf (at) proceedo dot com)

RMI clustered object...

          Hi all!
          You can create a clusterable RMI object with a -clusterable version and WebLogic
          documentation says the calls will be load balanced (unless -stickToFirstServer
          option is used) and can fail over in case of a problem. But what if the object
          is statefull??? If the method call is load-balanced to another server in the cluster
          the state is lost???
          Thank you very much in advance.
          Dave.


6.1 supports clustering stateful session beans. Use those instead. (Or a
          coherent cache ;-)
          Peace,
          Cameron Purdy
          Tangosol Inc.
          Tangosol Coherence: Clustered Coherent Cache for J2EE
          Information at http://www.tangosol.com/
          "Dave" <[email protected]> wrote in message
          news:3c1702d2$[email protected]..
          >
          > Hi all!
          > You can create a clusterable RMI object with a -clusterable version and
          WebLogic
          > documentation says the calls will be load balanced
          (unless -stickToFirstServer
          > option is used) and can fail over in case of a problem. But what if the
          object
          > is statefull??? If the method call is load-balanced to another server in
          the cluster
          > the state is lost???
          >
          >
          > Thank you very much in advance.
          > Dave.

Problems clustering a Weblogic Stateful EJB 3.0

Hello!
I'm developing a Stateful EJB 3.0 with clustering configuration for weblogic 11G. My client gets a reference to the RemoteInterface, invoke a method and it's working. Then I shutdown the server where the EJB was created and the client reinvoke (using the same reference) a method and get's this error:
javax.ejb.EJBException: Exception waiting for response; nested exception is:
     java.io.EOFException: Connection closed by peer; nested exception is: java.io.EOFException: Connection closed by peer
java.io.EOFException: Connection closed by peer
     at weblogic.iiop.EndPointImpl.handleCloseConnection(EndPointImpl.java:602)
     at weblogic.iiop.EndPointImpl.processMessage(EndPointImpl.java:545)
     at weblogic.iiop.EndPointImpl.handleMessage(EndPointImpl.java:500)
     at weblogic.iiop.EndPointImpl.dispatch(EndPointImpl.java:324)
     at weblogic.iiop.ConnectionManager.dispatch(ConnectionManager.java:126)
     at weblogic.iiop.MuxableSocketIIOP.dispatch(MuxableSocketIIOP.java:302)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:915)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:844)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:335)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
javax.ejb.EJBException: Exception waiting for response; nested exception is:
     java.io.EOFException: Connection closed by peer; nested exception is: java.io.EOFException: Connection closed by peer
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.unwrapRemoteException(RemoteBusinessIntfProxy.java:109)
     at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:91)
     at $Proxy0.getMas(Unknown Source)
     at com.ibermatica.pruebas.pruebaEJB30SF.getPrueba(pruebaEJB30SF.java:79)
     at com.ibermatica.pruebas.pruebaEJB30SF.main(pruebaEJB30SF.java:26)
Caused by: java.io.EOFException: Connection closed by peer
     at weblogic.iiop.EndPointImpl.handleCloseConnection(EndPointImpl.java:602)
     at weblogic.iiop.EndPointImpl.processMessage(EndPointImpl.java:545)
     at weblogic.iiop.EndPointImpl.handleMessage(EndPointImpl.java:500)
     at weblogic.iiop.EndPointImpl.dispatch(EndPointImpl.java:324)
     at weblogic.iiop.ConnectionManager.dispatch(ConnectionManager.java:126)
     at weblogic.iiop.MuxableSocketIIOP.dispatch(MuxableSocketIIOP.java:302)
     at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:915)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:844)
     at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:335)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
The description of my test is:
+I have a Weblogic cluster (c1, c2)
+I have developed an 3.0 Stateful EJB (configurated for replication)
+My client gets an EJB Instance from c1 and invoke one method (debugging)
+I stops my client
+I shutdown my server (c1)
+My client invokes another EJB method end gets the error described before.
It seems like the Server don't replicate the EJB.
My replicatión ejb deployment descriptor is (weblogic.xml):
<weblogic-enterprise-bean>
<ejb-name>Session30EJBSFBean</ejb-name>
<stateful-session-descriptor>
<stateful-session-clustering>

<use-serverside-stubs>true</use-serverside-stubs>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
</weblogic-enterprise-bean>
My ejb bean class is:
@Stateful(name = "Session30EJBSF", mappedName = "clustering30-cluster301-Session30EJBSF")
@Remote
public class Session30EJBSFBean implements Session30EJBSF {
private SessionContext _context;
private int contador= 0;
private String user="";
public Session30EJBSFBean() {
public void inicio(String user){
this.user= user;
contador=0;
public void mas(){
contador++;
public int getMas(){
return contador;
public String getUser(){
return this.user;
My Remote EJB:
import javax.ejb.Remote;
@Remote
public interface Session30EJBSF {
public void inicio(String user);
public void mas();
public int getMas();
public String getUser();
My client:
public class pruebaEJB30SF {
public pruebaEJB30SF() {
super();
public static void main(String[] args) {
pruebaEJB30SF pruebaEJB30SF = new pruebaEJB30SF();
try {
pruebaEJB30SF.getPrueba();
} catch (Exception e) {
e.printStackTrace();
public Context getInitialContext() throws NamingException {
//String url="t3://c1:8001";
String url="iiop://c1:8001";
String user="any";
String password="any";
Properties p= new Properties();
//p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.T3InitialContextFactory");
p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL,url);
p.put(Context.SECURITY_PRINCIPAL,user);
p.put(Context.SECURITY_CREDENTIALS,password);
return new InitialContext(p);
public void getPrueba() throws NamingException, RemoteException,
CreateException {
// <PROFILING>
Context ctx= getInitialContext();
//2.0 Stateful
Object ref= ctx.lookup("clustering30-cluster301-Session30EJBSF#.Session30EJBSF");
Session30EJBSF home= (Session30EJBSF)PortableRemoteObject.narrow(ref, Session30EJBSF.class);
Session30EJBSF ejb=home;
ejb.inicio("User1");
ejb.mas();
System.out.println( ejb.getMas());// I put here a breakpoint and I shutdown the serer c1
ejb.mas();
System.out.println( ejb.getMas());
ejb.mas();
System.out.println( ejb.getMas());//Caida
ejb.mas();
System.out.println( ejb.getMas());
I have developed a EJB 2.1 and a EJB 2.1 client and it's working. The most important change betwin ejb 3.0 client and my 2.1 client is that in 2.1 I use the getHandle method and a Home, not a Remote.
Please, can anyone help me.
Thanks.

Hi,
Please change your Client Code as below: URL must be pointing to the comma Separated address of your ManagedServers Address/Port which are part of Cluster like For Example Suppose you have 2 managedServers in ClusterA ..... t3://MS1Host:8003,MS2Host:8005
public Context getInitialContext() throws NamingException {
<strike><font color=red>String url="t3://c1:8001";</font></strike>
<b>String url="t3://ManagedServer1HostName:port,ManagedServer2HostName:port";</b>
String user="any";
String password="any";
Properties p= new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL,url);
p.put(Context.SECURITY_PRINCIPAL,user);
p.put(Context.SECURITY_CREDENTIALS,password);
return new InitialContext(p);
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

RMI problem with weblogic.jar

We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

I'd suggest that you run the vm with the debug flag (-verbose) and see where the classes are being loaded; and examine the classpath to determine where the old jar or classes are occurring.
Rita wrote:
We have re-jarred the Stub.class and put it under weblogic/rmi/extensions, but when the java app runs, it still tries to look in weblogic/rmi/extensions/server. So, I think somewhere in the weblogic.jar, the path specified is still weblogic/rmi/extensions. Do you know what need to be done?
Thanks,
Rita
Eduardo Ceballos <[email protected]> wrote:
Yes, please regenerate your stub classes. That is, re-run rmic or ejbc.
David Furlong wrote:
We have a pure Java client that connects to the Weblogic server.
While trying to connect we receive the error message below.
I have unjarred the weblogic.jar file and discovered that the
Stub.class is actually in weblogic/rmi/extensions/server/
while it expects it to be in weblogic/rmi/extensions .
Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
Thanks
Dave F
java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

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

Unicast Clustering in Weblogic 10.3

We are using Multicast with Weblogic 9.2 for clustering now but are now migrating to Weblogic 10.3 and want to switch to unicast. The documentation seems kind of hazy for Unicast clustering. I have a few questions.
1)The Unicast Broadcast Channel. What exactly is it and what is the format of one.
2) do I need to create a custom channel some where? I don't want to use the default channel because we have many domains in the same server.
3) Generally has does Unicast work and how is it different from multicast.
Thanks,
Tom.

Hi Tom
This really helped me
Ash

Calling rmi running in Weblogic 6.x from Jboss 4.0.5GA

Hi all,
Recently i have a project that needs me to call a remote ejb which is running in Weblogic 6.x. It is using Weblogic's proprietary protocol known as "t3". If i include weblogic.jar (i believe this version of weblogic doesn't deliver its client lib wlclient.jar) in my war file's WEB-INF/lib, i get this error:
2007-06-30 17:32:33,462 ERROR (GqsClient.java:93) - TestProject: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
I've tried to put it in server/default/lib but that throws another exception.
My test code:
Properties jndiProperties = new Properties();
jndiProperties.setProperty( Context.INITIAL_CONTEXT_FACTORY,
MY_INITIAL_CONTEXT_FACTORY );
jndiProperties.setProperty( Context.PROVIDER_URL, MY_PROVIDER_URL );
Context initialContext;
initialContext = new InitialContext( jndiProperties );
Object homeInt = initialContext.lookup( MY_EJB );
objectHome = ( SomeObjectHome ) PortableRemoteObject
.narrow( homeInt, SomeObjectHome.class );
objectRemote = objectHome.create();
Have i done anything wrong in the codes?
Where should i put my weblogic.jar?
org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.test.service.TestRmiClient]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: methods with same signature getEJBMetaData() but incompatible return types: [interface javax.ejb.EJBMetaData, interface javax.ejb.EJBMetaData]
java.lang.IllegalArgumentException: methods with same signature getEJBMetaData() but incompatible return types: [interface javax.ejb.EJBMetaData, interface javax.ejb.EJBMetaData]
        at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:669)
        at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
        at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
        at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
        at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
        at weblogic.rmi.internal.ProxyStub.newInstance(ProxyStub.java:69)
        at weblogic.rmi.internal.OIDManager.resolveObject(OIDManager.java:242)
        at weblogic.common.internal.ChunkedObjectInputStream.resolveObject(ChunkedObjectInputStream.java:81)
        at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveObject(ChunkedObjectInputStream.java:328)
        at java.io.ObjectInputStream.checkResolve(ObjectInputStream.java:1352)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
        at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:139)
        at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:152)
        at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
        at weblogic.rmi.internal.BasicRemoteRef.unmarshalReturn(BasicRemoteRef.java:233)
        at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:264)
        at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
        at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
        at $Proxy15.lookup(Unknown Source)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:342)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at com.dhl.apis.litetrace.service.GqsClient.init(GqsClient.java:84)
        at com.dhl.apis.litetrace.service.GqsClient.<init>(GqsClient.java:57)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:172)
        at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148)
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:52)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:490)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:366)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:234)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:144)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:283)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:321)
        at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:139)
        at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:252)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:190)
        at com.dhl.apis.common.spring.context.CustomContextLoaderListener.contextInitialized(CustomContextLoaderListener.java:30)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
        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.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
        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.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
        at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
        at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
        at org.jboss.web.WebModule.startModule(WebModule.java:83)
        at org.jboss.web.WebModule.startService(WebModule.java:61)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:1
12:05:02,781 INFO [STDOUT] 55)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy10.start(Unknown Source)
        at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy11.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy7.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
        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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy5.deploy(Unknown Source)
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
        at org.jboss.Main.boot(Main.java:200)
        at org.jboss.Main$1.run(Main.java:490)
        at java.lang.Thread.run(Thread.java:595)Message was edited by:
jinchuriki

put weblogic.jar in tomcats classpath
Gary Bartlett wrote:
Question -
Can anyone point me at documentation that will help me
understand what jar files are required to allow access EJB's that are deployed in
Weblogic 6.1 from a Servlet that is running under Tomcat.
I am currently getting the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory.
Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1394)
Thanks,
Gary Bartlett

Error in stateless-clustering in weblogic-ejb-jar.xml

Hi,
This is my <weblogic-ejb-jar.xml> and I see an error in <stateless-bean-is-clusterable>. Can anybody please help me regarding this.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>Sample1</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Sample2</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Sample3</ejb-name>
<stateless-session-descriptor>
<pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>TRUE</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
I am using weblogic 10.3 and EJB 3.0 Can I include all the EJBs in a single <weblogic-ejb-jar.xml> file and can I put it in the EAR->EarContent->META-INF folder, where the application.xml and weblogic-application.xml files exist.
Basically, I am trying to include <initial-beans-in-free-pool> and <stateless-bean-is-clusterable> for each of my EJBs. Since there is no annotation equivalent for them in EJB 3.0, I had to include the <weblogic-ejb-jar.xml> file. I appreciate if anybody can suggest me if there is any annotation equivalent for these.
Thank you,
Sowmya

Hi,
1. please try with <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
2. the EJB Specification requires "The deployment descriptor must be stored with the name META-INF/ejb-jar.xml in the ejb-jar file." So you shouldn't put the weblogic-ejb-jar.xml to EAR's META-INF folder.
3. <stateless-bean-is-clusterable> has a default value as "true". so you needn't specify it in your weblogic-ejb-jar.xml if you just want to have the "true" value.
4. default value of <initial-beans-in-free-pool> is 0. Since you're changing the default value, you'll have to specify it in weblogic-ejb-jar.xml. If you can put all EJBs in one ejb jar file, you can have only one weblogic-ejb-jar.xml in the META-INF folder of this ejb jar.
Thanks,
Amy

How to setup Clustering with Weblogic?

Dear All,
I am a beginner of using Weblogic. Now i need to setup Clustering in
company. I have 3 NT Server and install Weblogic 5.1.0 on each machine, the
name is Cluster1, Cluster2 and Cluster3. At the First Step, can someone tell
me how to setup the clustering and how to test it to esure that is work???
Thanks so much!
hk-beginner

more specifically,
http://www.weblogic.com/docs51/cluster/index.html
Ketan
"Billy Bunter" <[email protected]> wrote in message
news:[email protected]..
Look at the BEA docs.
beginner wrote:
Dear All,
I am a beginner of using Weblogic. Now i need to setup Clustering
in
company. I have 3 NT Server and install Weblogic 5.1.0 on each machine,the
name is Cluster1, Cluster2 and Cluster3. At the First Step, can someonetell
me how to setup the clustering and how to test it to esure that iswork???
Thanks so much!
hk-beginner

RMI Marshalling Problem: weblogic.Admin PING

WebLogic 5.1.0 with service pack 8 has been installed on a HPUX server. I'm
trying to ping the server from an NT box, but I'm getting some RMI
marshalling problems.
Here is the command that I run on NT:
C:\weblogic\jre1_2\jre\bin\java -classpath
c:weblogic/lib/weblogic510sp.jar;c:/weblogic/classes;c:/weblogic/lib/weblogi
caux.jar weblogic.Admin t3://HPServer:7001 PING > MarshallingProblem.txt
Here is what is in MarshallingProblem.txt (modified server name):
Failed to connect to t3://HPServer:7001 due to:
[weblogic.rmi.UnexpectedException: Marshalling:
- with nested exception:
[weblogic.rjvm.PeerGoneException:
- with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
creating response stream ] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible: stream classdesc serialVersionUID=6699361079932480379 local
class serialVersionUID=2825328378974757378]]]]
I previously had similar problems pinging the server from the server itself
until I included the servicepack in the classpath.
Anyone have any idea what going on in this situation?
Cameron Taggart

Cameron
Can you test with sp8 installed on your NT machine too ? And also make
sure you set the classpath with the sp8 jar files on NT before you run
weblogic.Admin PING
Raj Alagumalai
Cameron Taggart wrote:
WebLogic 5.1.0 with service pack 8 has been installed on a HPUX server. I'm
trying to ping the server from an NT box, but I'm getting some RMI
marshalling problems.
Here is the command that I run on NT:
C:\weblogic\jre1_2\jre\bin\java -classpath
c:weblogic/lib/weblogic510sp.jar;c:/weblogic/classes;c:/weblogic/lib/weblogi
caux.jar weblogic.Admin t3://HPServer:7001 PING > MarshallingProblem.txt
Here is what is in MarshallingProblem.txt (modified server name):
Failed to connect to t3://HPServer:7001 due to:
[weblogic.rmi.UnexpectedException: Marshalling:
- with nested exception:
[weblogic.rjvm.PeerGoneException:
- with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
creating response stream ] - with nested exception:
[java.io.InvalidClassException:
weblogic.security.acl.internal.AuthenticatedUser; Local class not
compatible: stream classdesc serialVersionUID=6699361079932480379 local
class serialVersionUID=2825328378974757378]]]]
I previously had similar problems pinging the server from the server itself
until I included the servicepack in the classpath.
Anyone have any idea what going on in this situation?
Cameron Taggart

Problem in clustering in Weblogic 5.1 (java.util.zip.ZipException)

Hi All,
We are using WLS 5.1 clustering. 2 WLS are running in 2 different unix box in same subnet. But we are getting the following exception ( Though all the Beans have been deployed successfully).
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.open(Compiled Code)
at java.util.zip.ZipFile.<init>(Compiled Code)
at java.util.zip.ZipFile.<init>(Compiled Code)
at weblogic.boot.ServerClassLoader.deploy(ServerClassLoader.java:132)
at weblogic.cluster.AnnotatedServiceOffer.expandClassPath(Compiled Code)
at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled Code)
at weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Compiled Code)
Fri Jan 25 16:57:22 MST 2002:<E> <MulticastSocket> Multicast socket receive error: java.lang.RuntimeException: I/O error opening JAR file from file:/opt/wlogic/weblogic/obscluster/server113/tmp_deployments/ejbjar-4247.jar
(cluster name we have changed to obscluster )
This Exception is coming in both the servers The difference is that the server whose ip ends with 112 is trying to open the file from server113 dir and the server whose ip ends with 113 is trying to open the file from server112 dir.
In web I have found that if the directory structure of 2 servers doesn't match then this porblem can arise. But for both of my servers the directory structure is same , at least until /opt/wlogic/weblogic/obscluster/ and then the directory server113 or server112 is created by Weblogic automatically when I have started the Server.
Any help regarding this will be very helpful.
Thanks & Regards
Srijeeb.

Hi everyone,
I think I have got the solution. Using sp11. added sp11 related jar in PRE_CLASSPATH . Problem Solved....
Thanks
Srijeeb

CORBA System Exception to RMI mapping for Weblogic

Hi,
I am in the process of porting some older code that was hosted in an Inprise AppServer
4.1 environment to Weblogic 8.1. The existing code is catching several CORBA system
exceptions that include the following :
org.omg.CORBA.NO_RESPONSE
org.omg.CORBA.UNKNOWN
org.omg.CORBA.NO_MEMORY
org.omg.CORBA.NO_RESOURCES
org.omg.CORBA.OBJECT_NOT_EXIST
As far as i understand, these exceptions will never be thrown by the Weblogic
8.1 Server. I wanted to see if someone can guide me as to which RMI exceptions
will be thrown by Weblogic server instead of the above mentioned CORBA exceptions
Thanks in advance
Muhammad

"Muhammad Choonara" <[email protected]> writes:
I am in the process of porting some older code that was hosted in an Inprise AppServer
4.1 environment to Weblogic 8.1. The existing code is catching several CORBA system
exceptions that include the following :
org.omg.CORBA.NO_RESPONSEUnmarshallException (probably)
org.omg.CORBA.UNKNOWNNo idea
org.omg.CORBA.NO_MEMORYOutOfMemoryException
org.omg.CORBA.NO_RESOURCESNo idea
org.omg.CORBA.OBJECT_NOT_EXISTNoSuchObjectException
>
As far as i understand, these exceptions will never be thrown by the Weblogic
8.1 Server. I wanted to see if someone can guide me as to which RMI exceptions
will be thrown by Weblogic server instead of the above mentioned CORBA exceptions
? andy

RMI Clustering in Weblogic 7.0

Similar Messages

Maybe you are looking for