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.
Build 200707260000-full,JDK1.5,MacOS intel (however I've seen the same issue also on Vista) 1)Install Netbeans and go to glasfish's updatetool 2)Install there Identity along with access manager 3)Start Netbens with clean userdir 4)Go to Runtime tab,click on Servers\Glassfish v2 and start it 5)After glassfish starts,click on its node and open AM 6)Right click on any of AM profiles and select Edit ERROR: All profiles will stay disabled, along with error messages of type "Server not running" (although it is) and then "Initialization failed"
Will address for beta1.
Do you see any exception in the nb's log file? If so, please attach it.
Hi Jarek, Could you check to see if there are any exceptions in the nb's log file? If so, please attach it to this issue. Thanks. Peter
I just reproduced the issue on Win Vista with current build (200708080000). Attaching messages.log , but it seems there's nothing related to the issue. Also attaching screenshot.
Created attachment 46320 [details] messages.log
Created attachment 46321 [details] screenshot
Could you install the AM using the installer from the following links: http://javaweb.sfbay/java/re/javaeesdk/5.0_03/nightly/bundles/latest/ Please use the platform version of the installer. There might be something wrong with the glassfish's updatetool.
I've used older version of SDK installer with same result yesterday.However then I logged into admin console and when I finished, I tried to edit profiles again.Then it worked! Since I've had some connecting issues with opening console with bundled glassfish,which was also fixed by successful logging from SDK installation,I think this could be somehow connected. I'm used to delete amserver folder in my userdir,each time I'm reinstalling Netbeans. Maybe there's something missing,when I install bundled Glassfish "on the green field",something what SDK installer sets by default,maybe some password or configuration file.I think also that Mac and Vista could have something common (other than cloned looks;-)), that is different in Linux,where this issue isn't reproducible. I'll try to reinstall Netbeans,delete amserver folder in the process and then both bundled glassfish with identity from update center and latest SDK.I'll also try this case in WinXP to see if it isn't Vista related.
Created attachment 46397 [details] glassfish server log from Output tab
I reproduced behaviour described in my last post - issue was valid until I logged into AM console (localhost:8080/amserver) as amadmin / admin123. This created folders .portlet-container , amserver and AccessManager and file AMconfig.properties in my home folder (not Netbeans6.0 Home, but my user home).Right after these was done,I'm able to normally edit AM properties in Netbeans6.0 . I tried to experiment with moving folders out and back in a it seems that crucial are especially last two folders and properties file,because if I take out either of this components,edit doesn't work again. However this workaround works only for glassfish I logged to AM console for - in this case older SDK build.This doesn't fix another glassfish instance issue.
First, let's not worried about using glassfish's update center to install AM. I don't think it configures the AM server for you. You have to log onto the AM admin console in order to trigger the configurator. The ee sdk installer does this automatically for you. This explains why after you logged into the am admin console, things start to work. Also, the AccessManager folder in your userdir contains information on whether the am is configured. If you remove it, the next time you log into AM admin console, it will trigger the configurator again. Now, let's concentrate on getting AM to work using ee sdk installer. Please try to do a clean install using the latest ee sdk installer. After installation, try starting the appserver and logging into the appserver admin console (http://localhost:4848/asadmin). Also, try logging into AM's admin console (http://localhost:8080/amserver). If successful, this means AM is up and running. Next, in your IDE, add a new appserver node pointing to this installation and see if you can edit the profile. These are the steps I used everytime and I haven't had any issue editing the profiles.
BTW, the username/password for the appserver is admin/adminadmin and amadmin/adminadmin.
The profiles are editable, once a fresh install of the Amserver-containing Appserver is done through the SDK installer. Previous installs of the Appserver over an existing one appparently corrupted the prior install as some information is retained in a file in the userdir. A fresh install to a different directory enable security profile editing.
I'm afraid I'm experiencing http://www.netbeans.org/issues/show_bug.cgi?id=112443 issue with SDK builds,so Ican't check if it configurates something,but as for bundled Glassfish (the one installed along with full installation) this works as described.As for my last working SDK glassfish it works the same way,it also doesn't install anything until I log into admin console. If this behaviour is correct,I'm afraid however,that we're losing another portion of "out of box" experience for users,since now I have to do complicated setup just to enable Access Manager in NetBeans. I think that we should at least upgrade our guidelines and help system because now it's all too confusing for users. I plan to incorporate all changes into test specification,but there should be also some visible tutorial guiding through setup process. Also current state of error messages in NB is very unsafisfactory - instead of "Initialization failed" or "Server not running" there should be stated,that user should log into AM console to configure AM. Also, if I don't clean manually userdir from AM folders and properties, next time I try to log into AM admin console of different type of glassfish (for me it worked perfectly with bundled one versus SDK),login fails.
Hi Bob, Can we add some information on how to set up the AM from the EE SDK in our help and tutorial? I am reassign this to Bob.
We can. I need a clear path through this as you allude to in your prior note. Is this entirely a doc bug, i.e., is the install experience resolved also per your prior note?)
I've checked SDK and bug 112443 is valid only for Vista and moreover it's eesdk installer related. SDK glassfish on another OS works,so I'll stick with this fact. Current AM use case in NB6 is this: - Install Netbeans 6 (doesn't matter if with or without another glassfish) - Install eesdk glassfish - Start IDE and add eesdk glassfish in Runtime tab - Start glassfish - Run AM server admin console and log in After these steps everything works fine,however problem will occur if userdir isn't cleaned from mentioned folders and files and you try to do the same with different glassfish - in my case I wasn't able to log into AM server console,until I cleaned userdir.
Sorry for confusion caused by last memo in my latest update.This occurs only in very rare scenario and I don't think any user will actually see it.I'll fill this as new issue.
I have, as requested, documented the additional SDK install to ensure that the AMServer is installed correctly -- the information will appear in the Identity SAML tutorial. I have also placed a subset of the information in the help, and also send the aM install information to the NetBeans 6 Beta1 release note writer and to the installation writer.
VERIFIED