Notification Service Container

MAGE

Hello Guys,

since a created my a notification service for my organization HumanInteractions or Tasks get issues.

Maybe i miss something in my notification service configuration, please need your help to fix this problem. Find below the issue i have:

SOAP Fault from Notification Service while delivering Task/Info for the activity 'Approval' : SOAP Fault from Notification Service while delivering Task/Info for the activity '
Caused By :
com.eibus.soap.SOAPFault:
Fault Code: ns0:Server
Fault String: The "HumanInteraction" request did not process successfully because of "The transaction has been marked rollback only because the bean encountered a non-application exception :java.lang.NullPointerException : null".
Actor: cn=Notification Service SGN,cn=soap nodes,o=GIP,cn=cordys,cn=appworkinst,o=ddd.com
Detail: Cordys.Notification.Messages.exceptionEncounteredHumanInteractionThe transaction has been marked rollback only because the bean encountered a non-application exception :java.lang.NullPointerException : nulljavax.ejb.EJBTransactionRolledbackException: The transaction has been marked rollback only because the bean encountered a non-application exception :java.lang.NullPointerException : null
at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:422)
at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:353)

Thank in advance,

Shanti Vardhan

MAGE

There should be some other root cause for this. If you can provide complete stack trace, it would be easy to find it out.

Steps

1. Clean Application server log.
2. Reproduce the issue
3. Provide the log

MAGE

Hi @Shanti Vardhan

thanks for your inputs. find attached the full log, you have to remove out the .txt from the file name.

Application_Server.xml.txt

Shanti Vardhan

MAGE

The jdbc string for the DSO pointed by BPM and Notification service container along with Platform Service container which Entity runtime points in PGI organization should be exactly same as that of DSO of system service container including case sensitivity. Even the user name and passwords of the DSO configuration must be same as that of system. I believe there is some mismatch. Please correct them restart ToMee and check the scenario.

MAGE

Hi @Shanti Vardhan

it works now. Many thanks for your valuable inputs.