I have a change-password form that must validate the current
user's password and am unable to find a Tomcat (8.0) method to use
for this. It's not in FormAuthenticator or any other class I could
find. Pointers would be appreciated.
It's complicated, but you can do it. What exact version of Tomc
Thanks Chris,
that seems to connect but sends no data back? The error is
3074385544:error:1409E0E5:SSL ... :ssl handshake failure:s3_pkt.c:637
Returns:
CONNECTED(0003)
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 b
> On Dec 22, 2016, at 11:31 AM, Christopher Schultz
> wrote:
>
> There's 7.0.73 but it shouldn't make too much of a difference. I just
> wanted to make sure you weren't running 7.0.1-RC or some weird thing
> that's ages old.
>
> In Tomcat 7 there is a setting on the component called
> "startS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roger,
On 12/22/16 3:44 PM, Roger Marquis wrote:
> I have a change-password form that must validate the current
> user's password and am unable to find a Tomcat (8.0) method to use
> for this. It's not in FormAuthenticator or any other class I could
I have a change-password form that must validate the current user's
password and am unable to find a Tomcat (8.0) method to use for this.
It's not in FormAuthenticator or any other class I could find. Pointers
would be appreciated.
Roger
-
On 22/12/2016 17:50, Greg Huber wrote:
> Chris,
>
> Thanks, I have been running this setup for ages, 8 plus years and various
> tomcat versions. It has never failed on <= 8.0.x I had to stop/start a
> couple of times to get it to fail and had to run a parallel maven build to
> slow things down.
On 22/12/2016 15:46, Fady Haikal wrote:
> We can see the below error on the log file please advise:
You are using multiple start/start threads and the RMI reference
cleaning isn't thread safe. Arguably that is a bug in Tomcat but if you
fix the RMI memory leaks in your application you won't hit th
> It's possible that there was an imperfect patch released by Debian.
Yep, they're missing r1763236 in wheezy; it was added to Jessie on
12/8 (commit 49e4e30b8c12ffc28378075545f413b725ad5cd9). Please notify
your maintainer to have it fixed :)
On Thu, Dec 22, 2016 at 1:48 PM, Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Per,
On 12/22/16 11:45 AM, Per Newgro wrote:
> no we don't see the same problems with a 7.0.64 installation. But
> what can we do with our debian version. I think it shall be
> possible to configure the datasource somehow.
It's possible that there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 12/22/16 12:50 PM, Greg Huber wrote:
> Thanks, I have been running this setup for ages, 8 plus years and
> various tomcat versions. It has never failed on <= 8.0.x
Interesting. Usually, things don't just stop working like that.
Did you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/22/16 12:52 PM, Peter Wallis wrote:
> Ahh! changed the server.xml entries to 8443 tried: openssl s_client
> -connect 192.168.1.149:8443 and got: CONNECTED(0003)
> 3074541192:error:140790E5SSL routhines:SSL23_WRITE:ssl handshake
>
Ahh!
changed the server.xml entries to 8443
tried:
openssl s_client -connect 192.168.1.149:8443
and got:
CONNECTED(0003)
3074541192:error:140790E5SSL routhines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:177:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL
Chris,
Thanks, I have been running this setup for ages, 8 plus years and various
tomcat versions. It has never failed on <= 8.0.x I had to stop/start a
couple of times to get it to fail and had to run a parallel maven build to
slow things down.
Do not read much on dumps, but what would this -l
> On Dec 22, 2016, at 11:31 AM, Christopher Schultz
> wrote:
>
> In Tomcat 7 there is a setting on the component called
> "startStopThreads"[1]. The default is 1 which means that a single
> thread will be used to start/stop applications during
> startup/shutdown, so the behavior you are seeing
Hello,
no we don't see the same problems with a 7.0.64 installation. But what
can we do with our debian version. I think it shall be possible to
configure the datasource somehow.
Thanks
Per
On 16 December 2016 09:12:24 GMT+00:00, Per Newgro
wrote:
Hello,
i've just updated my debian serve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jesse,
On 12/22/16 10:41 AM, Jesse Barnum wrote:
>
>> On Dec 22, 2016, at 10:39 AM, Christopher Schultz
>> wrote:
>>
>> On 12/22/16 10:20 AM, Jesse Barnum wrote:
>>> I am running multiple webapps on Tomcat 7, and I’ve noticed
>>> that when shutti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/22/16 11:03 AM, Peter Wallis wrote:
> Hi Christopher, re 443 on *nix; yes, set AUTHBIND='yes' in
> /etc/defaults/tomcat8
Okay. Are you sure you've got that configured properly? Try changing
port 443 to 8443 in server.xml and bouncing T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 12/22/16 5:18 AM, Greg Huber wrote:
> Here is the first dump and I cannot send all three. Its my prod
> server which is locked up at the moment. I need to get it back on
> line so is this enough info? I can emile the whole file which has
Hi Christopher,
re 443 on *nix; yes, set AUTHBIND='yes' in /etc/defaults/tomcat8
re openssl s_client -connect on a different machine; it times out
Did have a thought -- one that might not be obvious to you experts -- I am
serving that page via No-IP dynamic dns. Their support people are "cagey"
We can see the below error on the log file please advise:
OS: windows
Tomcat Version: 8.0.30
Cluster Tomcat
30-Nov-2016 08:32:21.197 SEVERE [Catalina-startStop-2]
org.apache.catalina.core.ContainerBase.stopInternal A child container
failed during stop
java.util.concurrent.ExecutionException:
org
> On Dec 22, 2016, at 10:39 AM, Christopher Schultz
> wrote:
>
> On 12/22/16 10:20 AM, Jesse Barnum wrote:
>> I am running multiple webapps on Tomcat 7, and I’ve noticed that
>> when shutting down Tomcat, the ContextListeners are called in
>> serial, instead of in parallel. Some of these webapp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jesse,
On 12/22/16 10:20 AM, Jesse Barnum wrote:
> I am running multiple webapps on Tomcat 7, and I’ve noticed that
> when shutting down Tomcat, the ContextListeners are called in
> serial, instead of in parallel. Some of these webapps take 5-15
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 12/22/16 2:43 AM, Peter Wallis wrote:
> Hi Christopher, so it seems I have done something exceptional :-)
> Thanks for taking a look...
>
> protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="150" SSLEnabled="true" schem
I am running multiple webapps on Tomcat 7, and I’ve noticed that when shutting
down Tomcat, the ContextListeners are called in serial, instead of in parallel.
Some of these webapps take 5-15 seconds to run various shutdown procedures.
This can exceed the timeout period for shutting down, which m
On 22 December 2016 10:16:18 GMT+00:00, Durga Srinivasu Karuturi
wrote:
>Hi,
>
>Shall i raise a defect?
Patience. Give the community a chance to look at it first. Given the time of
year, that might take longer than usual.
Mark
>
>Thanks,
>Durga Srinivasu
>
>On Wed, Dec 21, 2016 at 2:56 PM, D
Hi,
Shall i raise a defect?
Thanks,
Durga Srinivasu
On Wed, Dec 21, 2016 at 2:56 PM, Durga Srinivasu Karuturi <
durgasriniv...@gmail.com> wrote:
> Hi,
>
> We are stuck with this issue.
>
> Is this locally reproducible with sample web-app?
>
> Thanks,
> Durga Srinvasu
>
>
> On Tue, Dec 20, 2016
Mark,
Its locked up now and I have the dump but it wont let me email it. Can I
email the whole file somewhere?
Cheers Greg
On 22 December 2016 at 09:17, Mark Thomas wrote:
> On 22/12/2016 08:55, Greg Huber wrote:
> > I installed exactly the same versions on my newer centos 7 server and it
> >
OK, will see if I can do the dumps. Think i did something similar a while
back when tomcat got into a random loop/high cpu a while back.
Cheers Greg.
On 22 December 2016 at 09:17, Mark Thomas wrote:
> On 22/12/2016 08:55, Greg Huber wrote:
> > I installed exactly the same versions on my newer
On 22/12/2016 08:55, Greg Huber wrote:
> I installed exactly the same versions on my newer centos 7 server and it
> does not lock up.
>
> I have seem this problem before as the production box is old and very
> slow. There may have been some changes to the connector stuff for a
> map/list where it
I installed exactly the same versions on my newer centos 7 server and it
does not lock up.
I have seem this problem before as the production box is old and very
slow. There may have been some changes to the connector stuff for a
map/list where it is trying to add and remove at the same time causi
30 matches
Mail list logo
