I get this when I stop the traveler service but leave http running. In this case it's nothing to worry about (but I'm not sure what your situation is). The jvm runs as a sub-component of the http task. So when http is up and traveler is down, the jvm is still churning away trying to interact with the traveler task. This message is just the jvm stating the obvious; i.e. that the traveler task is down.

Nevermind the log error... Can you descirbe the problem first? What do you mean "Traveler doesn't work anymore"? Is the traveler task running or not?

Hi, 

It simply means that the Traveler has hung. Most of the times, it enters into a state where it cannot accept anymore requests as the system is already taking its time to process existing ones. You would have to open a PMR with IBM Traveler Support to have assistance with the overall sizing details of the system or you could refer to this link and make sure you are meeting all capacity requirements:

http://www-01.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/capacityplanning.dita?lang=en