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 175389 - com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error: ** BEGIN NESTE
Summary: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No oper...
Status: RESOLVED DUPLICATE of bug 175265
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-25 17:21 UTC by dako3256
Modified: 2009-10-25 19:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 150167


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dako3256 2009-10-25 17:21:44 UTC
Build: NetBeans IDE 6.7.1 (Build 200907230233)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows XP, 5.1, x86

User Comments:
GUEST: Editing SQL query in PHP file

GUEST: just trying to get sql auto completion to work

GUEST: mysql autocompletion

GUEST: just trying to get the sql auto-completion, It had already happend a few times. This is boring because I got to restart netbeans in order to make it work !!!!

dako3256: Inserting code into file, was using (ctrl+spacebar) for auto-complete.

gawan: after write "SELECT FROM " I press CTRL+SPACE

GUEST: trying to get the sql auto-completion

GUEST: Attempting to launch sql code complete in a php project using ctrl + space.



Stacktrace: 
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error:


** BEGIN NESTED EXCEPTION ** 

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException
MESSAGE: The last packet successfully received from the server was41575 seconds ago.The last packet sent successfully to the server was 41575 seconds ago, which  is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.

STACKTRACE:

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was41575 seconds ago.The last packet sent successfully to the server was 41575 seconds ago, which  is longer than the server configured value of 'wai
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
        at com.mysql.jdbc.Util.getInstance(Util.java:381)
Comment 1 Jiri Rechtacek 2009-10-25 19:40:17 UTC

*** This issue has been marked as a duplicate of 175265 ***