[
https://issues.jboss.org/browse/WFLY-11099?page=com.atlassian.jira.plugin...
]
Kabir Khan commented on WFLY-11099:
-----------------------------------
[~martyn-taylor] says:
{code}
Looks like JIRA is down.
The version in the product should be: version=0.29.0.redhat-00001
{code}
However as [~psakar] pointed out, we don't actually use qpid in the product, so for
upstream we can use whatever works. But as AMQ uses 0.29, is there any reason not to use
that in wildfly right now?
ActiveMQ 2.6.3.jbossorg-001 requires QPid Proton-J 0.27.3
(ClassNotFoundExceptions in messaging subsystem)
----------------------------------------------------------------------------------------------------------
Key: WFLY-11099
URL:
https://issues.jboss.org/browse/WFLY-11099
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.1.Final, 14.0.0.Final
Reporter: Jan-Willem Gmelig Meyling
Assignee: Jeff Mesnil
Priority: Major
With the update from Artemis 1.5.x to 2.6.x in WFLY-9407, Proton-J wasn't updated
from 0.16.x to 0.27.3, which leads to class not found exceptions for "Sasl... "
classes when remote acceptors are created and connected to (I tested with AMQP protocol).
When updating Proton-J to the newest version (0.29.0) my issues are gone.
I'm not sure which other modules are using the proton-j module, but my suggestion is
that we bump the version of Proton-j to the required 0.27.3 minimally.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)