I think Scott misunderstood the nature of this problem. This is not an "I can't
look up my MBean" user error, this is a bug in web-console. Most of the
web-console statistics displayed for an EJB is not available because of the bug.
It is easy to replicate even with the "JBoss AS Getting Started
Most likely you are running into this change in behavior for the default local
jndi names which affects the mbean name.
http://wiki.jboss.org/wiki/Wiki.jsp?page=WhyDoesTheLocalNameContainARandomNumber
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994762#399
What is to be read at the very first page: Ever feel like talking to yourself
?? Yep, I did using this forum.
Bye
Marcos
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994570#3994570
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
@chalad,
seems as we are at least two => seems to be a bug.
Removing the subcontext isn't an option in my project. As mentioned, Versions
4.0.4 and 4.0.5 have this bug.
Suprisingly no one else seems to use this feature which is essential to my
customer in production. Buying 24x7 support for ap
Yeap, I seem to be having the same problem as well.
In order to get it working I removed the prefix from the JNDI name, and left
the EJB name alone.
the thing is that this used to work perfectly well with previous veriosn of
JBoss (< 4.0.4)
View the original post :
http://www.jboss.com/index.h
Hi PeterJ,
the application runs, client accesses the bean! The Bean is deployed but under
jndi-name ejb/CustomerProcess. For me it seems as if Jboss is looking up for
CustomerProcess only. As mentioned, everything was working perfect under
Jboss4.0.3SP1. It was simply re-deployment under Jboss4
Have you checked the jmx-console to see what mbeans are declared in the
jboss.j2ee namespace? It would appear that the EJB named CustomerProcess was
not deployed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989736#3989736
Reply to the post :
http://www.
Hi !
Maybe I forgot to mention, that this is a critical issue, even for the customer
who is about migrating an existing application from another - commercial -
app.-server. Operating is the issue, not development.
No one else around here with the same problem, no one of jboss who could answer