We have installed BPM Process Center 8.0.1 Standard on Window 2008 R2 64 bits and 4 GB RAM yesterday, then we installed the Process Designer in a Windows 7 machine 4 GB RAM and imported the processes developed under BPM 8.0 and continue developing with them.
We were updating a coach and saving with no problems but after three or four saves (adding or removing components) the interface of Process Designer freezes with a pop-up with the following information:
A dump is created including javacore files
The problem is very easy to reproduce, it is allways the same behavior.
There is no information registered in SystemOut.log at that time
After restart Process Designer you can work again with PD but not to save changes in coaches for more than about 3 times!
Any help would be really appreciated
Pinned topic BPM 8.0.1 Process Designer hangs when saving
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-13T07:35:58Z at 2012-12-13T07:35:58Z by vlit
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-21T14:57:53ZThis is the accepted answer. This is the accepted answer.Hi,
It is funny - 4 GB of RAM for BPM server Windows 2008.
I think the heap by default - 768/2048?
All save - this is the new snapshot and a lot of them save in the cache in memory.
Out Of Memory, I think.
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-21T16:32:24ZThis is the accepted answer. This is the accepted answer.Hi, we have increased the RAM in the Process Center machine to 6 GB and also increase the heap size to 1 GB / 4 GB and repeated the test with the same result:
We have just add a button to the coach and save the change with good response time then add a new button and save with a bit worse response time then added a third button and received for a while a "Not responding" message but finally was saved and then I tried to add a fourth button but the PD hanged and the damp was generated.
Thanks in advanced, any idea is welcome.
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-21T17:42:59ZThis is the accepted answer. This is the accepted answer.
- toural 2700006VP7
Try to edit eclipse.ini file:
And by the way - set heap 4096/4096.
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-21T18:10:01ZThis is the accepted answer. This is the accepted answer.
- vlit 270002P57M
the dump was generated in the client.
After changing the eclipse.ini to the values you suggested, we no longer have the problem.
Thanks very much for your help!
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-22T14:49:14ZThis is the accepted answer. This is the accepted answer.Hello again. Unfortunately the issue reappeared but this time after save changes more than 30 times.
The configuration we have:
DB is installed in a separated machine
Heap size 4096/4096
RAM 6 GB
It seems the memory assigned affects directly and delay the moment the error appears.
Any idea is welcome
Thnaks in advnaced
Re: BPM 8.0.1 Process Designer hangs when saving2012-11-22T20:12:26ZThis is the accepted answer. This is the accepted answer.
- toural 2700006VP7
It's rather strange because RAM 2GB and heap=512 is usually enough.
But the memory leak presents in our case.
I advice only:
1. Reinstall Process Designer.
2. Try to do the same from an another workstation (RAM error may be).
3. Add -XX:MaxPermSize=256m or 512
4. Also, cannot your PD use not embedded JRE, but some other installed in your system? I that case, OOM is possible.
SystemAdmin 110000D4XK7615 Posts
Re: BPM 8.0.1 Process Designer hangs when saving2012-12-12T16:11:01ZThis is the accepted answer. This is the accepted answer.
- vlit 270002P57M
and depends of who big Coach is.
actually I use
that reduce a few OOM, but it is few, some developers have same quantity of OOM than initial, but other have less.
toural had you opened a PMR for this?
Re: BPM 8.0.1 Process Designer hangs when saving2012-12-13T07:35:58ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
I tried to reproduce this issue but I couldn't.
I think it is a problem on your ProcessCenrer side (or database, may be).
I've got an idea.
Your Process Center isn't in time to process all the PD requests, they accumulate in PD heap and provoke OOM.
Vladlen | http://bpmadmin.blogspot.com