Sadly, webMethods has a fundamentally flawed scheduler, the primary flaw being that it hangs. You will find other problems, like the fact the scheduled jobs share a single session (a potential disaster when dealing with database connections). We’ve had to write silly scheduled jobs which write to a file, then have some external Unix process watch for that file so we can detect scheduler hangs. These hangs can bring your server to its knees, since the various webMethods housekeeping services (i.e. session expiration) use the scheduler.
I rather dismayed to hear you report the problem still exists in 6.0. However, given my experiences with Developer 6, in which many things that once worked are now broken, I’m not suprised.
#Flow-and-Java-services#webMethods#Integration-Server-and-ESB