java.net.SocketException: No buffer space available when
We can't save the new rootservice URI to enable cross server communication link for RTC and RQM
An error occurred while requesting the root services document from server .. according to the log: 2010-07-13 13:42:49,966 ERROR .ibm.team.jfs.app.discovery.utils.RootServicesUtil - Error while fetching and parsing the root services document from "https://XXXXX:9443/jazz/rootservices" with host "XXXXX:9443" java.net.SocketException: No buffer space available (maximum connections reached?): connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:391) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:252) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:239) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:389) at java.net.Socket.connect(Socket.java:551) at com.ibm.jsse2.jc.connect(jc.java:175) at com.ibm.team.http.client.impl.NaiveSSLSocketFactory.connectSocket(NaiveSSLSocketFactory.java:97) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:129) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:349) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555) at com.ibm.team.http.client.impl.NullHttpCacheService.execute(NullHttpCacheService.java:33) at com.ibm.team.http.client.impl.HttpClientService.internalSend(HttpClientService.java:267) at com.ibm.team.http.client.impl.HttpClientService.send(HttpClientService.java:206) at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.initRootServicesDoc(RootServicesUtil.java:267) at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.getNodeList(RootServicesUtil.java:289) at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.getRdfResourceUrl(RootServicesUtil.java:296) at com.ibm.team.jfs.app.discovery.utils.RootServicesUtil.getOauthRequestConsumerKeyUrl(RootServicesUtil.java:215) at com.ibm.team.repository.service.internal.discovery.FriendsAdminRestService.getFriendsOAuthInfo(FriendsAdminRestService.java:177) at sun.reflect.GeneratedMethodAccessor138997.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke any suggestions?? |
5 answers
Ralph Schoon (63.7k●3●36●48)
| answered Jul 16 '10, 3:30 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
can you provide more details on OS, hardware architecture, server architecture and which server throws the error etc? Thanks, Ralph We can't save the new rootservice URI to enable cross server communication link for RTC and RQM |
Hi There,
We are receiving the same issue. We have the following setup: RTC v3 Windows Server 2008 64x WebSphere 7.0.0.9 SQL Server We copied the JTS and CCM databases from production to test server and have connected the new instance of RTC on Webshpere (before was tomcat) But now receive the socket exception around 45 minutes after starting the JTS application. The error is; com.ibm.team.repository.common.TeamRepositoryException: Error updating service contributions for the JTS Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): connect |
|
Ralph Schoon (63.7k●3●36●48)
| answered Mar 29 '11, 6:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
is this a Beta or a production Server? If it is production or you are in the process of migrating to RTC 3.0 you might want to create a PMR or work item. If this is beta, we should address this in a beta call. I could really only guess, that there is an issue with returning resources in WAS or the resource threshold in the OS. Ralph Hi There, |
|
|
Any way to resolve this issue?
Regards,
Felipe A. Hernández.
|
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.