The ramblings of a yorkshire tyke » JVM

Heroku add Java support but dumps containers!

spgennard — Sun, 28 Aug 2011 22:35:18 +0000

Recently I have reviewing various cloud solutions and what impact this has on the way you create/architect applications and I have come to the conclusion they are often way too complicated for most existing applications to be effectively hosted in …

Scripting Languages and COBOL

spgennard — Tue, 19 Jan 2010 10:39:04 +0000

The use of scripting languages with other languages has increased over the last couple of years, from a simple case of interoperability, reuse of scripting code to allowing your code to customised via the user of external scripts. All of …

Using sun.jvmstat.monitor to see active Java processes

spgennard — Sat, 05 Dec 2009 10:56:38 +0000

Monitor’ing Java processes can be achieved using the jvmstat monitor classes provided in the JVM. The documentation is a bit sketchy but with a little experimenting it can be done. Below is a little example that shows you how to …

Java process id via java.lang.management

spgennard — Fri, 04 Dec 2009 23:53:13 +0000

While working on a project recently I need to find out the current process of the active running Java process (for tracing/auditing), however I never found a 100% perfect solution but did come across an acceptable solution to use the …

Type Safety and COBOL

spgennard — Mon, 23 Nov 2009 23:27:34 +0000

Having read a recent bog about COBOL and type-safety, I though I would jot down some comments. ANS85 COBOL is naturally is type-unsafe due as every data item being part of one memory region (or storage area), because of this …

Fiddling with the JVM

spgennard — Mon, 09 Nov 2009 20:10:49 +0000

Java is a very safe language if used in a normal way, however just like the CLR it can be used in an unsafe manor. The main reason for using Java in a unsafe manor is performance, some unsafe operations …

Object COBOL/Java default exception handler

spgennard — Tue, 03 Nov 2009 22:16:54 +0000

While working on some support recently for our compiler (Micro Focus COBOL compiler that is), I became annoyed with the lack of a reasonable error messages/stack trace output from our Java/COBOL Object support. I have no idea why our default …