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

ClassPathXmlApplicationContext
context = new ClassPathXmlApplicationContext();
context.setAllowCircularReferences(false); 
context.setConfigLocation("/applicationContext.xml");
context.refresh();

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.


Comments

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
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
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("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

Jersey posting multipart data

This took me sometime to figure out mostly it was because I was only including jersey-multipart-1.6.jar but I was not including mimepull-1.3.jar.

So the intent is to upload a file using REST api and we need pass meta attributes in addition to uploading the file. Also the intent is to stream the file instead of first storing it on the local disk. Here is some sample code.
@Path("/upload-service") public class UploadService { @Context protected HttpServletResponse response; @Context protected HttpServletRequest request; @POST @Consumes(MediaType.MULTIPART_FORM_DATA) @Produces(MediaType.APPLICATION_JSON) public String uploadFile(@PathParam("fileName") final String fileName, @FormDataParam("workgroupId") String workgroupId, @FormDataParam("userId") final int userId, @FormDataParam("content") final InputStream content) throws JSONException { //.......Upload the file to S3 or netapp or any storage service } }
Now to tes…