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.
Apologies if this is logged under an incorrect heading. ACTION: Use Add Server Instance to create SJSAS instance. Enter Platform Folder location, leave all defaults and click Next. EXPECTED; Server instance to be created and displayed under Runtime -> Servers. ACTUAL: Occasionally I receive a message that it failed to create an instance and to look in the server log. Note: The frequency with which this occurs is quite small - say 1/20 - 30 times. It is more of an annoyance than anything. Workaround: Repeat the steps and it works. Screenshot supplied - no server log or updates exist - although message tells user to look in the server log.
Created attachment 31984 [details] Screenshot for 80552
Please attach the ide's log file if you see this again. The message is coming from the j2eeserver layer, but it is probably calling something from the plugin that has failed. Setting to future, since I haven't been able to reproduce this yet.
Now attaching IDE log as it's just happened again. So, I downloaded RC1 of NetBeans5.5 and installed. Using a new user directory, I then went to the Runtime tab and tried Add Server. I'm using GF v2 b15. I fill in the platform folder location with register local default domain (Note this domain has been used before successfully with other NB versions) and press Finish. The domain was not previously running prior to doing these steps. On four occasions I receive 'Failed to create instance Sun Java System Application Server. See the server log file for details'. I will now try and exit NB and restart to see what happens. Okay, so restarted and repeated steps and now okay. So sending log with failures and success.
Created attachment 35048 [details] IDE Messages log showing failures
it looks like the j2eeserver layer could be a bit nicer when the about how it handles the failed rename operation...
Seems to be a duplicate of issue 113360 *** This issue has been marked as a duplicate of 113360 ***