jbpm 3.1 alpha 2 (SAR) - no I/O problem

[jeb]

I have encounterd a very strage problem which is a real showstopper for me right now (jbpm deployed and used as SAR):

Using

 <state name="sendEmail">
 <transition name="emailSent" to="waitForConfirmation"></transition>
 <transition name="emailNotSent" to="checkReason"></transition>
 <timer duedate="20 seconds" repeat="2 minutes">
 <action class="de.bla.jbpm.mail.SendEmailAction">
 <template>validateEmail</template>
 <language>de</language>
 </action>
 </timer>
 </state>

I execute an ActionHandler (executes fine). In that Handler I did some

new InitialContext().lookup("something")

which thew an exception (visible only in jbpm_timers table) which may or may not have a trivial reason. The annoying bit is that this escapes every attempt of debugging as I am for some reason are not able to create any debugging output from it, neither through the usual
org.jboss.logging.Logger, nor thru System.out, System.err or even thru a File created for this purpose.
When this execute method is invoked from elsewhere (outside the jbpm context, but inside the same jboss) output on all these methods works fine.
At first I thought the wrong classfile got deployed or exceuted from the database so I created a deliberate NPE in the ActionHandler which promptly showed up in jbpm_timers, indicating that all the logging/file etc output got executed witch no exceptions or such but - no output.

Either something very strage goes one here or I need some holidays (or both...)

Any thoughts would be appreciated!

Jens

[tom.baeyens]

did you configure the logging in jboss properly ?

regards, tom.

[jeb]

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...


Jens

[jeb]

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...

BTW:
Happy new Year to all of you!

Jens

[aguizar]

Jens,

Perhaps you left a secondary JBoss installation running somewhere ;-) Can I still get that bottle of German beer?

[jeb]

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...

Jens

[koen.aers]

The jbpm team is very eager for beer... It definitely counts as supporting jbpm development. ;-)

Cheers,
Koen