-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 2/3/20 2:10 PM, Peter Rader wrote:
>> Does it ever work?
>
> Yes, I deployed and redeployed much larger WARs (i.e. 107MiB) many
> times to the same instance.
>
>>
>> The Tomcat manager has a default limit of 50MiB for uploads. Your
>>
> Does it ever work?
Yes, I deployed and redeployed much larger WARs (i.e. 107MiB) many times to the
same instance.
>
> The Tomcat manager has a default limit of 50MiB for uploads. Your WAR
> file it larger than that, so it might be failing.
Some weeks ago I changed this default limit to
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 2/2/20 11:31 AM, Peter Rader wrote:
> Hi,
>
> I am using maven to redeploy a application.
>
> Maven returning: [ERROR] Failed to execute goal
> org.codehaus.mojo:tomcat-maven-plugin:1.1:redeploy (default-cli) on
> project xxx: Cannot
> Please post updates to the original thread.
This is the original thread.
> As suggested in the original thread, it was a permissions issue ...
> permission denied because the port was already in use : )
Why do you think it is a permission issue? I already disproved that! How can
you break it
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
On Sun, Feb 2, 2020, 10:31 Peter Rader wrote:
> Hi,
>
> I am using maven to redeploy a application.
>
> Maven returning:
> [ERROR] Failed to execute goal
> org.codehaus.mojo:tomcat-maven-plugin:1.1:redeploy (default-cli) on project
> xxx: Cannot invoke Tomcat manager: Error writing to server ->
Hi,
I am using maven to redeploy a application.
Maven returning:
[ERROR] Failed to execute goal
org.codehaus.mojo:tomcat-maven-plugin:1.1:redeploy (default-cli) on project
xxx: Cannot invoke Tomcat manager: Error writing to server -> [Help 1]
10 matches
Mail list logo
