Location of tx manager component in source distro?

2007-10-23 Thread Guy Pardon 

Hi,

This component: https://svn.apache.org/repos/asf/geronimo/components/ 
txmanager/


...does not seem to figure in the source distribution 2.0.2 - or did  
I miss something?


Thanks
Guy

Re: Location of tx manager component in source distro?

2007-10-23 Thread Guy Pardon 

Hi,

I see. Then what is the name of the component's classes jar and where  
is it in the distribution?


Thanks again
Guy

On 23-okt-07, at 15:42, Kevan Miller wrote:



On Oct 23, 2007, at 9:11 AM, Guy Pardon wrote:


Hi,

This component: https://svn.apache.org/repos/asf/geronimo/ 
components/txmanager/


...does not seem to figure in the source distribution 2.0.2 - or  
did I miss something?


Hi Guy,
components are released separately from our server distribution.  
Instead they are embedded by the Geronimo server just like any  
other external software project. The downside to this is that it's  
not a one-stop-shop when it comes to our source code. The upside is  
that these components can be re-used more easily by other projects.


You'll find the source in our svn tree, here -- https:// 
svn.apache.org/repos/asf/geronimo/components/txmanager/tags/ 
geronimo-txmanager-parent-2.0.2/


Or the maven central repo --

http://repo1.maven.org/maven2/org/apache/geronimo/components/ 
geronimo-transaction/2.0.2/geronimo-transaction-2.0.2-sources.jar
http://repo1.maven.org/maven2/org/apache/geronimo/components/ 
geronimo-connector/2.0.2/geronimo-connector-2.0.2-sources.jar


--kevan

Integrating a third-party JTA

2007-10-22 Thread Guy Pardon 

Hi,

Does anybody have any useful pointers on how to integrate a third- 
party JTA (Atomikos) into Geronimo?


Thanks,
Guy

Re: Integrating a third-party JTA

2007-10-22 Thread Guy Pardon 

Hi,

Thanks. Where can I see samples of this (how is it done now)? I  
couldn't find the right module so far... Or is it in a jar somewhere?


Guy

On 22-okt-07, at 22:08, Dain Sundstrom wrote:

Other then code that attempts to cast the transaction manger to  
GeronimoTransactionManager (or other Geronimo transaction  
interfaces) it shouldn't be that difficult.  The biggest issue will  
be if you want to use the Geronimo connector implementation, then  
you will have to figure out how to adapt the JTA implementation to  
the org.apache.geronimo.transaction.manager.XAWork interface.  The  
second biggest issue, will be convincing G to correctly build the  
JTA implementation which will require a GBean wrapper of some kind.


-dain

On Oct 22, 2007, at 2:29 AM, Guy Pardon wrote:


Hi,

Does anybody have any useful pointers on how to integrate a third- 
party JTA (Atomikos) into Geronimo?


Thanks,
Guy

Re: Integrating a third-party JTA

2007-10-22 Thread Guy Pardon 

Thanks David,

That helps - I will have a look!

Guy

On 23-okt-07, at 00:21, David Jencks wrote:



On Oct 22, 2007, at 1:45 PM, Guy Pardon wrote:


Hi,

Thanks. Where can I see samples of this (how is it done now)? I  
couldn't find the right module so far... Or is it in a jar somewhere?


Our J2CA and JTA implementation is in https://svn.apache.org/repos/ 
asf/geronimo/components/txmanager/trunk.  You can see how we handle  
the J2CA transaction import using XATerminator and XAWork  
interfaces.  Also notice that in order to make transaction recovery  
work without necessarily all previously existing RMs starting up  
again we've named the RMs with NamedXAResource.  The idea is that  
when the tm starts up again it reads the log to find all the in- 
flight txs and as each RM starts up it registers with the TM and  
the outstanding in-flight txs in that RM are either rolled back or  
committed based on what's in the log.  In order to clear out txs  
where some or all RMs are actually committed before the tm logs  
complete we compare the names of the RM with the names stored  
with the xids in the log.


In the geronimo modules/geronimo-transaction module we have gbeans  
that start the actual TM components at runtime.  You will at least  
need to write some gbean wrappers for the Atomikos TM.  You'll  
probably want to write a replacement configs/transaction module to  
use instead of the standard one.  Then you can map uses of our tm  
module to yours with an entry in var/config/ 
artifact_aliases.properties.



Hope this helps
david jencks



Guy

On 22-okt-07, at 22:08, Dain Sundstrom wrote:

Other then code that attempts to cast the transaction manger to  
GeronimoTransactionManager (or other Geronimo transaction  
interfaces) it shouldn't be that difficult.  The biggest issue  
will be if you want to use the Geronimo connector implementation,  
then you will have to figure out how to adapt the JTA  
implementation to the  
org.apache.geronimo.transaction.manager.XAWork interface.  The  
second biggest issue, will be convincing G to correctly build the  
JTA implementation which will require a GBean wrapper of some kind.


-dain

On Oct 22, 2007, at 2:29 AM, Guy Pardon wrote:


Hi,

Does anybody have any useful pointers on how to integrate a  
third-party JTA (Atomikos) into Geronimo?


Thanks,
Guy

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

2006-11-28 Thread Guy Pardon (JIRA) 
[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37578 ] 

Guy Pardon commented on AMQ-1054:
-

James,

FYI: I am seeing this exactly on OSX/Unix myself.

What I can do is upload the whole thing as a ZIP (if you say whereto).

Guy






 XA recover fails for 4.0.1
 --

 Key: AMQ-1054
 URL: https://issues.apache.org/activemq/browse/AMQ-1054
 Project: ActiveMQ
  Issue Type: Bug
 Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
 for the JTA/XA part
Reporter: Guy Pardon
 Attachments: pom.xml


 XAResource.recover seems to fail for 4.x of ActiveMQ:
 ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
 08:43:35,152 
 [Lorg.apache.activemq.command.DataStructure; [thread: 
 SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: 
 org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: 
 com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
 borrowed this stack trace from). We have seen similar things in other 
 applications that tried to use ActiveMQ. I think this is a class cast error 
 in ActiveMQ...
 With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

2006-11-27 Thread Guy Pardon (JIRA) 
[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37567 ] 

Guy Pardon commented on AMQ-1054:
-

Hi James,

Thanks but no, we don't have to recover anything in this test case.  
It just fails for 4.0.2 and 4.0.1. Not so for 3.1.

Also see this on the JOMT list:

http://mail-archive.objectweb.org/jotm/2006-11/msg2.html

(second half of the message). The issue also seems to arise with JOTM.

Best,
Guy





 XA recover fails for 4.0.1
 --

 Key: AMQ-1054
 URL: https://issues.apache.org/activemq/browse/AMQ-1054
 Project: ActiveMQ
  Issue Type: Bug
 Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
 for the JTA/XA part
Reporter: Guy Pardon

 XAResource.recover seems to fail for 4.x of ActiveMQ:
 ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
 08:43:35,152 
 [Lorg.apache.activemq.command.DataStructure; [thread: 
 SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: 
 org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: 
 com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
 borrowed this stack trace from). We have seen similar things in other 
 applications that tried to use ActiveMQ. I think this is a class cast error 
 in ActiveMQ...
 With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

2006-11-27 Thread Guy Pardon (JIRA) 
[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37568 ] 

Guy Pardon commented on AMQ-1054:
-


James,

Did you try with JDK 1.4.2? That is the one we used.

Guy






 XA recover fails for 4.0.1
 --

 Key: AMQ-1054
 URL: https://issues.apache.org/activemq/browse/AMQ-1054
 Project: ActiveMQ
  Issue Type: Bug
 Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
 for the JTA/XA part
Reporter: Guy Pardon

 XAResource.recover seems to fail for 4.x of ActiveMQ:
 ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
 08:43:35,152 
 [Lorg.apache.activemq.command.DataStructure; [thread: 
 SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: 
 org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: 
 com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
 borrowed this stack trace from). We have seen similar things in other 
 applications that tried to use ActiveMQ. I think this is a class cast error 
 in ActiveMQ...
 With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

2006-11-21 Thread Guy Pardon (JIRA) 
[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37510 ] 

Guy Pardon commented on AMQ-1054:
-

Yes, 4.0.2 too.

Below is a test program (you need the atomikos jars in the classpath, as well 
as all activemq jars). Note that the only atomikos dependency is the Xid format.

Guy

package activemqtest;

import javax.jms.MessageConsumer;
import javax.jms.XAConnection;
import javax.jms.XASession;
import javax.transaction.xa.XAResource;
import javax.transaction.xa.Xid;

import org.apache.activemq.ActiveMQXAConnectionFactory;
import org.apache.activemq.command.ActiveMQQueue;

import com.atomikos.datasource.xa.DefaultXidFactory;

public class XATest {


public static void main ( String[] args ) throws Exception {

String url = tcp://localhost:61616;
String qName = MyQueue;
int timeout = 5;

DefaultXidFactory xidFactory = new DefaultXidFactory();

ActiveMQXAConnectionFactory xacf = new 
ActiveMQXAConnectionFactory();
xacf.setBrokerURL ( url );

ActiveMQQueue queue = new ActiveMQQueue();
queue.setPhysicalName ( qName );

XAConnection xaconn = xacf.createXAConnection();
xaconn.start();
XASession session = xaconn.createXASession();
XAResource xares = session.getXAResource();
MessageConsumer receiver = session.getSession().createConsumer 
( queue );

xares.recover ( XAResource.TMSTARTRSCAN );
xares.recover ( XAResource.TMNOFLAGS );
xares.setTransactionTimeout ( timeout );
xares.isSameRM ( xares );

Xid xid = xidFactory.createXid ( part1 , part2);
xares.start ( xid , XAResource.TMNOFLAGS );
receiver.receive ( timeout );
xares.end ( xid , XAResource.TMSUCCESS );
xares.rollback ( xid );
}

}


 XA recover fails for 4.0.1
 --

 Key: AMQ-1054
 URL: https://issues.apache.org/activemq/browse/AMQ-1054
 Project: ActiveMQ
  Issue Type: Bug
 Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
 for the JTA/XA part
Reporter: Guy Pardon

 XAResource.recover seems to fail for 4.x of ActiveMQ:
 ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
 08:43:35,152 
 [Lorg.apache.activemq.command.DataStructure; [thread: 
 SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: 
 org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
 at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: 
 com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
 [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
 Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
 Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
 borrowed this stack trace from). We have seen similar things in other 
 applications that tried to use ActiveMQ. I think this is a class cast error 
 in ActiveMQ...
 With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1054) XA recover fails for 4.0.1

2006-11-16 Thread Guy Pardon (JIRA) 
XA recover fails for 4.0.1
--

 Key: AMQ-1054
 URL: https://issues.apache.org/activemq/browse/AMQ-1054
 Project: ActiveMQ
  Issue Type: Bug
 Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
for the JTA/XA part
Reporter: Guy Pardon


XAResource.recover seems to fail for 4.x of ActiveMQ:

ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
[Lorg.apache.activemq.command.DataStructure; [thread: 
SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
at: org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
[thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown Source) 
[thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
[thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
at: 
com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
[thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
[thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 

Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
borrowed this stack trace from). We have seen similar things in other 
applications that tried to use ActiveMQ. I think this is a class cast error in 
ActiveMQ...

With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira