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

Ask Your Question

Where to put JSpaces.jar when deploying pu


I'm using GigaSpaces 6.6 and try to deploy my application as pu to the grid.

My application is implementing com/gigaspaces/datasource/DataProvider for persistence to database.

I tried to put JSpaces.jar in the Gigaspace startup classpath by setting it in POST_CLASSPATH env variable but I got the following error message in gsm:

WARNING org.jini.rio.monitor.feedback: Registering a ServiceBeanInstantiator
Caused by: java.lang.IllegalAccessError: tried to access method org.jini.rio.monitor.InstantiatorResource.setServiceRecords()V from class org.jini.rio.monitor.ServiceProvisioner

In gsc, the error shows as
WARNING org.jini.rio.cybernode: Failed registering lease with GSM: com.gigaspaces.grid.gsm.GSMProxy0, MaxConnPool: 1024 ">DynamicSmartStub [ImplObjClass: com.gigaspaces.grid.gsm.GSMImpl, ConnectionURL: NIO:///, MaxConnPool: 1024 ], retry count 1
Caused by: net.jini.core.lease.LeaseDeniedException: Getting ServiceRecords

When I tried to put JSpaces.jar into lib directory in pu deployment directory, I got class not found exception.

Can you please tell me which place should be the correct place to put the jar file and what could be the cause of the above problems?



This thread was imported from the previous forum.
For your reference, the original is available here

asked 2010-08-16 15:22:55 -0600

gddxykxq gravatar image

updated 2013-08-08 09:52:00 -0600

jaissefsfex gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

The JSpaces.jar should be already within the GigaSpaces container classpath. So you don't need to place it within the pu folder. You need to have the EDS implementation within the pu/shared-lib folder.

With with XAP 7.1 we have improved many features related to the EDS. Note that with XAP 7.1 we renamed the GigaSpaces runtime libraries. The EDS implementation jar should be under the pu/lib folder.

You problems seems to be related to some connectivity issue between the GSM and GSC. Have you set the LOOKUPLOCATORS across all the machines running the GSCs?


answered 2010-08-16 16:49:22 -0600

shay hassidim gravatar image
edit flag offensive delete link more

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


Asked: 2010-08-16 15:22:55 -0600

Seen: 108 times

Last updated: Aug 16 '10