Supported OS:
Requirements: Windows 10/8/7/Vista/XP
Mac OS X 10.10.3/10.9/10.8/10.7
I need help I accidentally deleted some pictures and I want them back as soon as possible. I've tried this Android Data Recovery. It finds them back, as well as many other older pictures.
- Reviewed by Mcakrami
Recover SMS, Contacts, Photos and Video on Android
Accidentally deleted messages or contacts on your Samsung handset? Or lost photos from the SD card on your Android device? No need to worry now! Wondershare Dr.Fone for Android is capable of recovering messages, contacts, photos and video on/from an Android phone or tablet. Due to the ease-to-use interface, it’s ideal for everyone, like single users or professionals, even concerned parents who want to protect their kids from negative information. Scan, preview and recover. Simple clicks bring you what you want.
The very first thing: Before using Android Data Recovery, make sure that your phone can be switched on and detected by your computer, and the battery is not less than 20%.
Directly scan and recover SMS, contacts, photos & video
Automatically scan your device after conne
Recover sent & received messages, and export in HTML to PC for easy
Retrieve deleted contacts, including names, numbers, Email & addresses, and export in HTML, vCard and CSV to PC;
Regain photos and video from SD cards inside Android devices to a computer.
Note: Currently, it’s unavailable to recover contacts and SMS lost due to rooting, restoring to factory settings, flashing ROMs, unlocking, device broken and system crash by Wondershare Dr.Fone for Android.
Browse, backup and re-sync data on your computer
Existing data and deleted data each have their own colo
Browse and backup them from a dev
Re-sync contacts backup to a device via .
Preview & selective recovery
Preview all recoverable contacts, messages and ph
Selectively recover what you want by selecting them from the scan result.
Support multiple Android devices & Android OS
Available for hot Android phones and tablets from Samsung, HTC, LG, Sony, Motorola, ZET, Huawei, etc.;
Support lots of Android OS
All rooted Samsung devices are supported, regardless of Android OS.
The list of devices and Android OS is still rapidly growing.
Note: If your Samsung device is not in the list, you can root it by yourself (only root, not flash ROM), and then use Wondershare Dr.Fone for Android to recover data.
Read-only and risk-free
Keep data on your device original, no damage, deletion or
Only read and recover the data, no personal information leaking, or things like that.
You May Be Interested
Our Promise
Android-Recovery-Transfer Software is dedicated to providing every Android Phone user with easy, effective, and risk-free tools.
Android Data Recovery
Copyright (C) android- 2016. All rights reserved.iPhone Data Recovery
World's 1st iPhone/iPad data recovery software
Recover iPhone photos, videos, contacts, messages, notes, call log and more without backup files.
Retrieve lost iPhone/iPad/iPod touch data from iCloud backup, iTunes backup (including encrypted one).
Repair iOS devices continuously looping recovery mode, stuck in Apple logo, black/white screen.
Regain lost data for iOS device due to delete accidentally, device crashed, smashed or broken, device loss, jailbreak, iOS upgrade or factory settings restore.
Recover and save lost data to computer or back to iDevices.
Supported OS:
Windows 10/8/7/Vista/XP
Mac OS X 10.6 - 10.12
Three Simple Steps to Recover Data From iOS Devices
1. Connect Your Device
2. Scan Your Device
3. Preview and Recover Your Data
1. Connect iDevices: Connect iOS device to computer, the software will detect your phone automatically.
2. Scan iDevices: After the software detect your phone, you can choose one mode to scan your iOS device directly or iTunes/iCloud Backup.
3. Preview and Recover: Preview the lost data and select the files you want to recover. You can save the recovered contacts in VCF,CSV, HTML format to PC or back to the devices. You are also allowed to save the recovered meida contents like photos, videos and more to computer, export text contents like text messages, notes, imessages and more to pc or back to the devices.
Three iOS Data Recovery Modes
Recover data from iOS Device directly - Connect your iOS Device to computer and you can scan your iPhone/iPad/iPod touch directly to recover deleted data.
Recover data from iTunes Backup - Find your computer iTunes backup automatically and scan the backup to recover your lost data.
Recover data from iCloud Backup - Log in to your icloud, download the iCloud backup then scan it to recover the deleted files.
Supported Recover Data from iPhone/iPad/iPod touch
Call History
WhatsApp History
Safari Bookmark
Facebook Messenger
Camera Roll
Photo Stream
Voice Memo
App Photos
App Documents
Supported Data Loss Situations
Recover data from iOS devices
Data Loss Scenarios
Recover data from iTunes/iCloud backup files
o iPhone 7/7 Plus, iPhone SE, iPhone 6s/6s Plus, iPhone 6/6 Plus, iPhone 5s/5c/5, iPhone 4s, iPhone 4/3gs
o iPad Pro, iPad Air 2/1, iPad mini 4/3/2/1, iPad 4/3/2/1
o iPod touch 6, iPod touch 5, iPod touch 4
o Intentional or accidental Deletion
o White Apple logo screen, black/white screen
o Continuously looping recovery mode
o System inaccessible
o System crashed
o Device damage/crashed/smashed
o Forgotten screen lock password
o iPhone 7/7 Plus, iPhone SE, iPhone 6s/6s Plus, iPhone 6/6 Plus, iPhone 5s/5c/5, iPhone 4s, iPhone 4, iPhone 3gs
o iPad Pro, iPad Air 2/1, iPad mini 4/3/2/1, iPad 4/3/2/1
o iPod touch 5, iPod touch 6, iPod touch 4
o No Supported iDevices
o Lost iOS device
o Factory reformatting
o Upgrade failure
o Jailbreak failure
o Failed to restore from iTunes backup files
Fix the "recovery mode loop", "stuck in white Apple logo" problem
In addition to the iPhone iPad iPod touch data can be restored, the iPhone Recovery Software also can repair the iDevices operating system. After your iOS devices continuously looping recovery mode, stuck in Apple logo, black/white screen and can't start up normally, you can switch to "Repair Operating System" feature for help. The "Repair Operating System" feature provide you the function to fix the iOS devices and let the device back to normal.
iPhone/iPad Data Recovery Tips
iPhone 7/7 Plus, iPhone SE, iPhone 6s/6s Plus, iPhone 6/6 Plus, iPhone 5s/5c/5, iPhone 4s, iPhone 4, iPhone 3GS
iPad Pro, iPad Air 2/1, iPad mini 4/3/2/1, iPad 4/3/2/1, iPod touch 6, iPod touch 5, iPod touch 4
iPhone Data Recovery
iPad Data Recovery
Media Content Recovery
Text Content Recovery
User Reviews
"Apart from backup of data, this software has also helped me to correct the operating system of my device. Now it is working smooth and fast."
- Melchers
"With this powerful tool, I was able to recover almost all of the lost photos and videos! Your program is a lifesaver and I will definitely be advertising for you!"
- Christian
"It worked great. I will suggest the product to everyone I know. I thank it for letting me have all my iPhone contacts back. Thanks again."
"There is nothing else you would require if you have such a versatile software in your PC. The guide available it allowed me to explore its excellent features."
We Promise
100% Clean
Our software is free of any forms of malware or virus. It is safe to install and run.
30-day money back
We promise up to&30-day money back guarantee.
Rapid service
Your satisfaction is our top priority. We provide you really fast service.
You May Be Interested in These Items
Mobile Transfer is a powerful phone to phone data transfer tool lets you seamlessly copy data between Android,...
iPhone Data Eraser is the best data eraser software to get your device started with a clean slate when you pla...
For manage Apple devices, iOS Manager lets you transfer music, video, playlists, iTunes U to iTunes/PC and man...
Copyright (C) 2016 iphone-. All Rights Reserved.iPhone(R), iTunes(R), iMac(R), iPod(R) and iPad(R) are registered trademarks of Apple Inc. Software available here is not developed by or affiliated with Apple Inc.AbstractJmsListeningContainer.SharedConnectionNotInitializedException
static&int
CACHE_AUTO
&&&&&&&&&&Constant that indicates automatic choice of an appropriate
caching level (depending on the transaction management strategy).
static&int
CACHE_CONNECTION
&&&&&&&&&&Constant that indicates to cache a shared JMS Connection.
static&int
CACHE_CONSUMER
&&&&&&&&&&Constant that indicates to cache a shared JMS Connection
and a JMS Session for each listener thread, as well as
a JMS MessageConsumer for each listener thread.
static&int
CACHE_NONE
&&&&&&&&&&Constant that indicates to cache no JMS resources at all.
static&int
CACHE_SESSION
&&&&&&&&&&Constant that indicates to cache a shared JMS Connection
and a JMS Session for each listener thread.
static&long
DEFAULT_RECOVERY_INTERVAL
&&&&&&&&&&The default recovery interval: 5000 ms = 5 seconds.
static&String
DEFAULT_THREAD_NAME_PREFIX
&&&&&&&&&&Default thread name prefix: "DefaultMessageListenerContainer-".
DEFAULT_RECEIVE_TIMEOUT
lifecycleMonitor, sharedConnectionMonitor
DefaultMessageListenerContainer()
&&&&&&&&&&&
protected &TaskExecutor
createDefaultTaskExecutor()
&&&&&&&&&&Create a default TaskExecutor.
protected &void
doInitialize()
&&&&&&&&&&Creates the specified number of concurrent consumers,
in the form of a JMS Session plus associated MessageConsumer
running in a separate thread.
protected &void
doRescheduleTask(Object&task)
&&&&&&&&&&Re-executes the given task via this listener container's TaskExecutor.
protected &void
doShutdown()
&&&&&&&&&&Destroy the registered JMS Sessions and associated MessageConsumers.
protected &void
establishSharedConnection()
&&&&&&&&&&Overridden to accept a failure in the initial setup - leaving it up to the
asynchronous invokers to establish the shared Connection on first access.
getActiveConsumerCount()
&&&&&&&&&&Return the number of currently active consumers.
getCacheLevel()
&&&&&&&&&&Return the level of caching that this listener container is allowed to apply.
getConcurrentConsumers()
&&&&&&&&&&Return the "concurrentConsumer" setting.
getIdleTaskExecutionLimit()
&&&&&&&&&&Return the limit for idle executions of a receive task.
getMaxConcurrentConsumers()
&&&&&&&&&&Return the "maxConcurrentConsumer" setting.
getMaxMessagesPerTask()
&&&&&&&&&&Return the maximum number of messages to process in one task.
getScheduledConsumerCount()
&&&&&&&&&&Return the number of currently scheduled consumers.
protected &void
handleListenerSetupFailure(Throwable&ex,
boolean&alreadyRecovered)
&&&&&&&&&&Handle the given exception that arose during setup of a listener.
initialize()
&&&&&&&&&&Initialize this container.
protected &void
messageReceived(Object&invoker,
Session&session)
&&&&&&&&&&Tries scheduling a new invoker, since we know messages are coming in...
protected &void
noMessageReceived(Object&invoker,
Session&session)
&&&&&&&&&&Marks the affected invoker as idle.
protected &void
recoverAfterListenerSetupFailure()
&&&&&&&&&&Recover this listener container after a listener failed to set itself up,
for example reestablishing the underlying Connection.
protected &void
refreshConnectionUntilSuccessful()
&&&&&&&&&&Refresh the underlying Connection, not returning before an attempt has been
successful.
protected &void
refreshDestination()
&&&&&&&&&&Refresh the JMS destination that this listener container operates on.
protected &void
scheduleNewInvokerIfAppropriate()
&&&&&&&&&&Schedule a new invoker, increasing the total number of scheduled
invokers for this listener container, but only if the specified
"maxConcurrentConsumers" limit has not been reached yet, and only
if this listener container does not currently have idle invokers
that are waiting for new messages already.
setCacheLevel(int&cacheLevel)
&&&&&&&&&&Specify the level of caching that this listener container is allowed to apply.
setCacheLevelName(String&constantName)
&&&&&&&&&&Specify the level of caching that this listener container is allowed to apply,
in the form of the name of the corresponding constant: e.g.
setConcurrentConsumers(int&concurrentConsumers)
&&&&&&&&&&Specify the number of concurrent consumers to create.
setIdleTaskExecutionLimit(int&idleTaskExecutionLimit)
&&&&&&&&&&Specify the limit for idle executions of a receive task, not having
received any message within its execution.
setMaxConcurrentConsumers(int&maxConcurrentConsumers)
&&&&&&&&&&Specify the maximum number of concurrent consumers to create.
setMaxMessagesPerTask(int&maxMessagesPerTask)
&&&&&&&&&&Specify the maximum number of messages to process in one task.
setRecoveryInterval(long&recoveryInterval)
&&&&&&&&&&Specify the interval between recovery attempts, in milliseconds.
setTaskExecutor(TaskExecutor&taskExecutor)
&&&&&&&&&&Set the Spring TaskExecutor to use for running the listener threads.
protected &boolean
sharedConnectionEnabled()
&&&&&&&&&&Use a shared JMS Connection depending on the "cacheLevel" setting.
protected &void
sleepInbetweenRecoveryAttempts()
&&&&&&&&&&Sleep according to the specified recovery interval.
&&&&&&&&&&Overridden to reset the stop callback, if any.
protected &void
startSharedConnection()
&&&&&&&&&&This implementations proceeds even after an exception thrown from
Connection.start(), relying on listeners to perform
appropriate recovery.
stop(Runnable&callback)
&&&&&&&&&&Stop this listener container, invoking the specific callback
once all listener processing has actually stopped.
protected &void
stopSharedConnection()
&&&&&&&&&&This implementations proceeds even after an exception thrown from
Connection.stop(), relying on listeners to perform
appropriate recovery after a restart.
protected &void
validateConfiguration()
&&&&&&&&&&Validate the configuration of this container.
createConsumer, createListenerConsumer, doReceiveAndExecute, getConnection, getSession, getTransactionManager, isPubSubNoLocal, isSessionLocallyTransacted, receiveAndExecute, receiveMessage, setPubSubNoLocal, setReceiveTimeout, setSessionTransacted, setTransactionManager, setTransactionName, setTransactionTimeout
checkMessageListener, commitIfNecessary, doExecuteListener, doInvokeListener, doInvokeListener, executeListener, getDestination, getDestinationName, getDurableSubscriptionName, getExceptionListener, getMessageListener, getMessageSelector, handleListenerException, invokeExceptionListener, invokeListener, isAcceptMessagesWhileStopping, isExposeListenerSession, isSubscriptionDurable, rollbackIfNecessary, rollbackOnExceptionIfNecessary, setAcceptMessagesWhileStopping, setDestination, setDestinationName, setDurableSubscriptionName, setExceptionListener, setExposeListenerSession, setMessageListener, setMessageSelector, setSubscriptionDurable
afterPropertiesSet, createSharedConnection, destroy, doStart, doStop, getBeanName, getClientId, getPausedTaskCount, getSharedConnection, isActive, isRunning, logRejectedTask, prepareSharedConnection, refreshSharedConnection, rescheduleTaskIfNecessary, resumePausedTasks, runningAllowed, setAutoStartup, setBeanName, setClientId, shutdown, stop, waitWhileNotRunning
getDestinationResolver, isPubSubDomain, resolveDestinationName, setDestinationResolver, setPubSubDomain
convertJmsAccessException, createConnection, createSession, getConnectionFactory, getSessionAcknowledgeMode, isClientAcknowledge, isSessionTransacted, setConnectionFactory, setSessionAcknowledgeMode, setSessionAcknowledgeModeName
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
setBeanName
DEFAULT_THREAD_NAME_PREFIX
public static final String DEFAULT_THREAD_NAME_PREFIX
Default thread name prefix: "DefaultMessageListenerContainer-".
DEFAULT_RECOVERY_INTERVAL
public static final long DEFAULT_RECOVERY_INTERVAL
The default recovery interval: 5000 ms = 5 seconds.
See Also:Constant Field Values
CACHE_NONE
public static final int CACHE_NONE
Constant that indicates to cache no JMS resources at all.
See Also:setCacheLevel(int),
Constant Field Values
CACHE_CONNECTION
public static final int CACHE_CONNECTION
Constant that indicates to cache a shared JMS Connection.
See Also:setCacheLevel(int),
Constant Field Values
CACHE_SESSION
public static final int CACHE_SESSION
Constant that indicates to cache a shared JMS Connection
and a JMS Session for each listener thread.
See Also:setCacheLevel(int),
Constant Field Values
CACHE_CONSUMER
public static final int CACHE_CONSUMER
Constant that indicates to cache a shared JMS Connection
and a JMS Session for each listener thread, as well as
a JMS MessageConsumer for each listener thread.
See Also:setCacheLevel(int),
Constant Field Values
CACHE_AUTO
public static final int CACHE_AUTO
Constant that indicates automatic choice of an appropriate
caching level (depending on the transaction management strategy).
See Also:setCacheLevel(int),
Constant Field Values
DefaultMessageListenerContainer
public DefaultMessageListenerContainer()
setTaskExecutor
public void setTaskExecutor(TaskExecutor&taskExecutor)
Set the Spring TaskExecutor to use for running the listener threads.
Default is a SimpleAsyncTaskExecutor,
starting up a number of new threads, according to the specified number
of concurrent consumers.
Specify an alternative TaskExecutor for integration with an existing
thread pool. Note that this really only adds value if the threads are
managed in a specific fashion, for example within a J2EE environment.
A plain thread pool does not add much value, as this listener container
will occupy a number of threads for its entire lifetime.
See Also:setConcurrentConsumers(int),
SimpleAsyncTaskExecutor,
WorkManagerTaskExecutor
setRecoveryInterval
public void setRecoveryInterval(long&recoveryInterval)
Specify the interval between recovery attempts, in milliseconds.
The default is 5000 ms, that is, 5 seconds.
See Also:handleListenerSetupFailure(java.lang.Throwable, boolean)
setCacheLevelName
public void setCacheLevelName(String&constantName)
throws IllegalArgumentException
Specify the level of caching that this listener container is allowed to apply,
in the form of the name of the corresponding constant: e.g. "CACHE_CONNECTION".
IllegalArgumentExceptionSee Also:setCacheLevel(int)
setCacheLevel
public void setCacheLevel(int&cacheLevel)
Specify the level of caching that this listener container is allowed to apply.
Default is CACHE_NONE if an external transaction manager has been specified
(to reobtain all resources freshly within the scope of the external transaction),
and CACHE_CONSUMER else (operating with local JMS resources).
Some J2EE servers only register their JMS resources with an ongoing XA
transaction in case of a freshly obtained JMS Connection and Session,
which is why this listener container does by default not cache any of those.
However, if you want to optimize for a specific server, consider switching
this setting to at least CACHE_CONNECTION or CACHE_SESSION even in
conjunction with an external transaction manager.
Currently known servers that absolutely require CACHE_NONE for XA
transaction processing: JBoss 4. For any others, consider raising the
cache level.
See Also:CACHE_NONE,
CACHE_CONNECTION,
CACHE_SESSION,
CACHE_CONSUMER,
setCacheLevelName(java.lang.String),
AbstractPollingMessageListenerContainer.setTransactionManager(org.springframework.transaction.PlatformTransactionManager)
getCacheLevel
public int getCacheLevel()
Return the level of caching that this listener container is allowed to apply.
setConcurrentConsumers
public void setConcurrentConsumers(int&concurrentConsumers)
Specify the number of concurrent consumers to create. Default is 1.
Specifying a higher value for this setting will increase the standard
level of scheduled concurrent consumers at runtime: This is effectively
the minimum number of concurrent consumers which will be scheduled
at any given time. This for dynamic scaling,
consider specifying the "maxConcurrentConsumers" setting instead.
Raising the number of concurrent consumers is recommendable in order
to scale the consumption of messages coming in from a queue. However,
note that any ordering guarantees are lost once multiple consumers are
registered. In general, stick with 1 consumer for low-volume queues.
Do not raise the number of concurrent consumers for a topic.
This would lead to concurrent consumption of the same message,
which is hardly ever desirable.
This setting can be modified at runtime, for example through JMX.
See Also:setMaxConcurrentConsumers(int)
getConcurrentConsumers
public final int getConcurrentConsumers()
Return the "concurrentConsumer" setting.
This returns the currently configured "concurrentConsumers"
the number of currently scheduled/active consumers might differ.
See Also:getScheduledConsumerCount(),
getActiveConsumerCount()
setMaxConcurrentConsumers
public void setMaxConcurrentConsumers(int&maxConcurrentConsumers)
Specify the maximum number of concurrent consumers to create. Default is 1.
If this setting is higher than "concurrentConsumers", the listener container
will dynamically schedule new consumers at runtime, provided that enough
incoming messages are encountered. Once the load goes down again, the number of
consumers will be reduced to the standard level ("concurrentConsumers") again.
Raising the number of concurrent consumers is recommendable in order
to scale the consumption of messages coming in from a queue. However,
note that any ordering guarantees are lost once multiple consumers are
registered. In general, stick with 1 consumer for low-volume queues.
Do not raise the number of concurrent consumers for a topic.
This would lead to concurrent consumption of the same message,
which is hardly ever desirable.
This setting can be modified at runtime, for example through JMX.
See Also:setConcurrentConsumers(int)
getMaxConcurrentConsumers
public final int getMaxConcurrentConsumers()
Return the "maxConcurrentConsumer" setting.
This returns the currently configured "maxConcurrentConsumers"
the number of currently scheduled/active consumers might differ.
See Also:getScheduledConsumerCount(),
getActiveConsumerCount()
setMaxMessagesPerTask
public void setMaxMessagesPerTask(int&maxMessagesPerTask)
Specify the maximum number of messages to process in one task.
More concretely, this limits the number of message reception attempts
per task, which includes receive iterations that did not actually
pick up a message until they hit their timeout (see the
"receiveTimeout" property).
Default is unlimited (-1) in case of a standard TaskExecutor,
reusing the original invoker threads until shutdown (at the
expense of limited dynamic scheduling).
In case of a SchedulingTaskExecutor indicating a preference for
short-lived tasks, the default is 10 instead. Specify a number
of 10 to 100 messages to balance between rather long-lived and
rather short-lived tasks here.
Long-lived tasks avoid frequent thread context switches through
sticking with the same thread all the way through, while short-lived
tasks allow thread pools to control the scheduling. Hence, thread
pools will usually prefer short-lived tasks.
This setting can be modified at runtime, for example through JMX.
See Also:setTaskExecutor(org.springframework.core.task.TaskExecutor),
AbstractPollingMessageListenerContainer.setReceiveTimeout(long),
SchedulingTaskExecutor.prefersShortLivedTasks()
getMaxMessagesPerTask
public int getMaxMessagesPerTask()
Return the maximum number of messages to process in one task.
setIdleTaskExecutionLimit
public void setIdleTaskExecutionLimit(int&idleTaskExecutionLimit)
Specify the limit for idle executions of a receive task, not having
received any message within its execution. If this limit is reached,
the task will shut down and leave receiving to other executing tasks.
Default is 1, closing idle resources early once a task didn't
receive a message. This applies to dyn see the
"maxConcurrentConsumers" setting.
The minimum number of consumers
(see "concurrentConsumers")
will be kept around until shutdown in any case.
Within each task execution, a number of message reception attempts
(according to the "maxMessagesPerTask" setting) will each wait for an incoming
message (according to the "receiveTimeout" setting). If all of those receive
attempts in a given task return without a message, the task is considered
idle with respect to received messages. Such a task may
however, once it reached the specified "idleTaskExecutionLimit", it will
shut down (in case of dynamic scaling).
Raise this limit if you encounter too frequent scaling up and down.
With this limit being higher, an idle consumer will be kept around longer,
avoiding the restart of a consumer once a new load of messages comes in.
Alternatively, specify a higher "maxMessagesPerTask" and/or "receiveTimeout" value,
which will also lead to idle consumers being kept around for a longer time
(while also increasing the average execution time of each scheduled task).
This setting can be modified at runtime, for example through JMX.
See Also:setMaxMessagesPerTask(int),
AbstractPollingMessageListenerContainer.setReceiveTimeout(long)
getIdleTaskExecutionLimit
public int getIdleTaskExecutionLimit()
Return the limit for idle executions of a receive task.
validateConfiguration
protected void validateConfiguration()
Description copied from class: AbstractJmsListeningContainer
Validate the configuration of this container.
The default implementation is empty. To be overridden in subclasses.
Overrides:validateConfiguration in class AbstractMessageListenerContainer
initialize
public void initialize()
Description copied from class: AbstractJmsListeningContainer
Initialize this container.
Creates a JMS Connection, starts the Connection
(if "autoStartup" hasn't been turned off),
and calls AbstractJmsListeningContainer.doInitialize().
Overrides:initialize in class AbstractPollingMessageListenerContainer
doInitialize
protected void doInitialize()
throws JMSException
Creates the specified number of concurrent consumers,
in the form of a JMS Session plus associated MessageConsumer
running in a separate thread.
Specified by:doInitialize in class AbstractJmsListeningContainer
JMSException - if registration failedSee Also:scheduleNewInvoker(),
setTaskExecutor(org.springframework.core.task.TaskExecutor)
doShutdown
protected void doShutdown()
throws JMSException
Destroy the registered JMS Sessions and associated MessageConsumers.
Specified by:doShutdown in class AbstractJmsListeningContainer
JMSException - if shutdown failedSee Also:AbstractJmsListeningContainer.shutdown()
public void start()
throws JmsException
Overridden to reset the stop callback, if any.
Specified by:start in interface LifecycleOverrides:start in class AbstractJmsListeningContainer
JmsException - if starting failedSee Also:AbstractJmsListeningContainer.doStart()
public void stop(Runnable&callback)
throws JmsException
Stop this listener container, invoking the specific callback
once all listener processing has actually stopped.
Note: Further stop(runnable) calls (before processing
has actually stopped) will override the specified callback. Only the
latest specified callback will be invoked.
If a subsequent start() call restarts the listener container
before it has fully stopped, the callback will not get invoked at all.
Parameters:callback - the callback to invoke once listener processing
has fully stopped
JmsException - if stopping failedSee Also:AbstractJmsListeningContainer.stop()
getScheduledConsumerCount
public final int getScheduledConsumerCount()
Return the number of currently scheduled consumers.
This number will always be inbetween "concurrentConsumers" and
"maxConcurrentConsumers", but might be higher than "activeConsumerCount"
(in case of some consumers being scheduled but not executed at the moment).
See Also:getConcurrentConsumers(),
getMaxConcurrentConsumers(),
getActiveConsumerCount()
getActiveConsumerCount
public final int getActiveConsumerCount()
Return the number of currently active consumers.
This number will always be inbetween "concurrentConsumers" and
"maxConcurrentConsumers", but might be lower than "scheduledConsumerCount".
(in case of some consumers being scheduled but not executed at the moment).
See Also:getConcurrentConsumers(),
getMaxConcurrentConsumers(),
getActiveConsumerCount()
createDefaultTaskExecutor
protected TaskExecutor createDefaultTaskExecutor()
Create a default TaskExecutor. Called if no explicit TaskExecutor has been specified.
The default implementation builds a SimpleAsyncTaskExecutor
with the specified bean name (or the class name, if no bean name specified) as thread name prefix.
See Also:SimpleAsyncTaskExecutor.SimpleAsyncTaskExecutor(String)
sharedConnectionEnabled
protected final boolean sharedConnectionEnabled()
Use a shared JMS Connection depending on the "cacheLevel" setting.
Specified by:sharedConnectionEnabled in class AbstractJmsListeningContainer
See Also:setCacheLevel(int),
CACHE_CONNECTION
doRescheduleTask
protected void doRescheduleTask(Object&task)
Re-executes the given task via this listener container's TaskExecutor.
Overrides:doRescheduleTask in class AbstractJmsListeningContainer
Parameters:task - the task object to rescheduleSee Also:setTaskExecutor(org.springframework.core.task.TaskExecutor)
messageReceived
protected void messageReceived(Object&invoker,
Session&session)
Tries scheduling a new invoker, since we know messages are coming in...
Overrides:messageReceived in class AbstractPollingMessageListenerContainer
Parameters:invoker - the invoker object (passed through)session - the receiving JMS SessionSee Also:scheduleNewInvokerIfAppropriate()
noMessageReceived
protected void noMessageReceived(Object&invoker,
Session&session)
Marks the affected invoker as idle.
Overrides:noMessageReceived in class AbstractPollingMessageListenerContainer
Parameters:invoker - the invoker object (passed through)session - the receiving JMS Session
scheduleNewInvokerIfAppropriate
protected void scheduleNewInvokerIfAppropriate()
Schedule a new invoker, increasing the total number of scheduled
invokers for this listener container, but only if the specified
"maxConcurrentConsumers" limit has not been reached yet, and only
if this listener container does not currently have idle invokers
that are waiting for new messages already.
Called once a message has been received, to scale up while
processing the message in the invoker that originally received it.
See Also:setTaskExecutor(org.springframework.core.task.TaskExecutor),
getMaxConcurrentConsumers()
establishSharedConnection
protected void establishSharedConnection()
Overridden to accept a failure in the initial setup - leaving it up to the
asynchronous invokers to establish the shared Connection on first access.
Overrides:establishSharedConnection in class AbstractJmsListeningContainer
See Also:refreshConnectionUntilSuccessful()
startSharedConnection
protected void startSharedConnection()
This implementations proceeds even after an exception thrown from
Connection.start(), relying on listeners to perform
appropriate recovery.
Overrides:startSharedConnection in class AbstractJmsListeningContainer
See Also:Connection.start()
stopSharedConnection
protected void stopSharedConnection()
This implementations proceeds even after an exception thrown from
Connection.stop(), relying on listeners to perform
appropriate recovery after a restart.
Overrides:stopSharedConnection in class AbstractJmsListeningContainer
See Also:Connection.start()
handleListenerSetupFailure
protected void handleListenerSetupFailure(Throwable&ex,
boolean&alreadyRecovered)
Handle the given exception that arose during setup of a listener.
Called for every such exception in every concurrent listener.
The default implementation logs the exception at error level
if not recovered yet, and at debug level if already recovered.
Can be overridden in subclasses.
Parameters:ex - the exception to handlealreadyRecovered - whether a previously executing listener
already recovered from the present listener setup failure
(this usually indicates a follow-up failure than can be ignored
other than for debug log purposes)See Also:recoverAfterListenerSetupFailure()
recoverAfterListenerSetupFailure
protected void recoverAfterListenerSetupFailure()
Recover this listener container after a listener failed to set itself up,
for example reestablishing the underlying Connection.
The default implementation delegates to DefaultMessageListenerContainer's
recovery-capable refreshConnectionUntilSuccessful() method, which will
try to re-establish a Connection to the JMS provider both for the shared
and the non-shared Connection case.
See Also:refreshConnectionUntilSuccessful(),
refreshDestination()
refreshConnectionUntilSuccessful
protected void refreshConnectionUntilSuccessful()
Refresh the underlying Connection, not returning before an attempt has been
successful. Called in case of a shared Connection as well as without shared
Connection, so either needs to operate on the shared Connection or on a
temporary Connection that just gets established for validation purposes.
The default implementation retries until it successfully established a
Connection, for as long as this message listener container is active.
Applies the specified recovery interval between retries.
See Also:setRecoveryInterval(long)
refreshDestination
protected void refreshDestination()
Refresh the JMS destination that this listener container operates on.
Called after listener setup failure, assuming that a cached Destination
object might have become invalid (a typical case on WebLogic JMS).
The default implementation removes the destination from a
DestinationResolver's cache, in case of a CachingDestinationResolver.
See Also:AbstractMessageListenerContainer.setDestinationName(java.lang.String),
CachingDestinationResolver
sleepInbetweenRecoveryAttempts
protected void sleepInbetweenRecoveryAttempts()Sleep according to the specified recovery interval.Called inbetween recovery attempts.
spring下的DefaultMessageListenerContainer使用方法和示例
上一篇：下一篇：
责任申明：本站内容均整理自互联网，若有侵权，请联系我们。使用本站提供的任务技术内容造成不良后果，本站不负任何责任。
欢迎投稿,电子邮件：（#号换成@）&& QQ群1： &&