Re: How to stop org.apache.jasper.servlet.TldScanner.scanJars via my war file's local context.xml rather than altering Tomcat 8?

2016-08-02 Thread Mark Thomas
On 02/08/2016 13:53, Cothren, Craig wrote: > I’m using tomcat 8.0.x so the 8.5 documentation may not apply, but I decided > to try it anyway. > > Added scanAllFiles="false" scanAllDirectories="false”/> to my context.xml. > > Nothing changed. As expected. Read a little further and follow the

Re: How to stop org.apache.jasper.servlet.TldScanner.scanJars via my war file's local context.xml rather than altering Tomcat 8?

2016-08-02 Thread Cothren, Craig
I’m using tomcat 8.0.x so the 8.5 documentation may not apply, but I decided to try it anyway. Added http://tomcat.apache.org/tomcat-8.5-doc/config/jar-scanner.html > > Mark > > > - > To unsubscribe, e-mail:

Define datasource, reference JDBC driver, and see init in console

2016-08-02 Thread KARR, DAVID
I'm attempting to use Tomcat(tomee) to run a REST service that will return some data from some SQL queries (Oracle). I've installed Tomee 7.0.1, which uses Tomcat 8.5.3. The JDBC driver is available from a private enterprise maven repo. I'd prefer to get it from there, as opposed to storing

Re: Problem with Cluster after upgrade to Tomcat 8.0.36.

2016-08-02 Thread false
As I understand that LocalMember - is my local node, and Member - is another node in the cluster and uniqueId's must be different? Вт, 2.8.16, Keiichi Fujino пишет: Тема: Re: Problem with Cluster after upgrade to Tomcat 8.0.36.

Re: jdbc check available database

2016-08-02 Thread Christoph Nenning
> Hello guys, > > I’ve SQL Server database with Tomcat 7 and, when I restart only database, > webapps on Tomcat didn’t works , it show me error to connect to database .. > > In webapp context I use jdbc driver for connect, so there is a kind of > method for retry to connect to database when

Re: Problem with Cluster after upgrade to Tomcat 8.0.36.

2016-08-02 Thread Keiichi Fujino
2016-08-01 22:48 GMT+09:00 false : > Hi all. > > Tomcat-8.0.36; JDK 1.8.0_102; CentOS 6.8. After upgrade from 8.0.28 to > 8.0.36 I have problem with my cluster. I use static membership cluster with > two nodes with BackupManager. After update I have errors in