How to resolve "timed out" error when creating the sample "Money that matters"?
I wanted to install the sample project "Money that matters" for investigation purpose.
But I can't do that because of the following exception. I've tried several times but in vain.
How can I fix it?
thanks.
My Environment:
Windows server 2012 64bit
RAM 8GB
I installed the application from JTS-CCM-QM-RM-repo-5.0.2 archive.
and installed the license of RTC-Developer-10-C-License-5.0.2.
/jts/setup was successfully done.
DB: SQL Server Developer(64-bit)
showing 5 of 10
show 5 more comments
|
Accepted answer
One other answer
Ralph Schoon (63.5k●3●36●46)
| answered Apr 28 '15, 2:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The deployment of the templates fails. Try to manually deploy the process templates in the applications and have a look at the server diagnostics information. Maybe the server runs out of memory, if you have everything on one machine.
Comments Hi Ralph,
Thank you for answering.
But I can not understand "manually deploy the process templates".
And I set the default memory 4GB to tomcat. Isn't that enough?
Anyway I tried to create the project using template.
If I used "Empty Lifecycle Project" template, I could create a project successfully.
If I used "Developer" template, I couldn't create a project and get the below error.
and I didn't see "out of memory" anywhere, at logs or diagnostics pages.
Error Stacktrace:
com.ibm.team.lpa.automation.TaskException: com.ibm.team.repository.common.TeamRepositoryException: Read timed out
at com.ibm.team.lpa.common.tasks.CreateProjectTask.runTask(CreateProjectTask.java:181)
at com.ibm.team.lpa.common.tasks.AbstractTask.run(AbstractTask.java:48)
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: com.ibm.team.repository.common.TeamRepositoryException: Read timed out
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.send(AuthenticatingClientService.java:462)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.access$2(AuthenticatingClientService.java:406)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService.send(AuthenticatingClientService.java:110)
at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy296.send(Unknown Source)
at com.ibm.team.lpa.common.tasks.CreateProjectTask.runTask(CreateProjectTask.java:158)
... 7 more
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:18)
at com.ibm.jsse2.b.a(b.java:226)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:120)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:454)
at com.ibm.jsse2.f.read(f.java:15)
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 org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at com.ibm.team.repository.service.internal.oauth.shared.AuthenticatingClientService$Operation.send(AuthenticatingClientService.java:460)
... 17 more
Go to the CCM Application, or any other application via the manage server URL's.
I re-installed predefined templates by "ccm -> templates -> Deploy Predefined Templates". It was done without any erros. But, the situation didn't change. I always get "Read timed out" exception. I maybe have found the root cause of the error.
I noticed the status of project area while creating a life cycle project is "uninitialized", and it doesn't change just after the "Read time out" exception. But just after waiting for about 20 minutes, its status becomes without "uninitialized". After that, I can link the project area to a new life cycle project using a template.
I think that "Read timed out" exception is caused by a time out of a waiting process for finishing the creation of project area. A project area creating process itself survives and go on background until it has finished creating the project area (it takes about 20 minutes).
So, I think I'd be able to create projects using templates, if I extends the waiting time more longer than the current.
I'll try to find how to do that and I'll write the result later.
I can confirm Ralph's answer. i was getting the same error and after deploying the templates, the sample project creation was successful. Could a check for the templates be included in the other prerequisite checking that is done to avoid this error?
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Have you tried to access /ccm, /qm and /rm separately and see if they are accessible? And can you create (empty) projects in each application?
Yes, I've tried /ccm, /qm and /rm directly typing the address bar on the web browser, and I could get each pages. But I have no menu to create projects in each application. If you mean "project area" by "project", yes I can create (empty) "project area" in each application.
Anyone found the solution of this problem?
Thanks
Regards
There is an accepted answer and several workarounds are mentioned if one sees this. It is also more than 1 year old and thousands of users have been able to setup the sample since then. It is also unclear if you have the same problem.
I try it all, and I don't have lucky. This solutions doesn't work for me.
What do you mean "try it all"? The problem is most likely caused by an underpowered machine. What is the spec of your machine and how many CLM applications have you installed together on the machine?
Hi, My Environment is :
DB2: 10.5fp8
WAS: 8.5.5fp10
JAZZ:6.0.2
I have installed all the application in One machine. I know that works, because one time it Worked. But now in other instalation fails.
Since 6.0 there are so many new applications with huge RAM requirements. 8GB is not going to cut it, not if you install everything on this one box. Plus full WAS and the DB's.
My answer would be, you have over committed your server several times and should not expect any performance or proper functionality from it. You have way too few RAM to be able to run the application server, the databases and the applications on that small box. At least put the DB on a different box or add more memory.
I updated to 16Gb and still have the same problem. Any Idea?
After you added the RAM, did you increase the -Xmx value in the startup script to make use of the extra RAM?