Just a note that I've duplicated the issue and am working on a fix for the next
release. Thanks huberth for your detailed explanations.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200028#4200028
Reply to the post :
I've got it. Try this:
public interface LifeCycle
| {
| public void create() throws Exception;
| public void start() throws Exception;
|
| public void destroy();
| public void stop();
| }
@Management(LifeCycle.class)
| @Service(objectName = myorg:service=MBeanB)
Going by what you have shown here, this looks like a bug to me. I think its
more a Microcontainer bug (as far as i know, that's what resolves the
dependencies) than a EJB3 bug.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182904#4182904
Reply to the post
Agreed. What do we do with it now? Should I raise a JIRA? Or do you?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182907#4182907
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4182907
On the other hand, come to think of it, the requirement to call the life cycle
methods at the right time is strictly EJB3.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182911#4182911
Reply to the post :
huberth wrote : On the other hand, come to think of it, the requirement to
call the life cycle methods at the right time is strictly EJB3.
I guess you are right. I think you could file a JIRA under EJBTHREE project and
point to this thread.
View the original post :
Raised https://jira.jboss.org/jira/browse/EJBTHREE-1530
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182922#4182922
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4182922
___
anonymous wrote : When MBeanA's start method is called, it calls a method on
MBeanB via its injected reference, which delegates to the singleton. The
problem is that at this point, a field in the singleton has not been
initialized, as MBeanB's start method hasn't yet been called.
|
As per
I added 'Starting' logs to my MBeans and got:
2008/10/16 09:35:43.366 INFO (main)
[com.myorg.rac.server.bwallocator.BWAllocatorAdminMBean.start:50] Starting
BWAllocatorAdminMBean
|
| 2008/10/16 09:35:45.661 ERROR (main)
[org.jboss.logging.util.LoggerStream.write:156]
I've attached a debugger to the server and placed a break-point in
BWAllocatorAdminMBean.start. Here's the stack trace in the main thread:
[EMAIL PROTECTED], priority=5, in group 'jboss', status: 'RUNNING'
| at
huberth wrote :
|
| I've got the source for AS 5.0CR2, and EJB3 1.0.0-Beta4.
If you have 5.0CR2 source then you will find most of the required java files in
there. The source for the other projects can be found under 5.0CR2
source/thirdparty/jboss/xxx folder.
huberth wrote :
| I
The thirdparty directory seems to cover a lot of (only?) non-jboss stuff. For
example, AbstractController.java is not under the 5.0 source directory
anywhere, and it seems to be an important player here. I found a copy of it
under viewvc, but it's obviously a different version as the line
Look closely at the chain of calls between the lower installMBean and the
resolveContexts calls. Further down inside the install call from installMBean
the code eventually transitions the state of StatisticsMBean to created, then
started, then installed, constantly calling
Here are the various classes involved, pruned down to the relevant bits. Let
me know if I've done too much pruning.
// MBeanB in the initial post
| @Management(StatisticsAdmin.class)
| @Service(objectName = com.alcatel.tpapps.common:service=StatisticsAdmin)
| @RemoteBinding(jndiBinding =
Can you please post the code of those MBeans and the exception stacktrace? That
will help in understanding the problem better.
While posting the logs or xml content or code, remember to wrap it in a code
block using the Code button in the message editor window and please hit the
Preview button
I should probably add that to get this far, I had to download, build and apply
the 1.0.0-Beta4 release of the EJB3 module.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4182236#4182236
Reply to the post :
16 matches
Mail list logo
