Hello Experts,
We are facing an issue which is very critical fo us at this moment in SAP PO 7.31.
2 months before the process flow was getting very slow.
After the discussion SAP BPM Green Token move very slow from one task to other! I got the clue about the Queue from Christial Loos.
I started searching that way and came to this point.
Our helpdesk is communicating with SAP too. They(SAP) said 'solve the error of the process run and then archive the process, there is no other way to remove the process instances'
I checked, undeployed each and every deployed projects on the server and redeployed only this project and ran the whole process again.
Everything went fine with the new deployment and the process is completed successfully ( completed on 15 Jan 2014 ).
But now, I am trying to archive a process which has been completed 21-Oct-2013.
When i try to archive this process after 15 min the Write is done but the delete fails.
I could not archive and remove the completed process instance.
Write phase log:
[2014.01.15 09:27:45 CET] INFO Job
bpm_proc_write_session (ID: 7de8fcf47e2311e3cc3100000091aa6e, JMS ID:
ID:3502010000000002-00000000004C) started on wo, 15 jan 2014 21:27:45:303 CET by
scheduler: 32708a3a0ac111e1802e00237d240438
[2014.01.15 09:27:45 CET] INFO
Start execution of job named: bpm_proc_write_session
[2014.01.15 09:27:45
CET] INFO Job status: RUNNING
[2014.01.15 10:03:50 CET] INFO Start
processing of archiving write command ...
Verify Indexes ...
Resident
Policy for object selection is instanceIds = [eea2f40e370711e3c0f800000091aa6e]
, timePeriod = 1389817666141 , inError = null , ProcessDefinitionID = null ,
completedProcesses = false , cancelledProcesses = false , completedFrom =
null , completedTo = null ,
Archiving 2014_01_15_22_03_50_908.xml
...
[2014.01.15 10:03:51 CET] INFO Archiving 2014_01_15_22_03_51_86.xml
...
[2014.01.15 10:03:53 CET] ERROR I/O problem occurred when executing
Archiving Command put
[2014.01.15 10:03:53 CET] ERROR Processing of
archiving write command failed
[2014.01.15 10:03:53 CET] ERROR
com.sap.ASJ.scheduler.rs0011#Job "7de8fcf47e2311e3cc3100000091aa6e" could not
be run as user "ferminusGGGG". For more details, check the server
traces.
[2014.01.15 10:03:53 CET] INFO Job bpm_proc_write_session (ID:
7de8fcf47e2311e3cc3100000091aa6e, JMS ID: ID:3502010000000002-00000000004C)
ended on wo, 15 jan 2014 22:03:53:758 CET
The result of this,
the queue is getting full. I have at this moment 21,457 Queued Actions and it is getting more and more.
Is there anyone experienced this kind of problem.
Any kind of suggestions are welcome.
Thanks in advance.
Regards,
Antony.