The Apache Tomcat team announces the immediate availability of Apache Standard
Taglib 1.2.5.
Apache Standard Taglib is an open source software implementation of the JSP
Standard Tag Library (JSTL) technology.
This release supports JSTL version 1.2 and includes minor bug-fixes to the
previous 1
Thanks Akbar,
It's worked.
Regards,
Vijay S
On Thu, Mar 19, 2015 at 10:31 PM, Akbar Thanakalacheruvu <
akb...@sumtotalsystems.com> wrote:
>
> -Original Message-
> From: Vijay Karthick [mailto:vijaykarthic...@gmail.com]
> Sent: Thursday, March 19, 2015 12:11 PM
> To: users@tomcat.apache
Christopher Shultz wrote:
//
Time to upgrade. Tomcat is hideously out of date (probably because you are
using RedHat's Tomcat package), at least by version number. I'm not sure what
RedHat does (if anything) about security fixes, etc. but a vanilla 6.0.18 is
probably vulnerable and has been for
Hi,
2015-03-19 5:34 GMT+02:00 Thusitha Thilina Dayaratne :
>
> Hi Chris,
>
> Thanks a lot for the quick response. Please find inline answers.
>
> On 3/18/15 5:39 AM, Thusitha Thilina Dayaratne wrote:
> >> I'm in the process of migrating embedded tomcat 7.0.59 application
> >> to Tomcat 8.0.20. Tom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thusitha,
On 3/18/15 11:34 PM, Thusitha Thilina Dayaratne wrote:
> Hi Chris,
>
> Thanks a lot for the quick response. Please find inline answers.
>
> On 3/18/15 5:39 AM, Thusitha Thilina Dayaratne wrote:
>>> I'm in the process of migrating embedde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vijay,
On 3/19/15 12:11 PM, Vijay Karthick wrote:
> In SAP BO environment, the SSL has been enabled in the Tomcat7
> version. However, the Tomcat is not initializing. Its states that
> password error. I've recreated the keystore file. However, we're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric,
On 3/19/15 11:15 AM, Eric Robinson wrote:
> Thanks for the feedback. We run various versions of RHEL (5.5 to
> 6.3) x64. Tomcat is mostly 6.0.18. Java is mostly 6u21 x 64.
Time to upgrade. Tomcat is hideously out of date (probably because yo
-Original Message-
From: Vijay Karthick [mailto:vijaykarthic...@gmail.com]
Sent: Thursday, March 19, 2015 12:11 PM
To: users@tomcat.apache.org
Subject: Fwd: SSL Issue on the 443 port on tomcat7
Hi,
In SAP BO environment, the SSL has been enabled in the Tomcat7 version.
However, the Tomca
> -Original Message-
> From: Vijay Karthick [mailto:vijaykarthic...@gmail.com]
> Sent: Thursday, March 19, 2015 11:11 AM
> To: users@tomcat.apache.org
> Subject: Fwd: SSL Issue on the 443 port on tomcat7
>
> Hi,
>
> In SAP BO environment, the SSL has been enabled in the Tomcat7 version.
>
On 3/19/2015 12:11 PM, Vijay Karthick wrote:
Hi,
In SAP BO environment, the SSL has been enabled in the Tomcat7 version.
However, the Tomcat is not initializing. Its states that password error.
I've recreated the keystore file. However, we're unable to fix it. Please
refer the Log on the Tomcat
Hi
Thanks for quick response.
> Hi,
>
> I'm having an extended StandardJarScanner to scan for jar files which are
> located in a custom location. In tomcat 8 Jar scan filters have been
> introduced. Is i possible to scan my custom location without extending the
> StandardJarScanner in Tomcat 8?
>
Hi,
In SAP BO environment, the SSL has been enabled in the Tomcat7 version.
However, the Tomcat is not initializing. Its states that password error.
I've recreated the keystore file. However, we're unable to fix it. Please
refer the Log on the Tomcat folder.
Server.xml :
The tomcat logs fo
On 19/03/2015 16:00, Thusitha Thilina Dayaratne wrote:
> Hi,
>
> I'm having an extended StandardJarScanner to scan for jar files which are
> located in a custom location. In tomcat 8 Jar scan filters have been
> introduced. Is i possible to scan my custom location without extending the
> StandardJ
Hi,
I'm having an extended StandardJarScanner to scan for jar files which are
located in a custom location. In tomcat 8 Jar scan filters have been
introduced. Is i possible to scan my custom location without extending the
StandardJarScanner in Tomcat 8?
In the [1] it say that we can specify comma
> PSYoungGen total 95808K, used 22323K [0x2aaac377,
> 0x2aaaca21, 0x2aaaca21)
> eden space 82432K, 10% used
> [0x2aaac377,0x2aaac402f7f8,0x2aaac87f)
> from space 13376K, 99% used
> [0x2aaac87f,0x2aaac94fd5a8,0x2aaac950)
>
Do NOT cross-post questions to the users list and the dev list. All this
does is annoy the very people you are relying on to take time out of
whatever else they are doing to help you.
If you aren't sure where to ask, user the users list.
On 19/03/2015 11:50, Thusitha Thilina Dayaratne wrote:
> Hi
Hi All,
Prior to Tomcat 7.0.58, we are able to set the context as "/". In the code
it will go to else part and set the context without any issues.
public void setPath(String path) {
if (path == null || (!path.equals("") && !path.startsWith("/"))) {
this.path = "/" + path;
Eric, if you are looking for a reasons and think, what can be done
with OOMs, take a look at this page:
http://www.oracle.com/technetwork/articles/java/vmoptions-jsp-140102.html
There is an options:
-XX:-HeapDumpOnOutOfMemoryError - it will make heapdump on OOM.
-XX:HeapDumpPath=./java_pid.hprof -
Hi,
I'm in the process of migrating to a embedded tomcat 7.0.59 application to
tomcat 8.0.20. In the application i'm setting the context as "*/*" This
works fine in tomcat 7
But in Tomcat 8 when I set the context as "*/*", internally it is set as "".
Is this a bug in Tomcat 8?
Thanks
Best Regar
19 matches
Mail list logo
