Hi,
Can someone suggest the simplest way to expose a FactoryBean as a ManagedResource? I'm trying to extend the Spring TimerFactoryBean so that Timers can be 'paused' and 'resumed' at runtime.
...
Type: Posts; User: mrtom; Keyword(s):
Hi,
Can someone suggest the simplest way to expose a FactoryBean as a ManagedResource? I'm trying to extend the Spring TimerFactoryBean so that Timers can be 'paused' and 'resumed' at runtime.
...
Hi!
I'm trying to use ConnectorServerFactoryBean to expose the platform mbean server. When starting up, JmxUtils.locateMBeanServer(null) never returns the platform mbean server as...
My SMLC seems to be behaving now (I must have been using the wrong appContext previously). I think I'll avoid DMLC altogether for the moment since I don't need to create XA transactions.
Thanks for...
Hi,
When closing the ApplicationContext (eg. undeploy in Tomcat) the process is blocked by my JMS consumer (using SimpleMessageListenerContainer). If I send a message to the queue it will then...
In the same comment below it mentions that..
"The recommended solution for handling failure of a subtransaction is a "nested transaction", where the global transaction can be rolled back to a...
Hi,
When 'setGlobalRollbackOnParticipationFailure' of my TransactionManager is set to the default of 'true' a nested transaction (PROPAGATION_NESTED) will affect the outer transaction. This isn't...
I don't think that using PROPOGATE_REQUIRED for the tasks would help. I need to guarantee that what the tasks do and what is reported are synchronised which is why I wanted them both to be part of...
I have created a simple workflow system where tasks can be automatically run in order. When tasks are executed it stores the results in the database but if an unhandled Exception is thrown in one of...
That confirms what I thought I knew. My problem is that an inner transaction with PROPAGATION_REQUIRES_NEW _is_ affecting the outer transaction.
When I am using savepoints in the outer transaction...
Hi,
I'm having problems when setting a save point and rolling back where another transaction is run in between with PROPAGATION_REQUIRES_NEW.
I'm doing this programmatically and basically looks...