Bug 1172856 - [GSS](6.4.0) Server side EJB Handler not compression response
Summary: [GSS](6.4.0) Server side EJB Handler not compression response
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.4.0
Assignee: Tomas Hofman
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-10 22:52 UTC by Brad Maxwell
Modified: 2019-08-19 12:44 UTC (History)
2 users (show)

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.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-4173 0 Major Closed Server side EJB Handler not compression response 2018-05-04 06:13:15 UTC

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 2 Tomas Hofman 2014-12-23 12:33:14 UTC 
Upstream PR: https://github.com/wildfly/wildfly/pull/7053
This PR: https://github.com/jbossas/jboss-eap/pull/2183
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.
Note You need to log in before you can comment on or make changes to this bug.