Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Coderanch by northfield Sid, 1 year ago
[Microsoft][ODBC Driver Manager] Data source name too long at ... org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485) ... org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
via Oracle Community by 807543, 1 year ago
[Microsoft][ODBC Driver Manager] Data source name too long at ... org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485) ... org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
via Eclipse Bugzilla by amitb74, 2 years ago
[Microsoft][ODBC Visual FoxPro Driver]Record is not locked. Error Code: 703 Call: UPDATE pellet_order SET plo_actual_amount = ?, plo_challenge = ?, eqp_id_destination = ?, plo_hold = ?, itm_density_uom = ?, plo_run_number = ?, plo_sequence = ? WHERE
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name too long
at
...
org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
...
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)	at java.lang.Thread.run(Thread.java:484)