This is a space where the community of Teamwork users can ask for support, explanations,
and also vote up or down questions, answers and feature requests.
>> Back to Teamwork's site.

Error on upgrading from 4.4 to 4.6

1

when i upgrade from 4.4 to 4.6 (i follow the instructions at the doc 100%) teamworks does not allow to login. catalina.out shows the following stacktrace:

org.jblooming.PlatformRuntimeException: Server time: 2011 02 15 19:30:10. An I/O error occured while sending to the backend.Server time: 2011 02 15 19:30:10. 
The exception thrown:

    at org.jblooming.persistence.hibernate.PlatformSchemaUpdater.updateToLatestVersion(PlatformSchemaUpdater.java:50)
    at com.twproject.waf.settings.TeamworkSettings.configureNeedingPersistence(TeamworkSettings.java:594)
    at org.jblooming.waf.configuration.LoaderSupport.afterPersistenceSetupForApp(LoaderSupport.java:335)
    at org.jblooming.waf.configuration.LoaderSupport.afterPersistenceSetup(LoaderSupport.java:329)
    at org.jblooming.waf.configuration.LoaderSupport.start(LoaderSupport.java:206)
    at org.jblooming.waf.configuration.LoaderSupport.contextInitialized(LoaderSupport.java:71)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:926)
    at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:889)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
    at org.apache.catalina.core.StandardService.start(StandardService.java:516)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.
    at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:214)
    at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
    at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:340)
    at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:286)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:68)
    at org.logicalcobwebs.cglib.proxy.Proxy$ProxyImpl$$EnhancerByCGLIB$$aab3cfcc.executeUpdate(<generated>)
    at org.jblooming.persistence.hibernate.HibernateUtilities.generateSchema(HibernateUtilities.java:170)
    at org.jblooming.persistence.hibernate.PlatformSchemaUpdater.updateToLatestVersion(PlatformSchemaUpdater.java:44)
    ... 29 more
Caused by: java.net.SocketException: Socket closed
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.io.BufferedInputStream.fill(Unknown Source)
    at java.io.BufferedInputStream.read(Unknown Source)
    at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:256)
    at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1163)
    at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
    ... 40 more

in the meantime psaux brings 2 postgres-processes: idle in transaction and ALTER TABLE waiting

i already tried a fresh installation via gui-installer on a new box and restored the database from a backup. same bahavior here. ps aux | grep postgres brings 

postgres 11555  0.0  0.2  47964  4132 ?        Ss   02:32   0:00 postgres: username teamwork 127.0.0.1(60374) idle in transaction                                                                
postgres 11556  4.6  0.3  49348  8076 ?        Ss   02:32   0:10 postgres: username teamwork 127.0.0.1(58161) ALTER TABLE waiting

what now?

asked Feb 15 '11 at 13:40

Bernhard%20M%C3%A4ser's gravatar image

Bernhard Mäser
81●4

edited Feb 15 '11 at 20:38

One Answer:
oldestnewestmost voted
0

In the fresh installation that you have done (that points to your database) go in the Teamwork installation folder and rename the file called admin.rename with admin.jsp , (TEAMWORK_ROOT/webapps/ROOT/commons/administration) then call this page from your browser, the link should be something like this

http://[your teamwork address]/commons/administration/admin.jsp

insert in the password field "domagic" and click on "show available releases" in the box on the right you should see the list of releases click to force the "4.5.0" (if you are currently on the 4.4. release) then click on "show available releases" again and on "4.5.17900" try to access your Teamwork, if the error persist post here a significant part of the platform.log file (TEAMWORK_ROOT/webapps/ROOT/WEB-INF/log).

I've also uploaded for you the installer of Teamwork 4.4.1600 on our server so that you can restore your previous version (In case you don't have a backup of your installation folder). you can download them here:

http://dl.open-lab.com/Teamwork_441600_unix.sh.bin

http://dl.open-lab.com/Teamwork_441600_unix.tar.gz

answered Feb 17 '11 at 03:26

Silvia%20Chelazzi's gravatar image

Silvia Chelazzi ♦♦
4085●1●9

edited Feb 17 '11 at 03:26

perfect silvia, that worked 100% for me! thankful greatings from vienna/austria!

(Feb 22 '11 at 21:31) Bernhard Mäser
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×22
×6
×5
×4
×2

Asked: Feb 15 '11 at 13:40

Seen: 342 times

Last updated: Feb 22 '11 at 21:31

Related questions

Upgrade teamwork 4.4 by hand.

Teamwork 4.7 patch release 4.7.25011 / postgres-hibernate bug

Precompile issue when deploying 4.5 to Glassfish 2.1

Update teamwork (Use postgres database) version of 4.4.16000 to 4.7.25010

I try to install upgrade

FAQ: Teamwork and PostgreSql

Teamwork stopped working after upgrade from 4.4 to 4.5

update check does not work properly

Plugin not work

4.6 install

| Teamwork faq | about | contact us | Teamwork blog | Teamwork documentation | feedback always welcome