IS Server logs

[Thahir.K.K]

Hi

I have connected two IS servers thru a broker in 6.01 setup. My server logs from both the machines get filled up with this message constantly every five seconds

Error getting broker log length: The client is no longer valid because it has been destroyed by the Broker.

I had disconnected all the clients, restarted the broker many times, at times the message stays away for say half hour after a broker restart, but that even only on one server, not a specific server it could be any of the two.

Every thing is working alright altho I have this message. I had tried with log level 5 and 4, the code before the message contained a "E" (like "xxxE") in it, so I guess it is an error and would log it with any log levels

Any help is highly appreciated

[dgreen]

Hi, Thahir.

I got kind of lost by the end of your message so forgive me if I am off-base on this one...

What tools are you running when this error occurs? Is it possible that the error is not related to either IS instance or the Broker, but instead a loose Document Tracker or something?

Use the Manager to find the broker's connected clients. You may find some hanger-ons that you didn't expect.

Let us know what you find.

[Thahir.K.K]

Hi Dan

I am not running any tools other than developer. Well let me be more specific. This is a development environment, so we run both IS from our laptop with server log redirected to console. End of the day the IS is shutdown. but the broker is running on the unix box uninterrupted. I am only connected thru developer to IS servers and thru administrator to the broker(but connection to the boker even thru administrator is very minimal) only the integration servers are connected to the broker. This is not exactly an EAI scenario rather a B2B scenario, so no adapters other than JDBC is used. Only IS is publishing and subscribing. document tracker is not used since everything seems working perfect. But just after the IS server boots up in the morning(we closed it in the evening...right) we get the message "Error getting broker log length....".

I tried removing all the clients, restarting the broker etc but to no use.

Guess I explained it in a clearer way

Thahir

[claire]

Hi,

did you already find a solution, I'm having the same problem....

thanks, Claire

[Thahir.K.K]

I had found the solution later, it was an RTFM. http://www.wmusers.com/wmusers/clipart/happy.gif

I am sorry I did not update the forum for any wandering soles

The read me file of WmLogUtil says

" webMethods Broker allows for one connection to the Broker Log
Queue at a time. For this reason, you must configure a single
Logging Utility for each Broker. Refer to the Logging Utility
documentation for instructions on how to configure the Logging
Utility and the Broker connection. "

So basically it means that if you had enabled broker logging on both the servers you would get this error "Error getting broker log length".

I guess it helps

[raghu80]

Please check the following link on advantage

http://advantage.webmethods.com/cgi-bin/advantage/main.jsp?w=0&targChanId=-536880653&faqId=1610687795

[ramesh_kuruba]

We are having the problem in the non-clustered environment. Do any one has the idea why this is being caused.

Error getting broker log length: The client is no longer valid because it has been destroyed by the Broker.

[cjcable]

Have you configured more than one logging utility?

There are a few entries on the Advantage site. Below is one of webMethods responses. Basically they contribute it to a server resource issue. If the connection to the broker doesn't get a response back in time, it will log this error.

http://advantage.webmethods.com/cgi-bin/advantage/main.jsp?w=0&targChanId=knowledgebase&oid=1611541821

[shiva_insolexen]

Go to the homepage of the logging utility package(http://hostname:5555/WmLogUtil/) and stopped the logging utility and the issue is resolved.

Thanks,
Shiva Juluru