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 141082 - Can't start glassfish from netbeans without TRACE on
Summary: Can't start glassfish from netbeans without TRACE on
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-21 23:09 UTC by gibsonw
Modified: 2008-07-23 01:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gibsonw 2008-07-21 23:09:01 UTC
My company's cyber security folks say that having TRACE enabled in glassfish (or any server) is a vulnerability. They 
want me to disable TRACE in glassfish. The glassfish folks say: put this line in the domain.xml.

<property name="enableTrace" value="false"/>

When I do this, I can no longer start glassfish from the netbeans services tab, and I suspect that TRACE is crucial to 
the tight integration between netbeans and glassfish.

Can you please advise me on this? Is there any way for me to make my cyber security people happy and yet still enjoy 
some of the nice integration between these two great products?
Comment 1 Vince Kraemer 2008-07-23 01:01:54 UTC
i just tried to replicate this on Windows Vista with NB 6.1 and GF V2 UR 2...

I could not replicate the problem.

The server started and I was able to interact with it (deploy apps, view deployed resource properties, etc...)

If this is still a problem, please reopen the issue and include more detailed information to help us replicate it.

One very important thing to attach would be the log file for the server/domain that doesn't want to start.

Another valuable bit of info would be the domain.xml file...

A description of how you added the property to the domain.xml would be useful, too.