Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Ben Brown
Liferay EE on Glassfish, in Jelastic.
September 17, 2013 5:02 AM
Answer

Ben Brown

Rank: Junior Member

Posts: 79

Join Date: July 7, 2010

Recent Posts

Hi,

When restarting Glassfish after deploying Liferay EE, the cluster won't restart. and I get:


An error has occurred
instance-168457205: Could not start instance instance-168457205 on node localhost-domain1 (localhost). Command failed on node localhost-domain1 (localhost): CLI801 Instance is already synchronized Waiting for instance-168457205 to start ..............................................................................................................................................Command start-local-instance failed. Error starting instance instance-168457205. The server exited prematurely with exit code 137. Before it died, it produced the following output: Launching GlassFish on Felix platform [#|2013-09-17T11:24:31.057+0000|INFO|glassfish3.1.2|com.sun.enterprise.server.logging.GFFileHandler|_ThreadID=1;_ThreadName=main;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2.2 (build 5)|#] [#|2013-09-17T11:24:31.572+0000|INFO|glassfish3.1.2|ShoalLogger|_ThreadID=1;_ThreadName=main;|GMS1095: member: instance-168457205 is joining group: gfcluster ...|#] [#|2013-09-17T11: .... msg.seeServerLog


However, the server log is empty....Is it a memory issue? I have uploaded the required dependencies to the lib folder, set the portal properties up to point to MySQL etc - anything I've missed?

Thanks for any help or advice.

Ben
Ben Brown
RE: Liferay EE on Glassfish, in Jelastic.
September 18, 2013 1:55 AM
Answer

Ben Brown

Rank: Junior Member

Posts: 79

Join Date: July 7, 2010

Recent Posts

Turned out to be just a lack of resources - increased the number of couldlets in Jelastic and all's well.

Thanks

Ben