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 159774 - Cannot register default glassfish v2 domain on OpenSolaris
Summary: Cannot register default glassfish v2 domain on OpenSolaris
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: All Solaris
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 12:40 UTC by giorgio42
Modified: 2009-03-06 21:02 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 giorgio42 2009-03-06 12:40:48 UTC
If I try to register the default glassfish application server on OpenSolaris (snv_108) located in /usr/appserver
NetBeans says "No default registerable default domains available. Check your file permissions.".

I have been able to register the server by changing the permissions of the config and logs directories in domains to 777
and domain.xml to 666 (world-writable).

Somehow I cannot imagine a single reason why NetBeans needs to be able to write to the logs directory.
NetBeans should be able to register and display a Glassfish domain without having write access to it.
Comment 1 giorgio42 2009-03-06 12:48:30 UTC
Actually I used a NB67 daily to register glassfish because OSOL snv108 comes with 1.6.0_12 and we all know what this
means...
Comment 2 Vince Kraemer 2009-03-06 15:46:32 UTC
The user that is running netbeans is the user that starts and stops the server...

the user that starts and stops the server has to have permission to write into the AS directories.  Are you running NB
as root when this message appears?

If the user cannot, they are not allowed to register the domain as a local domain.

There are a couple work-arounds... create a personal domain OR register the systems default domain as a remote domain...
but you will not be allowed to start and stop the domain if it is a remote domain...

If either of these work-arounds has a problem on OS, please reopen this issue with details steps describing how to
reproduce the problem.
Comment 3 giorgio42 2009-03-06 21:02:47 UTC
Thanks for the explanation. You should probably mark the bug report as invalid.

Obvioulsy I missed the possibility to register the instance as a remote instance which would have given me exactly the
functionality I expected and which you are stating: getting access to the instance but not being able to start and stop it.

Another approach I intend to try is to use RBAC and assign the NetBeans user the rights to manage the server through a
profile.