Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1172856 - [GSS](6.4.0) Server side EJB Handler not compression response
[GSS](6.4.0) Server side EJB Handler not compression response
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB (Show other bugs)
6.3.2
Unspecified Unspecified
unspecified Severity unspecified
: ER1
: EAP 6.4.0
Assigned To: Tomas Hofman
Jan Martiska
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-12-10 17:52 EST by Brad Maxwell
Modified: 2018-03-06 15:40 EST (History)
2 users (show)

See Also:
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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFLY-4173 Major Closed Server side EJB Handler not compression response 2018-05-04 02:13 EDT

  None (edit)
Description Brad Maxwell 2014-12-10 17:52:56 EST 
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 07:28:02 EST 
Tomas Hofman <thofman@redhat.com> updated the status of jira WFLY-4173 to Coding In Progress
Comment 4 Jan Martiska 2015-02-27 05:14:50 EST 
Looks like this got stuck in POST state
Comment 5 Jan Martiska 2015-03-02 09:48:15 EST 
Verified in EAP 6.4.0.ER3.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.