MariaDB Connector Issues

2015-06-01 Thread Cuneo, Nicholas
Hi,

We've been running for a while now using embedded Jetty but due to some 
upcoming infrastructure changes we're migrating to Tomcat 7.  I'm having an 
issue getting my servlet to recognize the mariadb connector
No suitable driver found for jdbc:mariadb://

This has been running in the past with Jetty, so I haven't made any code 
changes.  I've dropped the mariadb-java-client-1.1.8.jar in the tomcathome/lib 
directory as in my experience in the past this was all I needed to do.  However 
since I'm still getting this exception I'm not sure how to debug further.  I've 
tried running tomcat with the debug option
bin/catalina.bat debug
but I'm not really sure how to  use it properly other than running my servlet 
and viewing the classpath.

Any assistance on the matter would be helpful.

Thanks,

Nick Cuneo  /  Software Engineer, Cloud  /  Enterprise Software
Tel: +1 949 517 4802  /  Mobile: +1 949 243 4952
3 Ada  /  Irvine, CA 92618  /  USA
ncu...@tycoint.com  /  www.tyco.com
[cid:image001.png@01D09C6E.3CAA8C50]


This email (including any attachments) may contain information that is private 
or business confidential. If you received this email in error, please delete it 
from your system without copying it and notify sender by reply email so that 
our records can be corrected




This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.


RE: MariaDB Connector Issues

2015-06-01 Thread Cuneo, Nicholas
Apparently with Tomcat7/8 and Java 7+ (we are using java8) you must explicitly 
add the driver in the code:

Class.forName(org.mariadb.jdbc.Driver).newInstance();

I feel like this is a bug with Tomcat7/8 since after Java 6 this was no longer 
required (and indeed worked in Tomcat5 and 6).  Anyway, if anyone else runs 
into that problem they can resolve it.

Thanks,
Nick

From: Cuneo, Nicholas [mailto:ncu...@tycoint.com]
Sent: Monday, June 01, 2015 1:24 PM
To: Tomcat Users List
Subject: MariaDB Connector Issues

Hi,

We've been running for a while now using embedded Jetty but due to some 
upcoming infrastructure changes we're migrating to Tomcat 7.  I'm having an 
issue getting my servlet to recognize the mariadb connector
No suitable driver found for jdbc:mariadb://

This has been running in the past with Jetty, so I haven't made any code 
changes.  I've dropped the mariadb-java-client-1.1.8.jar in the tomcathome/lib 
directory as in my experience in the past this was all I needed to do.  However 
since I'm still getting this exception I'm not sure how to debug further.  I've 
tried running tomcat with the debug option
bin/catalina.bat debug
but I'm not really sure how to  use it properly other than running my servlet 
and viewing the classpath.

Any assistance on the matter would be helpful.

Thanks,

Nick Cuneo  /  Software Engineer, Cloud  /  Enterprise Software
Tel: +1 949 517 4802  /  Mobile: +1 949 243 4952
3 Ada  /  Irvine, CA 92618  /  USA
ncu...@tycoint.commailto:ncu...@tycoint.com  /  
www.tyco.comhttp://www.tyco.com
[cid:image001.png@01D09C6E.3CAA8C50]

This email (including any attachments) may contain information that is private 
or business confidential. If you received this email in error, please delete it 
from your system without copying it and notify sender by reply email so that 
our records can be corrected




This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.



This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.


RE: Deploying JerseyWS 2.8 w/o web.xml

2014-06-02 Thread Cuneo, Nicholas
We are using Ivy for our dependency manager, but I'm not exactly following what 
you mean.  Are you suggesting  I'm supplying a jar file in my war that  doesn't 
need to be there because Tomcat has its own version of it?

Thanks,
Nick


-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, May 30, 2014 4:55 PM
To: Tomcat Users List
Subject: Re: Deploying JerseyWS 2.8 w/o web.xml

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nick

On 5/30/14, 5:03 PM, Cuneo, Nicholas wrote:
 We are trying to deploy a webservice to tomcat 8.0.5 using Jersey WS
 2.8.  In the Jersey documentation it mentions deploying without the
 need for a web.xml in your war file using annotations, so I thought
 I’d give that a  try.

 However, when I go to deploy my webservice Tomcat is throwing the
 exception below, I can’t figure out what might be the issue.



 Some notes about our environment in case  they come into play:

 The webservice  is compiled with java 8.

 Tomcat is running on a linux server.

 As per the Jersey documentation, I have a class annotated with
 @ApplicationPath which extends ResourceConfig.  Our webservices exist
 in a separate package which is being loaded using the
 packages() function.



 30-May-2014 20:57:22.592 SEVERE [localhost-startStop-4]
 org.apache.catalina.startup.ContextConfig.processServletContainerIniti
 alizers


Failed to process JAR found at URL [/api] for
 ServletContainerInitializers for context with name [{1}]

 java.io.IOException: java.lang.ClassCastException: Cannot cast
 org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer
 to javax.servlet.ServletContainerInitializer

It looks like you might have a JAR file in WEB-INF/lib that contains 
ServletContextInitializer or something similar. Tomcat should veto the loading 
of such classes, but something may have slipped-by.

Remember that runtime class is classloader + class, so the above error may be 
confusing: JerseyServletContainerInitializer does in fact extend 
ServletContainerInitializer (at least given their current API
javadoc) so the problem is likely that the ClassLoaders do not match.

Perhaps you are using Maven and it's unaware that Tomcat provides some of the 
javax.* packages itself?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTiRpRAAoJEBzwKT+lPKRYeZUP/RQ4NlB9yxhGaXVdBNoPVKdq
L8DakkbBlHLOVnOgEcyK++s5iOUFXHSeRVJuTIDQs0fAiDnMjC4V+3wynCJbzgz1
174AsN50+LEG4wvJ+rVwS0yBaEzwn7bHKY5zR/J0Rrry4Ms6J4xTuuL8nofr/qkJ
muNFagg+Ypxfbo9qH0Y/XgFMU7IVy4+ti3dtVKXCZJjjOkaRC9DB6A/Win83onAC
FU8zO2bgrTyGtJFsF1IK5VE9V4lafSIy8HgszWUm3zbG1dmrXpii65vdF+gSBALs
kyTN4bekR15O9ubuHXspqZwpJyEBxRLy71048PEHg0gQ4BCluy6nmksxeRTTtVsH
30VRsp2p/JlUHIJWrB/mJ98Co0hN5h2dwzodARarTm8Qm9P/ZDCDzOLj2cHgv6cY
AodGJYuLcNDiwfyv74kVyf0sr/mj54ghZ61ttLYPpqwcZyDTf9dmPiS/SuB9uSWa
oHOcg36v6s0FSIXlvpM+MZ7R1n+m/Dsj2u5dRkt/L/WzNBR7BSQqfs6vPiYoz5H7
IVRhgxYGZLXTmhNx/0yk14zr3EF8Ww84oXlyXNui2kM6jpGgkbleSV/1dkd6F3Ud
/mZxY8a5rqrqrEN/qgFRx0gk2LEtnQhE8p4qHT/2ij0Q1UQXMpPQBL4bdLIe4Zep
FPjzCGsmV9amCd6jvJU2
=6tVn
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: Deploying JerseyWS 2.8 w/o web.xml

2014-06-02 Thread Cuneo, Nicholas
I think you are correct, maybe I need to exclude some jars from my bundle?

find . -name *.jar | xargs grep ServletContainerInitializer.class
Binary file ./servlet-api.jar matches

find ../webapps/api/WEB-INF/lib -name *.jar | xargs grep 
ServletContainerInitializer.class
Binary file ../webapps/api/WEB-INF/lib/jersey-container-servlet-jar-2.8.jar 
matches
Binary file ../webapps/api/WEB-INF/lib/javax.servlet-api-jar-3.0.1.jar matches

Thanks,
Nick


-Original Message-
From: Cuneo, Nicholas [mailto:ncu...@tycoint.com]
Sent: Monday, June 02, 2014 9:25 AM
To: Tomcat Users List
Subject: RE: Deploying JerseyWS 2.8 w/o web.xml

We are using Ivy for our dependency manager, but I'm not exactly following what 
you mean.  Are you suggesting  I'm supplying a jar file in my war that  doesn't 
need to be there because Tomcat has its own version of it?

Thanks,
Nick


-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, May 30, 2014 4:55 PM
To: Tomcat Users List
Subject: Re: Deploying JerseyWS 2.8 w/o web.xml

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nick

On 5/30/14, 5:03 PM, Cuneo, Nicholas wrote:
 We are trying to deploy a webservice to tomcat 8.0.5 using Jersey WS
 2.8.  In the Jersey documentation it mentions deploying without the
 need for a web.xml in your war file using annotations, so I thought
 I’d give that a  try.

 However, when I go to deploy my webservice Tomcat is throwing the
 exception below, I can’t figure out what might be the issue.



 Some notes about our environment in case  they come into play:

 The webservice  is compiled with java 8.

 Tomcat is running on a linux server.

 As per the Jersey documentation, I have a class annotated with
 @ApplicationPath which extends ResourceConfig.  Our webservices exist
 in a separate package which is being loaded using the
 packages() function.



 30-May-2014 20:57:22.592 SEVERE [localhost-startStop-4]
 org.apache.catalina.startup.ContextConfig.processServletContainerIniti
 alizers


Failed to process JAR found at URL [/api] for
 ServletContainerInitializers for context with name [{1}]

 java.io.IOException: java.lang.ClassCastException: Cannot cast
 org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer
 to javax.servlet.ServletContainerInitializer

It looks like you might have a JAR file in WEB-INF/lib that contains 
ServletContextInitializer or something similar. Tomcat should veto the loading 
of such classes, but something may have slipped-by.

Remember that runtime class is classloader + class, so the above error may be 
confusing: JerseyServletContainerInitializer does in fact extend 
ServletContainerInitializer (at least given their current API
javadoc) so the problem is likely that the ClassLoaders do not match.

Perhaps you are using Maven and it's unaware that Tomcat provides some of the 
javax.* packages itself?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTiRpRAAoJEBzwKT+lPKRYeZUP/RQ4NlB9yxhGaXVdBNoPVKdq
L8DakkbBlHLOVnOgEcyK++s5iOUFXHSeRVJuTIDQs0fAiDnMjC4V+3wynCJbzgz1
174AsN50+LEG4wvJ+rVwS0yBaEzwn7bHKY5zR/J0Rrry4Ms6J4xTuuL8nofr/qkJ
muNFagg+Ypxfbo9qH0Y/XgFMU7IVy4+ti3dtVKXCZJjjOkaRC9DB6A/Win83onAC
FU8zO2bgrTyGtJFsF1IK5VE9V4lafSIy8HgszWUm3zbG1dmrXpii65vdF+gSBALs
kyTN4bekR15O9ubuHXspqZwpJyEBxRLy71048PEHg0gQ4BCluy6nmksxeRTTtVsH
30VRsp2p/JlUHIJWrB/mJ98Co0hN5h2dwzodARarTm8Qm9P/ZDCDzOLj2cHgv6cY
AodGJYuLcNDiwfyv74kVyf0sr/mj54ghZ61ttLYPpqwcZyDTf9dmPiS/SuB9uSWa
oHOcg36v6s0FSIXlvpM+MZ7R1n+m/Dsj2u5dRkt/L/WzNBR7BSQqfs6vPiYoz5H7
IVRhgxYGZLXTmhNx/0yk14zr3EF8Ww84oXlyXNui2kM6jpGgkbleSV/1dkd6F3Ud
/mZxY8a5rqrqrEN/qgFRx0gk2LEtnQhE8p4qHT/2ij0Q1UQXMpPQBL4bdLIe4Zep
FPjzCGsmV9amCd6jvJU2
=6tVn
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action

RE: Deploying JerseyWS 2.8 w/o web.xml

2014-06-02 Thread Cuneo, Nicholas
The only error I saw in my catalina logs was the one I copied earlier.
Indeed, removing javax.servlet-api fixed the issue.

Thanks,
Nick


-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, June 02, 2014 9:58 AM
To: Tomcat Users List
Subject: Re: Deploying JerseyWS 2.8 w/o web.xml

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nicholas,

On 6/2/14, 12:38 PM, Cuneo, Nicholas wrote:
 I think you are correct, maybe I need to exclude some jars from my
 bundle?

 find . -name *.jar | xargs grep
 ServletContainerInitializer.class Binary file ./servlet-api.jar
 matches

 find ../webapps/api/WEB-INF/lib -name *.jar | xargs grep
 ServletContainerInitializer.class Binary file
 ../webapps/api/WEB-INF/lib/jersey-container-servlet-jar-2.8.jar
 matches Binary file
 ../webapps/api/WEB-INF/lib/javax.servlet-api-jar-3.0.1.jar matches

Yes, those are going to be a problem. and need to be removed from WEB-INF/lib

You should also remove anything that provides JSP or EL APIs.

Like I said, Tomcat should be protecting itself against such classes being 
loaded... are there any warnings during deployment that JAR files are being 
rejected?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTjK0XAAoJEBzwKT+lPKRYnNoQALTKiIDycnKxYmAWt7QdQy2c
evQYKt1xEQwDUq1qrng7KDWaF5qgy6udm682z0RLgfNVQOmklXEkR8TTnPyuhaDY
QNrTg0ojQytXcVdBiyqiectVTkj9Bqf3nATGqUN20CI2zUuEvK1Bt+dvGzBTRNji
ckJSgNZyA6dbODr84jLZG4s5eVwrS+Ee68EtDuJSxKPtjWiBwMtzJ+1inYL9xHY+
jUXC71UCroj7typlNVeSTL6pUlPrs1xq2FJGNQn6Q5IecevLHK08EZlKkcqVdc5A
BH8/VlSnFgYBIDXCWY+UydFT+M3GmwLX5h120oTczY9doPAHF0W4s6anrzt6hPc7
mMOjHhBbgyMi2EigS/kGCpK4opiLTkGouba8JQQPmc6IhMRZyaEW3WyDDfaFlRGQ
w3cN/mQ0QKY0sirOPa4O2wqeH6rW/tG6i20MCKDOkT9X7KXEvLkvfTZDuQyi7FOI
Ew81AztOODBci6MByrgt7MVPmhLd0I+jaqAERLk3bLAKbd5CFDe5yHo5l3f+JMGB
dS+cQUFLu51GteTLLnhoiyZpER6OXKliZxytlbqbMfyj+iuMvkbnLy+X8XAaiEWk
+BGskIIqLi70c4MOLbZwlVQxQp+DLuQhwWmIQ3Fa+Gf6gF1IhUhY/5AUxKz4hK3P
GdRQ++l8m626y7pfS3Cy
=LKd/
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.


Deploying JerseyWS 2.8 w/o web.xml

2014-05-30 Thread Cuneo, Nicholas
Hi,

We are trying to deploy a webservice to tomcat 8.0.5 using Jersey WS 2.8.  In 
the Jersey documentation it mentions deploying without the need for a web.xml 
in your war file using annotations, so I thought I'd give that a  try.
However, when I go to deploy my webservice Tomcat is throwing the exception 
below, I can't figure out what might be the issue.

Some notes about our environment in case  they come into play:
The webservice  is compiled with java 8.
Tomcat is running on a linux server.
As per the Jersey documentation, I have a class annotated with @ApplicationPath 
which extends ResourceConfig.  Our webservices exist in a separate package 
which is being loaded using the packages() function.

30-May-2014 20:57:22.592 SEVERE [localhost-startStop-4] 
org.apache.catalina.startup.ContextConfig.processServletContainerInitializers 
Failed to process JAR found at URL [/api] for ServletContainerInitializers for 
context with name [{1}]
java.io.IOException: java.lang.ClassCastException: Cannot cast 
org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer to 
javax.servlet.ServletContainerInitializer
at 
org.apache.catalina.startup.WebappServiceLoader.loadServices(WebappServiceLoader.java:185)
at 
org.apache.catalina.startup.WebappServiceLoader.load(WebappServiceLoader.java:151)
at 
org.apache.catalina.startup.ContextConfig.processServletContainerInitializers(ContextConfig.java:1597)
at 
org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1125)
at 
org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:768)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5058)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:702)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:976)
at 
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1762)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassCastException: Cannot cast 
org.glassfish.jersey.servlet.init.JerseyServletContainerInitializer to 
javax.servlet.ServletContainerInitializer
at java.lang.Class.cast(Class.java:3258)
at 
org.apache.catalina.startup.WebappServiceLoader.loadServices(WebappServiceLoader.java:182)
... 19 more


Thanks,

Nick Cuneo  /  Software Engineer, Cloud  /  Tyco Retail Solutions
Tel: +1 949 517 4802  /  Mobile: +1 949 243 4952
3 Ada  /  Irvine, CA 92618  /  USA
ncu...@tycoint.com  /  www.tyco.com
[cid:image001.png@01CF7C0F.E25B4660]


This email (including any attachments) may contain information that is private 
or business confidential. If you received this email in error, please delete it 
from your system without copying it and notify sender by reply email so that 
our records can be corrected




This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.