Bug 777944 (SOA-473) - DataFilerScheduler Mbean in state registered after server start-up
Summary: DataFilerScheduler Mbean in state registered after server start-up
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-473
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Deployment
Version: 4.2 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP02
Assignee: Aleksandar Kostadinov
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-24 14:50 UTC by Aleksandar Kostadinov
Modified: 2008-06-12 14:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-12 14:13:11 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777829 0 high CLOSED BindingServiceUnitTestCase failure for jboss.esb:service=DataFilerScheduler 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 777982 0 high CLOSED java.lang.NoClassDefFoundError: org/quartz/JobExecutionContext - seen on server startup - intermittent - timing issue? 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBQA-1430 0 None None None Never
Red Hat Issue Tracker SOA-473 0 None None None Never

Internal Links: 777829 777982

Description Aleksandar Kostadinov 2008-03-24 14:50:34 UTC 
Date of First Response: 2008-05-14 07:58:05
project_key: SOA

AFAICT the service should be in state started after server startup but is in state Registered. I tried to wait for few seconds after startup but it didn't help.

I used modified http://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/main/org/jboss/test/binding/BindingServiceUnitTestCase.java on http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/jboss-soa-platform-win-scripts to track it.
Comment 1 Aleksandar Kostadinov 2008-03-25 09:17:04 UTC 
Link: Added: This issue related JBQA-1430
Comment 2 Aleksandar Kostadinov 2008-04-02 10:40:58 UTC 
I see SOA-355 is the same or a similar issue.
Comment 3 Aleksandar Kostadinov 2008-04-02 10:40:58 UTC 
Link: Added: This issue related SOA-355
Comment 4 Kevin Conner 2008-05-14 11:58:05 UTC 
The reason for this is that the MBean does not take part in the normal lifecycle and, as a consequence, is never started/shutdown.

We should move this to a standard MBean and remove the servlet.
Comment 5 Kevin Conner 2008-05-14 12:05:09 UTC 
Link: Added: This issue related SOA-511
Comment 6 Kevin Conner 2008-05-14 13:51:08 UTC 
Link: Added: This issue depends JBESB-1724
Comment 7 Kevin Conner 2008-05-19 09:07:47 UTC 
Fixed in our CP branch, will be in the next merge into SOA.
Comment 8 Aleksandar Kostadinov 2008-06-12 14:13:11 UTC 
verified CR1
Note You need to log in before you can comment on or make changes to this bug.