Hi,

We are running IS 6.1 , and using JDBC Adapter version 6.0.3. We created a polling notification for oracle. The notification is getting disabled by itself after every 8 hours(approximatley), after every 8 hours we need to enable this polling notification. Please advise me on, wht the problem could, or let me know if there are any fixes provided to resolve this. Below is the list of updates applied on our IS 6.1.

IS_6-1_FP2_Fix7
IS_6-1_FP2_Fix2
IS_6-1_FP2_Fix1
IS_6-1_FP2
IS_6-1_SP1
TNS_6-1_Fix15
TNS_6-1_Fix6
TNS_6-1_Fix2

Regards,

Srinivas Kotturi.

Can you attach the error logs? Are you shutting down database server every 8 hours?

Sagar

Hi Sagar,

We are not shutting down the database server. Its up & running 24X7. And other point i forgot to mention is we have 2 IS servers clustered. Here goes the Error log.

2006-04-26 04:29:05 CAT [ART.116.3114] Adapter Runtime (Notification): Illegal state in clustered notification coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3. Notification will be shut down. Stack trace data … 6eca75b0d4cc11da9aeba94b66db11ac NULL 6eca75b0d4cc11da9aeba94b66db11ac
2006-04-26 04:29:02 CAT [ART.116.3110] Adapter Runtime (Notification): Error attempting to release repository resource for cluster coordination of notification coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3. Error: com.wm.app.repo.RepositoryNoLockException: com.wm.util.queue.ValuesHashNoLockException: [ISC.0066.9202] No Share or Exclusive lock for key: coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3 com.wm.util.queue.ValuesHashNoLockException: [ISC.0066.9202] No Share or Exclusive lock for key: coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3 Stack trace data … 6d139df0d4cc11da9ae7a94b66db11ac NULL 6d139df0d4cc11da9ae7a94b66db11ac
2006-04-26 04:29:02 CAT [ART.116.3109] Adapter Runtime (Notification): Error attempting to secure repository resources for cluster coordination of notification coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3. Error: com.wm.pkg.art.error.DetailedException: [ART.116.3110] Adapter Runtime (Notification): Error attempting to release repository resource for cluster coordination of notification coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3. Error: com.wm.app.repo.RepositoryNoLockException: com.wm.util.queue.ValuesHashNoLockException: [ISC.0066.9202] No Share or Exclusive lock for key: coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3 com.wm.util.queue.ValuesHashNoLockException: [ISC.0066.9202] No Share or Exclusive lock for key: coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3 [ART.116.3110] Adapter Runtime (Notification): Error attempting to release repository resource for cluster coordination of notification coredata.migration.commodity_core.notification:CDM_INSERT Stack trace data … 6d139df0d4cc11da9ae9a94b66db11ac NULL 6d139df0d4cc11da9ae9a94b66db11ac
2006-04-26 04:29:02 CAT com.wm.util.queue.ValuesHashNoLockException: [ISC.0066.9202] No Share or Exclusive lock for key: coredata.migration.commodity_core.notification:CDM_INSERT_NOTIFY3 Stack trace data … 6d115400d4cc11da9ae5a94b66db11ac NULL 6d115400d4cc11da9ae5a94b66db11ac

Regards,
Srinivas Kotturi.

Please note that you cann’t use polling notification in cluster environment. See the user guide (line #48) for details. User guide says

JDBC Adapter Notifications Not Supported in Clusters
JDBC Adapter notifications are not supported in Integration Server clusters. Only a single instance of a given notification can be enabled at a time. If you run multiple instances of the same notification, message ordering and message duplication problems can occur.

Hi Sagar,

I am aware that we cannot use polling notifications in cluster, that is why we are enabling the polling notification on only one IS server, and we are keeping it disabled on the other IS server. Even though the notification is getting disabled.

Regards,
Srinivas Kotturi.