[JBoss-dev] [ jboss-Bugs-708762 ] transacted JMS Managed Connection Not Initialized Correctly

2003-03-31 Thread SourceForge.net
Bugs item #708762, was opened at 2003-03-24 04:06
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=708762group_id=22866

Category: JBossMQ
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Paul Bandler (paulbandler)
Assigned to: Scott M Stark (starksm)
Summary: transacted JMS Managed Connection Not Initialized Correctly

Initial Comment:
If one creates a JMS client connection to a remote Q on 
a JBoss JMS Server using the JCA based JMS Adapter 
the 'transacted' property is not correctly set in the 
JmsConnectionRequestInfo - it is always set to true 
regardless of whether an XA or non-XA 
QueueConnection is being created.  This is caused by 
the source file 
connector/src/main/org/jboss/resource/adapter/jms/Jms
ManagedConnection.java setup method which initializes 
the local variable 'transacted' to true in all cases that is 
then passed to the factory methods rather than using 
the value from its own 'info' property.  The following 
change fixes the problem.

cvs diff JmsManagedConnection.java (in directory 
C:\cvshome\jboss-all-head-2802
\connector\src\main\org\jboss\resource\adapter\jms\)
Index: JmsManagedConnection.java
=
==
RCS 
file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/a
dapter/jms/JmsManagedConnection.java,v
retrieving revision 1.1.2.2
diff -r1.1.2.2 JmsManagedConnection.java
565c565
  boolean transacted = true;
---
  boolean transacted = info.isTransacted();

*CVS exited normally with code 1*

Note that as the JBoss transaction manager does not 
support prop-agating transaction contexts to other virtual 
machines I believe that if one tries to use an 
XAQueueConnection the message never gets sent as 
the transaction is not properly committed.  On the other 
hand if one tries to use a non-XAQueueConnection the 
above bug still causes the message to be buffered 
locally and not sent, so it is unclear if there is any way 
to send JMS messages from say MDB using managed 
JMS connections...?  This gives rise to the type of 
problems raised in following forum postings:

http://www.jboss.org/forums/thread.jsp?
forum=48thread=29403
http://www.jboss.org/forums/thread.jsp?
forum=48thread=29239
http://www.jboss.org/forums/thread.jsp?
forum=48thread=29060



--

Comment By: Scott M Stark (starksm)
Date: 2003-03-31 08:38

Message:
Logged In: YES 
user_id=175228

The change has been applied.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=708762group_id=22866


---
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-708762 ] transacted JMS Managed Connection Not Initialized Correctly

2003-03-24 Thread SourceForge.net
Bugs item #708762, was opened at 2003-03-24 12:06
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=708762group_id=22866

Category: JBossMQ
Group: CVS HEAD
Status: Open
Resolution: None
Priority: 5
Submitted By: Paul Bandler (paulbandler)
Assigned to: Nobody/Anonymous (nobody)
Summary: transacted JMS Managed Connection Not Initialized Correctly

Initial Comment:
If one creates a JMS client connection to a remote Q on 
a JBoss JMS Server using the JCA based JMS Adapter 
the 'transacted' property is not correctly set in the 
JmsConnectionRequestInfo - it is always set to true 
regardless of whether an XA or non-XA 
QueueConnection is being created.  This is caused by 
the source file 
connector/src/main/org/jboss/resource/adapter/jms/Jms
ManagedConnection.java setup method which initializes 
the local variable 'transacted' to true in all cases that is 
then passed to the factory methods rather than using 
the value from its own 'info' property.  The following 
change fixes the problem.

cvs diff JmsManagedConnection.java (in directory 
C:\cvshome\jboss-all-head-2802
\connector\src\main\org\jboss\resource\adapter\jms\)
Index: JmsManagedConnection.java
=
==
RCS 
file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/a
dapter/jms/JmsManagedConnection.java,v
retrieving revision 1.1.2.2
diff -r1.1.2.2 JmsManagedConnection.java
565c565
  boolean transacted = true;
---
  boolean transacted = info.isTransacted();

*CVS exited normally with code 1*

Note that as the JBoss transaction manager does not 
support prop-agating transaction contexts to other virtual 
machines I believe that if one tries to use an 
XAQueueConnection the message never gets sent as 
the transaction is not properly committed.  On the other 
hand if one tries to use a non-XAQueueConnection the 
above bug still causes the message to be buffered 
locally and not sent, so it is unclear if there is any way 
to send JMS messages from say MDB using managed 
JMS connections...?  This gives rise to the type of 
problems raised in following forum postings:

http://www.jboss.org/forums/thread.jsp?
forum=48thread=29403
http://www.jboss.org/forums/thread.jsp?
forum=48thread=29239
http://www.jboss.org/forums/thread.jsp?
forum=48thread=29060



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=708762group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development