search

google-code-export / maven-confluence-plugin

Automatically exported from code.google.com/p/maven-confluence-plugin
1 stars 0 forks source link

Error: "RPC handler object "confluence1" not found and no default handler registered" #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Simply running on my Maven project: 
mvn -X confluence-reporting:deploy

What is the expected output? What do you see instead?
has been imposssible connect to confluence due exception: java.lang.Exception: 
RPC handler object "confluence1" not found and no default handler registered -> 
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.bsc.maven:maven-confluence-reporting-plugin:3.4.2:deploy (default-cli) on 
project silbury_newsletter: has been imposssible connect to confluence due 
exception
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
    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 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: has been imposssible 
connect to confluence due exception
    at org.bsc.maven.confluence.plugin.AbstractBaseConfluenceMojo.confluenceExecute(AbstractBaseConfluenceMojo.java:166)
    at org.bsc.maven.confluence.plugin.ConfluenceDeployMojo.generateProjectReport(ConfluenceDeployMojo.java:313)
    at org.bsc.maven.confluence.plugin.ConfluenceDeployMojo.execute(ConfluenceDeployMojo.java:195)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    ... 19 more
Caused by: org.codehaus.swizzle.confluence.ConfluenceException: 
java.lang.Exception: RPC handler object "confluence1" not found and no default 
handler registered
    at org.codehaus.swizzle.confluence.Confluence.call(Confluence.java:934)
    at org.codehaus.swizzle.confluence.Confluence.call(Confluence.java:896)
    at org.codehaus.swizzle.confluence.Confluence.call(Confluence.java:882)
    at org.codehaus.swizzle.confluence.Confluence.login(Confluence.java:146)
    at org.codehaus.swizzle.confluence.ConfluenceFactory.createInstanceDetectingVersion(ConfluenceFactory.java:33)
    at org.bsc.maven.confluence.plugin.AbstractBaseConfluenceMojo.confluenceExecute(AbstractBaseConfluenceMojo.java:156)
    ... 23 more

What version of the product are you using? On what operating system?
3.4.2 on Ubuntu 13.10

Please provide any additional information below.

Original issue reported on code.google.com by bruce.th...@gmail.com on 2 Dec 2013 at 9:33

GoogleCodeExporter commented 9 years ago 
Hi

thx for feedback

Could you attach the pom file or just the plugin configuration ?

Seems a communication problem with confluence. It looks like the XMLRPC service 
at the Confluence isn't available. Has you enabled it? (see 
https://confluence.atlassian.com/display/DOC/Enabling+the+Remote+API)

Original comment by bartolom...@gmail.com on 4 Dec 2013 at 1:46

GoogleCodeExporter commented 9 years ago 
Sure thing!  Thank you for taking a look.

The XMLRPC is up and running at at the endpoint.  If I go to it in the browser, 
I see the XML response is here:
http://pastebin.com/BCJD58un

The POM configuration is here:
http://pastebin.com/DpLLqgg9

Original comment by bruce.th...@gmail.com on 4 Dec 2013 at 2:23

GoogleCodeExporter commented 9 years ago 
which version of confluence are you using for ?

Original comment by bartolom...@gmail.com on 4 Dec 2013 at 2:48

GoogleCodeExporter commented 9 years ago 
We are using Atlassian and they recently upgraded to 5.3..

Original comment by bruce.th...@gmail.com on 4 Dec 2013 at 2:56

GoogleCodeExporter commented 9 years ago 
Hi

Unfortunately i'm not able to reproduce problem

i've tried using confluence version 5.3.1-4528 and all works well

When plugin starts do you see a log message like this:

    [INFO] Confluence version [5.3.1-4528] development version [false]

If yes ... in your case what's  exactly your message ?

Original comment by bartolom...@gmail.com on 4 Dec 2013 at 11:51

GoogleCodeExporter commented 9 years ago 
Thank you for such great communication!

I don't see an INFO level log statement with the version of Confluence because 
I suspect that it hasn't connected yet.

I read the documentation 
(https://developer.atlassian.com/display/CONFDEV/Confluence+XML-RPC+and+SOAP+API
s) and it says that they are using the version 2 of the API so all requests 
need to be prefixed with "confluence2".  This might be the mismatch?  What do 
you think?

Original comment by bruce.th...@gmail.com on 5 Dec 2013 at 9:55

GoogleCodeExporter commented 9 years ago 
I think I found the problem!  Whomever did the configuration of Jira+Confluence 
did it in such a way as the default exposed RPC API is the Jira one.... so I 
can log in with my little XML RPC client pointing to "jira1.login" and it 
succeeds.

So, I will now have to sift through the configuration.

Thank you for your help! :)

Original comment by bruce.th...@gmail.com on 5 Dec 2013 at 11:05

GoogleCodeExporter commented 9 years ago 
You are absolutely right 

there are two supported protocols:  confluence1 and confluence2(>4) 

I built a factory to identify confluence's version and switch to the right 
protocol assuming that login service is supported always on confluence1

This assumption has always worked fine ... except in your case

I'll arrange a branch and SNAPSHOT that will perform login upon confluence2 
protocol in order to understand if it is there the problem

I'll keep you informed when it will be ready

Original comment by bartolom...@gmail.com on 6 Dec 2013 at 9:56

GoogleCodeExporter commented 9 years ago 
I have fixed the problem!  It was that I was connecting to Jira and not 
Confluence.  A simple user error on my part.  The plugin code looks great and 
works like a charm!  Thank you for your help! :)

Original comment by bruce.th...@gmail.com on 6 Dec 2013 at 10:13

GoogleCodeExporter commented 9 years ago 
Great new!

Thank you for using it .. allowing me to continuously improve it ;-)

Original comment by bartolom...@gmail.com on 6 Dec 2013 at 12:27