Problem starting up RRC 2.0.0.3
2 answers
Some diagnostic questions ...
Did RRC work for you OK before upgrading to 2.0.0.3?
Did you change anything else on your system?
Are you sure you are using a supported operating system and have enough RAM?
Did this problem happen the first time you started RRC after upgrading to 2.0.0.3?
I note this defect may be related; looks like a restart solved this one:
https://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=19077
Did RRC work for you OK before upgrading to 2.0.0.3?
Did you change anything else on your system?
Are you sure you are using a supported operating system and have enough RAM?
Did this problem happen the first time you started RRC after upgrading to 2.0.0.3?
I note this defect may be related; looks like a restart solved this one:
https://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=19077
Hi, sorry for not update this post. BTW, it is not hanged, it finally
starts after 15 or 16 minutes. But to login, again you need more than 10
minutes, etc...
It seems really an estrange problem. It is not related with any upgrade.
I was working with no problem with 2.0.0.3 for a while.
In the same image, I had RTC and RQM. And they suffered suddenly exactly
the same problem (all at the same time). What is more, command tools
like repotools or scm also had the problem... tens of minutes to execute.
After couple of hours trying to diagnose the issue, suddenly everything
started to start and behave normally. ??
I think it is an issue related to JVM, VMWare and hardware. Searching at
Jazz.net I found this work item:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=114738
Really don't know if it is related. But it seems similarly tricky.
I got some core dumps but nothing seemed to be hanged. It is just that
the JVM consumes a lot and everything goes really slow.
Problem now is I don't know how to reproduce. It appears and disappears
just during normal work. BTW, a copy of vmware image that was failing in
Thinkpad T400, works fine in Thinkpad W510. Thats the reason I think
this issue is related to JVM, VMWare and the hardware.
If you have any idea of any other test I can try to help diagnosing this
estrange issue, let me know....
Regards,
Chemi.
On 4/7/2011 4:08 AM, dmoul wrote:
starts after 15 or 16 minutes. But to login, again you need more than 10
minutes, etc...
It seems really an estrange problem. It is not related with any upgrade.
I was working with no problem with 2.0.0.3 for a while.
In the same image, I had RTC and RQM. And they suffered suddenly exactly
the same problem (all at the same time). What is more, command tools
like repotools or scm also had the problem... tens of minutes to execute.
After couple of hours trying to diagnose the issue, suddenly everything
started to start and behave normally. ??
I think it is an issue related to JVM, VMWare and hardware. Searching at
Jazz.net I found this work item:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=114738
Really don't know if it is related. But it seems similarly tricky.
I got some core dumps but nothing seemed to be hanged. It is just that
the JVM consumes a lot and everything goes really slow.
Problem now is I don't know how to reproduce. It appears and disappears
just during normal work. BTW, a copy of vmware image that was failing in
Thinkpad T400, works fine in Thinkpad W510. Thats the reason I think
this issue is related to JVM, VMWare and the hardware.
If you have any idea of any other test I can try to help diagnosing this
estrange issue, let me know....
Regards,
Chemi.
On 4/7/2011 4:08 AM, dmoul wrote:
Some diagnostic questions ...
Did RRC work for you OK before upgrading to 2.0.0.3?
Did you change anything else on your system?
Are you sure you are using a supported operating system and have
enough RAM?
Did this problem happen the first time you started RRC after upgrading
to 2.0.0.3?
I note this defect may be related; looks like a restart solved this
one:
https://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=19077