Per Reference Application 2.5 Released, Reference Application 2.5 has been released, and we have to get it up on demo.openmrs.org.
I understand there was some confusion about who will do this (and how). I presume that the infrastructure team owns and maintains demo.openmrs.org; or does someone else?
In practice I guess that (1) we need to deploy the new code, and (2) we need a new database snapshot so that on the (daily?) database reset, we go to the right state.
I see some changes on the downloads page and i do not know who is actually making them. I just wanted to add that the latest platform release is 2.0.1 instead of 1.11.6 or 2.0.0
I believe @jeffneiman made the changes to the web page, and it looks like this CI plan might be relevant: https://ci.openmrs.org/browse/DEMO.
I don’t know if there was a ticket on helpdesk for that (I can pretty much only see unresolved cases), so I don’t know any history.
This is everything I’ve found about the demo server:
What exactly is preventing me (or anyone with enough permissions, of course) to hit the button and deploy in Bamboo?
As per whose responsibility is that, I don’t particularly mind, but really it should be OK for release managers or anyone with enough knowledge to run the Bamboo deploy (if that’s working, of course). It’s better than waiting for us 
I updated our wiki to reflect those builds too.
I have tried to deploy the ref-app 2.5 but after successful deploy , i get 404 when i try demo.openmrs.org/openmrs. which has forced me to redeploy ref-app 2.4 and it works perfectly well, anything wrong. @dkayiwa i was deploying the same build that was deployed to the UAT
@jeffneiman are you the one who updated the downloads page? The current platform release is 2.0.1 not 2.0.0 and also ref-app 2.5 is built on platform 2.0.1 not 1.11.6
Problem with demo is the version of java installed. It has java 7, and it’s complaining about not having java 8 when starting.
I’m fairly sure we have a smoke test set somewhere, I can replicate that to demo deployment. Also I can print the tomcat logs to the build logs in case it fails.
But on the meanwhile, I have to discover how exactly we install java in demo
I guess by now you have Java upgraded. 
@dkayiwa refapp 2.5 is already released! i just said i was trying to deploy to the demo server the same build you had deployed on UAT
Well, I broke it
I’ve installed jdk8, restart tomcat in stage, the initial page loaded, did some database migrations.
I thought it was good and fine, but I had the following problem in demo:
2016-11-17 03:46:42,980 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1512 2016-11-17 03:46:42,984 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1513 2016-11-17 03:46:42,989 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1514 2016-11-17 03:46:42,993 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1517 2016-11-17 03:46:42,997 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1518 2016-11-17 03:46:43,001 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1519 2016-11-17 03:46:43,005 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1520 2016-11-17 03:46:43,009 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1521 2016-11-17 03:46:43,013 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1522 2016-11-17 03:46:43,017 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1523 2016-11-17 03:46:43,022 [pool-3-thread-1] INFO conf.BootStrap - Generated new download URL for Release id=1524 2016-11-17 03:46:46,831 [pool-3-thread-1] INFO conf.BootStrap - Performing bulk index 2016-11-17 03:47:29,562 [pool-3-thread-1] INFO conf.BootStrap - Starting mirror service Nov 17, 2016 3:47:30 AM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT Nov 17, 2016 3:47:30 AM org.apache.catalina.core.ContainerBase addChildInternal SEVERE: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1095) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1617) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 15 at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:131) at org.apache.tomcat.util.bcel.classfile.ConstantPool.(ConstantPool.java:60) at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:209) at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:119) at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2032) at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1923) at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1891) at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1877) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1270) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:855) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:345) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5161) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) … 10 more
Nov 17, 2016 3:47:30 AM org.apache.catalina.startup.HostConfig deployDirectory SEVERE: Error deploying web application directory /var/lib/tomcat7/webapps/ROOT java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:898) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1095) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1617) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Nov 17, 2016 3:47:30 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [“http-bio-8080”] Nov 17, 2016 3:47:30 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 265877 ms
Googling it, it appeared to be the version of tomcat we are using (http://stackoverflow.com/questions/6751920/tomcat-7-servlet-3-0-invalid-byte-tag-in-constant-pool/12730059#12730059 and https://bz.apache.org/bugzilla/show_bug.cgi?id=53735), but it wasn’t not trivial to upgrade. Also, several other test servers have the same version of tomcat!
So, I changed tomcat back to JAVA 7, and rollback 2.4 again. Of course it didn’t come alive 
Well, I just decided to roll forward to 2.5 again, but the application is down now
Can someone please help? @darius @raff @pascal @maany @burke
Am assuming that after upgrading to Java 8, you also changed tomcat to point to it. 
What is the exact version of tomcat that you are using?
LOL yes, tomcat is updated to use java 8, I made this mistake first!
7.0.26 tomcat, java 1.8.0_111, JRE only, headless.
@cintiadr is this in any way related to? Apache Tomcat/7.0.26 fails to run OpenMRS Platform 2.0 with the legacyui module
Maybe… is it ok to uninstall it for demo? If so, how can I do without causing drama, just deleting a couple of files?
If that’s the case, it would explain why some other environments work on the same tomcat version
I think its ok to uninstall it for demo.
@taremwatadeo since 2.5 is already released, when you did run the release again, you ended up by releasing reference application version 2.6, which should not be, and hence these failures: https://ci.openmrs.org/browse/RA-RA-2353. So i have deleted the 2.6 tag, which was a result of this, and changed from 2.7-SNAPSHOT back to 2.6-SNAPSHOT at https://github.com/openmrs/openmrs-distro-referenceapplication/commit/f7bbdad023a8230bd58974769a6dc7ef661c26ac