<< March 2010 | Home | May 2010 >>

LD 17 - Isle of the Firepiss

Ok,…just a quick post. It was again a desaster. The theme was islands and I decided to create a RTS. After about 15h I realized that it might be too complex (also I had quite a lot done on the model/logic-side) and switched to a so easy third person shooter project…!? :D Totally irrational…well! I’m not satisfied with the result, but it is better than nothing. Have a look here:


PS: The screenshot looks much better than the game finally happens to be :D

Tags :

‘Ludum Dare’ is ahead

A couple of days left until the next ludum dare gamedev-competition will be started. As always I’m so optimistic to finish a game but even I think to avoid my common mistakes I have to face the fact that the chance is quite high to suck again,… We’ll see.

At the moment I’m quite lost about the decission how to go on with my work. Stay with jME2, swtich to jME3 with its android-support, switch to Panda3d or even UNITY3D. Well, I stay for a while with jME2 and until then I will get crazy about other sollutions…

First let’s rock LD! This time….first time… :D

two simple jBoss - Problems

Usually I’m not posting this kind of topics here but this two problems kept me on fire at work for some hours.

Scenario: jBoss 4.2.2GA + MessageDrivenBeans

Problem 1:

Out of nowhere came the problem that when starting jBoss the MDB couldn’t start with the error:

jboss.mq:service=DestinationManager is not registered.

This might have multiple reasons but in my case the problem was that when more jBoss exists in the same network they connect to a cluster (at least in our configuration). That means that the destination-manager is only created on the first computer of the cluster. To prevent this you can specify a partition when starting jBoss and you have only a one computer cluster (as long noone uses the same partition)

So here is the magic line:

run.bat -c all -g yourPartitionName

The -g parameter is for specifing the partition to use. -c specifies the jBoss-configuration

Problem 2:

Once the MDB is started and registered to a queue it starts to process the queue if there are still messages in it. (Maybe jBoss crashed for some reason before finishing the queue). That can be a problem if the behaviour of the message depends on an EJB that is not loaded yet. For that you can use the @Depends annotation in your MDB.



or for multiple dependencies (didn’t test that yet):


(found this here)

After adding this the service is only created if the specified MBean is already registered. You can find the corresponding name for you MBean on startup (or server.log). Just keep looking for “[org.jboss.ejb3.JmxKernelAbstraction] installing MBean: ……”

Well,…seems like two easy issues not worth mentioning. But nevertheless you have to know it :D Hope I could help someone with that.

PS: Sry for the formatting terror!

Tags : ,
<< March 2010 | Home | May 2010 >>