Orbeon Forms community mailing list

Tamino Transaction

Classic

List

Threaded

4 messages Options

Ryan Puddephatt

Tamino Transaction

Hi all,

I'm looking to create a custom processor for the Tamino Transactions, I need to update around 7000 records in a Tamino DB, but currently the transaction will timeout after around 1000 records, and if there are any errors in the whole process will be roles back. I would like to be able to do an update and then close the tamino transaction, either with a seperate processor or an option on the current one.

Does anyone know how the transaction to Tamino is held open between processors and how I would access it from a seperate processor?

Thanks

Ryan

Ryan Puddephatt
Software Engineer

Teleflex Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotland
EH54 7DP

e> [hidden email]
t> +44(0)1506 407 110
f> +44(0)1506 407 108
w> www.teleflex.com

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Claudio Delgado

RE: Tamino Transaction

Hi.

Reading the code of the TaminoProcessor you can find this:

public void contextDestroyed(boolean success) {

try {

if (success) {

if(logger.isInfoEnabled())

logger.info("Committing Tamino transaction");

transaction.commit();

} else {

if(logger.isInfoEnabled())

logger.info("Rolling back Tamino transaction");

transaction.rollback();

}

It means when the pipe ends all Tamino operations executed by a TaminoProcessor are commited if the pipe ends without problems (please correct me if I’m wrong).

I don’t know if OPS’ Tamino Processor supports manual configuration to open the connection in AutoCommit mode, connection.Open(TaminoConnectionMode.AutoCommit);, but reading the code I think it could not be configured in OPS properties file.

You could write your custom processor to call the Tamino API and set the connection in AutoCommit mode, you also can perform X-Machine commands to manage the transaction SessionID and SessionKey to work in different Pipes and processors.

Hope it helps, why does the transaction crash after 1000 records?

Regards,

Claudio Delgado

Software AG Factory

Valparaiso - Chile

De: Ryan Puddephatt [mailto:[hidden email]]
Enviado el: viernes, 14 de julio de 2006 9:58
Para: [hidden email]
Asunto: [ops-users] Tamino Transaction

Hi all,

Does anyone know how the transaction to Tamino is held open between processors and how I would access it from a seperate processor?

Thanks

Ryan

Ryan Puddephatt
Software Engineer

Teleflex Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotland
EH54 7DP

e> [hidden email]
t> +44(0)1506 407 110
f> +44(0)1506 407 108
w> www.teleflex.com

Ryan Puddephatt

RE: Tamino Transaction

Hi Claudio,

Checking the code I noticed that, but when running the XPL the "Rollback"/"Committed" message comes when the XPL finishes even if there are several calls to Tamino, hence the thought that the transaction is carried over somehow.

I'll look into the auto commit property, I might be able to build it into the current processor as an extra configuration option. Currently it fails after 1000 records (roughly) because the connection times out, and then roles back.

I'll let you know how I get on

Ryan

From: Claudio Delgado [mailto:[hidden email]]
Sent: 14 July 2006 17:44
To: [hidden email]
Subject: RE: [ops-users] Tamino Transaction

Hi.

Reading the code of the TaminoProcessor you can find this:

public void contextDestroyed(boolean success) {

try {

if (success) {

if(logger.isInfoEnabled())

logger.info("Committing Tamino transaction");

transaction.commit();

} else {

if(logger.isInfoEnabled())

logger.info("Rolling back Tamino transaction");

transaction.rollback();

}

It means when the pipe ends all Tamino operations executed by a TaminoProcessor are commited if the pipe ends without problems (please correct me if I’m wrong).

I don’t know if OPS’ Tamino Processor supports manual configuration to open the connection in AutoCommit mode, connection.Open(TaminoConnectionMode.AutoCommit);, but reading the code I think it could not be configured in OPS properties file.

You could write your custom processor to call the Tamino API and set the connection in AutoCommit mode, you also can perform X-Machine commands to manage the transaction SessionID and SessionKey to work in different Pipes and processors.

Hope it helps, why does the transaction crash after 1000 records?

Regards,

Claudio Delgado

Software AG Factory

Valparaiso - Chile

De: Ryan Puddephatt [mailto:[hidden email]]
Enviado el: viernes, 14 de julio de 2006 9:58
Para: [hidden email]
Asunto: [ops-users] Tamino Transaction

Hi all,

Does anyone know how the transaction to Tamino is held open between processors and how I would access it from a seperate processor?

Thanks

Ryan

Ryan Puddephatt

RE: Tamino Transaction

Claudio,

I've searched the code and found the context item receiving and setting the transaction so it can be shared across the context of the XPL, I think I can make a tamino-force-commit processor that litterally does what it says on the tin! So I'll do that so I can do a force a commit when I need to

Thanks for your help

Ryan

From: Ryan Puddephatt [mailto:[hidden email]]
Sent: 14 July 2006 21:40
To: [hidden email]
Subject: RE: [ops-users] Tamino Transaction

Hi Claudio,

I'll let you know how I get on

Ryan

From: Claudio Delgado [mailto:[hidden email]]
Sent: 14 July 2006 17:44
To: [hidden email]
Subject: RE: [ops-users] Tamino Transaction

Hi.

Reading the code of the TaminoProcessor you can find this:

public void contextDestroyed(boolean success) {

try {

if (success) {

if(logger.isInfoEnabled())

logger.info("Committing Tamino transaction");

transaction.commit();

} else {

if(logger.isInfoEnabled())

logger.info("Rolling back Tamino transaction");

transaction.rollback();

}

It means when the pipe ends all Tamino operations executed by a TaminoProcessor are commited if the pipe ends without problems (please correct me if I’m wrong).

I don’t know if OPS’ Tamino Processor supports manual configuration to open the connection in AutoCommit mode, connection.Open(TaminoConnectionMode.AutoCommit);, but reading the code I think it could not be configured in OPS properties file.

You could write your custom processor to call the Tamino API and set the connection in AutoCommit mode, you also can perform X-Machine commands to manage the transaction SessionID and SessionKey to work in different Pipes and processors.

Hope it helps, why does the transaction crash after 1000 records?

Regards,

Claudio Delgado

Software AG Factory

Valparaiso - Chile

De: Ryan Puddephatt [mailto:[hidden email]]
Enviado el: viernes, 14 de julio de 2006 9:58
Para: [hidden email]
Asunto: [ops-users] Tamino Transaction

Hi all,

Does anyone know how the transaction to Tamino is held open between processors and how I would access it from a seperate processor?

Thanks

Ryan