public class InboundMessageLossTestCase extends AbstractJmsReliabilityTestCase
AbstractJmsFunctionalTestCase.AbstractScenario, AbstractJmsFunctionalTestCase.NonTransactedScenario, AbstractJmsFunctionalTestCase.Scenario, AbstractJmsFunctionalTestCase.ScenarioCommit, AbstractJmsFunctionalTestCase.ScenarioNotReceive, AbstractJmsFunctionalTestCase.ScenarioReceive, AbstractJmsFunctionalTestCase.ScenarioRollback
Modifier and Type | Field and Description |
---|---|
protected int |
latchTimeout |
protected Latch |
messageRedelivered |
acknowledgeMode, connection, consumer, deliveryMode, session
BROADCAST_TOPIC_ENDPOINT_KEY, DEFAULT_INPUT_MESSAGE, DEFAULT_OUTPUT_MESSAGE, INBOUND_ENDPOINT_KEY, jmsConfig, log, MIDDLE_ENDPOINT_KEY, MIDDLE2_ENDPOINT_KEY, MIDDLE3_ENDPOINT_KEY, OUTBOUND_ENDPOINT_KEY, purgeQueuesOnPreSetUp, purgeQueuesOnTearDown, scenarioCommit, scenarioNotReceive, scenarioNoTx, scenarioReceive, scenarioRollback
callbackCalled, CLASSNAME_ANNOTATIONS_CONFIG_BUILDER, IGNORED_DOT_MULE_DIRS, LOCK_TIMEOUT, muleContext, RECEIVE_TIMEOUT, TEST_MESSAGE, TEST_PAYLOAD, WORKING_DIRECTORY_SYSTEM_PROPERTY_KEY, workingDirectory
DEFAULT_TEST_TIMEOUT_SECS, globalTimeout, logger, name, TEST_TIMEOUT_SYSTEM_PROPERTY, TESTING_MODE_PROPERTY_NAME
Constructor and Description |
---|
InboundMessageLossTestCase() |
Modifier and Type | Method and Description |
---|---|
protected void |
doSetUp()
Enables the adding of extra behavior on the set up stage of a test right
after the creation of the mule context in
AbstractMuleContextTestCase.setUpMuleContext() . |
protected String[] |
getConfigFiles() |
void |
testCatchExceptionStrategyConsumesMessage() |
void |
testComponentException() |
void |
testDefaultExceptionStrategyConsumesMessage() |
void |
testNoException() |
void |
testRollbackExceptionStrategyConsumesMessage() |
void |
testRouterException() |
void |
testTransformerException() |
closeConsumer, createConsumer, doTearDown, listenOnQueue, putMessageOnQueue, readMessageFromQueue
checkConfig, createInputDestination, createJmsConfig, createOutputDestination, dispatchMessage, dispatchMessage, dispatchMessage, getBuilder, getClient, getConnection, getDeadLetterQueueName, getInboundEndpoint, getInboundQueueName, getJmsConfig, getOutboundEndpoint, getOutboundQueueName, getSmallTimeout, getStartUpProperties, getTimeout, isMultipleProviders, jmsProviderConfigs, purge, purgeTopic, purgeTopics, receive, receiveMessage, receiveMessage, receiveMessage, runAsynchronousDispatching, send, setJmsConfig, setMultipleProviders
clearFlowAssertions, getComponent, getComponent, getConfigFile, getConfigResources, getFlowConstruct, getFunctionalTestComponent, getSubFlow, loadResource, loadResourceAsString, lookupFlowConstruct, runFlow, runFlow, runFlow, runFlowAndExpect, runFlowAndExpectProperty, runFlowWithPayloadAndExpect, runSchedulersOnce, stopFlowConstruct, stopFlowSchedulers, testFlow, testFlow
addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doSetUpBeforeMuleContextCreation, doTearDownAfterMuleContextDispose, getConfigurationResources, getFileInsideWorkingDirectory, getSensingNullMessageProcessor, getTestConnector, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEventContext, getTestEventContext, getTestEventUsingFlow, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestMuleMessage, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestService, getTestService, getTestService, getTestSession, getTestTransactedInboundEndpoint, getTestTransformer, getTriggerableMessageSource, getTriggerableMessageSource, getWorkingDirectory, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, setDisposeContextPerClass, setStartContext, setUpMuleContext
clearExcludedFlag, clearRequestContext, clearTestCaseName, createTestTimeoutRule, dumpFilteredThreadsInTest, getTestHeader, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isDisabledInThisEnvironment, isExcluded, isFailOnTimeout, isOffline, isTestIncludedInExclusionFile, takeTestCaseName
protected Latch messageRedelivered
protected final int latchTimeout
protected String[] getConfigFiles()
getConfigFiles
in class FunctionalTestCase
protected void doSetUp() throws Exception
AbstractMuleContextTestCase
AbstractMuleContextTestCase.setUpMuleContext()
.
Under normal circumstances this method could be replaced by a
@Before
annotated method.
doSetUp
in class AbstractJmsFunctionalTestCase
Exception
- if something fails that should halt the test casepublic void testCatchExceptionStrategyConsumesMessage() throws Exception
Exception
public void testRollbackExceptionStrategyConsumesMessage() throws Exception
Exception
Copyright © 2003–2015 MuleSoft, Inc.. All rights reserved.