Hi All,
I am receiving the following error message while accessing my application -
(apcahe web server + tomcat through Mod jk)
Internal Server Error - Read
The server encountered an internal error or misconfiguration and was unable to
complete request.
# Reference Number
But there is no
Am 10.07.2013 00:46, schrieb Travis Bowen:
Ok I found where it is being used in the getRoles method however I'm
still wondering why it doesn't work. I don't see any way to define the
member group attribute name, it is uniqueGroup in the dir server I am
connecting to.
roleSearch will be used
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough date) for Tomcat
moving to the new spec versions introduced by Java EE 7?
Tomcat 8.
Implementation complete? Best guess is a couple of months. The more help
we get with the EL 3.0 implementation, the
Thanks!
On 7/10/2013 5:18 AM, Mark Thomas wrote:
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough date) for Tomcat
moving to the new spec versions introduced by Java EE 7?
Tomcat 8.
Implementation complete? Best guess is a couple of months. The
Hi all.
I've studied the documentation at
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support and
I have several questions on it.
1. While the APR/Native has config option SSLCACertificateFile that
defines the set of allowed client cert authorities the JSSE SSL has no
On 10/07/2013 12:25, Jan Vávra wrote:
Hi all.
I've studied the documentation at
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support and
I have several questions on it.
1. While the APR/Native has config option SSLCACertificateFile that
defines the set of allowed client
2. It seems me that checking of revocation of client certificate is done
via static crl files located in APR's SSLCARevocationPath or JSSE's
crlFile. If I write a cron task that periodically downloads crl list(s),
will the Tomcat react on this change of CRL file(s)? I've found in
On Jul 10, 2013, at 3:04 AM, Arnab Ghosh mail2arna...@yahoo.com wrote:
Hi All,
I am receiving the following error message while accessing my application -
(apcahe web server + tomcat through Mod jk)
Please indicate which versions of the software you are using.
Apache HTTPD:
That's good news to hear, men!
Thanks for the hard work.
Regards,
Pierre
On Wed, Jul 10, 2013 at 12:48 PM, Jess Holle je...@ptc.com wrote:
Thanks!
On 7/10/2013 5:18 AM, Mark Thomas wrote:
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough
Il 10/07/13 12:18, Mark Thomas ha scritto:
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough date) for Tomcat
moving to the new spec versions introduced by Java EE 7?
Tomcat 8.
Implementation complete? Best guess is a couple of months. The more help
Thanks for the info. However the issue is that groups are not stored as
uniqueMember but uniqueGroup so the roleSearch is not applicable.
Thanks,
Travis
From: Felix Schumacher felix.schumac...@internetallee.de
To: Tomcat Users List users@tomcat.apache.org,
Date: 07/10/2013 12:14 AM
On Jul 10, 2013, at 9:32 AM, Edoardo Panfili wrote:
Il 10/07/13 12:18, Mark Thomas ha scritto:
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough date) for Tomcat
moving to the new spec versions introduced by Java EE 7?
Tomcat 8.
Implementation
Il 10/07/13 17:09, Nick Williams ha scritto:
On Jul 10, 2013, at 9:32 AM, Edoardo Panfili wrote:
Il 10/07/13 12:18, Mark Thomas ha scritto:
On 10/07/2013 00:06, Jess Holle wrote:
Is there an ETA (in terms of both a version and rough date) for Tomcat
moving to the new spec versions
Am 10.07.2013 16:34, schrieb Travis Bowen:
Thanks for the info. However the issue is that groups are not stored
as uniqueMember but uniqueGroup so the roleSearch is not applicable.
You could try a roleSearch=|(uniqueMember={0})(uniqueGroup={0}). The
{i} should be replaced multiple times.
We appear to be having, on a multi-IP-address system, a collision with
port 8005, causing Tomcat to crash on takeoff.
Looking at server.xml, I see that 8005 is not mentioned in any
connector definition, but rather in this:
Server port=8005 shutdown=SHUTDOWN
I know how to bind a connector
On Jul 10, 2013, at 3:23 PM, James H. H. Lampert jam...@touchtonecorp.com
wrote:
We appear to be having, on a multi-IP-address system, a collision with port
8005, causing Tomcat to crash on takeoff.
Looking at server.xml, I see that 8005 is not mentioned in any connector
definition, but
On 10/07/2013 20:23, James H. H. Lampert wrote:
We appear to be having, on a multi-IP-address system, a collision with
port 8005, causing Tomcat to crash on takeoff.
Looking at server.xml, I see that 8005 is not mentioned in any
connector definition, but rather in this:
Server port=8005
I know how to bind a connector to a specific IP address, but I know nothing
about this. Neither do I know what would happen if, once Tomcat is up, we
were to attempt to send a shutdown message in the usual way: would we shut
Tomcat down, or would we shut whatever owns 127.0.0.1:8005?
As
On Jul 10, 2013, at 3:56 PM, John Renne j...@gniffelnieuws.net wrote:
I know how to bind a connector to a specific IP address, but I know nothing
about this. Neither do I know what would happen if, once Tomcat is up, we
were to attempt to send a shutdown message in the usual way: would we
When did it start that developers decided to place jsps in the WEB-INF
directory? Was that intended from the beginning, or was it stumbled upon?
Leo
We ended up changing the port number.
But do we have to change it anywhere else, for shutdown to work properly?
--
JHHL
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
On Wed, 2013-07-10 at 15:08 -0700, Leo Donahue - RDSA IT wrote:
When did it start that developers decided to place jsps in the WEB-INF
directory? Was that intended from the beginning, or was it stumbled
upon?
My guess is that it was a side effect of MVC adoption -- making views
accessible
I'm obviously new to Tomcat. Got it working fine on localhost, now trying
to get it to deliver web pages to the outside world.
Following instructions found in various places I added the following to the
server.xml file and restarted Tomcat:
users@tomcat.apache.org
Host name=books-on-line.com
From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
Subject: Re: Collision on port 8005 -- what to do about it?
We ended up changing the port number.
But do we have to change it anywhere else, for shutdown to work properly?
No, the startup and shutdown scripts both use the
I am out of the office until 24/07/2013.
For technical questions per DANSE/SPRINT email to Ariel Landau
ar...@il.ibm.com
Allternative possible mail: uri.sh...@gmail.com
Personal phone you can call freely: +372-5763-0084
Note: This is an automated response to your message [OT] WEB-INF sent on
From: john Matlock [mailto:johndmatl...@gmail.com]
Subject: Moving Tomcat to work externally.
Following instructions found in various places I added the following
to the server.xml file and restarted Tomcat:
If you followed something that said to put a Context element in server.xml,
you
On 7/10/2013 6:08 PM, Caldarale, Charles R wrote:
From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Moving
Tomcat to work externally.
Following instructions found in various places I added the
following to the server.xml file and restarted Tomcat:
If you followed something that
27 matches
Mail list logo
