[JBoss JIRA] (WFLY-9360) Upgrade Generic JMS RA 2.0.1.Final
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9360?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil edited comment on WFLY-9360 at 9/19/17 8:34 AM:
------------------------------------------------------------
TCK 7 tests that are fixed by the Generic JMS RA 2.0.1.Final:
* [core.queueConnection]
** fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [core.topicConnection]
** fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [jms.ee.ejb.sessionTtests]
** clientID not set on the pooled-connection-factory dscf => requires change to the standalone-full-tck7 configuration
* [jms.ee.mdb.xa]
** NOT FIXED
** related to JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context
** session will be non-xa or xa depending on an active tx. But Tibco 8 XA CF can not create plain JMS Context (that is created when the managed connection will create JMS resources (session & jms
* [core20]
** JMSSecurityException fixed by https://github.com/jms-ra/generic-jms-ra/pull/21
* [ee20.cditests]
** some are NOT FIXED (caused by JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context)
was (Author: jmesnil):
TCK 7 tests that are fixed by the Generic JMS RA 2.0.1.Final:
* [core.queueConnection]
** fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [core.topicConnection]
* fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [jms.ee.ejb.sessionTtests]
* clientID not set on the pooled-connection-factory dscf => requires change to the standalone-full-tck7 configuration
* [jms.ee.mdb.xa]
* NOT FIXED
* related to JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context
* session will be non-xa or xa depending on an active tx. But Tibco 8 XA CF can not create plain JMS Context (that is created when the managed connection will create JMS resources (session & jms
* [core20]
* JMSSecurityException fixed by https://github.com/jms-ra/generic-jms-ra/pull/21
* [ee20.cditests]
* some are NOT FIXED (caused by JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context)
> Upgrade Generic JMS RA 2.0.1.Final
> ----------------------------------
>
> Key: WFLY-9360
> URL: https://issues.jboss.org/browse/WFLY-9360
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Affects Versions: 11.0.0.CR1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The 2.0.1.Final release addresses issues raised by running the TCK with Tibco 8 as the JMS broker behind the Generic JMS RA
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9360) Upgrade Generic JMS RA 2.0.1.Final
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9360?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFLY-9360:
-----------------------------------
TCK 7 tests that are fixed by the Generic JMS RA 2.0.1.Final:
* [core.queueConnection]
* fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [core.topicConnection]
* fixed by https://github.com/jms-ra/generic-jms-ra/pull/20
* [jms.ee.ejb.sessionTtests]
* clientID not set on the pooled-connection-factory dscf => requires change to the standalone-full-tck7 configuration
* [jms.ee.mdb.xa]
* NOT FIXED
* related to JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context
* session will be non-xa or xa depending on an active tx. But Tibco 8 XA CF can not create plain JMS Context (that is created when the managed connection will create JMS resources (session & jms
* [core20]
* JMSSecurityException fixed by https://github.com/jms-ra/generic-jms-ra/pull/21
* [ee20.cditests]
* some are NOT FIXED (caused by JBEAP-13128 - Tibco 8 XA CF does not allow to create plain JMS Context)
> Upgrade Generic JMS RA 2.0.1.Final
> ----------------------------------
>
> Key: WFLY-9360
> URL: https://issues.jboss.org/browse/WFLY-9360
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Affects Versions: 11.0.0.CR1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The 2.0.1.Final release addresses issues raised by running the TCK with Tibco 8 as the JMS broker behind the Generic JMS RA
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9360) Upgrade Generic JMS RA 2.0.1.Final
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9360?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil moved JBEAP-13190 to WFLY-9360:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9360 (was: JBEAP-13190)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: Generic JMS RA)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.CR1)
> Upgrade Generic JMS RA 2.0.1.Final
> ----------------------------------
>
> Key: WFLY-9360
> URL: https://issues.jboss.org/browse/WFLY-9360
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JMS
> Affects Versions: 11.0.0.CR1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The 2.0.1.Final release addresses issues raised by running the TCK with Tibco 8 as the JMS broker behind the Generic JMS RA
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JGRP-2218) New payload interface
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2218?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2218:
---------------------------
Description:
h3. Goal
Change payload in {{Message}} from byte[] arrays to a {{Payload}} interface which can have multiple implementations.
h3. Reason
Currently, having to pass a byte[] array to a message leads to unnecessary copying:
* When an application has a ref to an NIO (direct) {{ByteBuffer}}, the bytes in the byte buffer have to be copied into a byte[] array and then set in the message
* When the application sends around byte[] arrays, but also wants to add some additional metadata, e.g. type (1000-byte requests/responses), it needs to create a new byte[] array of (say) 1001 bytes and copy the data (1000 bytes) plus the request type (1 byte) into the new copy. Example: {{MPerf}} and {{UPerf}}
* When an object has to be sent (e.g. in Infinispan), the object has to be marshalled into a byte[] array (first allocation) and then added to the message. With the suggested {{ObjectPayload}} (below), marshalling of the object would occur late, and it would be marshalled directly into the output stream of the bundler, eliminating the byte[] array allocation made by the application.
h3. Design
Instead of copying, the application creates an instance of {{Payload}} and sets the payload in {{Message}}. The {{Payload}} is then passed all the way down into the transport where it is marshalled and sent. There can be a number of payload implementations, e.g.
* {{ByteArrayPayload}}: wraps a byte[] array with an offset and length
* {{NioDirectPayload}}: wraps an NIO direct {{ByteBuffer}}
* {{NioHeapPayload}}: wraps an NIO heap-based {{ByteBuffer}}
* {{CompositePayload}}: wraps multiple Buffers. E.g. type (1 byte) and data (1000 bytes) as described above
* {{IntPayload}}: a single integer
* {{ObjectPayload}}: has an Object and a ClassLoader (for reading), plus a Marshaller which know how to marshal the object, this allows for objects to be passed in payloads and they're only marshalled at the end (transport).
* {{PartialPayload}}: a ref to a {{Payload}}, with an offset and length
* {{InputStreamPayload}}: has a ref to an input stream and copies data from input- to output stream when marshalling
The {{Payload}} interface has methods:
* {{size()}}
* {{writeTo(DataOutput)}}
* {{readFrom(DataInput)}}
* {{getInput()}}: this provides a {{DataInput}} stream for reading from the underlying payload
and possibly also
* {{acquire()}} and
* {{release()}} (for ref-counting)
* {{copy()}}
Each payload impl has an ID and it should be possible to register new impls. A {{PayloadFactory}} maintains a mapping between IDs and impl classes.
When marshalling a {{Payload}}, the ID is written first, followed by the payload's {{writeTo()}} method. When reading payloads, the {{PayloadFactory}} is used to create instances from IDs.
h4. Fragmentation
When fragmenting a buffer, the fragments are instances of {{PartialPayload}} which maintains an offset and length over an underlying payload. When marshalling a {{PartialPayload}}, only the part between offset and offset+length is written to the output stream.
h4. Reference counting
If we implement ref-counting, then payloads can be reused as soon as the ref-count is 0. For example, when sending a message, the payload's ref-count could be incremented by the app calling {{acquire()}}. (Assuming the message is a unicast message), {{UNICAST3}} would increment the count to 2. This is needed because {{UNICAST3}} might have to retransmit the message if it was lost on the network, and meanwhile the payload cannot be reused (changed). The app calls {{release()}} when the {{JChannel.send()}} call returns, but the payload cannot be reused until {{UNICAST3}} calls {{release()}} as well. This will happen when an {{ACK}} for the given message has been received.
h4. Payload factory
When a request is received, the buffer is created from the bytes received on the network, based on the ID. This should be done by asking a {{PayloadFactory}} component for a new buffer. A naive implementation might create a new buffer every time, and more sophisticated one might use a pool of payloads.
The {{PayloadFactory}} instance could be replaced by one's own implementation; this allows for an application to control the lifecycle of payloads: thus the creation of buffers by the application and of payloads received over the network can be controlled by the same payload management impl.
h4. Symmetry
When sending a {{CompositePayload}} of a 500 byte {{ByteArrayPayload}} and a 1000 byte {{NioDirectPayload}}, would we want to also get the same {{CompositePayload}} consisting of 2 payloads on the receiver side, or would we want to combine the 2 payloads into one and make the 2 payloads refer to the same combined byte[] array (or NIO buffer)? Should this be made configurable?
h4. Misc
* Since this issue includes API changes, the version will be 5.0
was:
h3. Goal
Change payload in {{Message}} from byte[] arrays to a {{Payload}} interface which can have multiple implementations.
h3. Reason
Currently, having to pass a byte[] array to a message leads to unnecessary copying:
* When an application has a ref to an NIO (direct) {{ByteBuffer}}, the bytes in the byte buffer have to be copied into a byte[] array and then set in the message
* When the application sends around byte[] arrays, but also wants to add some additional metadata, e.g. type (1000-byte requests/responses), it needs to create a new byte[] array of (say) 1001 bytes and copy the data (1000 bytes) plus the request type (1 byte) into the new copy. Example: {{MPerf}} and {{UPerf}}
* When an object has to be sent (e.g. in Infinispan), the object has to be marshalled into a byte[] array (first allocation) and then added to the message. With the suggested {{ObjectPayload}} (below), marshalling of the object would occur late, and it would be marshalled directly into the output stream of the bundler, eliminating the byte[] array allocation made by the application.
h3. Design
Instead of copying, the application creates an instance of {{Payload}} and sets the payload in {{Message}}. The {{Payload}} is then passed all the way down into the transport where it is marshalled and sent. There can be a number of payload implementations, e.g.
* {{ByteArrayPayload}}: wraps a byte[] array with an offset and length
* {{NioDirectPayload}}: wraps an NIO direct {{ByteBuffer}}
* {{NioHeapPayload}}: wraps an NIO heap-based {{ByteBuffer}}
* {{CompositePayload}}: wraps multiple Buffers. E.g. type (1 byte) and data (1000 bytes) as described above
* {{IntPayload}}: a single integer
* {{ObjectPayload}}: has an Object and a ClassLoader (for reading), plus a Marshaller which know how to marshal the object, this allows for objects to be passed in payloads and they're only marshalled at the end (transport).
* {{PartialPayload}}: a ref to a {{Payload}}, with an offset and length
The {{Payload}} interface has methods:
* {{size()}}
* {{writeTo(DataOutput)}}
* {{readFrom(DataInput)}}
* {{getInput()}}: this provides a {{DataInput}} stream for reading from the underlying payload
and possibly also
* {{acquire()}} and
* {{release()}} (for ref-counting)
* {{copy()}}
Each payload impl has an ID and it should be possible to register new impls. A {{PayloadFactory}} maintains a mapping between IDs and impl classes.
When marshalling a {{Payload}}, the ID is written first, followed by the payload's {{writeTo()}} method. When reading payloads, the {{PayloadFactory}} is used to create instances from IDs.
h4. Fragmentation
When fragmenting a buffer, the fragments are instances of {{PartialPayload}} which maintains an offset and length over an underlying payload. When marshalling a {{PartialPayload}}, only the part between offset and offset+length is written to the output stream.
h4. Reference counting
If we implement ref-counting, then payloads can be reused as soon as the ref-count is 0. For example, when sending a message, the payload's ref-count could be incremented by the app calling {{acquire()}}. (Assuming the message is a unicast message), {{UNICAST3}} would increment the count to 2. This is needed because {{UNICAST3}} might have to retransmit the message if it was lost on the network, and meanwhile the payload cannot be reused (changed). The app calls {{release()}} when the {{JChannel.send()}} call returns, but the payload cannot be reused until {{UNICAST3}} calls {{release()}} as well. This will happen when an {{ACK}} for the given message has been received.
h4. Payload factory
When a request is received, the buffer is created from the bytes received on the network, based on the ID. This should be done by asking a {{PayloadFactory}} component for a new buffer. A naive implementation might create a new buffer every time, and more sophisticated one might use a pool of payloads.
The {{PayloadFactory}} instance could be replaced by one's own implementation; this allows for an application to control the lifecycle of payloads: thus the creation of buffers by the application and of payloads received over the network can be controlled by the same payload management impl.
h4. Symmetry
When sending a {{CompositePayload}} of a 500 byte {{ByteArrayPayload}} and a 1000 byte {{NioDirectPayload}}, would we want to also get the same {{CompositePayload}} consisting of 2 payloads on the receiver side, or would we want to combine the 2 payloads into one and make the 2 payloads refer to the same combined byte[] array (or NIO buffer)? Should this be made configurable?
h4. Misc
* Since this issue includes API changes, the version will be 5.0
> New payload interface
> ---------------------
>
> Key: JGRP-2218
> URL: https://issues.jboss.org/browse/JGRP-2218
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 5.0
>
>
> h3. Goal
> Change payload in {{Message}} from byte[] arrays to a {{Payload}} interface which can have multiple implementations.
> h3. Reason
> Currently, having to pass a byte[] array to a message leads to unnecessary copying:
> * When an application has a ref to an NIO (direct) {{ByteBuffer}}, the bytes in the byte buffer have to be copied into a byte[] array and then set in the message
> * When the application sends around byte[] arrays, but also wants to add some additional metadata, e.g. type (1000-byte requests/responses), it needs to create a new byte[] array of (say) 1001 bytes and copy the data (1000 bytes) plus the request type (1 byte) into the new copy. Example: {{MPerf}} and {{UPerf}}
> * When an object has to be sent (e.g. in Infinispan), the object has to be marshalled into a byte[] array (first allocation) and then added to the message. With the suggested {{ObjectPayload}} (below), marshalling of the object would occur late, and it would be marshalled directly into the output stream of the bundler, eliminating the byte[] array allocation made by the application.
> h3. Design
> Instead of copying, the application creates an instance of {{Payload}} and sets the payload in {{Message}}. The {{Payload}} is then passed all the way down into the transport where it is marshalled and sent. There can be a number of payload implementations, e.g.
> * {{ByteArrayPayload}}: wraps a byte[] array with an offset and length
> * {{NioDirectPayload}}: wraps an NIO direct {{ByteBuffer}}
> * {{NioHeapPayload}}: wraps an NIO heap-based {{ByteBuffer}}
> * {{CompositePayload}}: wraps multiple Buffers. E.g. type (1 byte) and data (1000 bytes) as described above
> * {{IntPayload}}: a single integer
> * {{ObjectPayload}}: has an Object and a ClassLoader (for reading), plus a Marshaller which know how to marshal the object, this allows for objects to be passed in payloads and they're only marshalled at the end (transport).
> * {{PartialPayload}}: a ref to a {{Payload}}, with an offset and length
> * {{InputStreamPayload}}: has a ref to an input stream and copies data from input- to output stream when marshalling
> The {{Payload}} interface has methods:
> * {{size()}}
> * {{writeTo(DataOutput)}}
> * {{readFrom(DataInput)}}
> * {{getInput()}}: this provides a {{DataInput}} stream for reading from the underlying payload
> and possibly also
> * {{acquire()}} and
> * {{release()}} (for ref-counting)
> * {{copy()}}
> Each payload impl has an ID and it should be possible to register new impls. A {{PayloadFactory}} maintains a mapping between IDs and impl classes.
> When marshalling a {{Payload}}, the ID is written first, followed by the payload's {{writeTo()}} method. When reading payloads, the {{PayloadFactory}} is used to create instances from IDs.
> h4. Fragmentation
> When fragmenting a buffer, the fragments are instances of {{PartialPayload}} which maintains an offset and length over an underlying payload. When marshalling a {{PartialPayload}}, only the part between offset and offset+length is written to the output stream.
> h4. Reference counting
> If we implement ref-counting, then payloads can be reused as soon as the ref-count is 0. For example, when sending a message, the payload's ref-count could be incremented by the app calling {{acquire()}}. (Assuming the message is a unicast message), {{UNICAST3}} would increment the count to 2. This is needed because {{UNICAST3}} might have to retransmit the message if it was lost on the network, and meanwhile the payload cannot be reused (changed). The app calls {{release()}} when the {{JChannel.send()}} call returns, but the payload cannot be reused until {{UNICAST3}} calls {{release()}} as well. This will happen when an {{ACK}} for the given message has been received.
> h4. Payload factory
> When a request is received, the buffer is created from the bytes received on the network, based on the ID. This should be done by asking a {{PayloadFactory}} component for a new buffer. A naive implementation might create a new buffer every time, and more sophisticated one might use a pool of payloads.
> The {{PayloadFactory}} instance could be replaced by one's own implementation; this allows for an application to control the lifecycle of payloads: thus the creation of buffers by the application and of payloads received over the network can be controlled by the same payload management impl.
> h4. Symmetry
> When sending a {{CompositePayload}} of a 500 byte {{ByteArrayPayload}} and a 1000 byte {{NioDirectPayload}}, would we want to also get the same {{CompositePayload}} consisting of 2 payloads on the receiver side, or would we want to combine the 2 payloads into one and make the 2 payloads refer to the same combined byte[] array (or NIO buffer)? Should this be made configurable?
> h4. Misc
> * Since this issue includes API changes, the version will be 5.0
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-3282) Duplicate record is written in property file when group name set to empty
by Masafumi Miura (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3282?page=com.atlassian.jira.plugi... ]
Masafumi Miura updated WFCORE-3282:
-----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2832
> Duplicate record is written in property file when group name set to empty
> -------------------------------------------------------------------------
>
> Key: WFCORE-3282
> URL: https://issues.jboss.org/browse/WFCORE-3282
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.2.CR1
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
>
> Duplicate records are registered in mgmt-groups.properties and application-roles.properties if adding user with empty group name as follows.
> 1. Add user "testuser1" with empty group from add-user.sh.
> $JBOSS_HOME/bin/add-user.sh -sc ./standalone/configuration -u testuser1 -p RedHat1! -g ""
> 2. After that, the following record is written in the group property file.
> - mgmt-groups.properties (application-roles.properties)
> testuser1=
> 3. Add user "testuser2" with empty group from add-user.sh.
> $JBOSS_HOME/bin/add-user.sh -sc ./standalone/configuration -u testuser2 -p RedHat1! -g ""
> 4. After that, the user records that have empty group will be registered duplicately as below.
> - mgmt-groups.properties (application-roles.properties)
> testuser1=
> testuser2=
> testuser1= # duplicate record
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9359) wildfly8.1 can't graceful shut down JNDI perfectly
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9359?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-9359.
-----------------------------
Fix Version/s: (was: 8.1.0.Final)
Resolution: Out of Date
Graceful shutdown was first added in WildFly 9, with much improvements in 10 and additional ones in 11.
Please upgrade your server so you can benefit from this.
> wildfly8.1 can't graceful shut down JNDI perfectly
> --------------------------------------------------
>
> Key: WFLY-9359
> URL: https://issues.jboss.org/browse/WFLY-9359
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 8.x.x TBD
> Environment: wildfly8.1.0.Final
> servlet3.0
> mysql5.x
> eclipse neon.3
> jdk1.7
> Reporter: fantesy so
> Labels: graceful, shutdown, wildfly
> Attachments: DemoServlet.java, server.log
>
>
> I create a servlet to query some mysql data. And I use jboss JNDI which defined in standalone.xml。 I want this querying is needs to be done 1000 times。But when I shut down wildfly8.1.0 suddenly during the querying is running, the querying can't finished and will throw some exception is server.log。But I do this test case in apache-tomcat-8.0.36 and websphere7, the querying is finished before server is down。
> So I this wildfly8.1.x cant shutdown graceful perfectly。
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months