D
dbeavon
Guest
Since we migrated to PASOE from classic appserver we had to exchange the "clientconnect" (symbiont) JMS connections for "brokerconnect" connections that go thru a central java process. This "brokerconnect" adapter is a centralized point of failure. All agent processes and sessions are relying on the "brokerconnect" adapter process when they are exchanging messages with a remote JMS resource. Since it is a critical component of a PASOE server, is there any HealthScanner mechanism available to monitor this "brokerconnect" adapter? An unhealthy adapter can cause problems that quickly extend to PASOE as well. Ideally there would be some healthscanner mechanism that would effectively call "adaptman -query" and look for servers that were unresponsive and then cycle them or else cycle the entire adapter process. Better yet, Progress should consider bringing back "clientconnect" for independent and reliable JMS interactions with remote JMS resources. Any tips would be appreciated. I suppose it may be possible for us to implement our own healthscanner that parses the output from "adaptman -query". But it seems that other customers would benefit if it was built into the OE product itself.
Continue reading...
Continue reading...