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

Post 8.0 upgrade issues

Highlighted
Abhi_Agrawal
Regular Collector

Post 8.0 upgrade issues

Hi,

 

We have recently upgraded to PPM 8.0. We ahve not applied any service pack yet, but we have observed that after 8.0 upgrade; PPM server hangs after couple of hours and we have to bounce the server every time. We have also noticed that server logs are filling very fast (approx. 5-6 min).

This is our Sandbox environment with 1 application server. We refreshed database schema of Sandbox environment from Production environment which has 4 nodes (1 node is dedicated for PPM services).

Following exception messages continuously occurring in server log file: -

1. scheduler_Worker-1:org.quartz.core.ErrorLogger:2011/12/01-13:39:02.806 EST: Job (PPM_SERVICES._WORK_ITEM_PENDING_ASSIGNMENT_SERVICE threw an exception.

org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during

JMS processing; nested exception is org.jboss.mq.DestinationFullException: Maximum size 10000 exceeded for QUEUE.ppmLightServiceQueue]

at org.quartz.core.JobRunShell.run(JobRunShell.java:214)

at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

* Nested Exception (Underlying Cause) ---------------
org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is org.jboss.mq.DestinationFullException: Maximum size 10000 exceeded for QUEUE.ppmLightServiceQueue

2. Exception Correlation: GUID=A41531FE-42D8-915D-4A19-FBDC3313CB2B

Generated Time=2011/11/30-19:57:51.945 EST

Server Node Name: ppmsandbox.mhe.mhc

server:ppmLightServiceListenerContainer-2:SystemErr:2011/11/30-19:57:51.953 EST: at com.mercury.itg.pm.dao.WorkPlanDAO.getWorkPlanById(WorkPlanDAO.java:50)

 

Let me know if anyonce face this kind of issues or know the resolution.

Thanks in advance.

 

 

Regards,

Abhi

7 REPLIES
dirkf
Honored Contributor

Re: Post 8.0 upgrade issues

Hi Abhi,

 

you should make sure that all configurations that pointed to a cluster are removed and that kDeployStandalone.sh has been run etc. Check the documentation on that.

In addition you seem to show at least one pointer in the direction of Quartz-problems. SSO shows information about that and there is a fix available. I think tthat this is already fixed in 8.03 or 8.04, not sure.

 

Regarding the second issue, I would be expecting an indicator of what is causing the GUID exception ABOVE that GUID, so for instance something like this a line further up:

 

com.mercury.itg.exceptions.InfrastructureException: org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of com.mercury.itg.pm.model.WorkPlanImpl.workPlanSeq

 

However, this should be investigated by support.

All in all, it is highly advisable to install a later 8.0 Service Pack to solve known issues up front. I suggest going to 8.03 or 8.04, depending on your upgrade plan strategy.

 

Best regards,

Dirk

 

 

Abhi_Agrawal
Regular Collector

Re: Post 8.0 upgrade issues

Thanks Dirk! We will be applying SP3 service pack.
AlexSavencu
Honored Contributor

Re: Post 8.0 upgrade issues

Hi, Abhi,

 

just curious: why not upgrade to 8.04 or 9.12/9.13?

 

8.04 includes a ton of bug fixes and 9.1x introduces several new important features.

 

cheers

alex


--remember to kudos people who helped solve your problem
Abhi_Agrawal
Regular Collector

Re: Post 8.0 upgrade issues

We have applied SP3 service pack, but still getting these exceptions messages. Additionally, some more error exception messages are now appearing in the server logs.

Although, we have resolved 'Null value was assigned to a property of primitive type setter of com.mercury.itg.pm.model.WorkPlanImpl.workPlanSeq' issue by updating Active_Flag to 'No' for affected work plans. We were getting this error because these work plans were not exist any more in the system.
Abhi_Agrawal
Regular Collector

Re: Post 8.0 upgrade issues

Alex,

We cannot apply SP4 service pack because there is no upgrade path from PPM 8.0 SP4 to 9.12, so in future if we want to move to 9.12 then we cannot upgrade from SP4 hence we are not applying SP4 service pack.

--Abhi
Sascha_1
Member

Re: Post 8.0 upgrade issues

Hi,

 

in the past, HP published version 9.13. I think, this version will be compatible for an upgrade from prior release 8.04.

 

Regards,
Sascha

AlexSavencu
Honored Contributor

Re: Post 8.0 upgrade issues

Hi,

9.13 brings only enhancements in the document management area. As of now, there is no upgrade path from 8.04 to 9.13.

Cheers
Alex

--remember to kudos people who helped solve your problem
//Add this to "OnDomLoad" event