Re: [JBoss-dev] TransactionInterceptor in HEAD

2003-01-14 Thread David Jencks
We need to talk about this...

If the client is standalone and using UserTx, then all the calls in one 
tx MUST go to the same jboss server, since the client tm doesn't 
handle 2pc distributed tx or much of anything-- just committing one 
branch.  In other words, you probably shouldn't be using UT on the 
client with clustering at the moment.  Is there some way to make this 
sticky?  If the server fails, I guess an exception should be thrown on 
the client and the client should know enough to start the tx over??

If the client is a jboss instance, then this should be looking for the 
real jboss tm on that server.  This is not yet implemented as I recall.

Comments?

thanks
david jencks



On Monday, January 13, 2003, at 10:49 AM, Sacha Labourey wrote:

Hello,

The code for TransactionInterceptor (client side) in HEAD does this at 
one
point (in the invoke):

	transactionManagerServiceName =
	  new ObjectName (DEFAULT_CLIENT_TM_NAME_STUB) +
	invoker.getServerID().toObjectNameClause());

In the standard scenario, that is fine, but in the clustering case, 
what do
you expect invoker.getServerID() will return? This is problematic 
because
when the invocation goes through the interceptor, we still cannot say 
which
will be the target server (it is elected in the ... invoker itself!

Cheers,


sacha



---
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development




---
This SF.NET email is sponsored by: Take your first step towards giving 
your online business a competitive advantage. Test-drive a Thawte SSL 
certificate - our easy online guide will show you how. Click here to get 
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] TransactionInterceptor in HEAD

2003-01-13 Thread Sacha Labourey
Hello,

The code for TransactionInterceptor (client side) in HEAD does this at one
point (in the invoke):

transactionManagerServiceName =
  new ObjectName (DEFAULT_CLIENT_TM_NAME_STUB) +
invoker.getServerID().toObjectNameClause());

In the standard scenario, that is fine, but in the clustering case, what do
you expect invoker.getServerID() will return? This is problematic because
when the invocation goes through the interceptor, we still cannot say which
will be the target server (it is elected in the ... invoker itself!

Cheers,


sacha



---
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development