×
Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…
OLTP sessions are active more than many hours
- malai
-
Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 508
- Thank you received: 11
2 years 3 months ago #23834
by malai
OLTP sessions are active more than many hours was created by malai
Hi,
My understanding is that whenever T24.INITIALISE is getting involved there will an OLTP session created and it will be destroyed as soon the session terminated. In out environment we are seeing sessions that are pretty old by still looks active.
Current time is 9AM but the below T24 session record still exits in T24.SESSION table even though this was created around 5AM
Below is TSA.SERVICE for the same session
Like this there are around 40k records looks like they are running but the LAST.CONTACT time is pretty old.
What could be the reason behind. Please do support with your views and suggestions. Thanks.
My understanding is that whenever T24.INITIALISE is getting involved there will an OLTP session created and it will be destroyed as soon the session terminated. In out environment we are seeing sessions that are pretty old by still looks active.
Current time is 9AM but the below T24 session record still exits in T24.SESSION table even though this was created around 5AM
T24.SESSION.NO.... 1013
------------------------------------------------------------------------------
1 AGENT.NUMBER...... OLTP1013 xxxxxxxx
2 DATE.............. 20 SEP 2022
3 TIME.............. 05:06:27Below is TSA.SERVICE for the same session
AGENT............. OLTP1013
------------------------------------------------------------------------------
1 SERVER............ xxxxxxxxxxxxxxxx
2 AGENT.STATUS...... RUNNING
3 LAST.CONTACT...... 05:06:27
4 PROCESS.ID........ 1805784291
5 CURRENT.SERVICE... OLTP
10 PORT.ID........... 5347
19 T24.SESSION.NO.... 1013Like this there are around 40k records looks like they are running but the LAST.CONTACT time is pretty old.
What could be the reason behind. Please do support with your views and suggestions. Thanks.
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
Less
More
- Posts: 1183
- Thank you received: 157
2 years 2 months ago #23836
by VK
Cheers
VK
Replied by VK on topic OLTP sessions are active more than many hours
Hi
TSA.STATUS (your record is from there not from TSA.SERVICE) was never correctly updated. You can use F.OS.TOKEN to see who's active (of course it might contain obsolete records caused by crashes so check TIME.1 and TIME.2 for time/date of its creation respectively).
TSA.STATUS (your record is from there not from TSA.SERVICE) was never correctly updated. You can use F.OS.TOKEN to see who's active (of course it might contain obsolete records caused by crashes so check TIME.1 and TIME.2 for time/date of its creation respectively).
Cheers
VK
Please Log in or Create an account to join the conversation.
- malai
-
Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 508
- Thank you received: 11
2 years 2 months ago #23838
by malai
Replied by malai on topic OLTP sessions are active more than many hours
HI VK, thanks for your reply. The table F.OS.TOKEN and F.OS.TOKEN.USE is not having that many 40k records. They look normal only. On further investigation we found all those type of sessions are coming via EJB which is used by OSB integration service bus to post transactions to T24. But still wondering why those sessions are hanging around.
On a side note what is the usage of TIME.1 and TIME.2 fields in F.OS.TOKEN?
On a side note what is the usage of TIME.1 and TIME.2 fields in F.OS.TOKEN?
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
Less
More
- Posts: 1183
- Thank you received: 157
2 years 2 months ago #23839
by VK
Cheers
VK
Replied by VK on topic OLTP sessions are active more than many hours
Hi
TIME.1 and TIME.2 hold respectively time and date when the record has been created (in internal format so you shall use OCONV() to get it in human-readable format). Assuming timeout for your users you can see which session is still active.
"coming via EJB which is used by OSB integration service bus" - I think you need to report this to Temenos since it looks like an error to me.
TIME.1 and TIME.2 hold respectively time and date when the record has been created (in internal format so you shall use OCONV() to get it in human-readable format). Assuming timeout for your users you can see which session is still active.
"coming via EJB which is used by OSB integration service bus" - I think you need to report this to Temenos since it looks like an error to me.
Cheers
VK
Please Log in or Create an account to join the conversation.
Time to create page: 0.074 seconds