Ok this is resolved. It was permission issue. now tomcat runs under its own
user id and for some reason I missed to read tomcat.conf file.
Now it works however server start up is now very slow.
INFO: Server startup in 352544 ms
something which was very fast in earlier version 7.081 and 7.050
L
Hi,
Couple of hours(3 hrs) back I did yum update to install 7.0.82 version to
install latest security patch.
Yum update went well. Then tried to install ROOT war, after stopping and un
deploying existing ROOT.war. Deployment failed saying that ROOT folder
already exists. So deleted ROOT folder an
In my log file, I keep seeing Unable to login as service principal. (kerberos).
I followed these instructions:
https://tomcat.apache.org/tomcat-8.0-doc/windows-auth-howto.html
here is what I did:
I created a DNS entry for my intranet server. "pluto"
Ask my NT admin to create me a domain user (web_
On 26/10/17 20:17, Christopher Schultz wrote:
> So this is relying on the OpenSSLContext.finalize() method to clean-up
> after the native SSL context?
Correct.
> It's been "recommended" to not rely on
> finalizers for quite a long time. Is that advice no longer correct?
Like most general rule
On Thu, Oct 26, 2017 at 9:42 AM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> Just curious... why are you using BC and not the JVM-provided crypto
> provider? What JVM are you using?
>
When I first starting looking for examples on doing PGP encrypt
On Thu, Oct 26, 2017 at 3:00 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 10/16/17 9:43 AM, Chris Cheshire wrote:
>> On Fri, Oct 13, 2017 at 5:00 PM, Christopher Schultz
>> wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>
>>> When you say yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 10/26/17 12:07 PM, Mark Thomas wrote:
> On 26 October 2017 14:36:03 BST, Christopher Schultz
> wrote:
>> Mark,
>>
>> On 10/26/17 8:54 AM, Mark Thomas wrote:
>>> On 26/10/2017 09:31, Johan Compagner wrote:
Hi,
now with Lets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Darin,
On 10/26/17 10:56 AM, dbol...@dsginc.biz wrote:
> First I notice that we are not able to get to the app through the
> browser. The browser will just spin. Then I try to get to the
> TomCat host manager and never get the login box and it ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris and Keiichi,
On 10/17/17 5:31 PM, Chris Cheshire wrote:
> On Tue, Oct 17, 2017 at 3:44 AM, Keiichi Fujino
> wrote:
>> Hi
>>
>> You have set
>> factory="org.apache.tomcat.jdbc.pool.DataSourceFactory". In other
>> words, you do not use (tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 10/16/17 9:43 AM, Chris Cheshire wrote:
> On Fri, Oct 13, 2017 at 5:00 PM, Christopher Schultz
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>
>> When you say you have "autocommit disabled in mysql config" what
>> do you mean?
>>
>
>
Hi,
I have a webapp where the user can upload a PFX file to digitally sign PDF
files. After upgrading from 8.5.11(TomEE 7.0.3) to 8.5.23(TomEE
7.0.5-SNAPSHOT) I'm getting this exception:
java.security.UnrecoverableKeyException: failed to decrypt safe contents
entry: javax.crypto.BadPaddingExcepti
I do see a lot of these messages in the C:\Program Files\Apache Software
Foundation\Tomcat 8.523\logs\catalina.2017-10-26.log
26-Oct-2017 09:21:56.927 WARNING [localhost-startStop-2]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [WebSmart-api] appe
On 26 October 2017 14:36:03 BST, Christopher Schultz
wrote:
>Mark,
>
>On 10/26/17 8:54 AM, Mark Thomas wrote:
>> On 26/10/2017 09:31, Johan Compagner wrote:
>>> Hi,
>>>
>>> now with LetsCrypt its easy (and free) to get https up and
>>> running even if you just use tomcat But the problem is those
On 26/10/2017 09:31, Johan Compagner wrote:
. . .
But does tomcat monitor that file for changes and will it then use
the new one without restarting the whole server?
On 10/26/17, 5:54 AM, Mark Thomas replied:
Currently, no.
We have just added the ability to 9.0.x and 8.5.x to reload the
certi
Hi.
I will continue top-posting, because in this particular case it seems easier. Apologies
for that, it is against the list rules.
Looking at the log below, there is not much I can tell you, except this :
Log messages where the text starts with "org.restlet.engine" mean that they do not come
First I notice that we are not able to get to the app through the browser.
The browser will just spin. Then I try to get to the TomCat host manager
and never get the login box and it just spins. If I restart the TomCat
service then I can log into the host manager but not able to reach my app
They (oracle) first introduced this in Java9..
Its something that they don't expect that certain things are reused/cached
i believe
Now they backported that same bug also to java 8,
i think they already fixed it for the next java8 version:
https://bugs.openjdk.java.net/browse/JDK-8189789
On 26
Am 26.10.2017 um 15:36 schrieb Jörg Schubert:
Hello,
We have a very stange problem. Since updating java 8 to build 151 (x86-64),
tomcat is producing illegal compressed responses - sometimes. Firefox and
Chrome are complaining about content encoding errors. Firefox error message
is: an invali
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
Just curious... why are you using BC and not the JVM-provided crypto
provider? What JVM are you using?
- -chris
On 10/18/17 10:56 AM, Chris Cheshire wrote:
> Using bouncy castle v1.58, Tomcat 8.5, java 1.8.
>
> I have the unlimited securit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Atanu,
On 10/26/17 5:23 AM, Mark Thomas wrote:
> On 25/10/2017 13:08, Atanu Pal wrote:
>> Still can you help me explain little more about the root cause?
>>
>> That will help me to explain it to customer and setup a test
>> environment for future.
Hello,
We have a very stange problem. Since updating java 8 to build 151 (x86-64),
tomcat is producing illegal compressed responses - sometimes. Firefox and Chrome
are complaining about content encoding errors. Firefox error message is: an
invalid or unknown form of compression was used.
Tes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 10/26/17 8:54 AM, Mark Thomas wrote:
> On 26/10/2017 09:31, Johan Compagner wrote:
>> Hi,
>>
>> now with LetsCrypt its easy (and free) to get https up and
>> running even if you just use tomcat But the problem is those
>> certificate must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Markus,
On 10/25/17 10:53 AM, i...@flyingfischer.ch wrote:
>
>>
>> Yes, it's the SecureRandom initialization that is killing you.
>> Being a virtual server, it likely has no direct source of true
>> randomness so it needs to pull from whatever the
On 26/10/2017 09:31, Johan Compagner wrote:
> Hi,
>
> now with LetsCrypt its easy (and free) to get https up and running even if
> you just use tomcat
> But the problem is those certificate must be renewed every 3 months
> This is easy to do in a crontab script (that does the renew and makes a
> j
On 26/10/2017 02:49, Mukarram Baig wrote:
> hello good folks!
>
> I see that the endorsed directory related problem in tomcat 7.x for running
> in java 9 has been fixed by the patch by rjung in
> https://github.com/apache/tomcat70/commit/e7ae8664922cd54fabe847527bad614bcd5ce301#diff-da184cf589a251
On 25/10/2017 13:08, Atanu Pal wrote:
> Still can you help me explain little more about the root cause?
>
> That will help me to explain it to customer and setup a test
> environment for future.
> Thanks and Regards
> Atanu Pal
> E2Infosystems - Chennai
Difficult to say but a possible sequence of
Hi,
now with LetsCrypt its easy (and free) to get https up and running even if
you just use tomcat
But the problem is those certificate must be renewed every 3 months
This is easy to do in a crontab script (that does the renew and makes a
java keystore again)
So i can generate the pfx constantly j
27 matches
Mail list logo