Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..
67 views

SpyJMSException

Hi

 

Someone that seen below behaviour?

Our nodes are going down from time to time

Below are the errors that we see in the service node:

 

We have case at HP, we figuring it might be portconflicts for some reason.

 

My text in red

 

Below from service node

Service node restarted at 09:32 (Ready)

Throws errors about services, JMS

ERROR :scheduler_Worker-24:com.mercury.itg.core.scheduler:2014/06/19-09:42:20.581 CEST: Could not send service message for job (_NOTIFICATION_SERVICE_0_0) because org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.io.EOFException)

ERROR :scheduler_Worker-2:com.mercury.itg.core.scheduler:2014/06/19-09:42:20.581 CEST: Could not send service message for job (_WORK_ITEM_PENDING_ASSIGNMENT_SERVICE_0_0) because org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.io.EOFException)

 

Suddenly at 9:43 It starts HASingleton and deploying JMS producer...? At this time we loose usr node 1 (09:42:16)

STATUS server:AsynchViewChangeHandler Thread:com.mercury.itg.core.jms.service:2014/06/19-09:43:05.643 CEST: Starting HASingleton...

STATUS server:AsynchViewChangeHandler Thread:com.mercury.itg.core.jms.service:2014/06/19-09:43:05.643 CEST: Deploying JMS producer...

STATUS server:AsynchViewChangeHandler Thread:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2014/06/19-09:43:05.893 CEST: Starting web context: jbossmq-httpil

STATUS server:AsynchViewChangeHandler Thread:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2014/06/19-09:43:05.955 CEST: Completed start of web context: jbossmq-httpil

STATUS server:AsynchViewChangeHandler Thread:com.mercury.itg.core.jms.service:2014/06/19-09:43:06.236 CEST: Deployed JMS producer

STATUS server:Incoming-1,PRD_MC_CL,10.32.8.111:4694:com.kintana.core.server.cluster.MulticastAgent:2014/06/19-09:43:14.080 CEST: MulticastAgent[channelName - cache]:Mmember at10.32.8.111:3695 left group PRD_MC_CL

STATUS server:Incoming-2,PRD_MC_CL,10.32.8.111:4697:com.kintana.core.server.cluster.MulticastAgent:2014/06/19-09:43:15.127 CEST: MulticastAgent[channelName - integrity]:Mmember at10.32.8.111:3698 left group PRD_MC_CL

Jobs starting to run properly...:

STATUS server:ppmLightServiceListenerContainer-9:com.kintana.core.scheduler:2014/06/19-09:52:11.894 CEST: These tasks are executed on: Thu Jun 19 09:52:11 CEST 2014

nextTime = null

                             SCHEDULED_TASK_ID              WORKER_CLASS                                                                                                                                             SCHEDULED_TIME                                                  TASK_DATA_ID                           GROUP_ID                             SCHEDULED_TASK_RECUR_ID

                             93099                                                                           com.kintana.wf.server.WFIntExecutionExecuteWorkerThread                             2014-06-19 09:52:09.0               984112                                            null                                                   null

 

STATUS server:ppmLightServiceListenerContainer-9:com.kintana.core.scheduler:2014/06/19-09:59:11.915 CEST: These tasks are executed on: Thu Jun 19 09:59:11 CEST 2014

nextTime = null

                             SCHEDULED_TASK_ID              WORKER_CLASS                                                                                                                                             SCHEDULED_TIME                                                  TASK_DATA_ID                           GROUP_ID                             SCHEDULED_TASK_RECUR_ID

                             93100                                                                           com.kintana.wf.server.WFIntExecutionExecuteWorkerThread                             2014-06-19 09:58:53.0               984124                                            null                                                   null

 

We have cleaned QUARTZ-tables

0 Likes
4 Replies
CGut Absent Member.
Absent Member.

Re: SpyJMSException


Hi,
I was making some research in the knowledge base and I found a similar issue:
Usually see this kind of issued caused by either a landing page overloaded with portlets or by cached files issues.

Could you try the following?:

1. Stop PPM server.
2. Delete work & tmp folders from PPM_HOME/server/SERVER_NAME
(repeat for all nodes)
3. From the command prompt under PPM_HOME/bin run: sh
kJSPCompiler.sh
4. Re-start PPM server
5. From the command prompt under PPM_HOME/bin run: sh
kRunCacheManager.sh
6. Clean browser and java cache.

I suggest restarting primary node first since ‘It's make sense to start primary service node then start other nodes. The primary service node should setup backgroud service quarz in advance’.

Hope it helps.

Best regards,
Carolina.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..

Re: SpyJMSException

Thanks for your time. We have already tried that one unfortunately.

0 Likes
CGut Absent Member.
Absent Member.

Re: SpyJMSException

1. what version are you on?
2. Is the notification service running?
3. have any other clients reported on this object?


To bring the service node back we should restart the primary node (the first node started) first and then few minutes later the service node. After restarting it works.

Check that you are not starting a User Node first, seems PPM can be sensitive with the order starting up. please wait 20-30 seconds before starting the next node. if they all start at once, the "who is running the services?" communication gets mixed up.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Frequent Contributor.. hyllplan Frequent Contributor..
Frequent Contributor..

Re: SpyJMSException

9.22, yes, hmm i dont know what you mean by nr 3
Our startscript does the following
Wait 95sec
Start servicenode
Wait 75sec
Start usr node 1
Wait 75sec
Start usr node 2
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.