In our case, roughly like 10-15MB file (which probably translates to 20-30MB actual encoded data),
when put to database from a client using SQL INSERT, will cause Gateway to reboot.
system.db.startTransaction()'s timeout is set to 10006010 and no more causes the following:
INFO | jvm 26 | 2011/12/28 10:45:11 | WARN [TxTimoutDaemon ] [10:45:11,824]: Transaction "c18595b2-69c1-4916-9aa9-0238c4813902" being closed due to inactivity timeout. Make sure you close your
But this one persists:
ERROR | wrapper | 2011/12/28 10:46:58 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2011/12/28 10:46:59 | JVM did not exit on request, terminated STATUS | wrapper | 2011/12/28 10:47:05 | Launching a JVM... INFO | jvm 27 | 2011/12/28 10:47:09 | WrapperManager: Initializing... INFO | jvm 27 | 2011/12/28 10:47:16 | 28.12.2011 10:47:16 org.apache.catalina.startup.Embedded start INFO | jvm 27 | 2011/12/28 10:47:16 | INFO: Starting tomcat server
I’ve tried setting both of these in the “ignition.conf” file:
# default is 10 wrapper.cpu.timeout=40 # default is 30 wrapper.ping.timeout=120
The client will eventually fail with message: “Read timed out”.
It seems like the file gets to the gateway ok, but the gateway keeps quiet too long
when running the INSERT into the database, which triggers the restart.
Obvious workaround is to split the file internally, so that the SQL INSERTs will never
get too big and split/join the parts client-side to make a whole file.
Anyway, I’d like to hear your position on this.