While creating a Adapter Notification it’s throwing an error.
"[ISS.0085.9055] Node AZainulTraining.adapters.adapterNotif.noTrans:insertNotif_NoTransactionPublishDocument does not exist

[ISS.0085.9055] Node AZainulTraining.adapters.adapterNotif.noTrans:insertNotif_NoTransactionPublishDocument does not exist

com.wm.app.b2b.server.ServiceException: [ISS.0085.9055] Node AZainulTraining.adapters.adapterNotif.noTrans:insertNotif_NoTransactionPublishDocument does not exist
at wm.server.nsimpl.deleteNode(nsimpl.java:2434)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:411)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:739)
at wm.bci.internal.BciServiceInvokeNotifier.process(BciServiceInvokeNotifier.java:32)
at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:360)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:334)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:611)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:423)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:127)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:163)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:223)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:430)
at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
at java.lang.Thread.run(Thread.java:748)
."

Hi Zainul,

can you provide some more details about your use case, please?

Which Adapter (JDBC, SAP, MQ, …) is this related to?

Please note that notifications require a transactional connection pool, ideally a LOCAL_TRANSACTION one.
Connections with NO_TRANSACTION cannot be used for notifications.

Regards,
Holger

I’m creating a notification of “JDBC Adapter Type”

Giving an error with LOCAL_TRANSACTION too

[ISS.0085.9055] Node AZainulTraining.adapters.adapterNotification.localTrans:insertNotification_Persons_LocTransactionPublishDocument does not exist

[ISS.0085.9055] Node AZainulTraining.adapters.adapterNotification.localTrans:insertNotification_Persons_LocTransactionPublishDocument does not exist

com.wm.app.b2b.server.ServiceException: [ISS.0085.9055] Node AZainulTraining.adapters.adapterNotification.localTrans:insertNotification_Persons_LocTransactionPublishDocument does not exist
at wm.server.nsimpl.deleteNode(nsimpl.java:2434)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:411)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:739)
at wm.bci.internal.BciServiceInvokeNotifier.process(BciServiceInvokeNotifier.java:32)
at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:360)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:334)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:611)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:423)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:127)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:163)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:223)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:430)
at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
at java.lang.Thread.run(Thread.java:748)

Hi Zainul,

please share a screeenshot of your package/folder structure where you try to create the notification.
During creation there should be no need to invoke deleteNode service.
Is looking weird to me.

Regards,
Holger

also getting an error in ‘polling notification’

[ART.116.3020] Adapter Runtime (Notification): Unable to get list of notification types supported by node JDBCAdapter.
java.sql.SQLSyntaxErrorException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00904: “LAST_UPDATED”: invalid identifier

Hi Zainul,

which version of JDBC Adapter are you using?
Are the latest fixes for it applied to your environment?

Regards.
Holger

Reload WmART and WmJDBC packages
Reload the notification package
If possible recreate the notification
Check if the jar is compatible to the DB version that you are using otherwise refresh and restart the server.