Update from 3.4.10 to 3.5.0 - Klaros Test Management - Forum - Klaros-Testmanagement
Update from 3.4.10 to 3.5.0
sven finsterwalder, geändert vor 12 Jahren.
Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
Hello,
i try to update from 3.4.10 to 3.5.0 via command line installar.
I stop the application, install and restart it.
Now i open the webpage and at the bottom i see this: 3.4.10 - Build 647 (2012-02-03 22:25:27) and not 3.5.0 :-(
How can i check if the installation was successfull?
Thanks,
sven
i try to update from 3.4.10 to 3.5.0 via command line installar.
I stop the application, install and restart it.
Now i open the webpage and at the bottom i see this: 3.4.10 - Build 647 (2012-02-03 22:25:27) and not 3.5.0 :-(
How can i check if the installation was successfull?
Thanks,
sven
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
Hi Sven,
given that you haven chosen the correct installation path, there is the possibility that tomcat misses to redeploy the updated war file.
If you shutdown, manually delete <install_dir>/webapps/klaros-web directory and restart tomcat it should show the correct version.
Does this solve your problem?
Regards,
Torsten
given that you haven chosen the correct installation path, there is the possibility that tomcat misses to redeploy the updated war file.
If you shutdown, manually delete <install_dir>/webapps/klaros-web directory and restart tomcat it should show the correct version.
Does this solve your problem?
Regards,
Torsten
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
after i have delete that directory and start klaros again i saw the new version on klaros web, but when i try to update the database i got the following exception:
Problem in renderResponse: javax.el.ELException: /pages/include/includeDatabaseMigration.jspx @44,63 value="#{databaseMigration.activeRevision}": Error reading 'activeRevision' on type de.verit.klaros.web.migration.DatabaseMigration_$$_javassist_seam_38
I think tomorow i will start the update prozess again, because of my backups it is possibe
Problem in renderResponse: javax.el.ELException: /pages/include/includeDatabaseMigration.jspx @44,63 value="#{databaseMigration.activeRevision}": Error reading 'activeRevision' on type de.verit.klaros.web.migration.DatabaseMigration_$$_javassist_seam_38
I think tomorow i will start the update prozess again, because of my backups it is possibe
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
This looks like a database connectivity problem to me.
Are you sure that the database defined in <user.home>/.klaros/hibernate.properties is accessible?
If you are using derby, did you make sure there are no leftover tomcat processes present which are blocking the access?
Regards,
Torsten
Are you sure that the database defined in <user.home>/.klaros/hibernate.properties is accessible?
If you are using derby, did you make sure there are no leftover tomcat processes present which are blocking the access?
Regards,
Torsten
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
I retry it, but now my klaros-web directory is empty
stop klaros
i import the 3.4.10 db dump
delete klaros-web
start update by console
start klaros
wait and try to open klaros in webbrowser and got an 404 Error
stop klaros
i import the 3.4.10 db dump
delete klaros-web
start update by console
start klaros
wait and try to open klaros in webbrowser and got an 404 Error
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
The <install_dir>/logs directory should contain information about was is going on here.
An you please post the relevant sections or send them to support@verit.de?
An you please post the relevant sections or send them to support@verit.de?
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
Hi Torsten,
i have add the catalina.out file to this post.
i hope that helps to find the problem.
i have add the catalina.out file to this post.
i hope that helps to find the problem.
Anhänge:
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste BeiträgeINFO: Initializing Mojarra (1.2_14-b01-FCS) for context '/klaros-web_old'
This is puzzling me - which .war files or folders does your webapps folder contain?
There should be only one: klaros-web.war and only one klaros-web folder.
If there is anything else klaros related in this folder (besides the usual tomcat stuff like examples etc.) you should delete this after a shutdown and restart.
Hope this helps,
Torsten
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
Yes sure... i forgot to explain.
First there was a folder names klaros-web_old, because we dont want to delete the old web of 3.4.10 and rename the klaros-web folder to this. After that we delete this folder and now webapps looks like this:
4096 2012-03-06 12:15 ./
4096 2012-03-06 12:27 ../
4096 2011-09-05 16:27 docs/
4096 2011-09-05 16:27 examples/
4096 2012-03-06 11:58 klaros-web/
97152888 2012-02-29 15:27 klaros-web.war
4096 2011-09-05 16:27 manager/
4096 2011-09-05 16:27 ROOT/
And we restart a second time but there is no login page.
First there was a folder names klaros-web_old, because we dont want to delete the old web of 3.4.10 and rename the klaros-web folder to this. After that we delete this folder and now webapps looks like this:
4096 2012-03-06 12:15 ./
4096 2012-03-06 12:27 ../
4096 2011-09-05 16:27 docs/
4096 2011-09-05 16:27 examples/
4096 2012-03-06 11:58 klaros-web/
97152888 2012-02-29 15:27 klaros-web.war
4096 2011-09-05 16:27 manager/
4096 2011-09-05 16:27 ROOT/
And we restart a second time but there is no login page.
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0 (Antwort)
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste BeiträgeFirst there was a folder names klaros-web_old, because we dont want to delete the old web of 3.4.10 and rename the klaros-web folder to this.
This may explain the initial problems, as you actually had two different Klaros versions starting up on the same application server.
Please retry to delete the klaros-web folder (It gets unpacked from the war file on startup).
For me it looks like the exploded folder does not contain everything what is contained in the war.
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
It seem to work, but after a login i got that exception see attachment.
In the db-log there is no action, only in catalina.out
In the db-log there is no action, only in catalina.out
Anhänge:
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
Good to hear that it works now.
Thanks for reporting the log message, which is harmless (The db log will miss the project selection message) but still annoying.
Regards,
Torsten
Thanks for reporting the log message, which is harmless (The db log will miss the project selection message) but still annoying.
Regards,
Torsten
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
Ok, but when i try to edit a Test suite i got another exception:
in webbrowser -> Problem in renderResponse: null
cataline.out -> Log see attached
in webbrowser -> Problem in renderResponse: null
cataline.out -> Log see attached
Anhänge:
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
To my knowledge this error may only occur in the case when:
- The initial database migration for the 3.5 installation (DB Version 3.6 -> 3.7) has failed or been interrupted or
- a test result import (via Jenkins/Hudson) occurred on a pre-3.5 Klaros installation *after* a DB-Migration on the same database
You should start again from your database backup just to be on the safe side.
If all else fails: "UPDATE K_TEST_CASE_RESULT SET PENDING = false" or "UPDATE K_TEST_CASE_RESULT SET PENDING = 0" (for Derby)
should reset this field to the proper default.
- The initial database migration for the 3.5 installation (DB Version 3.6 -> 3.7) has failed or been interrupted or
- a test result import (via Jenkins/Hudson) occurred on a pre-3.5 Klaros installation *after* a DB-Migration on the same database
You should start again from your database backup just to be on the safe side.
If all else fails: "UPDATE K_TEST_CASE_RESULT SET PENDING = false" or "UPDATE K_TEST_CASE_RESULT SET PENDING = 0" (for Derby)
should reset this field to the proper default.
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste BeiträgeTorsten Stolpmann:
To my knowledge this error may only occur in the case when:
- The initial database migration for the 3.5 installation (DB Version 3.6 -> 3.7) has failed or been interrupted or
If all else fails: "UPDATE K_TEST_CASE_RESULT SET PENDING = false" or "UPDATE K_TEST_CASE_RESULT SET PENDING = 0" (for Derby)
should reset this field to the proper default.
- The initial database migration for the 3.5 installation (DB Version 3.6 -> 3.7) has failed or been interrupted or
If all else fails: "UPDATE K_TEST_CASE_RESULT SET PENDING = false" or "UPDATE K_TEST_CASE_RESULT SET PENDING = 0" (for Derby)
should reset this field to the proper default.
We use a postgre DB and yes we had an error at the initial database migration:
2012-03-06 13:30:37: ERROR, org.hibernate.util.JDBCExceptionReporter, http-18080-11 ERROR: column "pending" is of type boolean but expression is of type integer
Hint: You will need to rewrite or cast the expression.
Position: 41
2012-03-06 13:30:37: ERROR, de.verit.klaros.web.migration.FixTestCaseResultPendingFlagMigrator, http-18080-11
org.hibernate.exception.SQLGrammarException: could not execute native bulk manipulation query
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:92) ~[hibernate-core-3.6.8.Final.jar:3.6.8.Final]
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) ~[hibernate-core-3.6.8.Final.jar:3.6.8.Final]
at org.hibernate.engine.query.NativeSQLQueryPlan.performExecuteUpdate(NativeSQLQueryPlan.java:219) ~[hibernate-core-3.6.8.Final.jar:3.6.8.Final]
at org.hibernate.impl.SessionImpl.executeNativeUpdate(SessionImpl.java:1310) ~[hibernate-core-3.6.8.Final.jar:3.6.8.Final]
at org.hibernate.impl.SQLQueryImpl.executeUpdate(SQLQueryImpl.java:396) ~[hibernate-core-3.6.8.Final.jar:3.6.8.Final]
at de.verit.klaros.web.migration.FixTestCaseResultPendingFlagMigrator.migrate(FixTestCaseResultPendingFlagMigrator.java:54) ~[FixTestCaseResultPendingFlagMigrator.cl
ass:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_30]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_30]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:32) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
at de.verit.klaros.web.migration.FixTestCaseResultPendingFlagMigrator_$$_javassist_seam_46.migrate(FixTestCaseResultPendingFlagMigrator_$$_javassist_seam_46.java) [F
ixTestCaseResultPendingFlagMigrator.class:na]
at de.verit.klaros.web.migration.DatabaseMigration.migrate(DatabaseMigration.java:198) [DatabaseMigration.class:na]
at de.verit.klaros.web.migration.DatabaseMigration.migrateToCurrentRevision(DatabaseMigration.java:127) [DatabaseMigration.class:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_30]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_30]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam-2.2.2.Final.jar:2.2.2.Final]
We then alter the column from an bolean to an integer and start the application again.
DB-Log to that error:
2012-03-06 13:30:37 CET klaros klaros ERROR: column "pending" is of type boolean but expression is of type integer at character 41
2012-03-06 13:30:37 CET klaros klaros HINT: You will need to rewrite or cast the expression.
2012-03-06 13:30:37 CET klaros klaros STATEMENT: UPDATE K_TEST_CASE_RESULT SET PENDING = 0
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0 (Antwort)
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
Darn, this really is broken for PostgreSQL ...
thanks for reporting, we will put out a maintenance release ASAP.
thanks for reporting, we will put out a maintenance release ASAP.
sven finsterwalder, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0
Padawan Beiträge: 28 Beitrittsdatum: 25.05.11 Neueste Beiträge
thank you we are looking forward to hearing from you and the maintenance release.
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Update from 3.4.10 to 3.5.0 (Antwort)
Jedi Council Member Beiträge: 759 Beitrittsdatum: 12.02.09 Neueste Beiträge
This has been tracked as KLAROS-1548 (Migration for PostgreSQL is unable to update the pending field correctly) and fixed towards version 3.5.1 which is available now.
This bug prevented existing Users using PostgreSQL from upgrading successfully. Updating to 3.5.1 lets the upgrade complete successfully.
Thanks for reporting and sorry for the inconvenience,
Torsten
This bug prevented existing Users using PostgreSQL from upgrading successfully. Updating to 3.5.1 lets the upgrade complete successfully.
Thanks for reporting and sorry for the inconvenience,
Torsten