[Messaging, JMS & JBossMQ] - Re: JBossMQ Fails under load - Exiting on IOE
by alchemista
I'm still having the same problem. If there is an ERROR in the log, I would not ignore it, if it's just a DEBUG or INFO maybe. My connection will hard-die (i.e. never come back to life) after this error occurs too often.
On the server-side, the server.log throws the following error around the time the client gives the error posted earlier.
2006-11-30 16:31:34,159 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected
Error in method: public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message)
java.lang.OutOfMemoryError: Java heap space
2006-11-30 16:31:34,160 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Exception in JMSCI message listener
javax.ejb.EJBException: Unexpected Error
java.lang.OutOfMemoryError: Java heap space
at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:395)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
at org.jboss.ejb.Container.invoke(Container.java:873)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:1090)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1392)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
at org.jboss.mq.SpySession.run(SpySession.java:333)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2006-11-30 16:33:32,667 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
Setting up the UILClientIL Connection
2006-11-30 16:33:32,667 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
The UILClientIL Connection is set up
2006-11-30 16:34:59,549 ERROR [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.AddMsg20684031[msgType: m_addMessage, msgID: -2147473491, error: null]
java.lang.OutOfMemoryError: Java heap space
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990961#3990961
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990961
19 years, 5 months
[EJB/JBoss] - Almost identical session beans, one works one fails
by Melladh
The failing one is looked up like this, and I get a "not bound" exception when activating the servlet it's called from.
Context context = new InitialContext();
| Object listRef = context.lookup("java:comp/env/ejb/ListApplicants");
|
The working one is looked up the same way, except that it's called Applicant instead of ListApplicants. All the configurations look the same.
Home interface
package ejb;
|
| /**
| * Home interface for ListApplicants.
| */
| public interface ListApplicantsHome
| extends javax.ejb.EJBHome
| {
| public static final String COMP_NAME="java:comp/env/ejb/ListApplicants";
| public static final String JNDI_NAME="ejb/ListApplicants";
|
| public ejb.ListApplicants create(java.lang.String param)
| throws javax.ejb.CreateException,java.rmi.RemoteException;
|
| }
|
jboss.xml
<session>
| <ejb-name>ListApplicants</ejb-name>
| <jndi-name>ejb/ListApplicants</jndi-name>
| <local-jndi-name>ListApplicantsLocal</local-jndi-name>
| </session>
ejb-jar.xml
<session >
| <description><![CDATA[Description for ListApplicants]]></description>
| <display-name>Name for ListApplicants</display-name>
|
| <ejb-name>ListApplicants</ejb-name>
|
| <home>ejb.ListApplicantsHome</home>
| <remote>ejb.ListApplicants</remote>
| <ejb-class>ejb.ListApplicantsBean</ejb-class>
|
| <session-type>Stateful</session-type>
| <transaction-type>Container</transaction-type>
|
| </session>
This looks exactly the same for my ApplicantBean, with the names changed accordingly, and that one works! This one doesn't. Anyone have a clue about what's wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990953#3990953
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990953
19 years, 5 months
[EJB 3.0] - SocketException converted into UndeclaredThrowableException
by metelka
Hi,
I have a problem with exception reporting in EJB3 remote calls. My remote client has 20s timeout on remote calls and the timeout works fine, however the timeout exception is converted into UndeclaredThrowableException by jboss remoting/ejb3 invocation interceptors. I would expect to receive some kind of communication exception or remoting exception, which I could handle in my client code. Any ideas?
Thanks
SW versions: JBoss 4.0.4GA, EJB3 RC9, JBoss Remoting 1.4.4.
My stacktrace:
anonymous wrote :
| 2006-11-30 17:01:37,334 FATAL [cz.tipsport.pluginsys.gui.ApplicationUncaughtExceptionHandler] (AWT-EventQueue-0:) Unchecked exception thrown!
| java.lang.reflect.UndeclaredThrowableException
| at $Proxy44.findAddressees(Unknown Source)
| at cz.tipsport.tip.dms.gui.addressee.gui.AddresseeSelectorPanelCtl.(AddresseeSelectorPanelCtl.java:156)
|
| ... not important ...
|
| Caused by: java.rmi.MarshalException: Socket timed out. Waited 20000 milliseconds for response while calling on InvokerLocator [socket://172.16.19.42:3673/?timeout=20000]; nested exception is:
| java.net.SocketTimeoutException: Read timed out
| at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:302)
| at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
| at org.jboss.remoting.Client.invoke(Client.java:525)
| at org.jboss.remoting.Client.invoke(Client.java:488)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
| ... 114 more
| Caused by: java.net.SocketTimeoutException: Read timed out
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
| at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
| at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2490)
| at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2500)
| at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
| at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
| at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
| at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
| ... 126 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990952#3990952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990952
19 years, 5 months