Problem sharing session between RT and custom code

RT Users
1

I have written an application that runs alongside an RT4 instance, and
makes use of RT’s Logger, db handle and session.

In moving from mysql to Oracle, I’ve run into a problem that after lodign a
page from my app, the next request, whether to my app, or RT, hangs
trying to get an exclusive lock on the session lock file that it had used
without a problem on the previous request (and requests, if I start out
clicking around in RT).

I’ve determined that it is exclusive lock call by using strace. I’ve also
learned that while clicking through RT, and the first click into my app,
the session lock file is file descriptor 11, but the request after hitting
my app uses 13, but doesn’t close 11, so it looks like my app is not
untie-the session, but I’m relying on RT to tie/until the session - or so I
think.

I’m sure that there’s something that I’ve missed. Something that RT does
that I’ve orverlooked, or some assumption I’ve made that is invalid.

Can anybody tell me (why my autohandler might be causing RT to use a
different fd despite using the same session id, and why it might not be
correctly relinquishing the lock or the tied hash? Or nudge me in the
right direction?

Thanks,
Len.

lenjaffe@jaffesystems.com 614-404-4214 @lenjaffe
Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
www.lenjaffe.com http://www.theycomewithcheese.com
Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
Calendars: Perlish and otherwise.

2

Hi,

I think the only way somebody would help you is if you put up minimal
application code that replicates your problem. You have too many pieces.On Thu, Aug 22, 2013 at 1:50 AM, Len Jaffe lenjaffe@jaffesystems.comwrote:

I have written an application that runs alongside an RT4 instance, and
makes use of RT’s Logger, db handle and session.

In moving from mysql to Oracle, I’ve run into a problem that after lodign
a page from my app, the next request, whether to my app, or RT, hangs
trying to get an exclusive lock on the session lock file that it had used
without a problem on the previous request (and requests, if I start out
clicking around in RT).

I’ve determined that it is exclusive lock call by using strace. I’ve also
learned that while clicking through RT, and the first click into my app,
the session lock file is file descriptor 11, but the request after hitting
my app uses 13, but doesn’t close 11, so it looks like my app is not
untie-the session, but I’m relying on RT to tie/until the session - or so I
think.

I’m sure that there’s something that I’ve missed. Something that RT does
that I’ve orverlooked, or some assumption I’ve made that is invalid.

Can anybody tell me (why my autohandler might be causing RT to use a
different fd despite using the same session id, and why it might not be
correctly relinquishing the lock or the tied hash? Or nudge me in the
right direction?

Thanks,
Len.

–
lenjaffe@jaffesystems.com 614-404-4214 @lenjaffe
Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
www.lenjaffe.com http://www.theycomewithcheese.com
Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
Calendars: Perlish and otherwise.

Best regards, Ruslan.