I m getting this error when I m trying to enable JDBC Pooling Notifications for Packages.[ART.116.3038] Adapter Runtime (Notification): Error in Notification Callback:enableCallback notification packagename.adapterServices:InsertNotification.[ADA.1.114] The database objects for “packagename.adapterServices:process_InsertNotification” notification already exist. You can delete the objects and try enabling the notification again. To delete the existing database objects use the “pub.pollingNotificationUtils:dropDatabaseObjects” service.
I’m also getting this - I think it’s when IS stops working (e.g. has to be restarted) and the adapter notification doesn’t recover 100%, but I’m not sure.
Yes, that’s the manual remedy for it; that’s what we’ve been doing. I’m wondering why it does this in the first place, and why it doesn’t auto-recover.
I don’t know why it’d be different? Looks the same to me:
[ART.116.3038] Adapter Runtime (Notification): Error in Notification Callback:enableCallback notification PackageName.folderName:notificationName.
[ADA.1.114] The database objects for “PackageName.folderName:notificationName” notification already exist. You can delete the objects and try enabling the notification again. To delete the existing database objects use the “pub.pollingNotificationUtils:dropDatabaseObjects” service.
Based on the error did you try to delete the objects via pub.pollingNotificationUtils:dropDatabaseObjects (make sure you disable the notification first and re-enable it after deleting the objects) and it should start enable fine…
Have you tried this yet or any more issues your are seeing?