Post

3 followers Follow
0
Avatar

Spring boot support to Gemfire

We are working with Spring boot v1.3.5 / v/1.3.8 and trying to connect Gemfire v8.2.5 using Spring Data Gemfire. We are connecting to Gemfire and loading some data into cache ' load on start' while server start. We are able to connect to Gemfire and put some data using spring boot v1.3.5 however, the server is not completely starting after interacting with Gemfire. Not sure why. Any guidance on why this is happening ?  with Spring boot 1.5.3, the connection is working fine and sever is starting as expected. Due to non support Spring boot v.1.5.3 in PCF 1.6, we are reverting to Spring boot v1.3.5/ v1.3.8.  Appreciate any guidance in resolving this issue. 

Rajith Kumar N

Official comment

Avatar

Hello Rajith,

I'm not sure how you configure in terms of GemFire topology. However, why don't you take some thread dumps at the problematic server for further investigation? It seems that some threads could wait for something from GemFire side.

Akihiro Kitada

Please sign in to leave a comment.

4 comments

0
Avatar

Thanks Akihiro for your response.  Actual there is no error in local tomcat server. How do we check if any thread is hanging... 

Also, could it be version incompatibility?  are Spring boot v1.3.5 / v/1.3.8  and Gemfire v8.2.5  are compatible?

Thanks,

Rajith

Rajith Kumar N 0 votes
0
Avatar

Hello Rajith,

>Actual there is no error in local tomcat server. How do we check if any thread is hanging... 

First of all, you should take two or three thread dumps every a few seconds from the problematic Tomcat server java process with using "jstack -l <pid>" command.

If you are lucky, you may find java level dead-lock messages in the thread dumps. If you can't find java level dead-lock, next action could be detecting threads keeping same thread stuck across each thread dumps - it means the thread may be hung for a long time. Those thread could be problematic but you might find some kind of threads from Tomcat server's thread dumps - something like just waiting for HTTP requests.

Anyhow, it may be a time to file a support ticket for Pivotal for further investigation if you can take some thread dumps.

Regards.

Akihiro Kitada 0 votes
1
Avatar

Hi Akihiro,

Thanks for  your support. The issue is resolved. We tried to overwrite gemfire and spring dependencies and main pom.xml and it worked. Looks like its jar version issue.

Thanks,

Rajith

Rajith Kumar N 1 vote