[Kagilum]

Ok i dont know how but the Problem with the login doesn´t exit anymore now. But we are having a Problem in the App. Everytime i try to create or change a story etc. the message appers : iceScrum doesn’t have enough memory. Please contact your admin (more information in log file)
.

But it is taking the changes or creating the story. So not a big Problem.

But i cant login on my server with putty anymore with the message: Server unexpectedly closed network connection. So i cant get to the log file. I still see the Ressourcen of the Server in my Parellels Power Panel und the RAM has 1,5 gb free space. But i dont have access to the File-Managaer.

I hope you can help me.

[Kagilum]

Hi,

I wrote a small chrome extension to solve this problem :

https://chrome.google.com/webstore/detail/icescrum-optimizer/gehkpoaijpigjieajnpoibifhdibhidf

Feel free to ask anything that can improve the usability of IceScrum until they deliver the new UI.

[Kagilum]

Back from my vacation.

I found a tutorial http://jramier.wordpress.com/2014/04/08/install-icescrum-for-agile-project/

Only in the last step he mentions jbdc.jar but I cant find that file. not even with

sudo find -name jbdc.jar

I installed mysql-server and added this line to
/etc/icescrum/icescrum_config.properties

//Project

icescrum.project.import.enable = true

icescrum.project.export.enable = true

icescrum.project.creation.enable = true

icescrum.project.private.enable = true

icescrum.project.private.default = false





// Users

icescrum.gravatar.secure = false

icescrum.gravatar.enable = true

icescrum.registration.enable = true

icescrum.login.retrieve.enable = true





// Alerts

icescrum.auto_follow_productowner = true

icescrum.auto_follow_stakeholder  = true

icescrum.auto_follow_scrummaster  = true

icescrum.alerts.errors.to = "jonathan.ramier@kolibri.com"

icescrum.alerts.subject_prefix = "[icescrum]"

icescrum.alerts.enable = true

icescrum.alerts.default.from = "webmaster@icescrum.org"





//Attachments

icescrum.attachments.enable = true



// Server Url

grails.serverURL = http://it.aramisautode.com/icescrum





// Logging

icescrum.debug.enable = false

icescrum.securitydebug.enable = false





// Working directory

icescrum.baseDir = /usr/local/icescrum





// Cross Origin

icescrum.cors.enable = true

icescrum.cors.allow.origin.regex = "*"





// DataBase MySQL

dataSource.driverClassName=com.mysql.jdbc.Driver

dataSource.dialect=org.hibernate.dialect.MySQLDialect

dataSource.url=jdbc:mysql://localhost:3306/icescrum?useUnicode=true&characterEncoding=utf8&autoReconnect=true

//dataSource.dbCreate=update // permit to update database

dataSource.dbCreate=create // permit to recreate database, uncomment at first launching

dataSource.username = root

dataSource.password =

I now get this error in the tomcat log

INFO: Deploying web application archive /var/lib/tomcat7/webapps/icescrum.war

Oct 29, 2014 1:28:01 PM org.apache.catalina.loader.WebappClassLoader validateJarFile

INFO: validateJarFile(/var/lib/tomcat7/webapps/icescrum/WEB-INF/lib/geronimo-servlet_3.0_spec-1.0.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class

Oct 29, 2014 1:28:27 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Error listenerStart

Oct 29, 2014 1:28:27 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/icescrum] startup failed due to previous errors

Oct 29, 2014 1:28:27 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/icescrum] registered the JDBC driver [org.hsqldb.jdbcDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has bee$

Oct 29, 2014 1:28:27 PM org.apache.catalina.startup.HostConfig deployDirectory

INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT

Oct 29, 2014 1:28:27 PM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["http-bio-8080"]

Oct 29, 2014 1:28:28 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 27745 ms

Oct 29, 2014 1:28:43 PM org.apache.catalina.loader.WebappClassLoader validateJarFile

INFO: validateJarFile(/var/lib/tomcat7/webapps/icescrum/WEB-INF/lib/geronimo-servlet_3.0_spec-1.0.jar) - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: javax/servlet/Servlet.class

Oct 29, 2014 1:28:57 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Error listenerStart

Oct 29, 2014 1:28:57 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/icescrum] startup failed due to previous errors

Oct 29, 2014 1:28:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/icescrum] registered the JDBC driver [org.hsqldb.jdbcDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has bee$

[Kagilum]

I also got this problem while I can execute «java -version» via command line.
I fixed it by reinstall java 32bits version instead.

my environment –
– WIN Server 2012
– jdk 7 32bits
– icescrum R6#13.2

[Kagilum]

Thnx for the reply. Guess I’ll install sql then 🙂 thank you, wil let you know if it works

[Kagilum]

Hi Nicolas,

Right. I meant to say that the stories are «Planned».

Thank you for the suggestion. I will try it out.

Brian

[Kagilum]

Hi Nicolas,

Thank you for the reply.

Actually our requirement is distinguish INPROGRESS status into two status as DEVEVEOPMENT INPROGRESS and TESTING INPROGRESS.

[Kagilum]

Yes, sprint 2 is “In Progress” but the tasks are “Planned”.

[Kagilum]

Hi Nicolas,

Thank you for the response. You are right; the stories in this sprint are all in a state of “Planned”. The only exception is a story that was moved forward from the last sprint, whose state is “In Progress” and can be declared as done.

The question now is how do I change the state of the other stories to “In Progress”?

Thanks again,

Brian

[Kagilum]

Merci pour ces informations, je comprends mieux comment cet indicateur est généré.

Il me semble tout de même que cette façon de générer ce graphe pose 2 problèmes :

– A la fin d’un sprint, le graphe n’indique pas le reste à faire. Il faut démarrer un nouveau sprint pour le savoir (comment faire lorsqu’il s’agit du dernier sprint ?). Le graphe donne donc l’évolution du projet avec une vision «sprint N-1». Est-ce que le principe d’un burndown n’est pas de se mettre à jour à la fin d’un cycle afin de montrer ce qui est «Done» (fin de journée, fin de sprint, fin de release) ?

– En prenant toutes les stories estimées, le graphe mélange les stories de la release et les stories de la backlog pouvant être estimées par anticipation des futurs releases. Il faut donc s’interdire d’estimer des Stories de la backlog (non prévues dans la release courante) pour ne pas fausser cet indicateur si l’on souhaite rester au niveau «release».

[Kagilum]

Bonjour Nicolas,

Merci pour ces éléments.
Pour bien comprendre, est-ce que le nombre de points déclarés sur ce graphe représentent la somme des stories non finies et déclarées dans le plan de release (menu plan de release) à la fin de chaque sprint ?
Pouvez vous me confirmer qu’il ne s’agit pas de la somme des stories non finies dans le Product Backlog ?

[Kagilum]

Thank you Nicolas, your post gives a direction for a solution.

[Kagilum]

Thank you

[Kagilum]

Hi Nicolas,

Thanks for your reply, I’ll try to switch to Tomcat 8

Regards,
Bassam

[Kagilum]

thank you 😉 , the problem is solved

[Autor]

Entradas