Plugin development: Confluence 503 error?

[Meg Mitchell]

Hi,

I'm trying to start developing a simple Confluence plugin, but getting stuck at the setup stage. I followed the "helloworld" JIRA plugin tutorial without any issues. When I try to repeat the same steps to get a basic Confluence development environment up and running, I get a console message "confluence started successfully in 55s at http://HOSTNAME:1990/confluence". But actually going to this URL I get a 503 error. There's no error description on the page and the tomcat log directory is empty, so I'm not sure what the issue is. Is there something special or different I have to do to get Confluence running versus JIRA? Or any tips for further troubleshooting?

[paolovillella]

Same issue here, using both Java 1.7 and 1.8.

Some weeks ago it was running with no problems, allowing me to test the Atlassian Connect "Hello World" example. Now the on demand local version of JIRA is not starting at all, due to the "Unsupported major.minor version 52.0" error when deploying to Tomcat.

More information:

ATLAS Version: 5.0.4
ATLAS Home: /usr/share/atlassian-plugin-sdk-5.0.4
ATLAS Scripts: /usr/share/atlassian-plugin-sdk-5.0.4/bin
ATLAS Maven Home: /usr/share/atlassian-plugin-sdk-5.0.4/apache-maven-3.2.1

Issue had running the command:

atlas-run-standalone --product jira --version 6.5-OD-07-005 --bundled-plugins com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0.4,com.atlassian.webhooks:atlassian-webhooks-plugin:2.0.0,com.atlassian.jwt:jwt-plugin:1.2.2,com.atlassian.upm:atlassian-universal-plugin-manager-plugin:2.19.0.3-D20150522T180613,com.atlassian.plugins:atlassian-connect-plugin:1.1.36 --jvmargs -Datlassian.upm.on.demand=true

The output shows no errors, ending successfully with:

[INFO] [talledLocalContainer] Tomcat 7.x started on port [2990]
[INFO] jira started successfully in 164s at http://MacBook-Pro-di-pv.local:2990/jira
[INFO] Type Ctrl-D to shutdown gracefully
[INFO] Type Ctrl-C to exit

jira-LATEST.log excerpt:
 

SEVERE: Error configuring application listener of class com.atlassian.jira.web.ServletContextProviderListener
java.lang.UnsupportedClassVersionError: com/atlassian/jira/web/ServletContextProviderListener : Unsupported major.minor version 52.0 (unable to load class com.atlassian.jira.web.ServletContextProviderListener)

Hope someone has a clue. 
Thanks in any case. 

[Pavel]

Please make sure you are correctly setup java (e.g. check JAVA_HOME, PATH, mvn script may override java env, etc). It's working for me on sdk 5.0.4/5.0.13, java 8. I've got the same error after I setup java6 in my atlassian maven script.

[Boris]

Try using Java 1.8

[Fredrik Aron Riktor]

I'm running under java 1.8 now. I also notice that the documentation on setting up your development environment has started gravitating towards 1.8 over 1.6, although it is hardly consistent at this time. Plugin projects seem to be generated with 1.6 as preferred version, even though they do not work with 1.6. And while it is probably not related, I can no longer execute code from compile-scope-dependencies. May be some unrelated mishap, since I have made many changes since last time this seemed to work.

[Fredrik Aron Riktor]

It may not be a complete or suitable solution, but today I redownloaded the Atlassian-SDK and uninstalled the old one. I am now running on version 5.0.13 and Confluence plugin projects seem to work. I do not yet know this allows me to develop for our production system, as it runs another version of Confluence, but it might be an option for you.

(I also note that atlas-run-standalone --product JIRA now results in a site where the /jira/ folder returns 404. It seems that each version of the SDK has its share of crippling bugs, and I find no indication that Atlassian is aware of the problems we experience.)

[Fredrik Aron Riktor]

When jira (successfully) deploys its JIRA.war file the console lists an absolute path. When confluence fails to deploy its confluence.war file, the console lists only the filename. Also of note, jira seems to launch Tomcat 7.x, while confluence launches Tomcat 6.x. atlas-run-standalone --product confluence deploys a copy of confluence.war, console output listing absolute source and destination path in square brackets. The standalone launch lists no servere errors, and the resultant site is available (no 503). A freshly created plugin (atlas-create-confluence-plugin, followed by atlas-run from the created folder) fails (503).

[Fredrik Aron Riktor]

Extract from console, clearest error messages found: INFO: Deploying web application archive confluence.war apr 30, 2015 2:36:10 PM org.apache.tomcat.util.modeler.Registry registerComponent SEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/confluence,J2EEApplication=none,J2EEServer=none apr 30, 2015 2:36:10 PM org.apache.catalina.startup.HostConfig deployWAR SEVERE: Error deploying web application archive confluence.war java.lang.UnsupportedClassVersionError: com/atlassian/confluence/setup/ConfluenceConfigurationListener : Unsupported major.minor version 52.0 (unable to load class com.atlassian.confluence.setup.ConfluenceConfigurationListener) Extra details from "atlas-run -X" (verbose): URL [http://localhost:1990/cargocpc/index.html] is not responding: -1 java.net.ConnectException: Connection refused: connect Notifying monitor listener [org.codehaus.cargo.container.spi.deployer.DeployerWatchdog@161850a] Checking URL [http://localhost:1990/cargocpc/index.html] for status using a timeout of [600000] ms... URL [http://localhost:1990/cargocpc/index.html] is not responding: -1 java.net.ConnectException: Connection refused: connect Notifying monitor listener [org.codehaus.cargo.container.spi.deployer.DeployerWatchdog@161850a] Checking URL [http://localhost:1990/cargocpc/index.html] for status using a timeout of [600000] ms... Immediately before "confluence started successfully" it says "URL [http://localhost:1990/cargocpc/index.html] is responding...", but that is after the failure to deploy confluence.war and to load the class (UnsupportedClassVersion) com.atlassian.confluence.setup.ConfluenceConfigurationListener.

[Fredrik Aron Riktor]

I have the same problem. On Windows 7, XP (32-bit) and 2008 R2 with local firewalls disabled. I have tried with JDK 7 and Glassfish/JDK6 (as JAVA_HOME / PATH), and with variations of 64-bit and 32-bit jdks.

There is no console output when I try to access the confluence plugin page. (When I access the JIRA plugin page it says some jersey-stuff and then the page loads.)

I believe I made a functioning confluence plugin on my Windows 8 computer at some point, but that computer is presently out of order, and I have no idea what I might have done differently.