Monthly Archives: January 2010

Timeout is not equal timeout

25. January 2010 by Eugen Melnichuk

Last week I had to change a webservice-client in such a way as to be able to configure a timeout. The webservice is implemented with spring-webservices and uses the WebServiceTemplate class. (read more…)

category: Java | no comment
This post is written on 25. January 2010 by Eugen Melnichuk.

A Retrospective on 2009

13. January 2010 by Fabian Lange

2009 has passed a few days by now, so I think it would be appropriate to look back on what has happened last year. Just recently I said to somebody: “Well I am with codecentric for only a year and a half so far”, but in fact we did quite a lot in 2009. So there is a lot to look back. Like the 85 blogposts published. And there is a lot to look forward to. I am very proud of our achievements and our spirit.
(read more…)

category: General | no comment
This post is written on 13. January 2010 by Fabian Lange.

The Java Memory Architecture (1. Act)

6. January 2010 by Mirko Novakovic

One of the biggest strength of the Java Platform is the implementation of an automatic memory management in the Java Virtual Maschine. Everybody who has programmed with languages like C/C++ knows about the problems of managing memory allocation and deallocation in the code. With Java problems like deallocating memory too early (corrupted pointer) or too late (memory leak) cannot occur by specification. The question is: Why am I writing these blog entries?

The problem is that even with an implicit memory management integrated, Java cannot prevent application of being corrupt in sense of memory management, even it is not allowed to explicitly allocate memory in Java. The result of such wrongly programmed code normally is an exception of type: java.lang.OutOfMemoryError.

(read more…)

category: Java, Performance | 9 Comments so far
This post is written on 6. January 2010 by Mirko Novakovic.

Java OutOfMemoryError – A tragedy in seven acts

5. January 2010 by Mirko Novakovic

One day every professional Java programmer will suffer from this exception thrown by his Java application: java.lang.OutOfMemoryError.

With a little luck this error will occur during development of the application – if not and it happens in a production environment, you will quickly get a lot of unintentional attention by your management, as a Java OutOfMemoryError normally means that you had an application crash! The reasons for these memory problems in the Java Virtual Maschine are versatile and in many cases not easys to analyze. In our troubleshooting services we see workarounds for these errors every day: Servers are preventevly restarted every night as the heap gets closer and closer to its limits or – even worth – the application regulary crashes with an java.lang.OutOfMemoryError indicating that the hunger of the JVM for more memory was bigger than the available heap.

(read more…)

category: Java, Performance | 3 Comments so far
This post is written on 5. January 2010 by Mirko Novakovic.