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 # : 200810111401 ] [ JDK VERSION : 1.6.0_06 ] Hi, On a regular basis, and since I'm using build from late September, I get this stacktrace (partially shown) Caused by: java.sql.SQLException: Error in allocating a connection. Cause: No PasswordCredential found at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:115) at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.jav a:145) when restarting my EAR project. I can solve occasionally this by undeploying and deploying the application and stopping GF2v2ur2 in between (Undeploy the app, stop the AS, run/debug the project). I never had this problem in NB61, but yesterday I opened my project in NB61 again and faced the same problem. As if the problem is in the build scripts instead of something else. Iwan
Created attachment 71736 [details] The EAR files
Created attachment 71737 [details] The EJB files
Created attachment 71738 [details] The WAR files
Attached projects are incomplete (only NB metadata). Also, please add full stacktrace.
Created attachment 71770 [details] This is taken from the server.log of yesterday. It shows a relevant part of the log.
I found request for filing similar bug agains serverplugins on http://www.nabble.com/Re:-Database-connectivity-error-using-visual-webpack- td14793850.html under some conditions, so I'm reassigning.
please attach any files named sun-resources.xml that are in the projects used by this ear. the domain.xml file for server that is having this problem would be useful, too.
I can consistently reproduce this by making sure that the deployment gets a timeout and then hit CTRL-F5 again. In this case I get this problem. Iwan
Created attachment 71808 [details] Requested sun-resources.xml from the EJB project
Created attachment 71809 [details] Requested sun-resources.xml from the WAR project
Created attachment 71810 [details] Requested domain.xml from the server
Reporter provided us with requested files.
Looking at the sun-resources.xml's, I don't see any issues. But could you try to ping the connection pool"derby_netPool" from the admin console. Is the ping successful?
Can you tell me how to ping the pool? Just to let you know, this problem occurs consistently when the deployment timed out and I try to deploy again while the server is running. The problem every now and then happens even when the deployment didn't time out the first time around. Iwan
To Ping the connection pool, - Launch using the 'View Admin Console' action (from the server node in Services tab) - Navigate to the Connection Pool - 'derby_netPool' (Resources > JDBC > Connection Pools > derby_netPool) - There will be a 'Ping' button on the right side
As per your instructions, the ping succeeds.
Just an update to the matter: I followed Vince's instructions for setting up NB65 (dev 200810150201) and hit CTRL-F5 and the debug session started successfully. I hit CTRL-F5 again (without changing anything in the sources or whatsoever) and I get this issue (150051). I hit CTRL-F5 again, and the same problem occurs. When I now click the double arrows in the GF2 output window and according to the popup-hint restart the server, all goes well again. Iwan
I followed the steps in IZ 149993 to reproduce this issue and so far I have not been able to. Running in debug (CTRL-F5) started the server in debug mode and the browser opened. Successive CTRL-F5 (I tried at least 5 times) went through and the main page was launched several times correctly. Since the Ping succeeds, that means the connection pool is available and able to connect to the database The attached server.log shows this error, RAR7099: The mcf being used to allocate the connection and the MCF in the pool are not equal.|#] before the error message regarding allocating a connection. I am pinging the server team to identify what could cause this message.
Both the EJB & WAR projects have a JDBC resource each which refer to the same connection pool 'derby_netPool'. The properties of the this pool are slightly different between the two projects. Since connection pools of the same name are present in the two projects, each deploy results in re-register of the connection pool if no changes have been made. The server team indicated that when JDBC driver vendor specific properties are changed (or added) application server restart or application redeployment is required. Since each deploy of the application is causing the Pool to be updated causing the issue. Rename the connection pool in one of these projects to a unique name should resolve this error. I have attached a modified sun-resources.xml for the ejb project. The connection pool and the associated reference to it in the JDBC Resource definition have been changed to make it unique.
Created attachment 73155 [details] modified sun-resources.xml for EJB project
User was not able to reproduce this in RC1 and RC2. Closing issue.