[rt-users] [rt-announce] Development Snapshot 3.0.2++

[Dirk Pape]

Hello Jesse,

the problem reappeared now, where we became productive with rt-3.0.3pre4. 
My threading patch is not active here but Autoreplies are.

It is now quite often, that the Subject, if it is displayed in the 
MessageStanza (from the Head attribute of the datbase) is garbled (Umlauts 
wrong) an sometimes cut off.
if it is displayed in the title (from the Subject attribute in the 
database), is correctly written with Umlauts.

Could it be right what someone wrote that RT is not thread-safe?

Dirk.

--Am Dienstag, 10. Juni 2003 10:02 Uhr +0200 schrieb Dirk Pape 
<pape-rt at inf.fu-berlin.de>:

> I have to apologize. I cannot reproduce the described problem, if I
> remove one patch I have done, which enables RT to write almost correct
> threading headers into notification mails. I did not try to remove this
> patch before testing, because I did not see how it can be related to the
> problem. And for now after looking several hours into the code and
> testing it, I *still cannot see it*.
>
> I tracked my (header encoding) problem down to the following situation:
>
> 1. Have my threading patch installed (I attached a light version, which
> consists of only one file to be put in lib/RT/Action).
>
> 2. Send several emails with German Umlauts in subject and body to a
> queue, *which has an Autoreply set up*.
>
> 3. refresh the Ticket Listing of the Queue in the web while Tickets
> arrives
>
> 4. After some (5-10) Tickets arrived try the Ticket Display of the
> Tickets. The Subject header shown in the Ticket-Message-Display (not the
> Subject shown in other fields) of some Tickets (it is fuzzy!) is mangled
> and so is the Head-Field of those tickets in the mysql-database.
>
> 5. This then seems to be a "global apache switch" which can toggle after
> some other messages arrive but will definitely be set to normal behaviour
> if apache is restarted.
>
> So I have a workaround now but I would greatly appreciate, if someone
> takes a look into my code, which is fairly short and the problem is
> within 3 lines of code:
>
> It happens, when I leave the patch installed and comment out all calls of
> "$self->SetHeader" in my SetReferences subroutine, I cannot reproduce the
> problem any more.
>
> But why???? SetHeader is called multiple time everywhere in SendEmail.pm.