Skip navigation
4827 Views 8 Replies Latest reply: Oct 23, 2007 7:13 PM by Stefan Reuter RSS
sixthring KeyContributor 3,797 posts since
Apr 2, 2007
Currently Being Moderated

Sep 12, 2007 11:06 AM

Open Archive Issue

 

When reading the logs the conversations are not always threaded.  Is there a reason for this behavior?  See samples below.

 

 

 

 

 

Threaded:

 

 

 

 

 

 

 

Un-threaded:

 

 

 

 

  • Stefan Reuter KeyContributor 330 posts since
    Aug 3, 2005
    Currently Being Moderated
    Sep 15, 2007 7:04 AM (in response to sixthring)
    Re: Open Archive Issue

    The reason for this is a bug in Open Archive but though I also see this behavior for a few of my own conversations I have not yet been able to reproduce it.

    Did you observe anything that could help me reproduce this? any "special" circumstances in which this happens?

  • Bronze 9 posts since
    Jan 23, 2007
    Currently Being Moderated
    Sep 21, 2007 8:16 PM (in response to sixthring)
    Re: Open Archive Issue

    Hi Guys...

     

    in my case i'm getting two issues types. One of then is the same reported by "mtstravel". The another one happens when i choose one of the registers at the list. Always one of this two issues happen when i choose one of the registers at the list.

     

    I'm using Openfire 3.3.2 and the version 1.0.3 of the OpenArchive plugin.

     

     

    Thanks.

     

    Kleber.

    Attachments:
  • Bronze 9 posts since
    Jan 23, 2007
    Currently Being Moderated
    Sep 24, 2007 4:24 AM (in response to sixthring)
    Re: Open Archive Issue

     

    Ooppss... i forgot to say one important thing: i'm using PostGreSQL 8.1.9-1. The DataBase schema used is based on the attached script. I think that the script is ok, but could be something with PostGreSQL (particularly with the second issue -- error message)??

     

     

    Thanks again...

     

     

    Kleber.

     

     

    Attachments:
    • cstux KeyContributor 185 posts since
      Jul 27, 2006
      Currently Being Moderated
      Re: Open Archive Issue

      There is a simple patch for this Problem.

       

       

       

          • ./archive/com/reucon/openfire/plugin/archive/impl/JdbcPersistenceManager.java        2007-06-28 19:17:10.000000000 +0200

      +++ ./archive_new/src/main/java/com/reucon/openfire/plugin/archive/impl/JdbcPersist enceManager.java       2007-09-24 16:31:59.000000000 +0200

      @@ -791,7 +791,8 @@

      final long id;

       

      id = rs.getLong(1);

      • message = new ArchivedMessage(millisToDate(rs.getLong(2)), ArchivedMessage.Direction.valueOf(rs.getString(3)),

      +        //Log.error("--" + rs.getLong(2) + "-" + rs.getString(3) + "-" + rs.getString(4));

      +        message = new ArchivedMessage(millisToDate(rs.getLong(2)), ArchivedMessage.Direction.valueOf(rs.getString(3).trim()),

      rs.getString(4));

      message.setId(id);

      message.setSubject(rs.getString(5));

      Attachments:
        • cstux KeyContributor 185 posts since
          Jul 27, 2006
          Currently Being Moderated
          Sep 24, 2007 7:43 AM (in response to sixthring)
          Re: Open Archive Issue

           

          Hello,

           

           

          the insert with the enum is the problem with the Postgresql.

           

           

          The enum contains whitespaces at the end of the sql statement.

           

           

          The patch didn't solve this problem, because it removes the whitespaces only at the query and not at the insert.

           

          I think the problem is the prepareStatement function.

      • Stefan Reuter KeyContributor 330 posts since
        Aug 3, 2005
        Currently Being Moderated
        Oct 23, 2007 7:13 PM (in response to cstux)
        Re: Open Archive Issue

        Hm and where does that space come from on PostgreSQL? This looks like a bug in the JDBC driver...

        pstmt.setString(3, message.getDirection().toString());
        

        Thats the part of the insert. toString() evaluates to either "to" or "from" without any whitespace.

More Like This

  • Retrieving data ...

Bookmarked By (0)