Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

Reason behind 'SQL command exception while quering space using Gigaspace GUI interface'

java.sql.SQLException: Failed to execute SQL command. at com.j_spaces.jdbc.QueryHandler.visit(QueryHandler.java:307) at com.j_spaces.jdbc.RequestPacket.accept(RequestPacket.java:124) at com.j_spaces.jdbc.QueryProcessor.executeQuery(QueryProcessor.java:254) at com.j_spaces.jdbc.driver.GConnection.writeRequestPacket(GConnection.java:570) at com.j_spaces.jdbc.driver.GConnection.sendStatement(GConnection.java:600) at com.j_spaces.jdbc.driver.GStatement.execute(GStatement.java:274) at org.isqlviewer.sql.DatabaseConnection$ResultSetRetreiver.doQuery(DatabaseConnection.java:2569) at org.isqlviewer.sql.DatabaseConnection$ResultSetRetreiver.run(DatabaseConnection.java:2778) at java.lang.Thread.run(Thread.java:745) Caused by: com.gigaspaces.client.ReadMultipleException: Success:0, errors:1, [class java.rmi.RemoteException:1 StackTrace: java.rmi.RemoteException: Failed to find an active server for partition #1 to execute ReadTakeEntriesSpaceOperationRequestisTake=false,template=QueryTemplatePacket[typeName=com.tricode.saleslayer.coremodel.repository.contentrule.ContentRuleFact,uid=null,version=0,operationId=null],txn=null,maxResults=4999,modifiers=0,timeout=0,minResultsToWaitFor=4999,ifExist=false at com.gigaspaces.internal.remoting.routing.clustered.RemoteOperationsExecutorsCluster.getRemainingTime(RemoteOperationsExecutorsCluster.java:366) at com.gigaspaces.internal.remoting.routing.clustered.SpaceProxyLoadBalancingStrategy.findActiveMember(SpaceProxyLoadBalancingStrategy.java:52) at com.gigaspaces.internal.remoting.routing.clustered.SpaceProxyLoadBalancingStrategy.findActiveMemberUninterruptibly(SpaceProxyLoadBalancingStrategy.java:85) at com.gigaspaces.internal.remoting.routing.clustered.ClusterRemoteOperationRouter$AsyncOperationExecutor.executeAsync(ClusterRemoteOperationRouter.java:243) at com.gigaspaces.internal.remoting.routing.clustered.PostponedAsyncOperationsQueue$1.run(PostponedAsyncOperationsQueue.java:57) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) ] at com.gigaspaces.internal.client.spaceproxy.operations.ReadTakeEntriesSpaceOperationRequest.createPartialExecutionException(ReadTakeEntriesSpaceOperationRequest.java:181) at com.gigaspaces.internal.client.spaceproxy.operations.ReadTakeEntriesSpaceOperationRequest.getFinalResult(ReadTakeEntriesSpaceOperationRequest.java:172) at com.gigaspaces.internal.client.spaceproxy.actions.SpaceProxyImplReadTakeMultipleAction.newReadTakeMultiple(SpaceProxyImplReadTakeMultipleAction.java:97) at com.gigaspaces.internal.client.spaceproxy.actions.SpaceProxyImplReadTakeMultipleAction.readMultiple(SpaceProxyImplReadTakeMultipleAction.java:36) at com.gigaspaces.internal.client.spaceproxy.actions.SpaceProxyImplReadTakeMultipleAction.readMultiple(SpaceProxyImplReadTakeMultipleAction.java:26) at com.gigaspaces.internal.client.spaceproxy.actions.AbstractSpaceProxyActionManager.readMultiple(AbstractSpaceProxyActionManager.java:242) at com.gigaspaces.internal.client.spaceproxy.AbstractSpaceProxy.readMultiple(AbstractSpaceProxy.java:283) at com.j_spaces.jdbc.builder.QueryTemplatePacket.read(QueryTemplatePacket.java:807) at com.j_spaces.jdbc.builder.QueryTemplatePacket.read(QueryTemplatePacket.java:780) at com.j_spaces.jdbc.SelectQuery.executeEmptyQuery(SelectQuery.java:969) at com.j_spaces.jdbc.SelectQuery.executeOnSpace(SelectQuery.java:179) at com.j_spaces.jdbc.QueryHandler.handleRequest(QueryHandler.java:97) at com.j_spaces.jdbc.QueryHandler.visit(QueryHandler.java:303) ... 8 more

asked 2017-12-18 06:35:15 -0500

sgonuguntla gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

Hi, This error mean that primary space for the partition was not available at the time of the query, please see if there was a fail-over around that time.

Regards, Ester.

answered 2017-12-18 07:01:44 -0500

Ester gravatar image
edit flag offensive delete link more

Comments

We are able to query other space instances but the above error messages coming up only for one of the space class. We doubt that it is not a primary space issue. Furthermore we don't find any fail-over of primary space at the moment. It is only at the time of initial load from the database after the deployment however with further changes on the same space class, it starts working.

Please let us know what could be the reason behind for the above issue?.

sgonuguntla gravatar imagesgonuguntla ( 2017-12-19 02:48:31 -0500 )edit

Hi, Could it be that this query is executed before all the spaces in the cluster are turned to status ACTIVE? Can you check in your logs when this exception occur, if all spaces are in that state? Only when initial load is completed, the space is available for clients operations

inbarc gravatar imageinbarc ( 2017-12-19 03:12:29 -0500 )edit

another option is that particular query cause overload in the server.is the query limited in its results?

Ester gravatar imageEster ( 2018-01-18 04:07:53 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2017-12-18 06:35:15 -0500

Seen: 104 times

Last updated: Dec 18 '17