Jump to content


Photo

[Solved] Java deployment errors on Tommy (gebets)


  • This topic is locked This topic is locked
7 replies to this topic

#1 gebets

gebets

    Newbie

  • Members
  • 5 posts

Posted 08 December 2018 - 01:26 AM


"Java deployment failed with errors. For further information please contact support"

Gebets.

Trying to deploy the same war file that has been unchanged on the sever for several months and deployed fine previously. I am seeing the above message, please can someone provide more details.

#2 Krydos

Krydos

    Rank X Member

  • Root Admin
  • 17,316 posts
  • Gender:Male

Posted 08 December 2018 - 01:28 AM

Did you read https://www.helionet...tomcat-upgrade/ and https://www.helionet...59-tomcat-9012/ and did you get the email about upgrading Tomcat as well?

#3 Krydos

Krydos

    Rank X Member

  • Root Admin
  • 17,316 posts
  • Gender:Male

Posted 08 December 2018 - 01:32 AM

I tried deploying the .war for you and it worked fine for me.

#4 gebets

gebets

    Newbie

  • Members
  • 5 posts

Posted 08 December 2018 - 01:32 AM

Krydos, thanks for the quick reply, I'd missed that, I'll take a look at version 9.0.12 locally to try and replicate. Thanks.

#5 gebets

gebets

    Newbie

  • Members
  • 5 posts

Posted 08 December 2018 - 01:40 AM

Strange, I've tried deploying a couple of times in the past 24 hrs via cpanel/Java and on both occasions I've had the contact support error. I'll uplift local tomcat versions locally for consistency. Thanks for redeploying.

#6 gebets

gebets

    Newbie

  • Members
  • 5 posts

Posted 12 December 2018 - 01:43 PM

I've installed tomcat 9.0.12 locally and am not having any issues deploying my war file. It is a really simple web app consisting of just a single servlet to provide some admin functionality.

 

I've tried re-deploying my war via cpanel 3 times this afternoon and each time I'm hit with "Java deployment failed with errors. For further information please contact support"



#7 wolstech

wolstech

    Rank X Member

  • Root Admin
  • 9,564 posts
  • Gender:Male
  • Location:Pennsylvania

Posted 12 December 2018 - 05:23 PM

Lets have Krydos look at this again for you.


Please do not PM me for support. Posting on our forums lets all of us learn.

Do you play Minecraft? | Server Monitors | And the Dumbass of the Decade award goes to...


#8 Krydos

Krydos

    Rank X Member

  • Root Admin
  • 17,316 posts
  • Gender:Male

Posted 13 December 2018 - 04:30 AM

The error the deployment was giving was
13-Dec-2018 04:19:01.793 SEVERE [http-nio-8080-exec-26] com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container
 java.lang.OutOfMemoryError: unable to create new native thread
I restarted Tomcat and it deployed fine after that. I suspect someone else's .war is crashing the system by using up too many threads or memory. This is the same issue we had on Tomcat 8.5. When I have some time I'll try to figure out who.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users