Not able to start IceScrum 6.14.10 in Tomcat 7

[jlabuelo]

Hi all
I am trying to start icescrum, following the install guide, moving the war file to our tomcat 7 (under Java7), however even tomcat logs show that incscrum has been deoployed correctly… when we type in our browser
localhost:8080/icescrum takes forever and nothing is shown.

In the icescrum.logs we get these errors:

2016-07-12 22:07:24,706 [Thread-3] ERROR org.hibernate.util.JDBCExceptionReporter  - Column not found: ADDED in statement [SELECT id, added, modified, removed, added_data, modified_data, removed_data FROM icescrum2_scm_commit]
2016-07-12 22:07:28,487 [Thread-3] ERROR org.hibernate.util.JDBCExceptionReporter  - Column not found: TEXT_AS in statement [SELECT id, text_as, textican, text_to
                                                                 FROM icescrum2_story
                                                                 WHERE text_as IS NOT NULL OR textican IS NOT NULL OR text_to IS NOT NULL]

and

2016-07-12 22:07:38,097 [Thread-3] WARN  grails.util.GrailsUtil  - [WARNING] Property [data] of domain class pl.burningice.plugins.image.ast.Image has type [[B] and doesn't support constraint [blank]. This constraint will not be checked during validation.
2016-07-12 22:07:41,222 [Thread-3] INFO  AutobaseGrailsPlugin  - ---- Starting Autobase migrations  ----
2016-07-12 22:07:41,503 [Thread-3] INFO  liquibase.ext.logging.LiquibaseSlf4jLogger  - Waiting for changelog lock....
2016-07-12 22:07:51,503 [Thread-3] INFO  liquibase.ext.logging.LiquibaseSlf4jLogger  - Waiting for changelog lock....
2016-07-12 22:08:01,503 [Thread-3] INFO  liquibase.ext.logging.LiquibaseSlf4jLogger  - Waiting for changelog lock....
2016-07-12 22:12:41,550 [Thread-3] ERROR org.springframework.web.context.ContextLoader  - Context initialization failed
org.springframework.beans.factory.access.BootstrapException: Error executing bootstraps; nested exception is org.codehaus.groovy.runtime.InvokerInvocationException: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by SD1111100149 (192.168.2.12) since 12/07/16 14:42
	at org.codehaus.groovy.grails.web.context.GrailsContextLoader.createWebApplicationContext(GrailsContextLoader.java:87)
	at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
	at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4651)
	at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5154)
	at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5149)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.codehaus.groovy.runtime.InvokerInvocationException: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by SD1111100149 (192.168.2.12) since 12/07/16 14:42
	... 4 more
Caused by: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by SD1111100149 (192.168.2.12) since 12/07/16 14:42
	at liquibase.lockservice.LockService.waitForLock(LockService.java:81)
	at liquibase.lockservice.LockService$waitForLock.call(Unknown Source)
	at liquibase.LiquibaseDsl.update(LiquibaseDsl.groovy:63)
	at liquibase.LiquibaseDsl$update.call(Unknown Source)
	at autobase.Autobase.migrate(Autobase.groovy:43)
	at autobase.Autobase$migrate.call(Unknown Source)
	at AutobaseGrailsPlugin$__clinit__closure9.doCall(AutobaseGrailsPlugin.groovy:103)
	at AutobaseGrailsPlugin.invokeMethod(AutobaseGrailsPlugin.groovy)
	at AutobaseGrailsPlugin$_closure2.doCall(AutobaseGrailsPlugin.groovy:114)
	... 4 more

Any ideas about what must we perform to get icescrum running in our tomcat 7??

Thanks a lot!

[Vincent Barrier]

Hello,

I suspect that you restart at some point Tomcat when iceScrum was starting and doing some database stuff, this explains: liquibase.exception.LockException: Could not acquire change log lock.

If you don’t have any data, the simple thing to do is to delete the database and recreate it.

• Stop Tomcat
• Delete database
• Create an empty database
• – CHECK is you have remove tomcat-jdbc.jar from lib folder in tomcat folder (as documentation said)
• Start Tomcat with all parameters set (follow documentation)
• Wait around 60/70sec for iceScrum to start
• Enjoy

[jlabuelo]

Hello Vincent

Thanks a lot for your answer, seems that the error is gone now!.
However we are not able to start tomcat nor icescrum. Checking the icescrum.log files seems that everything has been created (DB, configuration…), but after one hour waiting we are not able to access tomcat home page neither icescrum.

Reviewing the log files in tomcat7-stderr.log we found this message

"Información: validateJarFile(C:\Archivos de programa\Apache Software Foundation\Tomcat 7.0\webapps\icescrum\WEB-INF\lib\geronimo-servlet_3.0_spec-1.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Exception in thread "Timer-0" Exception in thread "[Pool-Cleaner]:Tomcat Connection Pool[1-14775795]"

In icescrum.log we have this, which I think seems to be ok

2016-07-13 11:30:49,359 [Thread-3] INFO  org.codehaus.groovy.grails.web.context.GrailsConfigUtils  - [GrailsContextLoader] Grails application loaded.
2016-07-13 11:30:49,640 [Thread-3] INFO  org.atmosphere.cpr.AtmosphereFramework  - Installing BroadcastFilter class(es) org.atmosphere.client.TrackMessageSizeFilter
2016-07-13 11:30:49,671 [Thread-3] INFO  org.atmosphere.cpr.AtmosphereFramework  - Installed AtmosphereHandler org.icescrum.atmosphere.IceScrumAtmosphereHandler@153dd8b mapped to context-path: /stream/app/*
2016-07-13 11:30:49,718 [Thread-3] INFO  org.atmosphere.cpr.DefaultBroadcaster  - /stream/app/* support Out Of Order Broadcast: false
2016-07-13 11:30:49,734 [Thread-3] INFO  org.atmosphere.cpr.AtmosphereFramework  - Auto detecting WebSocketHandler in /WEB-INF/classes/

Any sugestion please?, thanks a lot once more!

[Vincent Barrier]

– Did you follow the install guide and set command line options? Could you share them here?
– Did you update the server.xml file as expected?

We need full log file and details as much as you can give us.

[jlabuelo]

Hi Vincent

Yes I have set up the setenv.bat file in the Tomcat7Dir/bin folder as this

set CATALINA_OPTS = -Dicescrum.log.dir = D:\Icescrum\Logs_Ice

set CATALINA_OPTS = %CATALINA_OPTS% -Duser.timezone=UTC -Dicescrum_config_location=D:\Icescrum\Logs_Ice\Config\config.groovy

set CATALINA_OPTS = %CATALINA_OPTS% -Xmx512m -XX:MaxPermSize=256m -Djava.awt.headless=true -server

And also have configured the server.xml including the lines suggested in the installation guide

  <Connector port="8080" protocol="org.apache.coyote.http11.Http11NioProtocol"
           connectionTimeout="2000" maxThreads="500" URIEncoding="UTF-8"
               redirectPort="8443" />

Also I have deleted the jdbc conector jar file in the Tomcat7Dir/lib folder….

When I launch tomact7 everything seems ok in the logs… but after serveral hours waiting nothing happens.

If you tell me how I can attach files to the forum I cam upload both files.

Cheers

[Nicolas Noullet]

Hi,

Can you tell us precisely which version of Java 7 and Tomcat 7 you use?

There is no built-in attachment on the forum. You can upload them on an online storing service (dropbox, google drive, https://gist.github.com/…) or send them by email at: nnoullet at kagilum . com.

[jlabuelo]

Hi There
it has been a couple of weeks I wanted to install Icescrum.war in our server, as I was not able, we decided to move to an «Icescrum.jar» installation and it worked fine. However we have found an issue in this «simple» installation and it is that this Icescrum install version is not accesible from an external ip address.

Going back to install the Icescrum.war version, we get this error message once we launch the tomcat7.exe :

Exception in thread «Timer-0»
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread «Timer-0»
Exception: in thread «[Pool-Cleaner]: Tomcat connection pool[1-29138338]»

Our Java version is 1.7.0_45 and our tomcat version is Tomcat 7

Our Catalina configuration is as follows:

export CATALINA_OPTS=-Xms128m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=1024m -Djava.awt.headless=true -server -Duser.timezone=UTC -Dicescrum_config_location=C:\Documents and Settings\Administrador\.icescrum -Dicescrum.log.dir=E:\IceScrumWar\logs

We have followed the installation instructions but we are not able to get Icescrum.war to be launched in our tomcat7, and we would like to get it accesible from external ip also.

any ideas please?

[jlabuelo]

Hi Again

I have been able to start now icescrum in tomcat 7. However the problem comes now when we try to recover the data already created with the icescrum.jar.

We have set the same configturation file config.groovy and set that the users directory under the same path as with icescrum.jar… but no configuration under config.groovy is taken and now Icescrum.war requires to enter the setup parameters again. Even introducing the same db connections etc… projects, tasks,… are not shown.

Is there any document that explains how to move from icescrum.jar to icescrum.war?

Thanks a lot

[Nicolas Noullet]

Hi, sorry for the late reply.

There is no documentation that explains how to migrate from icescrum.jar to icescrum.war because every case is different. Sometimes, it will just work out of the box depending on your environment and how you configured it.

In addition to the DB, iceScrum needs files on your filesystem. In most cases, the paths for these files can be configured but if you leave the default location then they depend on the start path of iceScrum and on the user who starts iceScrum. Moving from icescrum.jar to icescrum.war may change one or both of these contexts.

If you use an external DBMS (such as MySQL) then ensuring that the old config.groovy file is taken into account by your new installation should be enough.

If you use the default database (this is strongly not recommended, as stated in our documentation) then your data is stored under prodDba.script and prodDba.properties file in the start path of iceScrum.

If you want the old data to be taken into account in the new installation, first backup every prodDba file to be sure to avoid losing your data, don’t skip the backup step! Then the easiest way to do so is looking for the new prodDba files on your filesystem and replacing them by the old ones.

[Autor]

Entradas