In this release of JBoss EAP 6, when security credentials are not specified in the XML for the recovery element, then recovery does not start for particular JMS resource.
This behavior is not intended as a connection should be created with "no credentials" (or something similar).
This issue is expected to be resolved in a future release of the product.
When security credentials are not specified in xml recovery element then recovery does not start for particular jms resource. But when no credentials are used then connection should be created with "no credentials" (or create connection with null or something similar).
It's meant that when RA config like this will be used then connection should be created with 'no credentials':
It's documented in xsd template as well
<xs:element name="recover-credential" type="credentialType" minOccurs="0" maxOccurs="1">
Specifies the security options used when creating a connection during recovery.
Note: if this credential are not specified the security credential are used for recover too
This issue comes from the question on stack overflow forum
Fixed as part of JBJCA-1181
Fix tested on 6.3.1.CP.CR1.
Instead of having possibility to run recovery without credentials you get error message to log:
WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-8) IJ020016: Missing <recovery> element. XA recovery disabled for: java:/JmsXA
In general. This issue is meant to be fixed in 6.4.0 so set target version appropriately.
The expected behavior came from customer case:
A Subject instance is required by spec
would you be so kind and point me to the place where it's mentioned in spec? I'm not able to find such note, neither in jca nor jms spec.
If we consider e.g. HornetQ settings there is no need to define recovery credentials. In other words you can run recovery without authentication seamlessly.
I'm opening this bz once again as I think that it's a real issue.
JCA 1.7: 188.8.131.52
Ivo Studensky <email@example.com> updated the status of jira JBJCA-1181 to Reopened
Jesper Pedersen <firstname.lastname@example.org> updated the status of jira JBJCA-1181 to Closed