This content has been marked as final.
Show 5 replies
-
1. Re: A performance problem with Seam
bulloncito May 16, 2007 6:10 PM (in response to moises_paula)my backing bean, was calling Transactions.isTransactionMarkedRollback(...), that was trying to lookup for a name (userTransactionName). On tomcat, where
there are no JNDI server started, I see a lot of javax.naming.CommunicationException in my logs.
... if there is a lookup, then there must be a jndi server started, otherwise transactionMakedRollback is probably useless -
2. Re: A performance problem with Seam
bgrossi May 17, 2007 9:47 AM (in response to moises_paula)"bulloncito" wrote:
my backing bean, was calling Transactions.isTransactionMarkedRollback(...), that was trying to lookup for a name (userTransactionName). On tomcat, where
there are no JNDI server started, I see a lot of javax.naming.CommunicationException in my logs.
... if there is a lookup, then there must be a jndi server started, otherwise transactionMakedRollback is probably useless
The Moises' problem was that the lookup and seam's transaction management IS "useless", and it's degrading performance considerably. We need an option to disable that (and other) features/interceptors... Now we have hardcoded in Component.initDefaultInterceptors():
if ( getScope()==CONVERSATION )
{
addInterceptor( new Interceptor( new ManagedEntityIdentityInterceptor(), this ) );
}
and in ManagedEntityIdentityInterceptor.aroundInvoke(..) we have:
...
finally
{
if ( !PassivatedEntity.isTransactionMarkedRollback() )
{
entityRefsToIds(ctx);
}
}
That code (PassivatedEntity.isTransactionMarkedRollback()) was trying to lookup jndi, and returning false if it's fail... (the function is correct, but causes an try to open an socket!)
Bruno E. Grossi -
3. Re: A performance problem with Seam
bulloncito May 17, 2007 12:11 PM (in response to moises_paula)... the problem is calling a Transaction from JNDI when there's not even a JNDI server, there will be no such managed transactions, maybe some configuration in persistence.xml to disable such transactions, maybe disabling JTA or something like that.
-
4. Re: A performance problem with Seam
lowecg2004 Jun 1, 2007 7:31 AM (in response to moises_paula)Another angle on this... Do you have DOCTYPE defined for your pages.xml files?
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=109896 -
5. Re: A performance problem with Seam
lowecg2004 Jun 1, 2007 7:50 AM (in response to moises_paula)sorry, meant to say "another angle on why you might be getting a performance degradation after migrating".
my post is nothing to do with interceptors/JDNI etc.