Skip to main content

Spring proxyFactoryBean not applying interceptors and circular dependencies

We use AOP a lot but due to legacy reasons we dont use aspectJ yet and we are using Spring ProxyFactoryBean and use interceptors to apply AOP behavior like light weight instrumentation or transactions.

Lately we ran into two or three issues where on some proxyFactoryBeans the interceptors wont be applied.  My hunch was it was some circular dependency between beans so I added DEBUG on org.springframework.beans in log4j and it spitted tons of logs, I did a grep

 grep "that is not fully initialized yet - a consequence of a circular reference" ~/apache-tomcat-7.0.30/logs/tomcat.log |awk -F "singleton" '{print $2}'|sort|uniq  

it would print some message like 

bean 'gdriveClient' that is not fully initialized yet - a consequence of a circular reference
 bean 'gdriveRestServiceHelper' that is not fully initialized yet - a consequence of a circular reference
 bean 'filerServiceRequestHandlerFactory' that is not fully initialized yet - a consequence of a circular reference
 bean 'objectReplicationManager' that is not fully initialized yet - a consequence of a circular reference
But this was a painful way to  analyse it and I wanted to future proof the code so that developers in future cant introduce a circular dependency.

Today I found that instead of loading context like 
ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext("/applicationContext.xml");
You  can do something like

context = new ClassPathXmlApplicationContext();

and this would fail on first circular reference encountered.  This prints in log entire hierarchy of bean it was trying to load so its very easy to chain the beans to find circular reference. I haven’t committed the code yet but the idea is to fix all existing circular dependencies and then enable this code.


Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost(""); factory.setPort(5672); Conne…

Spring query timeout or transaction timeout

If you are using spring to manage transactions then you can specify default transaction timeout using

    <bean id="transactionManager"
        <property name="dataSource" ref="dataSource" />
        <property name="defaultTimeout" value="30" /> <!--30 sec--->             

or you can override the timeout in the annotation

    @Transactional(readOnly = false, timeout=30)

or if you are doing it programatic transactions then you can do

DataSourceTransactionManager transactionManager = new DataSourceTransactionManager(dataSource);

 or you can override the timeout for one particular transaction

TransactionTemplate transactionTemplate = new TransactionTemplate();

Python adding pid file

I have a thumbnail generator that launches multiple processes and the correct way to shut it down is to send kill -HUP to the parent process. To automate I had to write a pid file from python, it was a piece of cake
def writePidFile(): pid = str(os.getpid()) f = open('', 'w') f.write(pid) f.close()