All jobs in JobSandbox are stuck in SERVICE_PENDING even though they should be run.
org.ofbiz.base.start.Start implements a Singleton pattern but Commons Daemon breaks the singleton contract by instantiating it through reflection. This means that there are 2 instances of Start in a running application using jsvc
When running a heap dump of an OFBiz server running with jsvc; I noticed two instances of Start are present: #1 (which was created by DaemonLoader) and #2 (created during static init)
From the attached screenshots, you can see that the static instance variable points to #2 instead of #1.
This is a problem because #1 actually contains the correct application state, but anyone using Start.getInstance() will get #2 which has not been initialized.
At least one service suffering from this is the JobPoller which has a few lines in the polling code:
Which will never be able to exit - thus all scheduled jobs will never be run.
I noticed this in 13.07 but it could affect other versions - I have not checked them.