Bug 1172856

Summary: [GSS](6.4.0) Server side EJB Handler not compression response
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: EJBAssignee: Tomas Hofman <thofman>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: kkhan, thofman
Target Milestone: ER1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When using EJB compression in previous versions of JBoss EAP 6, the client was sending a compressed request, but the server was sending an uncompressed response, even though it was configured to return a compressed response. In this release, the server will respond with a compressed response as it should.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brad Maxwell 2014-12-10 22:52:56 UTC
When compression is enabled for request/response, the jboss-ejb-client is sending a compressed request, but the application server is responding with an uncompressed response.

On the server enabling TRACE on org.jboss.as.ejb3, we can see the server receives a compressed request

TRACE [org.jboss.as.ejb3] (default task-5) Got message with header 0x1b on channel Channel ID 56b01772 (inbound) of Remoting connection TRACE [org.jboss.as.ejb3.invocation] (default task-5) Received a compressed message stream

Client side, Enabling TRACE on the client side for org.jboss.ejb.client we see it is 0x5 where it should be 0x1b

TRACE org.jboss.ejb.client.remoting.ChannelAssociation - Received message with header 0x5

Comment 1 JBoss JIRA Server 2014-12-23 12:28:02 UTC
Tomas Hofman <thofman> updated the status of jira WFLY-4173 to Coding In Progress

Comment 4 Jan Martiska 2015-02-27 10:14:50 UTC
Looks like this got stuck in POST state

Comment 5 Jan Martiska 2015-03-02 14:48:15 UTC
Verified in EAP 6.4.0.ER3.