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

Ask Your Question

Instantiated PU but shouldn't be ?


I've had a look through the docs but I can't really find a solution to this...

I have a pu being deployed and instatiated even though errors are thrown in the bean during initialisation. For example we read a password for a database through a properties file, if this is incorrect a SQLException is thrown and nothing is loaded correctly but the pu is still shown in the UI as being deployed.

How do I stop this from being deployed ?


{quote}This thread was imported from the previous forum. For your reference, the original is [available here|http://forum.openspaces.org/thread.jspa?threadID=3122]{quote}

asked 2009-06-05 03:57:23 -0500

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

jaissefsfex's avatar
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

Ok done a little more digging and found the problem, but not a solution...

Inside the pu.xml we use the context loader to make sure that all actions are performed on a primary instance and not the backup instance. The exception is thrown inside the context loader and the pu is still deploying successfully (the GUI shows the pu as green). Without the context loader the pu doesn't deploy.


Using the above example the exception would be thrown in SpaceModeContextBean but the whole pu would deploy.

Is this a GS bug ?

answered 2009-06-05 07:59:42 -0500

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: 2009-06-05 03:57:23 -0500

Seen: 101 times

Last updated: Jun 05 '09