Welcome Guest ( Log In | Register )


 
Reply to this topicNew Topic
Integrator V2.1.1 error (log id logger_157_0000000006203364 is inactive, discarding further logging)
eGroups Migratio...
post Dec 23 2008, 08:13 AM
Post #1


Community Admin
Group Icon

Group: Administrators
Posts: 100,048
Joined: 19-December 08
Member No.: 258


Hi All,

Does anyone know what the following warning in the TraceViewer means and how it's caused, but more important how to solve?

Logger entry with log id logger_157_0000000006203364 is inactive, discarding further logging

Thanks in advance,
Rgds,
Wim
Go to the top of the page
 
+Quote Post
eGroups Migratio...
post Dec 23 2008, 08:14 AM
Post #2


Community Admin
Group Icon

Group: Administrators
Posts: 100,048
Joined: 19-December 08
Member No.: 258


QUOTE (eGroups Migration @ Dec 23 2008, 09:13 AM) *
Hi All,

Does anyone know what the following warning in the TraceViewer means and how it's caused, but more important how to solve?

Logger entry with log id logger_157_0000000006203364 is inactive, discarding further logging

Thanks in advance,
Rgds,
Wim


Probably means that XIB has given up waiting for an acknowledgement of some sort for a sent message.

Go to the message log and do search / lookup. enter the logger id below (removing any spaces at the end) and you will see the message this refers to.

regards

Zac
Go to the top of the page
 
+Quote Post
eGroups Migratio...
post Dec 23 2008, 08:14 AM
Post #3


Community Admin
Group Icon

Group: Administrators
Posts: 100,048
Joined: 19-December 08
Member No.: 258


QUOTE (eGroups Migration @ Dec 23 2008, 09:14 AM) *
Probably means that XIB has given up waiting for an acknowledgement of some sort for a sent message.

Go to the message log and do search / lookup. enter the logger id below (removing any spaces at the end) and you will see the message this refers to.

regards

Zac


The warning was caused by some XIB component trying to create a new Message Log entry based on the logger id logger_157_0000000006203364. This failed because the logger id was inactive. You need to activate this logger id using the statement MBC_HIERCHMSGENV.ActivateLoggerEntry, do your processing and customised logging, and then de-activate the logger id by using the statement MBC_HIERCHMSGENV.InactivateLoggerEntry.

Michael
Go to the top of the page
 
+Quote Post

Reply to this topicNew Topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Skin designed by IPB Forum Skins