On attempting a publish, the RH server is not contactable.
The Web ADmin has reported this message:
"java.sql.SQLException: Maximum possible connections are open and all the connections are busy. Kindly review the "maxload" in the server.properties file and adjust it according to the expected load."
In your server.properties file there is a setting that controls the maximum number of connections that are allowed. It sounds like this number has been exceeded. Now I am not a server or database wizard so I have no idea why this is so. I've certainly not come across this scenario. Could it be that the connections are not being released when they are finished with? You'd probably need to speak to your IT or Server peeps to check this out. If all else fails the vale of your connections limit could be increased, but I don't know what implications this could have.
|The RoboColum(n)||@robocolumn||Colum McAndrew|
Adding to Colum's good suggstions. I thought I'd point out that the error message thrown "server.properties" is actually robohelp_server.properties. Your server admin can find it along this path on the server machine.
C:\Program Files (x86)\Adobe\Adobe RoboHelp Server 9\WEB-INF\robohelp_server.properties
Here is the default way the attributes are installed:
ProjectsDirBase=c:\\program files (x86)\\adobe\\adobe robohelp server 9\\robo
So it would seem that you might experiment with increasing the maxload as shown.
Also, I'm not sure it's relevant here, but you might also check the Tomcat Administration app and its "Java Tab" properties and assure that
the admin specifies 256 as the value for both the Initial Memory Pool and Maximum Memory Pool boxes.
Adobe Certified RoboHelp and Captivate Instructor