1. in the stack trace, the source line from where the exception is thrown out (at SrvrConnect.cpp:7805) is not relevant to current source code, the code in there do not include any signal handler code corresponding to the stack trace.
2. the exception is from JVM (JVM signal handler), mxosrvr do not call any java code directly.
3. the query is a very regular "select count(*)". mxosrvr should not trigger such kind of JVM exception directly.
4. can't reproduce in workstation.
mark as invalid for now, if it is still reproducible in cluster with latest build, pls reopen it with more information.
here is some analysis.
1. in the stack trace, the source line from where the exception is thrown out (at SrvrConnect. cpp:7805) is not relevant to current source code, the code in there do not include any signal handler code corresponding to the stack trace.
2. the exception is from JVM (JVM signal handler), mxosrvr do not call any java code directly.
3. the query is a very regular "select count(*)". mxosrvr should not trigger such kind of JVM exception directly.
4. can't reproduce in workstation.
mark as invalid for now, if it is still reproducible in cluster with latest build, pls reopen it with more information.