-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
3.1.2, 3.2
-
1
-
Severity 3 - Minor
-
1
-
Steps to reproduce:
- Install an RPC plugin http://confluence.atlassian.com/display/CONFDEV/RPC+Module
- Use the service (remote client)
- Redeploy/upgrade the RPC plugin
- Upon next usage, Confluence returns IllegalArgumentException:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Tried to invoke method public abstract java.lang.String atlassian.confluence.extra.helloworldrpc.HelloWorldPublic.helloWorld() with arguments . The arguments do not match the signature.; nested exception is:
java.lang.IllegalArgumentException: object is not an instance of declaring class
faultActor:
faultNode:
faultDetail:
{}faultData:null
{http://xml.apache.org/axis/}hostname:azwandidesktop
Tried to invoke method public abstract java.lang.String atlassian.confluence.extra.helloworldrpc.HelloWorldPublic.helloWorld() with arguments . The arguments do not match the signature.; nested exception is:
java.lang.IllegalArgumentException: object is not an instance of declaring class
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1774)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2930)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
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 localhost.confluence.rpc.soap_axis.helloworld.HelloworldSoapBindingStub.helloWorld(HelloworldSoapBindingStub.java:101)
at com.azwandi.app.ConnectConfluence.main(ConnectConfluence.java:29)
Disconnected from the target VM, address: '127.0.0.1:65299', transport: 'socket'
Process finished with exit code 0
Flushing Confluence caches is not sufficient. A Confluence restart is required to get rid of the problem.
[CONFSERVER-19306] Broken Webservice when redeploying RPC Plugin Module
Developing SOAP Plugins with this bug is annoying.
Atlassian's plugin architecture is actually designed to develop and upload plugins without a Confluence restart.
This bug also affects Confluence 4.3 (and probably 5.x).
Please fix this bug.
Nearly three years old and no comment / edit from atlassian?!?
This bug prevents us from using continuous deployment in our project.
So hard to fix?
Super annoying bug 
We run into this problem all the time in the Confluence SharePoint Connector; we have to explicitly add a requirement to our upgrade notes telling Administrators to restart their Confluence server after upgrading the SharePoint Connector plugin, in order to work around this bug.
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center