CODEWITHSUNDEEP
servletsejbejb-3.0web.xmlout-of-memory
aspiringCoder
aspiringCoder

Reputation: 415

webapp version 2.4 to 2.5 out of memory

I have a requirement to update the EJB version of an application which has a schema version of 2.4, the ejb version being upgraded to is 3.0 which uses annotations, in order for the annotations to be read I need to upgrade the web app version to 2.5. When I do that and go to redeploy the app I see a out of memory error.

Can anyone push me in the right direction as to what is happening here?

00000034 annotations I ArchiveInputStreamData mapData Collision on [ .class ] in [ Demo.war ] 00000034 annotations I ArchiveInputStreamData mapData Collision on [ .class ] in [ Demo.war ] 00000034 annotations I ArchiveInputStreamData mapData Collision on [ .class ] in [ Demo2.war ]

I can't put the whole thread due to privacy, its running on Was 8.0.0.2 and java 6, really after that snippet about I see lots of

Which suggests and out of memory now I had the webapp version of 2.4 previously all I did was change the header to

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

thanks,

Stefan

Upvotes: 0

Views: 1112

Answers (1)

Ravi Trivedi
Ravi Trivedi

Reputation: 2360

This is the right header. I don't see version=2.5 line in your dump.

<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

Beside this, in absence of error trace, I can guess that your web.xml may not be in order according to new schema rules.

You can still post the error trace. Just remove the classes so that privacy can be maintained. It only becomes guessing games when full or important part of error trace is not present.

Upvotes: 1

Related Questions