This content has been marked as final. Show 6 replies
It is a desktop problem totally unrelated to Marketo and/or SOAP API. I am familiar with this sort of Java errors.It is likely Java 6 is sending the XML request over SSLv2.
The solution is changing the client to use SSLv3 and above to avoid such interoperability issues.
The simplest and quickest solution is moving to Java 7.
Moving to java 7 is not an option. Can you explain what needs to be done?
I suggested Java 7 for a very strong reason: the life cycle of Java 6 ended in February 2013 therefore updates, fixes and support for that version have ceased. Running mission critical systems on unsupported version is a high and unnecessary risk no company should take.
Short considereation before you go for a deep dive into Java troubleshooting: reiterating my previous post, that is unrelated to Marketo. Oracle Global Support would be your best resource. I have been on that side for several years.
That error can range from simple malformed XML to convoluted Java configuration or conflictling SSL library versions.
ParseError at [row,col] means the response could not return any result. That is not zero record, that is really null.
You would start double checking whether the endpoint is correct. In the past it was similar to http://app.marketo.com/soap/mktows/2_2?WSDL
The new ones have the Munchkin ID embedded such as https://XXX-YYY-ZZZ.mktoapi.com/soap/mktows/2_2
It may an attempt to read data before it is actually written. That happens when multiple threads are used (Tomcat).
There are valuable Oracle documents to help you at http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/tutorial/doc/SJSXP4.html
Delete this - just noticed you are using Java
The endpoint used is according to new version. the problem does not happen always, it happens when a lot of SOAP messages are sent to Marketo, out of 70 for example, 5 fails with this error.
BTW, i used:
to solve other problems i encountered, this was recommended from this forum.
Might this cause the problem?
It is really a deep Java issue unrelated to Marketo. You just confirmed Oracle Support is the best resource to help you.
I have a fairly good idea what the problem is because I have been on that side for years. I just no longer can access the internal Metalink documents.