Tomcat logging for Internal Server Errors (500)

Hi All, I need some help tracking down a random infrequent Internal Server Error that isn’t getting logged anywhere.  I’m using Tomcat 7.0.53 behind apache httpd with mod_jk 1.2.39. I use new relic application monitoring, and I see in their application error reports that a 500 error from

JNDI initialization since Tomcat 8.0.1

Hi, I'm experimenting with java 8, spring data JPA, hibernate and tomcat 8. Spring Data JPA initializes hibernate on deployment. On tomcat 8.0.0-RC10 everything is fine. Using Tomcat 8.0.1 or newer, an exception is thrown when hibernate tries to fetch the datasource from JNDI:

Re: JNDI initialization since Tomcat 8.0.1

2014-04-13 15:10 GMT+04:00 Christian cm...@famiru.de: Hi, I'm experimenting with java 8, spring data JPA, hibernate and tomcat 8. Spring Data JPA initializes hibernate on deployment. On tomcat 8.0.0-RC10 everything is fine. Using Tomcat 8.0.1 or newer, an exception is thrown when hibernate

Re: JNDI initialization since Tomcat 8.0.1

Is hibernate initialized via a listener in web.xml, or where? I don't know exactly how it is initialized. I use spring annotation configuration with a javax.servlet.ServletContainerInitializer but I don't know, if hibernate gets loaded immediately. Looking at the call stack, it seems that it

When tcnative 1.1.30.dll for windows officially will be released?

Hello I would like to know when tcnative 1.1.30 will be released offically?Second, does this version of 1.1.30 of tcnative will be fix the Heartbleed Best Regards, Noam Gold

Re: JNDI initialization since Tomcat 8.0.1

2014-04-13 19:32 GMT+04:00 Christian cm...@famiru.de: Is hibernate initialized via a listener in web.xml, or where? I don't know exactly how it is initialized. I use spring annotation configuration with a javax.servlet.ServletContainerInitializer but I don't know, if hibernate gets loaded

Re: JNDI initialization since Tomcat 8.0.1

On 13.04.2014 22:02, Konstantin Kolinko wrote: I do not know, what version of hibernate you are using, but if I look at 4.3.x sources [1], the following method mentioned in your stacktrace changes TCCL and thus breaks JNDI: org.hibernate.boot.registry.

Re: Does heartbleeding bug impact on Tomcat 6.x, 7.x and 8.x

Andre, On 12.4.2014 0:51, André Warnier wrote: Ognjen Blagojevic wrote: On 11.4.2014 10:52, André Warnier wrote: 3) if he has recorded past encrypted traffic to/from your server, and saved this recording, then he can at any time go back and decrypt this past traffic, and pick up anything