Creating new sample project fails
8 answers
Now I cannot remember whether it is 10 mins or 15mins but there is a timeout on each step of the sample creation and if one of the steps takes longer than that time the sample creation stops with an error.
Is the sample creation very slow? On a laptop typically the entire sample creation usually takes only 15-20mins in totals.
That said looking at the error it looks like it is failing during the process template creation, which is strange for RM as this template is the same for any RM project.
Are you able to create the RM JKE Banking Project separately outside of the sample? The project template is the same project contents that is used in the sample creation, just without the OSLC linking to the CCM and QM domains.
Is the sample creation very slow? On a laptop typically the entire sample creation usually takes only 15-20mins in totals.
That said looking at the error it looks like it is failing during the process template creation, which is strange for RM as this template is the same for any RM project.
Are you able to create the RM JKE Banking Project separately outside of the sample? The project template is the same project contents that is used in the sample creation, just without the OSLC linking to the CCM and QM domains.
Hi Israel,
A socket timeout during the LPA sample creation is unexpected, so this would make me think that either a) the performance of the server in general is slow, b) there is a large amount of data already in use on the server which could be affecting the performance of the product, or c) the server is under-spec'd for the amount of data in use.
Some things to check:
1) Could you please navigate to your personal dashboard and add the widget named "Performance Health Check", and run the test? Any results which appear in the orange or red should be investigated further.
2) What version of CLM are you using?
3) Since this seems related to RRC, do you have a rough estimate for how many requirements exist in the RRC repository (i.e. all projects)?
4) About how long into the process of creating the sample project does the error appear? Does the error appear after 5 minutes? 10? 15? Longer?
5) What are the specs of the server in use? How much total RAM is on the server? How much heap is configured for the CLM instance (check the Xmx, Xms, Xmn values in the JVM configuration)?
6) Please check the RM logs for any errors during the timeframe that the sample project is being created.
Thanks in advance,
Mike Jaworski
Comments
Arun K Sriramaiah
Sep 29 '14, 8:45 a.m.Hi Israel.
What's is the error message are you getting.
Are you able to access the old project after upgrade ?
Give us the RTC;RQM;RRC .log information.
Regards,
Arun.
Israel Lazar
Sep 30 '14, 10:10 a.m.I got this error when he tried to create RM project
Error creating the sample: java.net.SocketTimeoutException: Read timed out
Error Stacktrace:
com.ibm.team.lpa.automation.TaskException: java.net.SocketTimeoutException: Read timed out
at com.ibm.team.lpa.common.tasks.DeployPredefinedProcessTemplatesTask.runTask(DeployPredefinedProcessTemplatesTask.java:60)
at com.ibm.team.lpa.common.tasks.AbstractTask.run(AbstractTask.java:56)
at com.ibm.team.lpa.tasks.util.ConditionalTask.run(ConditionalTask.java:36)
at com.ibm.team.lpa.automation.CompositeTask.run(CompositeTask.java:208)
at com.ibm.team.lpa.automation.CompositeTask$MonitoredSubTask.run(CompositeTask.java:124)
at com.ibm.team.lpa.automation.CompositeTask.run(CompositeTask.java:208)
at com.ibm.team.lpa.common.tasks.LoggingCompositeTask.run(LoggingCompositeTask.java:37)
at com.ibm.team.lpa.automation.AsyncTask$TaskRunner.run(AsyncTask.java:40)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:140)
at com.ibm.jsse2.b.a(b.java:286)
at com.ibm.jsse2.b.a(b.java:67)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:313)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:765)
at com.ibm.jsse2.f.read(f.java:20)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
at com.ibm.team.jfs.app.http.client.internal.ExtensibleRequestDirector.execute(ExtensibleRequestDirector.java:149)
at com.ibm.team.lpa.common.clients.LpaRequestDirector.internalExecute(LpaRequestDirector.java:180)
at com.ibm.team.lpa.common.clients.LpaRequestDirector.execute(LpaRequestDirector.java:147)
at com.ibm.team.lpa.common.http.client.cache.HttpClientCache.executeCacheMiss(HttpClientCache.java:205)
at com.ibm.team.lpa.common.http.client.cache.HttpClientCache.execute(HttpClientCache.java:161)
at com.ibm.team.lpa.common.http.client.cache.HttpClientCache.execute(HttpClientCache.java:87)
at com.ibm.team.lpa.common.http.client.cache.HttpClientCacheDirector.execute(HttpClientCacheDirector.java:30)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at com.ibm.team.lpa.common.tasks.DeployPredefinedProcessTemplatesTask.runTask(DeployPredefinedProcessTemplatesTask.java:54)
... 8 more