Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow Notification sending On and Off

Highlighted
cat_gon0208
Super Collector

Workflow Notification sending On and Off

Hi All,

 

On 15 July, we have upgraded from 7.5 to 9.12, after which we have encountered an issue where the workflow notification is sending on and off for one workflow and totally no email sent out for the other workflow, while the other workflow is sending notification just fine.

 

We have checked the serverlog and we have found some notification related error hours after the upgrade, but then it only appeared once in the serverlog that's why we cannot pinpoint if this could be the cause of the issue.

 

Appreciate any inputs that you can provide.

 

ERROR JSESSIONID=0FC772A3E2AFF794993DC95E3F345667.TREBLE,USERNAME=admin server:TP-Processor2:com.kintana.web:2012/07/15-13:46:16.375 SGT: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=DD5CB924-3604-637C-8252-C29891AEF3B8
nested detail:DB Package error:

ORA-00001: unique constraint (PPM_OSCARB.KNTA_NOTIFICATIONS_NLS_PK) violated
ORA-06512: at "PPM_OSCARB.KNTA_NOTIFICATIONS_TRIG", line 11
ORA-04088: error during execution of trigger 'PPM_OSCARB.KNTA_NOTIFICATIONS_TRIG' {KNTA_NOTIFICATIONS_TH-302} (KNTA-10498)

 

An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=DD5CB924-3604-637C-8252-C29891AEF3B8
at com.kintana.core.util.AgentUtils.runCallableStatement(AgentUtils.java:1739)
at com.kintana.core.util.AgentUtils.runCallableStatement(AgentUtils.java:1562)
at com.kintana.core.util.AgentUtils.runCallableStatement(AgentUtils.java:1527)
at com.kintana.core.server.NotificationAgent.saveNotification(NotificationAgent.java:558)
at com.kintana.core.server.NotificationAgent.saveNotificationPacket(NotificationAgent.java:483)
at com.kintana.core.server.NotificationAgent.saveNotificationsForConditionValue(NotificationAgent.java:359)
at com.kintana.rpt.server.ReportSubmissionDBAdapterImpl.save(ReportSubmissionDBAdapterImpl.java:160)
at com.kintana.core.arch.DBAdapter.saveWrapper(DBAdapter.java:138)
at com.kintana.core.arch.Home.save(Home.java:148)
at com.kintana.rpt.web.ctrl.ReportDetailsController.processAction(ReportDetailsController.java:195)
at com.kintana.rpt.web.ctrl.ReportDetailsController.initialize(ReportDetailsController.java:140)
at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:86)
at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:88)
at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:111)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:145)
at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:80)
at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:108)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:861)
at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1378)
at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:40)
at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:51)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.PerformanceFilter.applyFilter(PerformanceFilter.java:57)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)

12 REPLIES
Erik Cole
Honored Contributor

Re: Workflow Notification sending On and Off

Just a thought...you might make sure all your triggers are still valid...

 

select object_name,status
from user_objects
where object_type = 'TRIGGER'

 

cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

Hi Erik,

 

Thanks for your attention.

 

All triggers are VALID.

 

Is there any possible reasons for this?

 

Thanks.

 

Catherine

cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

Hi Erik,

 

Thanks for your attention.

 

All triggers are VALID.

 

Is there any possible reasons for this behaviour?

 

Thanks.

 

Catherine

Raj Ghimire
Occasional Visitor

Re: Workflow Notification sending On and Off

Is this only happening in one instance ?

If so, Have you tried Refreshing the affected Workflows from Test instance? The PPM WF Migration process often re-validates important components of the workflow and that could help resolve your issue. I would suggest to give it a try once, if you haven't already.

Thanks.

-Raj

Jim Esler
Honored Contributor

Re: Workflow Notification sending On and Off

You can try deleting and rebuilding the notifications on the workflow having problems. We have seen issues like this in 9.1 when recipient entries on a notification were edited rather than deleted and recreated. Usually, though, the problem is seen during migration, not during execution.

cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

Hi Guys,

 

This is still an issue in our organization right now.

 

It has been 2 weeks since we had this and still unable to resolve.

 

I would like to give you guys more background and see whether this ever happened to you.

 

1. Before our upgrade from 7.5 to 9.12, email notification is working as expected. Workflow notification is sent and received accordingly.

 

2. We did an upgrade on July 15, on the same day that the upgrade was completed and successful we had some enhancement to different objects, part of the enhancement we did was the insertion of a row in the KNTA_NOTIFICATIONS_NLS for some custom reports, we are not sure if this could have caused the issue.

 

3. On July 16, day after the upgrade we have noticed a weird behaviour in the workflow email notification where an email is sent on and off. There will be a time that an email will be fired in a particular execution step but then after an hour that same execution step will not send an email. Another strange thing is that the email notification is not even written in the NOTIFICATIONS table eg, KNTA_NOTIF_TXN_PARENTS

 

4. We had an error in the serverlog few hours after the upgrade about the trigger -- which I have pasted in this thread, but then when we checked our triggers all are valid

 

We will appreciate any inputs, troubleshooting suggestions that you can provide us. It is affecting us very bad.

 

Thanks.

 

Catherine

Jim Esler
Honored Contributor

Re: Workflow Notification sending On and Off

On the Setup tab for the notification, is the box for "Don't send if obsolete" checked? If more than one path is active in the workflow, a notification is considered obsolete if another step also becomes eligible before the notification for this step is generated. We have seen this suppress notifications for Eligible events.

cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

hi jim, however, the email is sent intermittently. if there is an obsolete email notif will it ave this behaviour?
Jim Esler
Honored Contributor

Re: Workflow Notification sending On and Off

This can be a race condition between the workflow and the Notification Service. If another step becomes eligible before the Notification Service generates the notification, it can be suppressed. Note that if your workflow does not have multiple paths active concurrently, this is not the issue. If this could be your problem, clear the checkbox on the notification that is not being sent reliably and see if the problem goes away.

cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

Hi All,

 

This is still an issue in our organization.

 

Can anyone advise us on what to do next please?

 

Thanks.

 

Catherine

AlexSavencu
Honored Contributor

Re: Workflow Notification sending On and Off

Hi,

 

to me it looks like there is an issue with the sequence of the NOTIF_TXN_PARENTS table. I would check the values in the table against the current value of the sequence, and if this is the case, I would increase the sequence to a larger value.

 

cheers

alex


--remember to kudos people who helped solve your problem
cat_gon0208
Super Collector

Re: Workflow Notification sending On and Off

Hi Alex,

 

This is the first thing that R&D asked us to check. they have provided us a query to check on all the table sequence but everything is ok.

 

Additional info, if a notification is not sent out we also cannot find a record in the notif _txn_parents table

 

strangely that if notif is sent there is a record if not sent no record in the table

 

thanks

//Add this to "OnDomLoad" event