Getting this error- java.rmi.ConnectException: LRMI transport protocol over NIO broken connection with ServerEndPoint

04-08-2017 18:22:17,854 [http-84-2] DEBUG com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool - Test of PooledConnection [com.mchange.v2.c3p0.impl.NewPooledConnection@1bdb9c9] on CHECKOUT has SUCCEEDED. 04-08-2017 18:22:17,854 [http-84-2] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - trace com.mchange.v2.resourcepool.BasicResourcePool@f5b8b1 [managed: 3, unused: 2, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@fc1e73) 04-08-2017 18:22:22,183 [http-84-1] DEBUG com.mchange.v2.c3p0.impl.NewPooledConnection - com.mchange.v2.c3p0.impl.NewPooledConnection@309600 handling a throwable. java.sql.SQLException: Error occurred while writing request at com.j_spaces.jdbc.driver.GConnection.writeRequestPacket(GConnection.java:573) at com.j_spaces.jdbc.driver.GConnection.sendStatement(GConnection.java:600) at com.j_spaces.jdbc.driver.GStatement.executeQuery(GStatement.java:383) at com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:35) at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:440) at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:395) at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:455) at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:463) at com.clsa.settlementfeed.connector.FetchDataFromTCM.getOrders(FetchDataFromTCM.java:61) at com.clsa.settlementfeed.delegate.RPKHelper.populateDMAOrders(RPKHelper.java:99) at com.clsa.settlementfeed.service.RPKService.getDMAOrders(RPKService.java:103) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:554) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:724) Caused by: java.rmi.ConnectException: LRMI transport protocol over NIO broken connection with ServerEndPoint: [NIO://vklnlp828:33160/pid[4583]/574147126338_3_1698202016255992393]; nested exception is: java.nio.channels.ClosedChannelException at com.gigaspaces.lrmi.nio.CPeer.invoke(CPeer.java:725) at com.gigaspaces.lrmi.ConnPoolInvocationHandler.invoke(ConnPoolInvocationHandler.java:49) at com.gigaspaces.lrmi.MethodCachedInvocationHandler.invoke(MethodCachedInvocationHandler.java:71) at com.gigaspaces.lrmi.DynamicSmartStub.invokeRemote(DynamicSmartStub.java:438) at com.gigaspaces.lrmi.DynamicSmartStub.invoke(DynamicSmartStub.java:419) at com.gigaspaces.reflect.$GSProxy4.executeQuery(Unknown Source) at com.j_spaces.jdbc.QueryProcessorStub.executeQuery(QueryProcessorStub.java:57) at com.j_spaces.jdbc.driver.GConnection.writeRequestPacket(GConnection.java:570) ... 43 more Caused by: java.nio.channels.ClosedChannelException at com.gigaspaces.lrmi.nio.Reader.throwCloseConnection(Reader.java:500) at com.gigaspaces.lrmi.nio.Reader.readBytesFromChannelBlocking(Reader.java:242) at com.gigaspaces.lrmi.nio.Reader.readBytesBlocking(Reader.java:655) at com.gigaspaces.lrmi.nio.Reader.bytesToPacket(Reader.java:574) at com.gigaspaces.lrmi.nio.Reader.readReply(Reader.java:151) at com.gigaspaces.lrmi.nio.CPeer.invoke(CPeer.java:661) ... 50 more Caused by: java.io.IOException: Connection has been closed by peer at com.gigaspaces.lrmi.nio.Reader.throwCloseConnection(Reader.java:501) ... 55 more

We use jdbc api of gigaspace and call direct query like- select .... from xxx.Client_Order co, xxx.Client_Execution ce where ...

asked 2017-08-04 08:11:27 -0500

anuja
1 ●1 ●2 ●2

edit retag flag offensive close merge delete

add a comment

0

hey ,please contact xap_support@gigaspaces.com

answered 2017-08-10 04:14:21 -0500

livnat
1

edit flag offensive delete link

add a comment

0

Hi,

Thanks for your response.

We connect like below-

gigaspace.groups=grp gigaspace.user.name=gigaspace gigaspace.user.password=34354fgfdxzd gigaspace.transaction.manager.type=distributed

gigaspace.c3p0.connection.checkout.timeout=0 gigaspace.c3p0.connection.min.pool.size=10 gigaspace.c3p0.connection.max.pool.size=100 gigaspace.c3p0.connection.max.statements=50 gigaspace.c3p0.connection.acquire.increment=5

genesis.gigaspace.connection.max.active=100

<bean id="tcmGSdataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource"> <property name="driverClass" value="com.j_spaces.jdbc.driver.GDriver"/> <property name="jdbcUrl" value="jdbc:gigaspaces:url:jini://*/*/mySpace?locators=${gigaspace.locator}&groups=${gigaspace.groups}"/> <property name="user" value="user"/> <property name="password" value="password"/> <property name="autoCommitOnClose" value="false"/> <property name="checkoutTimeout" value="${gigaspace.c3p0.connection.checkout.timeout}"/> <property name="minPoolSize" value="${gigaspace.c3p0.connection.min.pool.size}"/> <property name="maxPoolSize" value="${gigaspace.c3p0.connection.max.pool.size}"/> <property name="acquireIncrement" value="${gigaspace.c3p0.connection.acquire.increment}"/> <property name="properties"> <props> <prop key="gs.tx_manager_type">${gigaspace.transaction.manager.type}</prop> <prop key="user">${gigaspace.user.name}</prop> <prop key="password">${gigaspace.user.password}</prop> </props> </property> </bean>

<bean id="GSjdbcTemplate" class="org.springframework.jdbc.core.JdbcTemplate">
    <property name="dataSource" ref="GSdataSource" />
</bean>

answered 2017-08-07 00:29:36 -0500

anuja
1 ●1 ●2 ●2

edit flag offensive delete link

add a comment

0

you haven't specified if you are working with direct proxy. please note that its recommended to work with a cluster proxy ,if you are using direct proxy you have probably lost connection to container.

answered 2017-08-06 02:46:53 -0500

livnat
1