Hello guys,
I have been getting this error on all the JDBC polling notifications, even though the services related to this notifications are working, I opened a SR with technical services it didn’t helped, so I was wondering, any of you guys had experienced this error and have the solution. Any help is greatly appreciated.
The error is as follows,
>>>BasicData:message=null,date=Tue Jan 25 16:20:40 CST 2005,stack=
com.wm.pkg.art.error.DetailedException: [ART.116.3011] Adapter Runtime (Notification): Existing transaction rolled back before execution of Scheduler.Adapters:Scheduler_SrcMW_NB.
at com.wm.adk.notification.WmNotification.makeDetailedException(WmNotification.java:813)
at com.wm.adk.notification.WmNotification.checkTransaction(WmNotification.java:388)
at com.wm.adk.notification.WmPollingNotification.execute(WmPollingNotification.java:88)
at com.wm.pkg.art.scheduler.NotificationData.run(NotificationData.java:321)
at com.wm.pkg.art.scheduler.ClusteredNotificationData.run(ClusteredNotificationData.java:221)
at com.wm.util.CronJob.run(CronJob.java:490)
at com.wm.pkg.art.scheduler.ClusterCronJob.run(ClusterCronJob.java:116)
at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
at java.lang.Thread.run(Thread.java:534)
,errorCode=116.3011,errorMessageArgs=[0]Scheduler.Adapters:Scheduler_SrcMW_NB,errorResourceBundleName=com.wm.pkg.art.i18n.resources.AdapterRuntimeResourceBundle,detail=null<<<
Thanks in advance,
mkbhaseeb
I’m getting the same error:
ART.116.3011] Adapter Runtime (Notification): Existing transaction rolled back before execution of …
Did you find out what caused it?
I’m using WM 7.1 Suite
Thanks
It looks like your service is taking longer time than the transaction timeout. If the execution of a transaction takes longer than the transaction timeout interval, all
transacted operations are rolled back.
There are few work a rounds:
- Increase the time of “watt.art.tmgr.timeout=TransactionTimeout” in server.cnf file.
- Use “pub.art.transaction:setTransactionTimeout” to override the transaction timeout.This service only overrides the transaction timeout interval for the flow service in which you call it.
Hi,
The IS Extended Settings already have set the following:
watt.art.tmgr.timeout=-1
Which I believe means to wait unlimited time for the transaction to complete.
Also, I’m using an LOCAL_TRANSACTION (implicit transaction) in the Adapter Notification that is giving the error.
Do I need to override the Timeout “pub.art.transaction:setTransactionTimeout”?, if I have set the “watt.art.tmgr.timeout” to “-1”.
What else can be causing the error?
StackTrace à
com.wm.pkg.art.error.DetailedException: [ART.116.3011] Adapter Runtime (Notification): Existing transaction rolled back before execution of mpAudatex.notificacion:notInsertAudatex.
com.wm.pkg.art.error.DetailedException: [ART.116.3011] Adapter Runtime (Notification): Existing transaction rolled back before execution of mpAudatex.notificacion:notInsertAudatex.
at com.wm.adk.notification.WmNotification.makeDetailedException(WmNotification.java:1065)
at com.wm.adk.notification.WmNotification.checkTransaction(WmNotification.java:528)
at com.wm.adk.notification.WmPollingNotification.execute(WmPollingNotification.java:148)
at com.wm.pkg.art.scheduler.NotificationData.run(NotificationData.java:537)
at com.wm.util.CronJob.run(CronJob.java:497)
at com.wm.util.pool.PooledThread.run(PooledThread.java:118)
at java.lang.Thread.run(Thread.java:595)
,errorCode=116.3011,errorMessageArgs=[0]mpAudatex.notificacion:notInsertAudatex,errorResourceBundleName=com.wm.pkg.art.i18n.resources.AdapterRuntimeResourceBundle,detail=null<<<
You might be getting an error from database while inserting the record which is causing the rollback. Find out if there is a time limit on database side per transaction.
Changing to the recommended jdbc jars for my database did the trick.
Thanks
It wasn’t the jdbc drivers; it started to do it again… It seems to improve every time the Integration Server is restarted.
Ideas?