-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 2/2/20 4:48 PM, Peter Rader wrote:
> The old version of the application had a daemon that have not yet
> finished his execution.
Tomcat cannot detect this situation, so it's unlikely to be the direct
problem. How did you come to your
On Sun, Feb 2, 2020, 15:49 Peter Rader wrote:
> The old version of the application had a daemon that have not yet finished
> his execution.
>
> Unfortuantely there is no further logging why the old version not stoped
> yet.
>
> I expected to have the "mvn redeploy" waiting forever for this
>
The old version of the application had a daemon that have not yet finished his
execution.
Unfortuantely there is no further logging why the old version not stoped yet.
I expected to have the "mvn redeploy" waiting forever for this deamon-locked
problem. What I can not do is write a bug report
Thank you for your reply.
> Always look for the last "Caused by" in a stack trace for root cause. An
> "IOException: Error writing to server" is indicative of a permissions
> issue - I would start there, possibly the user account running the process.
As pointed out in No. 3 the log said that the
