[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1077) Fix problem in CompressingMarshaller
[
https://jira.jboss.org/jira/browse/JBREM-1077?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1077:
----------------------------------
There's another chapter to the story.
I noticed recently that NewCompressingMarshallerTestCase, which runs in about half a
minute on my Windows laptop, takes about 13 minutes on one of the Red Hat linux test
machines. It turns out that the GZipOutputStream constructor takes an order of magnitude
longer in linux than in Windows. I've changed CompressingMarshaller so that it reuses
a single GZipOutputStream but replaces the Deflater with each call to write().
CompressingUnMarshaller has the symmetric changes with respect to Inflater. Now
NewCompressingMarshallerTestCase takes about 18 seconds on my Fedora laptop.
Fix problem in CompressingMarshaller
------------------------------------
Key: JBREM-1077
URL: https://jira.jboss.org/jira/browse/JBREM-1077
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder), 2.2.3.SP1
Attachments: CompressionInvokerMarshaller.java,
CompressionInvokerUnmarshaller.java, ejb3-compression.tgz, jboss-remoting.jar,
jboss-remoting.jar, jboss-remoting.jar
In org.jboss.remoting.marshal.compress.CompressingMarshaller.write(),
gzos.finish();
oos.flush();
should be
oos.flush();
bos.flush();
gzos.flush();
gzos.finish();
as it is on the 2.x branch.
--
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