[
https://jira.jboss.org/jira/browse/JBAS-6781?page=com.atlassian.jira.plug...
]
Ron Sigal commented on JBAS-6781:
---------------------------------
JBREM-1077 "Fix problem in CompressingMarshaller" is targeted for Remoting
release 2.5.2, which should ship with AS 5.1.0.GA.
SocketExceptions when using CompressingMarshaller/UnMarshaller
--------------------------------------------------------------
Key: JBAS-6781
URL:
https://jira.jboss.org/jira/browse/JBAS-6781
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Remoting
Affects Versions: JBossAS-5.0.1.GA
Environment: Windows XP, JDK 1.5.0_16
Reporter: Rostyslav Smirnov
Assignee: Ron Sigal
Attachments: client.jar, echo.ear, sources.jar
Using compression with EJB3 produces lots of socket exceptions in the server log. The
frequency of the exceptions seems to increase as the size of transferred data increases or
as the speed of the connection decreases.
2009-04-14 10:57:58,872 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper]
(WorkerThread#0[127.0.0.1:2794])
ServerSocketWrapper[Socket[addr=/127.0.0.1,port=2794,localport=3873].f2a5fc] unable to
writing CLOSING byte
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
at
org.jboss.remoting.transport.socket.ServerSocketWrapper.close(ServerSocketWrapper.java:56)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:653)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
Steps to reproduce:
1) Enable compression for EJB3:
In jboss-5.0.1.GA\server\default\deploy\ejb3-connectors-jboss-beans.xml change the line
<parameter>socket://${jboss.bind.address}:${port}</parameter>
to
<parameter>socket://${jboss.bind.address}:${port}/?marshaller=org.jboss.remoting.marshal.compress.CompressingMarshaller&unmarshaller=org.jboss.remoting.marshal.compress.CompressingUnMarshaller</parameter>
2) Deploy echo.ear
3) Run the client.jar
The server.log should have plenty of socket write errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira