Have you tried running the adapter in debug mode while it is processing the events? You may see an error that is occurring that is not being reported back to the broker via Adapter::errorNotify causing the adapter to stop responding. Also, check the system logs to see if there is something being logged by the adapter process. Depending on where your adapter is running (x86 or Unix) will determine where your logging is going. Try those things and if you still have problems, then you will have to give more detailed info on what your event lifecycle looks like for this adapter and its component.
Steve
#Adapters-and-E-Standards#webMethods#Integration-Server-and-ESB