When I access http://localhost:8080/admin-console/secure/resourceInstanceMetrics.seam?path=-2&conversationId=8&conversationPropagation=end, I do not see the JBoss ESB node. I don't see much of anything.
Thank you for clarifying that the Community Edition has not been upgraded.
I had difficulty logging into JIRA yesterday, but I will try again today; however, I did do much research via Google which took me to the JIRA postings you refer to and also StackOverflow posting Are you saying that even though the generated log message has the [ERROR] status, it really is just a warning? I still need to view more at the console than I am able to see now.
I am not sure how to make this jpg more readable for you; basically this is from the Summary tab; there is some information on the Metrics tab and nothing on the configuration, control, or content tabs.
What do you suggest I do at this time? I do believe I followed the directions correctly.
Sorry about that. I completely missed the ERROR log entry below the WARN that I referenced. That appears to be the same issue that Nikos ran into earlier in the thread and addressed by steps 5 and 6 in Morten's instructions:
5. In deploy/profileservice-secured.jar/META-INF/ejb-jar.xml: change <res-ref-name>profileService</res-ref-name> to <res-ref-name>java:profileService</res-ref-name> (3 occurences)
6. In deploy/profileservice-jboss-beans.xml: Change <property name="jndiName">ProfileService</property> to <property name="jndiName">java:ProfileService</property> (1 occurence)
I would say follow Morten's steps again. Maybe you made a mistep the first time through? I can't reproduce your issue locally, so I'm afraid that's the best advice I can give. If there are any other exceptions/errors than the one you listed in your post, please include those.
I did have one message tagged as an [ERROR] as you can see above; is that one not an error? The display is not working yet so I assume that ERROR is valid. I logged into jira, but I do not see this issue there. I did see information regarding it in StackFlow.
Right, I somehow missed that ERROR the first time I read your post. I mentioned that and the possible source in my most recent post above.
One thing to note on replacing values in steps 5 and 6. Do not do a global search replace on 'profileService' as this will replace a number of other configuration elements and certainly could cause problems. Make sure that you only replace the occurrences noted in Morten's post. As I said, it works for me, so I'm afraid that's the best advice I can give.
thank you very much for the replies; I will recheck that I did make the corrections in Morten's post properly. Perhaps I did correct whre I should not have or vice versa. I will let you know when I do get it working.
I do believe it is working correctly now; thank you for confirming the instructions were up to date and informing me the community edition had not been updated. How often are the community editions updated?
It depends on the project. For example, JBoss ESB has had two minor releases (4.8 and 4.9) since this thread was originally started. The issue you hit needs to be fixed in the AS, so it would take another JBoss AS 5.x release to fix it. The JBoss AS forums are probably your best bet for finding out if there will be another release of JBoss AS 5.x.
Thank you to Morten for the excellent instructions.
confirmed that Morten's steps are also required for JBoss 5.1.0.GA + ESB 4.9
thanks for the fix guys!
I think that the plugin file that you want is:
Sorry for use this old post , but I'm hitting the same problem with jboss 5.1.0.GA & ESB 4.9 , Any idea of where I can get file : the jopr-embedded-jbas5-1.3.2.GA.war , because the url in Morten's post seems not working.
Thanks in Advance.
just an note to add regarding Morten's step. He is putting in 5th step:
which seems to work ok.
I would like to note that in original file profileservice-jboss-beans.xml there is a comment:
<!-- To remove the unsecure proxy binding, change the jndiName property to a local binding like java:ProfileService and update the deploy/profileservice-secured.jar ejb-jar.xml profileService resource-ref/mapped-name.
so perhaps the <mapped-name>ProfileService</mapped-name> should be changed instead of
I've tried to change either of them. In both cases the Admin console shows ESB tree view as expected, so it would be great if someone give us some clarification which option is adequate.