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.

Bug 147320 - V3:Sample Java Web JsfJpaCrud/WebJps does not work
Summary: V3:Sample Java Web JsfJpaCrud/WebJps does not work
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-16 01:12 UTC by davisn
Modified: 2009-03-30 05:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (66.37 KB, text/plain)
2008-09-16 01:13 UTC, davisn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description davisn 2008-09-16 01:12:28 UTC
-javax.el.ELException: Exception [EclipseLink-4002] occurs when execute the sample
-The problem also happens with JsfCrud and WebJps which requires database connection

Steps To Reproduce:
1. Install NB 6.5 nightly All Trunk build (09/15/2008)
2. Start NB IDE
3. Create Sample > Java Web > JsfJpaCrud project
4. Change the runtime for GF V2 to GF V3
5. Select run > click at any link in the JsfJpaCrud project to execute 
BUG: 
     HTTP Status 500 -
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.0.1 (Build 1.0 - 
20080827)): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated 
because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection 
refused: connect.
Error Code: 0
root cause
javax.el.ELException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.0.1 (Build 1.0 - 20080827)): 
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated 
because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection 
refused: connect.
Error Code: 0
root cause
Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.0.1 (Build 1.0 - 20080827)): 
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated 
because: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection 
refused: connect.
Error Code: 0
root cause
java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: 
java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused: connect.
Comment 1 davisn 2008-09-16 01:13:32 UTC
Created attachment 69913 [details]
messages.log
Comment 2 Vince Kraemer 2008-10-02 01:12:28 UTC
the db server wasn't started....

we could add starting JavaDB to the start processing... but folks have complained about that in the past... which is why
we don't do that automagic when we start V3.
Comment 3 Vince Kraemer 2008-10-02 01:19:04 UTC
autostart needs UI. we are past UI and feature freeze.
Comment 4 Vince Kraemer 2008-10-25 05:27:10 UTC
this must get resolved in 7.0 time frame. raising to "blocking level"...
Comment 5 Vince Kraemer 2008-11-03 16:47:25 UTC
Note... this is getting lowered to P3... which is the level that it was originally... I had raised the priority to force
it to be a blocker for 7.0... not as a blocker for 6.5... but the dashboard is a bit confused...
Comment 6 Vince Kraemer 2009-03-30 05:28:53 UTC
this is fixed...

http://hg.netbeans.org/main/rev/9b6d17383358