Skip to main content

Netbeans 7.3 And MySQL Java Connector Versioning Error


Error code 1064, SQL state 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT' at line 1

 While I was developing J2EE application (using Netbeans 7.3 as my IDE of choice and MYSQL as DB) some days ago, I stumble on the error above.

 At first, I thought is was my application querying problem until I made  a little search on the internet. I came across this link which comment helped in solving the issue. 

 The solution is:

  1. To download the latest version of MySQL Java Connector,
  2. Copy the jar file into "C:\Program Files\NetBeans 7.3\ide\modules\ext" directory
  3. Open Netbeans Services Panel - Open the Database Node - Open the Drivers Node -Right -Click On the MYSQL(Connector/J Driver) and select Customize
  4. On the customize panel, click add and point to the jar file you copied to "C:\Program Files\NetBeans 7.3\ide\modules\ext" 
  5. Delete the old path that existed on the customized panel.
  6. Click Ok And Restart Netbeans.


Comments

Post a Comment

Popular posts from this blog

Fix HTTP error code 513 on Wildfly

Description :  Many users have reported a network issue where they see a large number of connections in TIME_WAIT and IDLE states. This indicates that the connections are not being closed properly by the server or the client.  When I analyzed the network traffic, I found that the server was sending HTTP Error 513 to the client, which means that the server is overloaded and cannot handle more requests. The client was also logging a socket close event, which means that the client was terminating the connection. This can be simulated using Jmeter. The HTTP error code 153 resulted from the max concurrent connection limit reached, and the allowed queue was also full. This issue can cause performance degradation and resource wastage on both the server and the client. To resolve this issue, we recommend the following steps: Resolution :  1. Investigate the process of holding onto the connection longer than necessary. 2. Increase the server capacity or scale up the server to handle mo
Post a Comment
Read more

Wildfly EJB Remote Client Exceptions.......

Below are exceptions and the solutions I applied while developing a remote client enterprise application. To start with, enable debug for your application server to see the detail and good luck troubleshooting. Exceptions : Starting with  java.lang.ClassNotFoundException: org.hibernate.collection.internal.Persistent......... Solution : I fixed the exception be adding hibernate Entity Manager Dependencies. Exception: Error javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial Solution : Add JBOSS-CLIENT Dependencies to your project Exception : IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling Solution : Confirm that your EJB module have been deployed. Exception : org.jboss.naming.remote.client.initialcontextfactory wildfly     javax.naming.NamingException: WFLYNAM0027: Failed instantiate Initia
Post a Comment
Read more