Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Weird logs in the tracefile

 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi folks.
I've got logs in the tracefile (WAS 4.03/AIX) I didn't see before. I have no idea where it comes from..
Have you ever seen something like that :
(The websphere security is on)
[8/15/02 13:49:19:526 EDT] 2135ccb5 CoordinatorIm I WTRN0066W: Transaction com.ibm.ejs.jts.jts.CoordinatorImpl@1943751868#tid=20993 has timed out after 600 seconds.
AND
[8/14/02 18:36:39:387 EDT] 2cd4de25 SystemOut U 95> [2002-08-14 18:36:39.386], [ServerID: 1917109904], [VaultImpl.init_security_context]:
[8/14/02 18:36:39:387 EDT] 2cd4de25 SystemOut U JSAS0070E: Unable to complete secure association at the client. Retry the client program after a few minutes wait. If the problem still persists, contact support for assistance.

The message is logged on each second (sometime less)!!
 
Devan Lipsey
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are also running on AIX & 4.03 and get the same messages. We are going to look further into it next week and I'll post a reply if we figure it out.
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just for info.
I have open a PMR at IBM Tech Support.
So I'll let you know if they find some clues.
Just a question Devan. Do you have a efix installed over your 4.03.?
We have PQ62684
 
kettle
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It could be a IBM bug as we were getting security context error in 3.5.3.
Also make sure you are not loosing connection to source of security authentication like edirectory or active directory.
 
Devan Lipsey
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bill,
We do have e-fixes applied over 4.03. They are:
PQ59543, PQ60281 and PQ62684
I hope this helps...
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And do you still have the log problem mentioned above ??
As far are we are concerned, it sounds like it's an applicative problem....I mean a bug in our code.... More research needed...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic