I’ll be happy to discuss it.
I’m not an expert, but from my past experience, I think that for security reasons network people try to keep separately (as network) the webserver and the back office data (e.g. DB Server).
The webServer will have static IP/domain name and will be installed in a separate and very protected network, what they call DMZ, where firewalls will control HTTP/FTP/etc connection to and from Internet. I don’t know exactly how a DMZ is configured, but some how you will get also more protection to inside calls (that is versus/from back office systems).
The most of mine precedent installations of wM used to have IS inside local LAN, together with back-office, using proxy/NAT to access Internet.
In this case, however, IS is exposing several DSP pages as UserInterface, so for the network people is acting as a web server, so they decided to setup IS inside DMZ. It seams that is affecting DB connections especially through sequelink drivers (of any versions).
Oracle jdbc thin driver instead is acting a little bit better: while still having exceptions sometimes, it seams that connection pools using this driver will somehow open a new connection allowing IS to continue the work. Sequelink/DataDirect versions, once the connections are broken, failed to manage the situation and implied IS functionality becomes unavailable until IS completely restart…
I was wondering if there is a way to get control, programmatically, over the way wM manages the connection pool, so that I could intercept this exceptions and decide to clean the connection from the pool creating a new one instead! In your opinion, it’s this possible?
Please fill free to consider all my previous suppositions wrong, as there may be a way to correct/better configure the network and have everything working just fine!