aspose file tools
The moose likes Web Services and the fly likes SAAJ(1.1) INCOMPATIBILTY WITH JAVA 1.6 Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "SAAJ(1.1) INCOMPATIBILTY WITH JAVA 1.6" Watch "SAAJ(1.1) INCOMPATIBILTY WITH JAVA 1.6" New topic
Author

SAAJ(1.1) INCOMPATIBILTY WITH JAVA 1.6

Naveen Raghupatruni
Greenhorn

Joined: Jul 22, 2009
Posts: 2
We are using SAAJ 1.1 in our application.When the client is loaded with Java 1.5, SAAJ attachments are being downloaded successfully.
When the client is loaded with Java 1.6, SAAJ attachments are NOT being downloaded and we are getting erorr at 180MB.

Is this a known issue with SAAJ and Java1.6. Can anyone please help ?

Here is the below error we see at client console ::
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.readFully(HttpSOAPConnection.java:633)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:379)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:169)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:140)
at com.sun.sunit.webservice.soap.SOAPClient.invokeService(SOAPClient.java:94)
at com.sun.sunit.webservice.soap.SOAPClient.invokeService(SOAPClient.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:74)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:38)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:74)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:38)
at com.sun.sunit.bugtraq.client.command.ClientConnection.invokeService(ClientConnection.java:108)
at com.sun.sunit.bugtraq.client.command.CrGetAttachmentCommand.afterExecute(CrGetAttachmentCommand.java:157)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:74)
at com.sun.sunit.util.MethodUtil.invokeMethod(MethodUtil.java:38)
at com.sun.sunit.bugtraq.client.command.ClientConnection.invokeService(ClientConnection.java:108)

Is this a known issue with SAAJ and Java1.6. Can anyone please help ?

Thanks,
Naveen.
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24059
    
  13

Looks like you were just running with barely enough memory before, and 1.6 is using a little more, so you should just bump the heap size up a little?


[Jess in Action][AskingGoodQuestions]
Naveen Raghupatruni
Greenhorn

Joined: Jul 22, 2009
Posts: 2
We have increased heap size at client to 1gb but the download fails at little higher levels.

When using 1.5, attachments upto 2gb are downloading without any heap size specifications at client.

Thanks,
Naveen.
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: SAAJ(1.1) INCOMPATIBILTY WITH JAVA 1.6
 
Similar Threads
No identifier specified for entity:
SAAJ client issue
Error while running JBoss Server
after copy server.xml from jboss 4.0.3 to jboss 4.2, the server cannot be run
Application start through JMX fails for JBoss5xx