I want to call a tuxedo service with the module php_tuxedo.
The service TUXEDO is called correctly (the return values in output buffer are OK).
But the Tuxedo session is never close and so, the application is "in wait" .
I used tux_tpclose() and tux_tpterm() : it's the same.
I used : php 4.1.1, apache 1.3.24, mod_php_tuxedo_0.4.1, tuxedo 6.5, server Linux
Thanks for your help.
(Sorry for my bad english)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A couple clarifications please...
When you say the "session", do you mean on the client (web)
side, or on the server side?
At first glance, this sounds like the server side is not closing
correctly.
Your call to tux_tpterm should be the correct call, and in
fact at the end of the php web hit, its called automatically for
you.
The only other possibility is you are meaning the web session
itself never closes or hangs on tpterm. Again, are you
sure there isn't a bug on the Tuxedo Server side?
Please let me know and I'll try and help more.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-07-12
More precisions:
When I say session, I mean session on server side.
I ve this problem when Client Tuxedo 7.1 called service on Server Tuxedo 6.5.
I' ve tried with client tuxedo 7.1 called service on Server Tuxedo 7.1 and that it's OK.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So it sounds like php-tuxedo on 6.5 is just duplicating a
problem you have already seen with a normal Tuxedo 6.5
client (non-php).
PHP-Tuxedo, does nothing special, it really does turn
your apache web server into a Tuxedo client, so if a problem
exists in a normal C client, it will probably exist in PHP.
You claim the problem is fixed if both client and server are
running 7.1... Then I would suggest upgrading php-tuxedo
to use 7.1. While its not the easiest to support, it can be
done safely. It will involve changing the linking, and we also
found a small code bug that I will have to forward to you later
this weekend involving multi-threaded clients (which 7.1 is).
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"To join an application, a multithreaded Workstation client must always call
tpinit(3c) with the TPMULTICONTEXTS flag set, even if the client is running
in single-context mode."
This looks like a new flag that I don't have a predefined
value for, so add something like this to php_tuxedo.c and
then use it in the flags of tux_tpinit:
I want to call a tuxedo service with the module php_tuxedo.
The service TUXEDO is called correctly (the return values in output buffer are OK).
But the Tuxedo session is never close and so, the application is "in wait" .
I used tux_tpclose() and tux_tpterm() : it's the same.
I used : php 4.1.1, apache 1.3.24, mod_php_tuxedo_0.4.1, tuxedo 6.5, server Linux
Thanks for your help.
(Sorry for my bad english)
A couple clarifications please...
When you say the "session", do you mean on the client (web)
side, or on the server side?
At first glance, this sounds like the server side is not closing
correctly.
Your call to tux_tpterm should be the correct call, and in
fact at the end of the php web hit, its called automatically for
you.
The only other possibility is you are meaning the web session
itself never closes or hangs on tpterm. Again, are you
sure there isn't a bug on the Tuxedo Server side?
Please let me know and I'll try and help more.
Brian
More precisions:
When I say session, I mean session on server side.
I ve this problem when Client Tuxedo 7.1 called service on Server Tuxedo 6.5.
I' ve tried with client tuxedo 7.1 called service on Server Tuxedo 7.1 and that it's OK.
Thanks
So it sounds like php-tuxedo on 6.5 is just duplicating a
problem you have already seen with a normal Tuxedo 6.5
client (non-php).
PHP-Tuxedo, does nothing special, it really does turn
your apache web server into a Tuxedo client, so if a problem
exists in a normal C client, it will probably exist in PHP.
You claim the problem is fixed if both client and server are
running 7.1... Then I would suggest upgrading php-tuxedo
to use 7.1. While its not the easiest to support, it can be
done safely. It will involve changing the linking, and we also
found a small code bug that I will have to forward to you later
this weekend involving multi-threaded clients (which 7.1 is).
Brian
We discovered a bug in that involves multi-threaded clients
of Tuxedo. 7.1 and 8.0 build a multi-threaded client.
http://edocs.beasys.com/tuxedo/tux80/atmi/pbthr13.htm
"To join an application, a multithreaded Workstation client must always call
tpinit(3c) with the TPMULTICONTEXTS flag set, even if the client is running
in single-context mode."
This looks like a new flag that I don't have a predefined
value for, so add something like this to php_tuxedo.c and
then use it in the flags of tux_tpinit:
REGISTER_LONG_CONSTANT("TUX_TPMULTICONTEXTS", TPMULTICONTEXTS, CONSTANT_FLAG);
I hope to get a final fix for this and other related issues,
but for now this patch will have to do.
Brian