did you configure the logging in jboss properly ?
I would think I configured the logging correctly as I see the output when I call the execute() from within my ear on the same JBoss - apart from that misconfigured logging should not be able to break output to System.out, System.err and even a File - but then what could do that?
It's almost as if all I/O gets intercepted somewhere.
By the way I see jbpm loggin in the logfiles and on the console as well, but everything fine, no errors reported....
I have seen strange things before, but this VERY odd. I'll send out a bottle of beer to the first one who solves this mystery...
Ahrgh! What a stupid reason for this problem:
A few days ago I made for some tests a clone of my jboss development installation to another server and left it running there - so, this one was picking up the jbpm tasks and the debug/file etc output was on this machine - and of course the jndi lookup failed because the looked up resource was not reachable from this machine...
Happy new Year to all of you!
Perhaps you left a secondary JBoss installation running somewhere ;-) Can I still get that bottle of German beer?
Alex, I will print out your sentence "Perhaps you left a secondary Jboss installation running somewere" and pin in to the edge of my Screen - as a troubleshooting aid for furture mental blackouts of myself.
I can't send you a bottle of Beer for solving this problems, but I would send you one regardless if that counts as supporting jbpm development...
The jbpm team is very eager for beer... It definitely counts as supporting jbpm development. ;-)