See Thread at: http://www.techienuggets.com/Detail?tx=14429 Posted on behalf of 
a User

Have u got any solution to that problem. I am having the same problem.
Omair

In Response To: 

Hello,

i wrote a simple stateless bean to test the TimerService. i am using jboss 
4.2.0GA

Whenerver i initialize the time i run into the following exception:


2007-10-02 14:56:55,437 ERROR [org.jboss.ejb.txtimer.TimerServiceImpl] Cannot 
create txtimer
  | java.lang.IllegalStateException: Unable to persist timer
  |     at 
org.jboss.ejb.txtimer.DatabasePersistencePolicy.insertTimer(DatabasePersistencePolicy.java:124)
  |     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |     at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  |     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  |     at java.lang.reflect.Method.invoke(Method.java:585)
  |     at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
  | ...
  | ...
  |     at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
  |     at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
  |     at 
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
  |     at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  |     at java.lang.Thread.run(Thread.java:595)
  | Caused by: org.jboss.util.NestedSQLException: Could not enlist in 
transaction on entering meta-aware object!; - nested throwable: 
(javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist 
resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 
-3f57fdff:555:47023fba:53 status: ActionStatus.ABORT_ONLY >); - nested 
throwable: (org.jboss.resource.JBossResourceException: Could not enlist in 
transaction on entering meta-aware object!; - nested throwable: 
(javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist 
resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 
-3f57fdff:555:47023fba:53 status: ActionStatus.ABORT_ONLY >))
  |     at 
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:94)
  |     at 
org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.insertTimer(GeneralPurposeDatabasePersistencePlugin.java:199)
  |     at 
org.jboss.ejb.txtimer.DatabasePersistencePolicy.insertTimer(DatabasePersistencePolicy.java:120)
  |     ... 317 more
  | Caused by: org.jboss.resource.JBossResourceException: Could not enlist in 
transaction on entering meta-aware object!; - nested throwable: 
(javax.transaction.SystemException: java.lang.Throwable: Unabled to enlist 
resource, see the previous warnings. tx=TransactionImple < ac, BasicAction: 
-3f57fdff:555:47023fba:53 status: ActionStatus.ABORT_ONLY >)
  |     at 
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:343)
  |     at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:518)
  |     at 
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:399)
  |     at 
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
  |     at 
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
  |     ... 319 more
  | Caused by: javax.transaction.SystemException: java.lang.Throwable: Unabled 
to enlist resource, see the previous warnings. tx=TransactionImple < ac, 
BasicAction: -3f57fdff:555:47023fba:53 status: ActionStatus.ABORT_ONLY >
  |     at 
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TransactionSynchronization.checkEnlisted(TxConnectionManager.java:744)
  |     at 
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enlist(TxConnectionManager.java:577)
  |     at 
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:337)
  |     ... 323 mor

I googled a bit and found some issues. Now I still dont know what to do. Do  i 
need to configure the TimerService with my database (MySQL)? I think for me its 
not neccessary to persist the status. Its enough for me if the timer is 
executed as long as the application is running.

Any hints would be great.

regards,
hasc


_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to