[JBoss JIRA] (WFLY-4193) Update spec versions on Kithensink README.md files
by Rafael Benevides (JIRA)
Rafael Benevides created WFLY-4193:
--------------------------------------
Summary: Update spec versions on Kithensink README.md files
Key: WFLY-4193
URL: https://issues.jboss.org/browse/WFLY-4193
Project: WildFly
Issue Type: Enhancement
Reporter: Rafael Benevides
Assignee: Jason Greene
On Every Kitchensink Quickstart, there's a "What is it?" section that contains JAVA EE 6 spec versions. It should be updated to JAVA EE 7.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4113) 8.2.0.Final build hangs
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-4113?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-4113:
-----------------------------------
Workaround should be just a matter of updating jboss-remoting.jar to a later version.
> 8.2.0.Final build hangs
> -----------------------
>
> Key: WFLY-4113
> URL: https://issues.jboss.org/browse/WFLY-4113
> Project: WildFly
> Issue Type: Feature Request
> Components: Test Suite
> Affects Versions: 8.2.0.Final
> Reporter: Peter Major
> Assignee: David Lloyd
> Attachments: jstack.txt
>
>
> When trying to build 8.2.0.Final locally, my build just hangs indefinitely while executing a unit test in the controller module:
> {noformat}
> Running org.jboss.as.controller.ModelControllerClientTestCase
> {noformat}
> Running jstack against the build suggests that there is a deadlock between
> {noformat}
> - waiting to lock <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeMessages(RemoteConnectionChannel.java:560)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:542)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:423)
> - locked <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:232)
> {noformat}
> and
> {noformat}
> - waiting to lock <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:122)
> at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:154)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:122)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:115)
> at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:139)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:157)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:283)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> {noformat}
> Preferably locks should be obtained in the same order across the different code paths to prevent deadlocks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4173) Server side EJB Handler not compression response
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFLY-4173?page=com.atlassian.jira.plugin.... ]
Tomas Hofman reassigned WFLY-4173:
----------------------------------
Assignee: Tomas Hofman (was: David Lloyd)
> Server side EJB Handler not compression response
> ------------------------------------------------
>
> Key: WFLY-4173
> URL: https://issues.jboss.org/browse/WFLY-4173
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Tomas Hofman
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4173) Server side EJB Handler not compression response
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4173?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4173:
-----------------------------------------------
Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1172856|https://bugzilla.redhat.com/show_bug.cgi?id=1172856] from NEW to ASSIGNED
> Server side EJB Handler not compression response
> ------------------------------------------------
>
> Key: WFLY-4173
> URL: https://issues.jboss.org/browse/WFLY-4173
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: David Lloyd
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years