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 196401 - Unable to run integrated J2EE environment under normal user account.
Summary: Unable to run integrated J2EE environment under normal user account.
Status: RESOLVED INVALID
Alias: None
Product: installer
Classification: Unclassified
Component: JDK bundle (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Yulia Novozhilova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-07 16:28 UTC by karlkras
Modified: 2011-05-06 16:07 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 karlkras 2011-03-07 16:28:20 UTC
In order to define an application server, e.g., Glassfish, into the services repository of NB, I am forced to run NB under root permissions so certain files in the Glassfish bundle can be touched or executed by NB when accessed through the IDE.
The J2EE bundle for linux out of the box requires you to install under root access. After which, while I as a non-root user can then start the IDE in my own account, if I attempt to access the GF server it errors with permission access violations.
Other postings that I've found of users having this problem simply run NBs as root and live with it, I don't believe this is a viable option in a true shared OS. For starters, if there multiple users on the system it shouldn't be a reasonable workaround to have them all working under the root account (I hope I don't have to explain why), all added NBs plugins, personal configuration settings, etc, that each user on the system using NBs desire would go straight into the root account, sort of breaks the idea of "personal settings", eh?

I don't purport on being an experience Linux administrator so how this can be fixed is out of my range, there may in fact be an obvious tweak I can make to adjust this but have come up empty in my search for a solution.

I was able to configure GF separately so that it can be controlled by users on the system who have been assigned to a glassfishadm group without the restriction of being root, but I don't know how or if such a group designation can be assigned to the NBs process in a like manner.

In my view this is essentially broken for any real multi-user environment application.
Comment 1 Ondrej Vrabec 2011-03-07 16:31:09 UTC
> The J2EE bundle for linux out of the box requires you to install under root
access.
Sorry, what installer exactly, can you provide a link?
Comment 2 karlkras 2011-03-07 16:51:48 UTC
Ummm, well sure. Go here:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=java_ee_sdk-6u2-jdk-6u24-oth-JPR@CDS-CDS_Developer

Select Linux 64 (in my case, I'm pretty sure 32 bit will do the same thing)/English and download.

Now install it. That's the install I'm referring to, The main install procedure of getting NBs and GF on the system initially.

I believe at minimum instructions should be provided in how to configure the product post install so it can be accessed via "normal" users, if it's even possible?
Comment 3 Yulia Novozhilova 2011-05-06 13:23:07 UTC
This bug is about J2EE SDK installer, It has nothing to do with NetBeans  installer. 
Petr, maybe you know who owns j2ee + jdk bundle installer so that the right person could see the bug?
Comment 4 Petr Jiricka 2011-05-06 16:07:52 UTC
Here are the comments that I received from the GlassFish team:

Running Java EE SDK installers does not require a root access/user.
In this case, I think that the user is trying to setup an install directory that will be shared
by many users. If so, then the following hints should help
-Change the permissions of files under <GFroot>/bin so that everyone can execute.
-use --domaindir option with a writable directory path for all asadmin domain related commands