[GLASSFISH-5895] XA in asadmin create-jms-resource Created: 05/Sep/08  Updated: 08/May/12  Resolved: 08/May/12

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 9.1peur2
Fix Version/s: 4.0_b34

Type: Bug Priority: Minor
Reporter: bahadir_g Assignee: Simon Meng
Resolution: Fixed Votes: 2
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: HP


Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-18701 asadmin create-jms-resource subcomman... Sub-task Resolved Mike Fitch  
Issuezilla Id: 5,895

 Description   

The command below creates a non-XA JMS connection factory instead of an XA one
althought it is said XA is default in the documentation.

"asadmin create-jms-resource --host localhost --port 4848 --user admin --restype
javax.jms.QueueConnectionFactory jms/TESTPRO_XAConnFactory"

Another attempt to create an XA JMS connection factory with the following
command fails to create a connection factory also

create-jms-resource --host localhost --port 4848 --user admin
â€"-transaction-support=XATransaction --restype javax.jms.ConnectionFactory
jms/QSDP_XAConnFactory

I couldn't find any additional explanation in the docs and also got no answer
for my question at glassfish forum if I missed something.
So it seems there is no way to create an XA JMS connection factory from CLI
commands instead of Admin GUI.



 Comments   
Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by tronda [ 13/Feb/09 ]
      • Issue 5895 has been confirmed by votes. ***
Comment by Tom Mueller [ 25/Jan/11 ]

Cleared the Fix version field since this issue isn't going to be fixed in V3.

Comment by Tom Mueller [ 18/Feb/11 ]

Assigning to correct category (JMS).

Comment by David Zhao [ 14/Feb/12 ]

In 3.1.2, create-jms-resource command does not support parameter -transaction-support.

Comment by Simon Meng [ 04/May/12 ]

The transaction-support attribute can be set properly with property parameter. The following command works fine:
create-jms-resource --restype javax.jms.ConnectionFactory --property transaction-support=XATransaction jms/QSDP_XAConnFactory

This issue should be a document issue. Current glassfish document does not mention that transaction-support and some other attributes can be set in property parameter.

Comment by Simon Meng [ 08/May/12 ]

The required functionality is already in product. The document need be updated properly. See GLASSFISH-18701.

Generated at Tue Jun 02 09:00:42 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.