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.
it appears that there is an issue with glassfish v3 preview that ships with netbeans 6.7 rc 3 in relation to the java 1.6 update 14 release. I had to roll back to jdk 1.6 update 13. I was unable to create a jdbc pool. the web gui for glassfish complained with something on-screen (via the gui) that _SYSTEM was in error. rolled back to update 13, and the messages changed to being unable to resolve the class. I tried adding the jar for postgresql to the app server jvm path options page, but, this did not seem to make any difference, and, the jvm information did not appear to show that this jar file had been added to the classpath. I resorted to placing a copy of the .jar file in the glassfish/lib directory, after which it was now able to find the postgresql classes it needs.
please provide the steps necessary to recreate the issue.
note: I'm using Vista x64 and the 64 bit version of the jdk 1.6 update 14. here are the steps: 1. perform a clean install of netbeans rc3, with the following variations over all default options: set the path for all of the installable items so that they are all within c:\program files\nb67rc3 ie: group netbeans, glassfish v2 and glassfish v3 under the c:\program files\nb67rc3 directory. 2. open windows explorer, and navigate to c:\program files\nb67rc3, and bring up the security settings. alter the permissions os that users of the computer have full access to everything under c:\program files\nb67rc3 3. start netbeans 4. activate the following features: java se, java web and ee, and php options. 5. open the services window 6. expand the servers item, and start glassfish v3 prelude 7. wait for it to start 8. right click on the glassfish v3 prelude item, and select the item that views the admin console 9. click on 'never register' if the registration box appears. 10. click on 'application server' on the left hand panel. 11. click on JVM Settings on the right hand panel. 12. click on 'Path Settings' on the sub panel that appeared. 13. download from http://jdbc.postgresql.org/download/postgresql-8.3-604.jdbc4.jar the jdbc driver for postgresql and save it somewhere on your computer. 14. on the admin console, go down to the 'classpath suffix' and add the path to the location where you stored the above jdbc jar file. 15. save the parameters. 16. restart (from netbeans) the glassfish server. 17. back at the admin console, click the 'home' button and wait for the console to re-initialize and display. 18. drill into the 'resources->jdbc' and click on the 'connection pools'. on the right hand side, select 'new' 19. supply a set of details for the server. eg: name: test1 resource type: javax.sql.DataSource database vendor: PostgreSQL enable 'connection validation->required' checkbox. supply values for the: DatabaseName, Password, PortNumber, ServerName, User. delete the other properties. hit the 'finish' button. you may now see a bunch of error messages in the server log output. 20. you will now be at a point where the list of connection pools is displayed. 21. click on the item you just created, and then click on the 'ping' button. you should see the error message. 22. use the 'application server', 'monitor', 'jvm' and then use the 'configure monitoring' and set the 'jvm' option to 'high' (and save it). now, go back and reselect the 'jvm' and observe the details. nowhere does it mention the jar file that was supposed to be added to the config path.
Thank you for the complete description. Note: since there is a work-around, I am lowering the priority to p2. You may want to use the JDBC driver deployment feature... See: http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_jdbc for a bit more info.
hey, not so quick. the issue I'm seeing here is not just that the server does not see the driver, it's that there is some sort of compatibility issue between glassfish on jdk 1.6 u 14 and anything to do with jdbc drivers. there is more at play here than meets the initial inspection. the error message comes up as something like '_SYSTEM' where it's really trying to say something about an incompatibility with jdk 1.6 u 14. reverting to update 13 sidesteps the issue, but, you're distributing glassfish with update 14 aren't you? evidently there is a more recent build of glassfish v3 prelude that you need to be supplying with netbeans.
mschovanek, could you please look at this issue ? Thanks in advance.
http://wiki.netbeans.org/BugPriorityGuidelines says this should be marked as a p2 issue...
to vkramer: It should be fixed as mentioned here: http://forums.java.net/jive/thread.jspa?threadID=62254&tstart=0#349049 do we have a build with this fix which we can put into 67_patch1?
I am able to reproduce the issues that you have described in this entry. There are actually a couple issues... 1. v3 Prelude does not appear to be compatible with jdk 6 update 14. 2. netbeans doesn't start the server correctly (take into account the classpath changes that a use can make via the admin console). I am writing up an issue for the server's issue tracker... https://glassfish.dev.java.net/issues/show_bug.cgi?id=8608. there is nothing the plugin can do to correct the problem in the server. the user can use the server's Java properties to change the jdk that is used to start the v3 Prelude instance. The incomplete classpath is something that we can fix in the plugin.
thank you for running with this issue guys!
According to comment in the v3 Prelude issue the server part should be already fixed. So marking as 67patch-candidate. Please fix the Nb part ASAP.
Well, the server part is fixed, but the fix is not included in the build of v3 Prelude that we bundle in NB 6.7. It sounds like to really fix it, we would need to get an updated version of the v3 Prelude, right? And that can not be updated through the 6.7 patch. BTW, Peter, I think you meant "Prelude" rather than "Preview" in your original report.
From what I heard, the plan is to produce an updated version of GlassFish v3 Prelude, and put it into an update release of 6.7. Is there anything that needs to be/should be done on the NetBeans side? I am thinking about this comment by Vince: "The incomplete classpath is something that we can fix in the plugin."
The classpath problem is really a p2 in my mind (it should not ship in 6.8). the primary issue that was being reported is clearly a p1 and should be part of the patch.
Please be proactive and fix the things you see are needing attention (even if they are not the main item I was talking about) - eg: netbeans thinking the startup of glassfish v3 prelude has failed is a very annoying issue. perhaps I should open a separate ticket for that....? keep up the good work guys!
I intend to fix it... but it may not be ready for the patch 1 cut-off. Just trying to set expectations.
peter said he would look at this.
V3 plugin does not have full support for launching V3 with all the modifiers possibly in domain.xml (e.g. classpath-prefix, -suffix, etc.) It is time we resolved this, so I'll add full support for all options since they are changeable in Admin GUI now and supported by native glassfish launcher.
that's great news! please do let me know when it's there. thank you very much for taking this on!
The GF v3 prelude part fixed and verified in Nb 6.7.1 FCS build with bundled GF build.
So what is the remaining part that is not fixed yet? Anyone who is familiar with the problem (Peter B, Vince, Peter W), can you please file it as a new issue, so this one can be closed as fixed? Thanks.
I need to wrap up changes to support the classpath attribute specifiers. This is about 90% complete. I can finish it tomorrow.
Just pushed the patch for this - wait for confirmation from main-golden. http://hg.netbeans.org/web-main/rev/7ec0e3cd6572
Are we going to patch this in 6.7.x (I'm guessing too late for 6.7.1?) Let me know, I can make new diff (part of the require code was already committed (6.8 timeframe) and is not represented in the changeset above.)
You are right it's too late for 6.7.1 (aka patch 1). Let's keep the 67patch-candidate status whiteboard; if there is a decision to make patch 2, then you can provide the diff. Right now there is no plan to do patch 2.
Integrated into 'main-golden', will be available in build *200907241401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/7ec0e3cd6572 User: pcw@netbeans.org Log: #167719 - Integrated V3 launcher enhanced to use jvm-config classpath attributes. Related refactorings.