Executor Service with Blocking Queue
Producer

protected BlockingQueue queue = null;


Why not apply generics? BlockingQueue&lt;Integer&gt; avoids awkard casting later on.

Why is this protected? Fields are typically private, and there doesn't seem any motivation in your example to widen visibility on the field itself

} catch (InterruptedException e) {
    e.printStackTrace();
}


This is not the proper way to handle an InterruptedException. The ExecutorService uses interruption for forced shutdown (shutDownNow()), but since you eat the interruption the ExecutorService will not be responsive to forced shotdown. In general you would always propagate interruption to the caller.

Consumer

Actually the remarks for Producer go for Consumer as well.

but also

while (ExecutorTest.isRunning) {


Alternatively you could simply use interruption to stop the task : while (!Thread.currentThread().isInterrupted()).
But what's worse is that isRunning is actually a field on ExecutorTest, This means Consumer class depends on ExecutorTest class for its proper working.

ExecutorTest

ExecutorService executorService = Executors.newFixedThreadPool(4);

executorService.execute(consumer);
executorService.execute(consumer);
executorService.execute(consumer);
executorService.execute(consumer);


Perhaps a small for loop, and make the literal 4 variable or a constant.

// wait for the threads to finish
while (isRunning) {
};


This is unnecessary, you already do executorService.awaitTermination(10, TimeUnit.SECONDS);
A busy wait like this is also a poorer way to await some other thread, as you are wasting CPU cycles.