Ok, I posted my issue on the other forum
(http://www.jboss.com/index.html?module=bbop=viewtopict=108476). It has some
new information that I didn't have yet when I posted to this forum, so you
might have a look and see if you happen to recognize the issue right off the
bat. I'm sure all that
My problem initially was that my MDB was not binding, as evidenced by their
absence in the jmx-console. I deduced that it was because of the errors I was
seeing in the server log.
Well, after re-installing today, I can now see my MDB EJB in the jmx-console.
I thought it was still breaking,
JBM is a raw JMS provider, it doesnoe handle deployment of MDBs.
Anything to do with MDB deployment is handled by the MDB container which is
managed as a separate project by different people.
If you're having problems with MDB deployment, e..g problems getting the
descriptors right etc, then
| jboss.mq:service=DestinationManager
|
Tells me you are trying to deploy a jboss mq destination inside jboss
messaging. This won't work.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044451#4044451
Reply to the post :
anonymous wrote : jboss.mq:service=DestinationManager
| Tells me you are trying to deploy a jboss mq destination inside jboss
messaging. This won't work.
It sure would appear that way. Given that I followed the instructions in the
User's Guide and used the MDB verbatim, why isn't this
As I say, you probably didn't perform the install correctly, or have
subsequently deployed a service without incorrect jbossmq configuration.
Do a text search in all *.xml files in your jboss installation for jbossmq to
see where the offender is.
View the original post :
Ok, I started again from scratch. This time I did the web install of JEMS
1.2.0.GA. I selected the all option rather than the default installation.
The next window in the installation shows all the components, with checkboxes
next to each one to toggle their installation. Notably,
You must have a service referencing jboss.mq:service=DestinationManager
somewhere in your config otherwise you won't get that exception.
Without looking at your install first hand it's hard for me to diagnose what
has happened.
And yes, it does work out of the box, we test it before each
Please post your ejb.jar.xml and jboss.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044506#4044506
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4044506
___
jboss-user
ejb-jar.xml is as above. jboss.xml is as in the User's Guide, Ch 7.4, p. 25.
DestinationManager appears in many files under [JBOSS_HOME], in these dir's:
[JBOSS_HOME]\docs\examples\jms*
[JBOSS_HOME]\server\default\conf
[JBOSS_HOME]\server\default\deploy
[JBOSS_HOME]\server\default\deploy\jms
After you installed, did you successfully run the examples?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044521#4044521
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4044521
___
I completed everything in Ch. 5, inlcuding the Queue Example (Ch. 5.3
Installation Validation), which worked like a charm. I haven't tried
anything else in Ch. 7 other than 7.4, which is the MDB EJB2.1 example that
refuses to work.
View the original post :
All the examples should run after a successful install.
If they do not then something went wrong with the install.
The most common reason for this is you didn't run the release-admin.xml script
over a fresh install of JBoss AS.
Without seeing your install is hard to see what has happened.
Well, I've ant'd release-admin.xml over a fresh install twice, and I ended up
with the same issue both times. So we can most likely rule that out.
Is there something that I could post that would help to figure this out? Right
now I'm only slightly concerned with what went wrong; but I'm more
I just did a complete run from scratch.. and everything ran fine.
I - downloaded jboss-4.0.4.GA and jboss-4.0.5.GA.
II - unziped jboss-4.0.4.GA
III - set JBOSS_HOME=/myDir/jboss-4.0.4.GA
IV - downlaoded jboss-messaging-1.2.0.SP1 and unziped it
V - cd /myDir/jboss-messaging-1.2.0.SP1/util
VI
Make sure you are using 1.2.1.SP1
http://labs.jboss.com/jbossmessaging/downloads
I remember one bug when running the MDB example alone, fixed on SP1:
http://jira.jboss.com/jira/browse/JBMESSAGING-254
View the original post :
anonymous wrote : Make sure you are using 1.2.1.SP1
|
I don't see 1.2.1.SP1, only 1.2.0.SP1, which I already have
(jboss-messaging-1.2.0.SP1.zip).
anonymous wrote :
| I - downloaded jboss-4.0.4.GA and jboss-4.0.5.GA.
|
| II - unziped jboss-4.0.4.GA
|
| III - set
anonymous wrote : I don't see 1.2.1.SP1, only 1.2.0.SP1, which I already have
(jboss-messaging-1.2.0.SP1.zip).
I meant 1.2.0.SP1. Typo!
I tried both 4.0.4.GA and 4.0.5.GA.. and got same results!
anonymous wrote : Such as? Am I supposed to say a few Hail Mary's? ;)
|
| But seriously,
After running release-admin, the only reference I see to mq is at:
./messaging/deploy/cache-invalidation-service.xml
... Which is commented out.
| !--
| mbean code=org.jboss.mq.server.jmx.Topic
|
name=jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge
|
You shouldn't make any reference to MQ... look at
messaging/deploy/jboss-messaging.sar/destinations-service.xml for information
about how to create topics.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044544#4044544
Reply to the post :
In conf\jboss-service.xml there's
mbean code=org.jboss.management.j2ee.LocalJBossServerDomain
| name=jboss.management.local:j2eeType=J2EEDomain,name=Manager
| ...
| attribute
name=JMSServicejboss.mq:service=DestinationManager/attribute
| ...
In conf\login-config.xml there's!--
I don't understand what problem those are causing...
You could pretty much ignore them.
The first one is a JSR-77 (management) reference
second one.. is login-config.. which is not being used.
The third one are just invokers configurations... not used by messaging.
You are confusing
22 matches
Mail list logo
