Multiple last resources have been added to the current transaction. This is transactionally unsafe a

[adi reddy]

I have two DataSource to be executed in EJB bean class.

the following is the my EJB class code:

@Stateless
public class AbcTimerBean implements AbcTimerLocal, AbcTimerRemote {
  @Resource
   javax.ejb.TimerService timerService;
 public void setTimerInterval(long pInterval) {
	timerService.createTimer(7000, 5000, "hello");
  }

  @Timeout
  public void handleCallback(Timer pTimer) {
       LookupDao lookupDAO = new LookupDao();
       String types = lookupDAO.getLookupValue();
       ImportDao importDAO = new ImportDao();
       importDAO.processData(types); 

  }
 public boolean cancelTimer(String pTimerId){
//some statements
}
public boolean cancelAllTimers(){
//some statements
}

}

The AbcTimerLocal is as follows:

@Local
public interface AbcTimerLocal {
	
	void setTimerInterval(long milliseconds);
	boolean cancelTimer(String pTimerId);
	boolean cancelAllTimers();

}

In some servelt i am calling the setTimerInterval() method, in this the timer is creating, so that every 5000 millisec the Time Out ( handleCallback(..)) will call. In the callback or time out method i am calling two different DAO's which are call two different DataSources and will execute some SQL statements.

while executing the second DAO method, i am getting the following WARN message in JBoss server.log

WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning] Multiple last resources have been added to the current transaction. This is transactionally unsafe and should not be relied upon. Current resource is org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@d38525

My question is , Why I am getting this WARM message and under waht situation will get this message?

[Jaikiran Pai]

See https://community.jboss.org/wiki/Multiple1PC

[adi reddy]

Thanks JaiKiran,

I ahve seen that link already and i have done some changes in time out method:

i have created one method inside my EJB class as follows:

@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
    public String getImportTypes(LookupDao lookupDAO) throws LookupDaoException {
        String importTypes = lookupDAO.getLookupValue();
         return importTypes;
   }

calling this method in the time out method

@Timeout  
  public void handleCallback(Timer pTimer) {  
       LookupDao lookupDAO = new LookupDao();  
       String types = getImportTypes(lookupDAO );  
       ImportDao importDAO = new ImportDao();  
       importDAO.processData(types);   
  
  }  

according to that thread which you posted, the method which annotated with @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) will execute its own transactional context.
But i dont know what wrong with above code, still I am getting WARN messages.
I have tried to call both DAO methods like above but no use...........

[Jaikiran Pai]

adi reddy wrote:
calling this method in the time out method

@Timeout  
  public void handleCallback(Timer pTimer) {  
       LookupDao lookupDAO = new LookupDao();  
       String types = getImportTypes(lookupDAO );  
       ImportDao importDAO = new ImportDao();  
       importDAO.processData(types);   
  
  }  

according to that thread which you posted, the method which annotated with @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) will execute its own transactional context.

You are just doing a plain Java call. So that won't work and won't create a new transaction. See this thread for more details https://community.jboss.org/message/525521#525521