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.
1. Create the sample Depot application and do the setup steps described in the HOWTO 2. Run the application (with GlassFish v3 set as the deployment server) Application is not deployed and exception is printed in the server log. I am using v3 promoted build 21.
Created attachment 68613 [details] Exception from the server output
Looks like GF does not use the bundled JRuby. Could this be caused by the update to JRuby 1.1.4? BTW, when I use an older build of GlassFish (the one you get when you choose to download it by the plugin), I get a different exception (attached), but things still don't work.
Created attachment 68616 [details] Exception with an older build of GF
Reproducible with GF V3 b20 too. But with fresh userdir it works fine. (See: ${userdir}/config/GlassFish/Instances/.nbattrs)
> Looks like GF does not use the bundled JRuby V3 plugin will inject whatever the NetBeans bundled JRuby install is when starting GlassFish. There are a few loopholes where this might not happen and maybe you ran across one of those. But in general it should just work, even across an upgrade. That said, I'm getting the impression that the 1.1.4 upgrade changed a number of JRuby api's and since this was just released and integrated last night, I have not looked into the impact. It will take a few days to shake things out. We don't guarantee stability of the user dir between individual development builds, IIRC.
The second exception is fallout from JRuby 1.1.4 upgrade. The next promoted build of GlassFish should resolve that one. I'd really like to know the steps required to reproduce the first exception. I know one way and that way is not a P2. Since this is filed as a P2, I'd like to know the P2 way.
Here are my steps: 1. Download the zip-based distribution of NetBeans (I used Hudson build 3678) 2. Add GF v3 Prelude build to the Services tab (I used daily build from Sep 4) 3. Create a new Rails app with "Built-in JRuby 1.1.4" as the Ruby platform and the v3 Prelude build as the server 4. Click Run on this Rails app
I tried your steps with current builds and cannot reproduce -- In particular, if (a) the server is NOT running and (b) you start the Rails app via <Run> on it's project/popup menu, then this exception should _never_ happen. If, on the other hand, you started the server from it's own start menu first, immediately after installing it and only then selected <Run> to execute the Rails app, you could see this exception. In that case, I know what the problem is. Stopping the server and selecting <Run> again will fix it and you should also never see it again for that server install.
You are right, I can only reproduce with the steps you described. So this is not a P2 - I am downgrading to P3, but this may even be a P4.
Changed subject to reflect consensus on revised description.
Assigned engineer: please correct the tm value. nb 6.7 has shipped, so a tm of 6.7 is invalid at this point
pickup half of pcw's issues
dropping to p4 with tm of TBD
it looks like this is similar to issue 174025. Please reopen if you can reproduce it in recent builds...