I have been developing for JIRA for over a year without a problem. Today I have tried to create a sample plugin for confluence following the basic tutorial, but when I do the atlas-run command, I get an error suggesting that JVM had crashed somewhere along the way. Sometimes I can get to a login screen and crash occurs when I try to access some page, sometimes it just dies during startup.
Im confused since everything works fine for my local JIRA servers.
[INFO] [talledLocalContainer] 2019-03-25 10:49:20,575 DEBUG [374:StdOutHandler [C:\Program Files\Java\jdk1.8.0_31\jre\bin\java.exe]] [plugins.synchrony.bootstrap.LoggingOutputHandler] processLine {"synchrony":{"request":{"remote-addr":"127.0.0.1","uri":"/synchrony/heartbeat","request-method":"get","query-string":null},"response":{"status":200},"ns":"synchrony.middleware.logging","level":"info","message":"synchrony.middleware.logging [info] null"}}
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # A fatal error has been detected by the Java Runtime Environment:
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006ff91460, pid=7068, tid=6236
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # JRE version: Java(TM) SE Runtime Environment (8.0_31-b13) (build 1.8.0_31-b13)
[INFO] [talledLocalContainer] # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.31-b07 mixed mode windows-amd64 compressed oops)
[INFO] [talledLocalContainer] # Problematic frame:
[INFO] [talledLocalContainer] # V [jvm.dll+0xa1460]
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # An error report file with more information is saved as:
[INFO] [talledLocalContainer] # C:\JIRA\confluenceBp\target\container\tomcat8x\cargo-confluence-home\hs_err_pid7068.log
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] # If you would like to submit a bug report, please visit:
[INFO] [talledLocalContainer] # http://bugreport.java.com/bugreport/crash.jsp
[INFO] [talledLocalContainer] #
[INFO] [talledLocalContainer] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[INFO] [talledLocalContainer] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=48m; support was removed in 8.0
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:1990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:1990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:53 min
[INFO] Finished at: 2019-03-25T10:53:55+01:00
[INFO] Final Memory: 43M/199M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.2.6:run (default-cli) on project confluenceBp: Unable to execute mojo: Execution null of goal org.codehaus.cargo:cargo-maven2-plugin:1.4.7:start failed: Deployable [http://localhost:1990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
The content of hs_err_pid7068.log - https://pastebin.com/8dMVusMM.
The Atlassian troubleshooting page for Confluence crashes suggests that usually the problem is with memory or seg faults, which doesnt seem to be my case.