This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 147041 - [65cat] Deployment error: The Sun Java System Application Server could not start. More information about the cause is in the Server log file. Possible reasons include: - IDE timeout: refresh the server node
Summary: [65cat] Deployment error: The Sun Java System Application Server could not st...
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vince Kraemer
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-12 09:56 UTC by big_al
Modified: 2008-09-17 17:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 106794

Attachments
stacktrace (2.71 KB, text/plain)
2008-09-12 09:57 UTC, big_al 		Details
a diff for Petr H to review (5.69 KB, text/plain)
2008-09-13 01:14 UTC, Vince Kraemer 		Details
DeploymentException patch (1.91 KB, text/plain)
2008-09-15 17:32 UTC, Petr Hejl 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description big_al 2008-09-12 09:56:52 UTC 
Build: NetBeans IDE Dev (Build 200809101401)
VM: Java HotSpot(TM) 64-Bit Server VM, 1.6.0_05-b13-52, Java(TM) SE Runtime Environment, 1.6.0_05-b13-120
OS: Mac OS X, 10.5.4, x86_64

User Comments: 
Waiting for an application to be deployed

Stacktrace: 
Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
 - IDE timeout: refresh the server node to see if it's running now.
 - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.) 
 - Incorrect server configuration (domain.xml to be corrected manually) 
 - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
 - Invalid installation location.

See the server log for details.
        at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:190)
        at org.netbeans.modules.maven.j2ee.ExecutionChecker.performDeploy(ExecutionChecker.java:108)
        at org.netbeans.modules.maven.j2ee.ExecutionChecker.executionResult(ExecutionChecker.java:84)
        at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:180)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Comment 1 big_al 2008-09-12 09:57:12 UTC 
Created attachment 69726 [details]
stacktrace
Comment 2 Vince Kraemer 2008-09-12 15:19:28 UTC 
Please attach the server log.
Comment 3 Vince Kraemer 2008-09-13 01:13:53 UTC 
While I wait for the server log, I decided that I was really tired of seeing this exception in the ant output window
when it provides almost no value...

So, i am going to make a change in j2eeserver to avoid generating the exception in the ant output... but keep it in the
IDE log... so we can debug the code. 

Petr H: please take a look at the attached diffs.  Please comment by Monday AM PDT.
Comment 4 Vince Kraemer 2008-09-13 01:14:47 UTC 
Created attachment 69792 [details]
a diff for Petr H to review
Comment 5 Petr Hejl 2008-09-15 17:29:51 UTC 
Hi Vince,
I'm bit unsure about your intention. I'm not sure about hiding the stacktrace, requesting the IDE log later. Perhaps
following patch could be acceptable (I noticed DeploymentException is wrapped to DeploymentException in deploy code and
perhaps DeploymentException is the one we are interested in). What do you think (I haven't time to test it, perhaps I
could test it later tonight)?
P.
Comment 6 Petr Hejl 2008-09-15 17:32:55 UTC 
Created attachment 69891 [details]
DeploymentException patch
Comment 7 Vince Kraemer 2008-09-15 18:04:45 UTC 
If the server cannot start, we generate a fairly long message that explains the possible causes and the action that the
user should take.  That gets wrapped up into a BuildException and when the user reads the ant output there is a fairly
useful message and a stack trace. Most of the time the stack trace is useless and distracting, to the user... because
the message says why the build failed... the server did not start. This is a situation which should cause the build to
fail... but it is common enough that it is not "exceptional"... which is why we have the long message.
Comment 8 Vince Kraemer 2008-09-15 18:33:43 UTC 
are you expecting your diff instead of my diff or is this diff "in addition" to my diff?
Comment 9 Vince Kraemer 2008-09-17 01:28:51 UTC 
http://hg.netbeans.org/main/rev/dece599a17bf

Fixes the stack trace in the ant output.  The exception will still be in the server log, but it is useful for code
diagnosis there.  The user needs see the message that the server failed to start and concentrate on that, not get
distracted by the stack trace.

big_al: if this doesn't resolve the issue you were reporting, please reopen this issue with more details.
Comment 10 Quality Engineering 2008-09-17 17:27:20 UTC 
Integrated into 'main-golden', will be available in build *200809171401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/dece599a17bf
User: Vince Kraemer <vkraemer@netbeans.org>
Log: #147041 : exception in ant log when GF server doesn't start is unnecessary.
   The log that has useful data is the server log and the message tells the user to look there.
   Some users miss that wheat due to the stack trace chaff.