-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 2/6/19 12:21, James H. H. Lampert wrote:
> Thanks. I do have some follow up questions
>
> On 2/6/19, 1:04 AM, Mark Thomas wrote:
>> On the TLS Connector:
>>
>> sslEnabledProtocols="TLSv1.1,TLSv1.2"
>
> Ok. So the active connector we cur
On 06/02/2019 17:21, James H. H. Lampert wrote:
> Thanks. I do have some follow up questions
>
> On 2/6/19, 1:04 AM, Mark Thomas wrote:
>> On the TLS Connector:
>>
>> sslEnabledProtocols="TLSv1.1,TLSv1.2"
>
> Ok. So the active connector we currently have for this particular
> installation (which
Thanks. I do have some follow up questions
On 2/6/19, 1:04 AM, Mark Thomas wrote:
On the TLS Connector:
sslEnabledProtocols="TLSv1.1,TLSv1.2"
Ok. So the active connector we currently have for this particular
installation (which has multiple IP addresses, hence the "address"
clause) is:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark and James,
On 2/6/19 04:04, Mark Thomas wrote:
> On 05/02/2019 23:49, James H. H. Lampert wrote:
>> We've just received word from a customer that they had two
>> vulnerabilities flagged on a security scan of the box their
>> Tomcat server is r
On 05/02/2019 23:49, James H. H. Lampert wrote:
> We've just received word from a customer that they had two
> vulnerabilities flagged on a security scan of the box their Tomcat
> server is running on.
>
> 38628 - TLS 1.0 still supported.
> Ok, assuming that the box and the JVM can go up to a more
We've just received word from a customer that they had two
vulnerabilities flagged on a security scan of the box their Tomcat
server is running on.
38628 - TLS 1.0 still supported.
Ok, assuming that the box and the JVM can go up to a more current TLS
level, and a more current cipher, what do I
Fellow List members:
In the end, this morning, having been told that getting the development
instance running under Java 8 had become a priority, and knowing that
Tomcat was running under Apache (and also learning that Apache itself
wasn't running under a service name containing recognizable w
nder Java 8; they are all derived from Google's Tomcat-8
> pre-installed image.
No changes to Tomcat itself... just switching from Java 7 to Java 8?
Do you have anything in server.xml that mentions specific class names
that might be missing from Java 8? Maybe some custom
JreMemoryLeakPrevent
On 12/18/18, 2:49 PM, Caldarale, Charles R wrote:
The above indicates you have a Tomcat (or something much like it) already
running...
You would think so, and yet if I switch the JAVA_HOME line in setenv.sh
to Java 7, it launches just fine. . . .
WAIT A SECOND!
Port 443 is open, and the
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
> Subject: Re: Tomcat 8 runs under Java 7, but not Java 8
> Excerpt from the relevant time period, catalina.2018-12-18.log:
> > 18-Dec-2018 20:18:55.419 SEVERE [main]
org.apache.catalina.core.Stand
On 12/18/18, 12:50 PM, Mark Thomas wrote:
They don't appear to be very helpful.
They certainly didn't suggest anything to me.
What do the Tomcat logs show? catalina.-mm-dd.log is likely to be
the most useful but check them all.
Dear Mr. Thomas, et al:
Excerpt from the relevant time peri
Hi James,
Le 18/12/2018 à 21:40, James H. H. Lampert a écrit :
> I just installed Java 8 (not as the default JRE) on a Google Compute
> Debian 8 instance that has been running Tomcat 8 under Java 7.
I assume you are using the tomcat8 package from the distribution. Tomcat
on Debian 8 Jessi
On 18/12/2018 20:40, James H. H. Lampert wrote:
> I just installed Java 8 (not as the default JRE) on a Google Compute
> Debian 8 instance that has been running Tomcat 8 under Java 7.
>
> If I change setenv.sh to add
>> JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/"
I just installed Java 8 (not as the default JRE) on a Google Compute
Debian 8 instance that has been running Tomcat 8 under Java 7.
If I change setenv.sh to add
JAVA_HOME="/usr/lib/jvm/java-8-openjdk-amd64/"
and I try to "service tomcat8 start," I get
Job for tomcat8.se
umn 19: Document root element
> "taglib",
> > > must match DOCTYPE root "null".
> > > org.xml.sax.SAXParseException: Document root element "taglib", must
> match
> > > DOCTYPE root "null".
> > >
> > > Aug
t; Aug 23, 2017 9:36:49 AM org.apache.commons.digester.Digester
> > error
> > SEVERE: Parse Error at line 6 column 19: Document root element "taglib",
> > must match DOCTYPE root "null".
> > org.xml.sax.SAXParseException: Document root element "taglib
x27;,
> returnNull=true
> Aug 23, 2017 9:36:50 AM org.apache.struts.util.PropertyMessageResources
>
> INFO: Initializing, config='org.apache.struts.action.ActionResources',
> returnNull=true
> Aug 23, 2017 9:36:51 AM org.apache.struts.util.PropertyMessageResources
>
zaha/rzahainstalljdk.htm
>
>
>
> On 7 September 2017 at 15:56, André Warnier (tomcat)
> wrote:
>
> > On 07.09.2017 16:21, Vinay A S wrote:
> >
> >> Hello,
> >>
> >> We have installed Apache Tomcat version 4.1.30 on our iSeries server
;
> (Ok, I am pushing it a bit; it was 2004, 13 years ago; so they may have
> been born, but still in primary school)
>
> Recently we have upgraded the OS400 Operating System from Version 7.1 to
>> 7.3 where Java 7 and Java 8 are introduced. After this upgrade, Tomcat is
>> gi
On 9/7/17, 2:43 PM, Christopher Schultz wrote:
It sounds like James H.H. Lampert may be able to help you with your
problem. He's been pounding his head against his AS/400 environment
for years.
Greetings!
I finally get a chance to talk about something I know, rather than beg
for help about so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ananthi,
On 9/7/17 5:12 AM, Ananthi K4 wrote:
> We have installed Apache Tomcat version 4.1.30 on our iSeries
> server. Recently we have upgraded the OS400 Operating System from
> Version 7.1 to 7.3 where Java 7 and Java 8 are introduc
2004, 13 years ago; so they may have been born, but
still in primary school)
Recently we have upgraded the OS400 Operating System from Version 7.1 to
7.3 where Java 7 and Java 8 are introduced. After this upgrade, Tomcat is
giving an HTTP status 500 exception report.
I don't know if anyone
Hello,
We have installed Apache Tomcat version 4.1.30 on our iSeries server.
Recently we have upgraded the OS400 Operating System from Version 7.1 to
7.3 where Java 7 and Java 8 are introduced. After this upgrade, Tomcat is
giving an HTTP status 500 exception report.
We explored the Tomcat
Hello,
We have installed Apache Tomcat version 4.1.30 on our iSeries server.
Recently we have upgraded the OS400 Operating System from Version 7.1 to
7.3 where Java 7 and Java 8 are introduced. After this upgrade, Tomcat is
giving an HTTP status 500 exception report.
We explored the Tomcat
ater under Java 7?
No specific issues I am aware of.
General things to look out for:
- GC settings 'optimized' for an older JVM that don't make sense for the
newer JVM. Best to remove them all and start from a clean slate.
- Web applications including libraries that are now p
Ladies and Gentlemen of the Tomcat List:
To date, the overwhelming bulk of our own Tomcat experience has been
under Java 6 JVMs. And we have a customer who will likely be losing that
JVM soon.
Are there any "gotchas" running 7.0.47 or later under Java 7?
--
James H. H. Lampert
Am 26.01.2016 um 10:40 schrieb André Warnier (tomcat):
On 26.01.2016 10:19, Christoph P.U. Kukulies wrote:
Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:
Am 25.01.2016 um 19:34 schrieb George Sexton:
On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:
Thanks. Will give that a try.
2016-01-26 12:19 GMT+03:00 Christoph P.U. Kukulies :
> Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:
>>
>> Am 25.01.2016 um 19:34 schrieb George Sexton:
>>>
>>>
>>>
>>> On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:
Thanks. Will give that a try.
How can I tell, w
On 26.01.2016 10:19, Christoph P.U. Kukulies wrote:
Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:
Am 25.01.2016 um 19:34 schrieb George Sexton:
On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:
Thanks. Will give that a try.
How can I tell, which java engine Tomcat is actually u
Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:
Am 25.01.2016 um 19:34 schrieb George Sexton:
On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:
Thanks. Will give that a try.
How can I tell, which java engine Tomcat is actually using?
At a CMD prompt I'm getting:
C:\> java -vers
CMS system again I now found that it did some
unpleasant things for which I wanted to rule out tomcat7 being the
culprit
and switch the jvm.dll in the tomcat7 configurator to the jre1.7
jvm.dll.
Then suddenly I got the same error as under tomcat6.0 when I tried
to start tomcat7 again.
Could
w found that it did some
unpleasant things for which I wanted to rule out tomcat7 being the
culprit
and switch the jvm.dll in the tomcat7 configurator to the jre1.7
jvm.dll.
Then suddenly I got the same error as under tomcat6.0 when I tried
to start tomcat7 again.
Could it be that the Java8
>>>
>>> My thoughts came to tomcat6 possibly not being compatible with Java8 and
>>>> so I decided to install tomcat 7.0 which started fine.
>>>>
>>>> When starting my CMS system again I now found that it did some
>>>>
it be that the Java8 installer screws the existing Java 7 ? Or
does it change some global parameters that tomcat reads at start time.
Thanks.
--
Christoph
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
Fo
tart tomcat7 again.
Could it be that the Java8 installer screws the existing Java 7 ? Or
does it change some global parameters that tomcat reads at start time.
Thanks.
--
Christoph
-
To unsubscribe, e-mail: users-unsubs
did some
unpleasant things for which I wanted to rule out tomcat7 being the
culprit
and switch the jvm.dll in the tomcat7 configurator to the jre1.7 jvm.dll.
Then suddenly I got the same error as under tomcat6.0 when I tried to
start tomcat7 again.
Could it be that the Java8 installer screws
omcat6.0 when I tried to
start tomcat7 again.
Could it be that the Java8 installer screws the existing Java 7 ? Or
does it change some global parameters that tomcat reads at start time.
If you take the default installation location and do not allow it to
remove the old one, Java 8 will not al
uddenly I got the same error as under tomcat6.0 when I tried to start
> tomcat7 again.
>
> Could it be that the Java8 installer screws the existing Java 7 ? Or does it
> change some global parameters that tomcat reads at start time.
1. That "The service "Apache Tomcat 6.0 Tomc
ould it be that the Java8 installer screws the existing Java 7 ? Or
does it change some global parameters that tomcat reads at start time.
If you take the default installation location and do not allow it to
remove the old one, Java 8 will not alter your java 7 installation.
However, which java
hat it did some
unpleasant things for which I wanted to rule out tomcat7 being the culprit
and switch the jvm.dll in the tomcat7 configurator to the jre1.7 jvm.dll.
Then suddenly I got the same error as under tomcat6.0 when I tried to
start tomcat7 again.
Could it be that the Java8 installer screws th
On 27.10.2015 17:01, Vinicius Corrêa de Almeida wrote:
I analized some releases and i noticed that not using java 7 features like
multi catch and in java 8 do not use lambda expressions and others
features, so i came by this email to know why the developers not using this
features?
I believe
On 10/27/2015 12:01 PM, Vinicius Corrêa de Almeida wrote:
I analized some releases and i noticed that not using java 7 features like
multi catch and in java 8 do not use lambda expressions and others
features, so i came by this email to know why the developers not using this
features?
Which
I analized some releases and i noticed that not using java 7 features like
multi catch and in java 8 do not use lambda expressions and others
features, so i came by this email to know why the developers not using this
features?
[jar:file:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar!/]
for TLD files
java.io.FileNotFoundException:
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar (No
such file
or directory)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(Zi
led pulse-java.jar)
>
> INFO: Deploying web application archive
> /var/lib/tomcat7/webapps/SecureServiceExample.war
> Jan 12, 2015 3:03:01 PM org.apache.catalina.startup.TldConfig tldScanJar
> WARNING: Failed to process JAR
> [jar:file:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/e
Hi André, thanks for your reply.
well spotted, I've corrected my Xmx/Xms error and restarted.
On 13-01-2015 14:07, André Warnier wrote:
Peter Lavin wrote:
Tomcat7 was installed using apt-get. With the default memory
settings (around line 271 in catalina.sh) as follows...
CATALINA_OPTS="$CATA
application archive
/var/lib/tomcat7/webapps/SecureServiceExample.war
Jan 12, 2015 3:03:01 PM org.apache.catalina.startup.TldConfig tldScanJar
WARNING: Failed to process JAR
[jar:file:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar!/]
for TLD files
java.io.FileNotFoundException:
/usr/lib
/tomcat7/webapps/SecureServiceExample.war
Jan 12, 2015 3:03:01 PM org.apache.catalina.startup.TldConfig
tldScanJar
WARNING: Failed to process JAR
[jar:file:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar!/]
for TLD files
java.io.FileNotFoundException:
/usr/lib/jvm/java-7-openjdk
On 03.02.2014, at 22:19, Singh, Ragini wrote:
> Hello,
>
> I upgraded Java 1.6.45 to Java 1.7.51 using java-1.7.0-oracle.x86_64 : Oracle
> Java Runtime Environment on RHEL 5. Used the "alternatives" command to make
> the Java 7 as Java version.
> Now in my custo
rsion using
JAVA_HOME. Is there a way I can find out which version of JAVA Tomcat is using?
Thank you,
-Ragini
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, February 03, 2014 3:42 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 / Java 7
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ragini,
On 2/4/14, 10:05 AM, Singh, Ragini wrote:
> Thank you Christopher!! I understand that the message is just an
> INFO and not an error. Also, I haven’t installed tcnative as I am
> not using it. My question was regarding the difference in mess
Tomcat is using?
Thank you,
-Ragini
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, February 03, 2014 3:42 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 / Java 7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ragini,
On 2/3/14, 4:19 PM
nd to make the Java 7 as Java
version. Now in my custom startup script if I define JAVA_HOME as
JAVA_HOME="/usr/lib/jvm/java" tomcat 7 recognizes the java as 1.6 (
the previous version) and gives this message "INFO: The APR based
Apache Tomcat Native library which allows optimal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ragini,
On 2/3/14, 4:19 PM, Singh, Ragini wrote:
> I upgraded Java 1.6.45 to Java 1.7.51 using
> java-1.7.0-oracle.x86_64 : Oracle Java Runtime Environment on RHEL
> 5. Used the "alternatives" command to make the Java 7 as Java
&
Hello,
I upgraded Java 1.6.45 to Java 1.7.51 using java-1.7.0-oracle.x86_64 : Oracle
Java Runtime Environment on RHEL 5. Used the "alternatives" command to make the
Java 7 as Java version.
Now in my custom startup script if I define JAVA_HOME as
JAVA_HOME="/usr/lib/jvm
Yes it is compatible, and no, there is nothing you really need to do except
to test your applications that they work too.
On Mon, Jan 27, 2014 at 9:37 AM, Singh, Ragini wrote:
> Hello,
>
> Is Tomcat 7.0.42 compatible with Java 7?<
> http://stackoverflow.com/questions/9294355/
Hello,
Is Tomcat 7.0.42 compatible with Java
7?<http://stackoverflow.com/questions/9294355/is-tomcat-7-now-compatible-with-java-7>
If yes, do you know if there is something special to migrate an existing
installation of Tomcat 7/Java 6 to Tomcat 7/Java 7?
-Ragini
Thanks for clarifying the JSSE issue. It's a shame that JSSE can't make
use of available JCE algorithms. I've just been trying to establish the
limits of the Java 7 implementation, and I think I understand that now.
Yes, the ECDHE ciphersuites are definitely the choice for str
Hi
the JSSE Reference Guide defines which possibilities for anyone
implementing a JSSE provider (let's call it an API if you want).
Oracle's provider only implements a part of this API, misleading you
to believe SHA384 is available when it's unfortunately not.
About Bouncy Castle, I believe they
t?
> Martin
> __
> Please do not alter or disrupt this transmission..Thank You
>
>
>
>
>> Date: Thu, 22 Aug 2013 14:53:55 +0100
>> Subject: Re: Tomcat 7 / Java 7 with TLS 1.2 algorithms
>> From: aterrest...@gmail.com
>> To: us
Thanks, Aurélien. I'd seen the SHA384 versions listed in the JSSE Cipher
Suite Names and thought they were available:
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#ciphersuites
I was really hoping to use one of the GCM suites, but I gather those are
not offi
mcat 7 / Java 7 with TLS 1.2 algorithms
> From: aterrest...@gmail.com
> To: users@tomcat.apache.org
>
> According to RFC 5246 Appendix C (TLS 1.2), there is no SHA384. See :
> http://www.ietf.org/rfc/rfc5246.txt
>
> The JSSE Reference Guide also doesn't talk about th
According to RFC 5246 Appendix C (TLS 1.2), there is no SHA384. See :
http://www.ietf.org/rfc/rfc5246.txt
The JSSE Reference Guide also doesn't talk about this SHA384 as an
implementation requirement. See :
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#impl
Thi
According to RFC 5246 Appendix C (TLS 1.2), there is no SHA384. See :
http://www.ietf.org/rfc/rfc5246.txt
The JSSE Reference Guide also doesn't talk about this SHA384 as an
implementation requirement. See :
http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#impl
Thi
I've already done that, though as far as I can see that doesn't effect
the digest algorithms (only the encryption options).
- Dennis
On 08/23/2013 12:24 AM, Aurélien Terrestris wrote:
Hello
I suppose you need to run your JVM with the unrestricted policy files (on b=
oth client and server si
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
does this not work for you?
Martin Gainty
__
Please do not alter or disrupt this transmission..Thank You
From: d...@sosnoski.com
Subject: Tomcat 7 / Java 7 with TLS 1.2 algorithms
To:
Hello
I suppose you need to run your JVM with the unrestricted policy files (on b=
oth client and server sides). You have to download them from Oracle website=
for your java version, and replace the old.
These files are :
local_policy.jar
US_export_policy.jar
Regards
2013/8/22 :
> Tomcat 7.0.
Tomcat 7.0.40 seems to work well with TLS 1.2, forced by using a
sslEnabledProtocols="TLSv1.2" attribute on the . But I haven't been
able to make it work with any of the SHA256/384 algorithms - they always show
up in the "Ignoring unsupported cipher suite" list. I get the same thing
happening w
On Apr 1, 2013, at 3:44 PM, Satheesh Babu wrote:
> Good Evening!
>
> We're running our production applications in Tomcat 5.5/JRE 1.5, and there is
> a need for us to migrate our applications to Java 7(JRE 1.7). There is no
> information available either on java or
On 04.02.2013, at 19:40, Christopher Schultz
wrote:
> It's a "maybe". If you use "-target 1.6" and you make sure not to use
> any APIs that are Java 1.7+ (not sure if the compiler actually checks
> when you use -target 1.6)
It does not. -target only sets the class file format. There's an option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 2/4/13 2:37 PM, André Warnier wrote:
> Thanks to all. I got more than I was bargaining for.
>
> To summarise thus, if I understand correctly what was said here,
> and asking forgiveness in advance for pretty bad English style :
>
> - any
Thanks to all. I got more than I was bargaining for.
To summarise thus, if I understand correctly what was said here, and asking forgiveness in
advance for pretty bad English style :
- any well-written java application, which does not use any vendor-specific JVM API (or
"internals") should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 2/4/13 1:42 PM, Williams, Nick wrote:
>> No wonder those guys were so reticent to change the JDBC API to
>> (directly) support the upcoming Java Date & Time APIs: they've
>> made everyone so angry in the past they don't want to do it again
> No wonder those guys were so reticent to change the JDBC API to
> (directly) support the upcoming Java Date & Time APIs: they've made everyone
> so angry in the past they don't want to do it again ;)
> - -chris
Chris,
DID/WILL they update the JDBC API to support the new date/time API? Or did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 2/4/13 9:55 AM, Caldarale, Charles R wrote:
>> From: André Warnier [mailto:a...@ice-sa.com] - the classes of a
>> servlet that has been compiled under a Sun/Oracle Java 1.7 JDK
>> will run fine under Tomcat 6 and a Sun/Oracle Java 1.6 JVM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/4/13 8:57 AM, Mark Thomas wrote:
> On 04/02/2013 13:41, Caldarale, Charles R wrote:
>>> From: Mark Thomas [mailto:ma...@apache.org] Subject: Re: Tomcat
>>> and Sun/Oracle Java 7
>>
>>>> What is th
On 2/4/2013 9:32 AM, Williams, Nick wrote:
-Original Message-
From: Jess Holle [mailto:je...@ptc.com]
...
It's that you can't make Java source code which /implements /JDBC interfaces
and make it compilable with both Java 6 and Java 7. The JDBC interfaces have
new methods
stalling in production have not
been tested on Java 7, I would stick with Java 6 for a while, but it
is already the time to start testing them with Java 7.
In theory, applications developed with Java 6 should run on Java 7 just fine.
In practice, it needs testing, and there exist
http://ww
> -Original Message-
> From: Jess Holle [mailto:je...@ptc.com]
>
> ...
> It's that you can't make Java source code which /implements /JDBC interfaces
> and make it compilable with both Java 6 and Java 7. The JDBC interfaces have
> new methods in Java 7 *and
It's not that Tomcat doesn't *run* fine with Java 7 even if you're
making use of JDBC.
And it's not that you can't have code that calls JDBC APIs that works
fine with Java 6 and Java 7.
It's that you can't make Java source code which /implements /JDBC
int
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: Tomcat and Sun/Oracle Java 7
> - tomcat 6 will run fine under a Sun/Oracle Java 1.6 JVM
> - tomcat 7 will run fine under a Sun/Oracle Java 1.6 JVM
> - tomcat 6 will run fine under a Sun/Oracle Java 1.7 JVM
> - tomc
On 04/02/2013 14:39, André Warnier wrote:
> Mark Thomas wrote:
>> On 04/02/2013 13:41, Caldarale, Charles R wrote:
>>>> From: Mark Thomas [mailto:ma...@apache.org] Subject: Re: Tomcat and
>>>> Sun/Oracle Java 7
>>>>> What is the status of Tomcat
Mark Thomas wrote:
On 04/02/2013 13:41, Caldarale, Charles R wrote:
From: Mark Thomas [mailto:ma...@apache.org] Subject: Re: Tomcat and
Sun/Oracle Java 7
What is the status of Tomcat vs Sun/oracle Java 7 ? I vaguely
remember seeing some messages on this list about some kind of
incompatibility
On 04/02/2013 13:41, Caldarale, Charles R wrote:
>> From: Mark Thomas [mailto:ma...@apache.org] Subject: Re: Tomcat and
>> Sun/Oracle Java 7
>
>>> What is the status of Tomcat vs Sun/oracle Java 7 ? I vaguely
>>> remember seeing some messages on this list about
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: Tomcat and Sun/Oracle Java 7
> > What is the status of Tomcat vs Sun/oracle Java 7 ?
> > I vaguely remember seeing some messages on this list about some kind of
> > incompatibility.
> There are no known iss
On 04/02/2013 09:37, André Warnier wrote:
> Hi.
> What is the status of Tomcat vs Sun/oracle Java 7 ?
> I vaguely remember seeing some messages on this list about some kind of
> incompatibility.
> But I cannot find anything readily mentioned in Tomcat 7's Release Notes
> or
Hi.
What is the status of Tomcat vs Sun/oracle Java 7 ?
I vaguely remember seeing some messages on this list about some kind of
incompatibility.
But I cannot find anything readily mentioned in Tomcat 7's Release Notes or
similar p
On 26 November 2012 18:22, Mark Thomas wrote:
> Johanes Soetanto wrote:
>
>>Hi all,
>>
>>I am wondering whether there is a known issue with running Tomcat
>>6.0.35 with Java 7 ?
>
> None I can think of.
>
>>I see lots of "(502)Unknown error 502:
On 26 November 2012 21:05, Konstantin Kolinko wrote:
> 2012/11/26 Johanes Soetanto :
>> Hi all,
>>
>> I am wondering whether there is a known issue with running Tomcat
>> 6.0.35 with Java 7 ?
>>
>
> 1. There certainly were fixes in Tomcat 7. I am n
2012/11/26 Johanes Soetanto :
> Hi all,
>
> I am wondering whether there is a known issue with running Tomcat
> 6.0.35 with Java 7 ?
>
1. There certainly were fixes in Tomcat 7. I am not sure whether all
of them they were backported to Tomcat 6 or not.
I think you would have bet
Johanes Soetanto wrote:
>Hi all,
>
>I am wondering whether there is a known issue with running Tomcat
>6.0.35 with Java 7 ?
None I can think of.
>I see lots of "(502)Unknown error 502: proxy: pass request body
>failed.." error in our Apache log after running our
Hi Muz,
We use RewriteRule instead of ProxyPass which works.
RewriteRule /app(.*)$ https://127.0.0.1:8443/app$1 [P,L]
I have even changed this to use ProxyPass but without any noticeable difference
ProxyPass /app https://127.0.0.1:8443/app
ProxyPassReverse /app https://127.0.0.1:8443/app
Joha
On 26 November 2012 14:28, Johanes Soetanto wrote:
> Unknown error 502
Hi Johanes,
What are your proxypass settings?
Thanks,
Muz
Hi all,
I am wondering whether there is a known issue with running Tomcat
6.0.35 with Java 7 ?
I see lots of "(502)Unknown error 502: proxy: pass request body
failed.." error in our Apache log after running our Tomcat with Java
7. Once I change back Tomcat to use Java 6, I see no er
2012/8/18 Jess Holle :
> Until it is updated, Tomcat's annotation scanning will be broken for some
> Java 7 byte code. That's not really a tenable state long term.
>
I have filed an issue, as this really needs to be addressed before
Tomcat 8 is released.
https://issues.
On 8/17/2012 3:18 PM, Konstantin Kolinko wrote:
2012/8/16 Jess Holle :
It appears that when one installs the groovy-all-2.0.1-indy.jar in a Tomcat
web app, BCEL chokes on the Java 7 specific byte-code therein ala
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte
tag
2012/8/16 Jess Holle :
> It appears that when one installs the groovy-all-2.0.1-indy.jar in a Tomcat
> web app, BCEL chokes on the Java 7 specific byte-code therein ala
>
>org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte
> tag in constant pool:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jess,
On 8/16/12 12:19 PM, Jess Holle wrote:
> On 8/16/2012 11:14 AM, Pid * wrote:
>> On 16 Aug 2012, at 17:10, Jess Holle wrote:
>>> It appears that when one installs the groovy-all-2.0.1-indy.jar
>>> in a Tomcat web app
On 8/16/2012 11:14 AM, Pid * wrote:
On 16 Aug 2012, at 17:10, Jess Holle wrote:
It appears that when one installs the groovy-all-2.0.1-indy.jar in a Tomcat web
app, BCEL chokes on the Java 7 specific byte-code therein ala
org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid
On 16 Aug 2012, at 17:10, Jess Holle wrote:
> It appears that when one installs the groovy-all-2.0.1-indy.jar in a Tomcat
> web app, BCEL chokes on the Java 7 specific byte-code therein ala
>
> org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte
> tag i
1 - 100 of 135 matches
Mail list logo
