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 227670 - glassfish startup failed security manager
Summary: glassfish startup failed security manager
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.3
Hardware: PC Mac OS X
: P1 normal (vote)
Assignee: TomasKraus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 17:51 UTC by lanthale
Modified: 2013-03-25 09:36 UTC (History)
1 user (show)

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 lanthale 2013-03-19 17:51:43 UTC
I just upgraded from NB 7.2.1 to 7.3 and my glassfish domain always is starting with the following error message:

Listening for transport dt_socket at address: 9009
Exception in thread "main" java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "getenv.GlassFish_Platform")
   at java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
   at java.security.AccessController.checkPermission(AccessController.java:560)
   at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
   at java.lang.System.getenv(System.java:883)
   at com.sun.enterprise.glassfish.bootstrap.ASMainHelper.whichPlatform(ASMainHelper.java:105)
   at com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:68)
   at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55) 

On commandline I can start glassfish with that domain fine. An empty domain is starting also in netbeans fine. But if the security manager is activated inside of the domain than the exception above is occuring.
Comment 1 lanthale 2013-03-19 17:52:34 UTC
Changed to P1 because all domains I am using are using the security manager. It is an essantial function.
Comment 2 TomasKraus 2013-03-20 10:37:46 UTC
This is not a P1 bug because there is a workaround - user can always start glassfish manually using asadsmin.
Comment 3 TomasKraus 2013-03-20 16:47:38 UTC
Checked into Glassfish Tooling Library:
---------------------------------------
changeset:   466:c9b145313fdc
summary:     Bug# 227670 - Glassfish startup failed with security manager

changeset:   253:2d37aededc7d
branch:      0.3-b036
summary:     Bug# 227670 - Fixed PE

changeset:   252:5acd5f65cf13
branch:      0.3-b036
summary:     Bug# 227670 - Glassfish startup failed with security manager
Comment 4 TomasKraus 2013-03-20 16:48:57 UTC
Checked into web-main:
----------------------
changeset:   248402:5534e617164e
branch:      javaee7
summary:     #227670 - Glassfish startup failed with security manager

changeset:   248415:571b3ed1e31b
summary:     #227670 - Glassfish startup failed with security manager
Comment 5 Quality Engineering 2013-03-23 01:59:33 UTC
Integrated into 'main-golden', will be available in build *201303222300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/5534e617164e
User: Tomas Kraus <TomasKraus@netbeans.org>
Log: #227670 - Glassfish startup failed with security manager
Comment 6 Jiri Skrivanek 2013-03-25 08:36:59 UTC
Please, consider whether this fix should go to 7.3 patch or to 7.3.1 at least.
Comment 7 TomasKraus 2013-03-25 09:36:43 UTC
It's already fixed in 7.3.1