jboss-remoting-issues
August 2012
jboss-remoting-issues@lists.jboss.org
- 1 participants
- 2 discussions
[JBoss JIRA] (JBREM-1313) Release 2.5.4.SP4
by Ron Sigal (JIRA)
Ron Sigal created JBREM-1313:
--------------------------------
Summary: Release 2.5.4.SP4
Key: JBREM-1313
URL: https://issues.jboss.org/browse/JBREM-1313
Project: JBoss Remoting
Issue Type: Release
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.4.SP3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
- 1
- 3
[JBoss JIRA] (JBREM-1314) 3873 was closed suddenly
by Richard Zhang (JIRA)
Richard Zhang created JBREM-1314:
------------------------------------
Summary: 3873 was closed suddenly
Key: JBREM-1314
URL: https://issues.jboss.org/browse/JBREM-1314
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Richard Zhang
While JBOSS5.1.0 GA running, there was an exception log in server.log like:
2012-05-30 07:43:43,176 INFO (main)[org.jboss.bootstrap.microcontainer.ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 38s:998ms
2012-06-26 21:00:08,515 ERROR (WorkerThread#0[2001:1890:1001:240c:0:0:0:4:50783])[org.jboss.remoting.transport.socket.ServerThread] WorkerThread#0[2001:1890:1001:240c:0:0:0:4:50783] exception occurred during first invocation
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor422.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:909)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:491)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)
at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:100)
at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:54)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.java:75)
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.java:58)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:179)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:162)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:66)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)
... 6 more
And we checked the 3873 using "netstat -antp" command. Don't know when this port was closed.
Could someone tell me how to prevent it or the root cause. Thanks in advance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
- 2
- 3
- ← Newer
- 1
- Older →