Thanks mark for quick reply.
Raised below issue for tracking purpose:
https://bz.apache.org/bugzilla/show_bug.cgi?id=61057
Meanwhile we continue to use ecj-4.5.1 with latest tomcat 8.5.14.
Thanks,
Durga Srinivasu
On Sun, Apr 30, 2017 at 11:52 PM, Mark Thomas wrote:
> On 30/04/17 18:36, Durga
On 30/04/17 18:36, Durga Srinivasu Karuturi wrote:
> Hi,
>
> We have tried migrating tomcat from 8.5.11 --> 8.5.14 for latest security
> fixes and found our jasaperreports functionality is broken.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=495598
>
> I have tried 4.5.1 (from old tomcat 8.
Hi,
We have tried migrating tomcat from 8.5.11 --> 8.5.14 for latest security
fixes and found our jasaperreports functionality is broken.
Reports compilation is failing with unresolved type errors even though all
related jars are in classpath
1. java.util.ResourceBundle cannot be resolved to a t
On 29/04/17 03:47, Arjit Gupta wrote:
> Hi,
>
> I am building tomcat 7.0.77 with java7 on HP-UX(OS) itanium(IA64) processor.
> After building it successful I am running *ant test*.
> Multiple tests are failing due to below exception.
>
> *Exception in thread "Thread-18" java.lang.AssertionError:
On 29/04/17 11:10, Mohammed Manna wrote:
> Hello,
>
> I have retried using the following javac and jasper settings for my project
> (using ANT build) - and it still doesn't reveal those 64K errors even when
> the compilers are the same.
Isn't that good? Doesn't that mean you've found a solution t
On 29/04/17 15:13, George Stanchev wrote:
> TC 8.5.14 and noticed in the logs the following warning:
>
> "The truststoreProvider [AnyCert] does not support the
> certificateVerificationDepth configuration option"
>
> In our case, we're using Shib's AnyCert trust manager to accept any
> client cer
On 29/04/17 16:23, Naveen Nandyala - Vendor wrote:
> Hi Team,
>
> We are using Tomcat "7.0.61.0", and running on SUSE Linux Enterprise
> Server 11 (x86_64), Version 11, and PatchLevel 3. Our tomcat
> instance is going down due to below message,
No it isn't.
Something is shutting down Tomcat.
Th
Hi,
Looks like it is not able to unregistered during closing the DataSource -
which causes memory leak, and Tomcat complains about it.
Check in your web application if any jdbc unregister method using, also try
to move your jdbc drivers to tomcat common lib directory instead of using
in web appli
