Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
4.0
-
None
-
4
-
Description
A patch for 4.1.2 is available that fixes one category of known causes of this problem. Instructions for applying this patch are available JRA-20351-4.1.2-patch-instructions.txt
.
The patch is to basically replace the axis-1.3.jar in your JIRA install with the attached axis-1.3-altassian-1.jar. You must make sure you remove axis-1.3.jar or the patch may not work.
It seems that the AXIS internal map of SOAP types is not stable.
The WSDL generated by JIRA changes over time, especially after certain SOAP requests are made.
For example of this see JRA-19928
Other customers have reported that after a certain time the actual SOAP messages send back have different types
For example this is from a support case
When I start up JIRA and make a SOAP request for bug info (any old bug), I get (for example): </fixVersions><id xsi:type="xsd:string">23835 </id><key xsi:type="xsd:string">SS-4096 </key><priority xsi:type="xsd:string">7 </priority><project xsi:type="xsd:string">SS </project><reporter xsi:type="xsd:string">breichle </reporter><resolution xsi:type="xsd:string">1 </resolution><status xsi:type="xsd:string">6 </status><summary xsi:type="xsd:string">Sorting by Time column </summary><type xsi:type="xsd:string">1 </type> After some time, I make the same request and I get: <fixVersions soapenc:arrayType="ns2:RemoteVersion[1]" xsi:type="soapenc:Array"><fixVersions href="#id6"/> </fixVersions><id xsi:type="soapenc:string">23835 </id><key xsi:type="soapenc:string">SS-4096 </key><priority xsi:type="soapenc:string">7 </priority><project xsi:type="soapenc:string">SS </project><reporter xsi:type="soapenc:string">breichle </reporter><resolution xsi:type="soapenc:string">1 </resolution><status xsi:type="soapenc:string">6 </status><summary xsi:type="soapenc:string">Sorting by Time column </summary><type xsi:type="soapenc:string">1 </type>
Breden Bain did some investigations into this and found that the AXIS code does in fact change "serializers" in its internal map over time. not being an AXIS expert (and the fact that the code is complicated to say the least) he did not spend more time on it.
We need to get to the bottom of this as more and more support cases are coming in with this problem.
This is a placeholder issue to allow that work to be done.
As of JIRA 4.3.4 this problem is still occuring. e.g. support case EHSP-18282
The return types are base 64 encoded like this:
<customfieldId xsi:type="ns17:String" xmlns:ns17="http://lang.java"><bytes xsi:type="xsd:base64Binary">Y3VzdG9tZmllbGRfMTA0NjE=</bytes><empty xsi:type="xsd:boolean">false</empty></customfieldId>
Attachments
Issue Links
- causes
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...