Robert Kanter created OOZIE-1312:
------------------------------------
Summary: thrift exceptions when running tests
Key: OOZIE-1312
URL: https://issues.apache.org/jira/browse/OOZIE-1312
Project: Oozie
Issue Type: Bug
Components: tests
Affects Versions: trunk
Reporter: Robert Kanter
I've been sometimes seeing exceptions from thrift when running different unit
tests. It's typically just a short stack trace from an exception, but
sometimes there's also some other messages about {{ASSERTION FAILED}} in some c
files.
They get printed out to the console, not the log files. They do not cause the
test to fail.
Here's an example of one of the exception:
{code}
110920 [pool-20-thread-1] ERROR org.apache.thrift.server.TThreadPoolServer -
Error occurred during processing of message.
java.lang.NullPointerException
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:34)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at
org.apache.hadoop.hive.metastore.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:48)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:176)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
*** java.lang.instrument ASSERTION FAILED ***: "error == JVMTI_ERROR_NONE" at
../../../src/share/instrument/Reentrancy.c line: 80
*** java.lang.instrument ASSERTION FAILED ***: "test == expected" at
../../../src/share/instrument/Reentrancy.c line: 81
*** java.lang.instrument ASSERTION FAILED ***: "error == JVMTI_ERROR_NONE" at
../../../src/share/instrument/Reentrancy.c line: 80
*** java.lang.instrument ASSERTION FAILED ***: "test == expected" at
../../../src/share/instrument/Reentrancy.c line: 81
*** java.lang.instrument ASSERTION FAILED ***: "error == JVMTI_ERROR_NONE" at
../../../src/share/instrument/Reentrancy.c line: 139
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
