Eclipse Community Forums: Gemini » Gemini, JMS, Spring, Weblogic

Home » Eclipse Projects » Gemini » Gemini, JMS, Spring, Weblogic(Problem in sending message from a bundle to queue on Weblogic 92)

Show: Today's Messages :: Show Polls :: Message Navigator

Gemini, JMS, Spring, Weblogic [message #856718]

Wed, 25 April 2012 23:27

Pouyan Vatan.

Messages: 2
Registered: April 2012

Junior Member

Hi,
I have developed an OSGI application using the following technology
- Embedding OSGi in Tomcat(Gemini)
- Spring (NOT SpringDM)
- Vaadin
- Hibernate
One of the Bundle that I have is JMS client which is supposed to send an a message to a JMS queue which it is on Weblogic 9.2 server.
The main application (which is a WAR file) is installed/deployed as bundle on OSGI framework (Gemini) as well.
There is no issue in installing the bundles and running the application but, in application, when i tired to send mms message to WL server, I get the following error:

weblogic.utils.AssertionError: ***** ASSERTION FAILED *****
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:973)
at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManagerClient.java:144)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:875)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:512)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:330)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:320)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:965)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:887)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:343)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)
Caused by: java.lang.ClassNotFoundException: Failed to load class weblogic.common.internal.PeerInfo
at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:208)
at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:135)
at weblogic.rmi.utils.Utilities.loadClass(Utilities.java:305)
at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:436)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectInputStream.java:268)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1574)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at weblogic.utils.io.ChunkedObjectInputStream.readObjectFromPreDiabloPeer(ChunkedObjectInputStream.java:232)
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:969)
... 12 more

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:7001: Bootstrap to localhost/127.0.0.1:7001 failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:767)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
at com.zenithss.together.modules.jms.helper.JmsSender.sendMessage(JmsSender.java:66)
at com.zenithss.together.modules.jms.views.JmsCommandView$RunListener.buttonClick(JmsCommandView.java:213)
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:597)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:512)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
at com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
at com.vaadin.ui.Button.fireClick(Button.java:550)
at com.vaadin.ui.Button.changeVariables(Button.java:217)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.changeVariables(AbstractCommunicationManager.java:1451)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1399)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1318)
at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:763)
at com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:296)
at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:501)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:185)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:151)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:269)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.net.ConnectException: t3://127.0.0.1:7001: Bootstrap to localhost/127.0.0.1:7001 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
... 38 more
Caused by: java.rmi.ConnectException: Bootstrap to localhost/127.0.0.1:7001 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:334)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
... 41 more

NOTE1: I have a same version of JDK on both servers. As you can see the application and WL9.2 server are on the same machine (localhost) so JDK is the same
NOTE2: I have "127.0.0.1 localhost" in my /etc/hosts
NOTE3: I have "localhost" as Listen Address on Weblogic
It's been one month that I am stocked in this issue. any help would be appreciated !

Thanks
Pouyan

Report message to a moderator

Re: Gemini, JMS, Spring, Weblogic [message #857499 is a reply to message #856718]

Thu, 26 April 2012 15:39

Pouyan Vatan.

Messages: 2
Registered: April 2012

Junior Member

Hi Again,

Also I want to mention that , I developed a Simple Java Application to send a message to the queue on the sever. When I run it, everything works fine and I am able to send the message, but when run the OSGI App. and my JMS module/bundle, i get that exception.
The code in JMS module/bundle is almost exactly the same as my the sample (java application).

Thanks
Pouyan

[Updated on: Thu, 26 April 2012 15:39]

Report message to a moderator