• Zueri3
  • NEWBIE
  • 0 Points
  • Member since 2004

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 2
    Replies
hi

I'm using axis 1.1 to create cases from emails I get and upload the attachments (as an attachment to the case).
this program has been running for a few months now and yesterday I started getting errors on (SoapBindingStub)x.create((SObject[])y) that tell me: "attachment data exceeded maximum size"
unfortunately, I am unable to reproduce the error; I successfully uploaded a file of 1 MB today while none of yesterday's files exceeded 150 KB.
I am not exactly sure what the message is about, so I checked the organisation's storage usage. the storage limit is well over 3 GB with ~1.4 GB currently used.
is it possible that the api erroneously checks used space with the default enterprise edition limit of 1 GB?
this is just about the only thing I could think of that might cause such an error (or maybe attachments may use only a certain %age of storage space? or a single user may use only a certain amount of space?)...
the really weird thing is that out of 10 items only 2 failed and 8 worked both before and after the failed ones and I can't really see any meaningful difference in the files. it's not even the biggest files that fail.
also, if it were some programming error / encoding problem, I'd expect all 10 to fail...
the same thing applies for the storage space limits, really. I'd expect the program to fail to upload anything if I had run into some kind of limit...
so, as you can see, I'm quite clueless...any help would be appreciated.

thanks in advance
  • February 12, 2005
  • Like
  • 0
This is interesting, I haven't been able to find much about it. It happens on describeSObject. (axis 1.3)
Anyone have this problem before?
J



AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: CRLF expected at end of chunk: 72/84
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.io.IOException: CRLF expected at end of chunk: 72/84
at org.apache.commons.httpclient.ChunkedInputStream.readCRLF(ChunkedInputStream.java:206)
at org.apache.commons.httpclient.ChunkedInputStream.nextChunk(ChunkedInputStream.java:218)
at org.apache.commons.httpclient.ChunkedInputStream.read(ChunkedInputStream.java:175)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at org.apache.commons.httpclient.AutoCloseInputStream.read(AutoCloseInputStream.java:107)
at java.io.FilterInputStream.read(FilterInputStream.java:111)
at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:214)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:134)
at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:87)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:105)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager$RewindableInputStream.read(XMLEntityManager.java:2622)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:1033)
at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.sforce.soap.partner.SoapBindingStub.describeSObject(SoapBindingStub.java:1347)
...
  • February 07, 2006
  • Like
  • 0
hi

I'm using axis 1.1 to create cases from emails I get and upload the attachments (as an attachment to the case).
this program has been running for a few months now and yesterday I started getting errors on (SoapBindingStub)x.create((SObject[])y) that tell me: "attachment data exceeded maximum size"
unfortunately, I am unable to reproduce the error; I successfully uploaded a file of 1 MB today while none of yesterday's files exceeded 150 KB.
I am not exactly sure what the message is about, so I checked the organisation's storage usage. the storage limit is well over 3 GB with ~1.4 GB currently used.
is it possible that the api erroneously checks used space with the default enterprise edition limit of 1 GB?
this is just about the only thing I could think of that might cause such an error (or maybe attachments may use only a certain %age of storage space? or a single user may use only a certain amount of space?)...
the really weird thing is that out of 10 items only 2 failed and 8 worked both before and after the failed ones and I can't really see any meaningful difference in the files. it's not even the biggest files that fail.
also, if it were some programming error / encoding problem, I'd expect all 10 to fail...
the same thing applies for the storage space limits, really. I'd expect the program to fail to upload anything if I had run into some kind of limit...
so, as you can see, I'm quite clueless...any help would be appreciated.

thanks in advance
  • February 12, 2005
  • Like
  • 0