Skip to main content

New Plugin (1.0.13) doesn't recognize server is started

8 replies [Last post]
gcruscoe
Offline
Joined: 2003-06-30

First, I would like to say I really like the new enhancements to the plugin (1.0.12 and 1.0.13). I see now that you can set the name when adding the server (as of 1.0.13 I believe). This solves my previous post about the name change. So that is good!

However when using this new plugin it does not seem to recognize that the server has started. I see that it is now supposed to recognize when the server is started externally, but this doesn't seem to work either.

To reproduce:
Delete all existing servers and install the new Glassfish 1.0.13 plugin. Create the new Server based on this configuration (I changed the name to V2 instead of v2). Go to the server View and start. you can see the console and the glassfish log view that the server has started successfully. The Progress indicator stays at 7% and never indicates the server has started. After the timeout (default 240 seconds), Eclipse displays the popup that the server startup failed.

This is on a Linux system with everything working through 1.0.11.

Anyone have any ideas... Switching back to 1.0.11 is my only option so far.

Thanks,
Geoff

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
gcruscoe
Offline
Joined: 2003-06-30

I have now tested this with 1.0.14 with the exact same results.

I have a very basic domain.xml file (pretty much the installed defaults + jdbc resources).

... a moment passes as I do more testing...

Okay so I found the problem... I will report the bug and see if anyone thinks it is worth fixing...

It has to do with symbolic links...

If there are any symbolic links in the path the appserver (when doing the add), then the app server fails to work. I didn't try to study why it doesn't work.

in my case I refer to glassfish as $HOME/local/glassfish

when in reality
$HOME/local -> /var/home/$USER/local (due to hard drive space problems)

and

glassfish -> glassfish-v2ur2-b04 (so everyone can have a consistent view of the default glassfish server instance instead of having to change it every time we have a new release / minor update).

Anyway either of these links is enough to break the glassfish plugin (yes I bothered to try with each of the links separately just to check -- since the /var/home... is actually a different partition -- this caused problems in eclipse for publishing (the -Djava.io.tmpdir= fix).

Hope this helps someone else.

-Geoff

acuster
Offline
Joined: 2008-11-21

Hello,

I can confirm the same problem and solution.

Originally, I had both Eclipse and Glassfish in /usr/local/java which is on a different partition from /home. The server would not start correctly.

Now, I have a copy of Eclipse and Glassfish v2 and v3 in /home and starting/stoping the server and deploying the application works.

--adrian

mjenkins
Offline
Joined: 2007-09-20

I have the same problem on Windows. The progress bar stays at 7% and I get the failed to start message. The app server is actually running however. Any clue as to the problem or resolution?

GlassFish v2.1
Eclipse 3.4.1
Plugin 1.0.17

Message was edited by: mjenkins

rouche
Offline
Joined: 2009-01-23

Same problem on Windows.

Start the server and then at 7% while hes binding the data sources Poof! Glassfish server failed to start. But the server is actually starting, the logs are getting populated.

It seems to be hapenning with Glassfish 2.1 when an application is already deployed as you start the server. Seems like the plugin "loose" from server.

Glassfish 2.1
Eclipse 3.4.1
Plugin 1.0.24

gcruscoe
Offline
Joined: 2003-06-30

Is you server on a different drive than Eclipse. That would be similar. Or did you setup a shortcut that you are using? Those would both match pretty well.

rouche
Offline
Joined: 2009-01-23

No to both questions.

Note: If i undeploy the application, server starts correctly. Then i redeploy.

But since our deploy takes 3 minutes, its unnacceptable.

gcruscoe
Offline
Joined: 2003-06-30

Sorry, but this is unrelated to the previous posts. The previous posts were about the app server not being recognized to start when it was starting just fine.

You case seems to be that with the app deployed it is taking too long to start the app server.

I would try to start a new thread (or search for an existing one) with that in mind.

Incidentally, 3 minutes for an app to deploy is an awfully long time. Are you sure the problem isn't app / windows related?

good luck!

-Geoff

gcruscoe
Offline
Joined: 2003-06-30

I realized that I left some pretty important information off the post.

I searched the bug lists and didn't find anything.
I am using eclipse 3.4.1
I am using the current production release of glassfish (v2ur2-b04).

I have deleted and readded the servers several times with the same results every time.

Should I report a bug?