| Author |
Message
|
| rediffuser |
 Posted: Wed Oct 06, 2004 12:44 pm Post subject: |
 |
|
Novice
Joined: 06 Oct 2004
Posts: 10
|
Are you building the app right?
I am not sure if you have to do this
Quote:
In ibm-ejb-jar-bnd.xmi I am putting
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_MyMDB" listenerInputPortName="MyListenerPort">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_MyMDB"/>
</ejbBindings>
If you build your .ear file right all you have to do is deploy and nothing else.
WHY are you doing this?
Same question again... how is this app built?
--->>
Then How does App server will call my MDB when there is message in
MyQueue of MyCOnnectionFactory??
Yes I am building it correctly..
Actually its existing ear in whcih I have added my MDB |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Oct 06, 2004 1:06 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Actually its existing ear in whcih I have added my MDB |
How did you add???
Using ant script or using WSAD how? |
|
| Back to top |
|
|
| rediffuser |
| Posted: Wed Oct 06, 2004 1:19 pm Post subject: |
|
|
Novice
Joined: 06 Oct 2004
Posts: 10
|
using ant script..
But I guess problem is with configuration and not MDB..
what do you think? |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Oct 06, 2004 1:22 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
But I guess problem is with configuration and not MDB..
|
I don't think so.
The problem is with you app or on how you are building it. On the WAS admin console all you do is create a QCF (you should use client mode because MQ is running on a different box )
Q destination and a listener port and you have already done this. |
|
| Back to top |
|
|
| rediffuser |
| Posted: Wed Oct 06, 2004 1:28 pm Post subject: |
|
|
Novice
Joined: 06 Oct 2004
Posts: 10
|
If this is so then why listner is not able to start when I try to start it.
Also why I am getting MBean related error (2033) as said earlier
As per you even if we are creating QCG and QDest...
how lisner/App server will call MDB (there should be some link between MDB and listner)
Where should we mention to app server .. call this MDB when there is mesasge in this Queue ??? Are you getting my point??
Yes I am using CLient Mode (and not Binding) |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Oct 06, 2004 1:58 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 06, 2004 2:11 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| vennela wrote: |
| I am not sure how you do this using ant though. |
Presumably you would use an ant task to run a WAS scripting command that would create the QCF and etc. for you, based on the deployment descriptor.
But I'm just guessing, myself.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Oct 06, 2004 2:21 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Jeff:
I think you can use wsadmin instead of admin console to script things like creating QCF and Qs and Listener ports.
But ant is like if I have couple of servlets, JSPs, MDB applications etc, ant can be used to create an EAR file that can be deployed on WAS. (equivalent of makefile) This is where I think his problem is. He is not able to build his EAR file right. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 06, 2004 2:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Venela,
His EAR file is fine as far as Java is concerned. What is wrong is possibly his deployment descriptor, and I'm not even too sure about that.
In any case the deployment team needs to specify the link between the qcf/queue to the "virtual" port the bean is listening on. The team will also need to check that the port is unique. If it's already used ... no luck.
All these tasks would really have little to do with the deployment descriptor but much more with the appserver setup.
You cannot create an MDB deploy it and just expect it to work.
First you need to add the WAS setup that will allow it to work. (Just like a datasource config in jdbc). And then you still need to restart the MDB service from the config console...
Enjoy  |
|
| Back to top |
|
|
| knuti |
| Posted: Wed Feb 16, 2005 4:03 am Post subject: install on server1 |
|
|
Newbie
Joined: 16 Feb 2005
Posts: 1
|
i had the same problem the other day;
i had setup my own was-server, so not to disturb others while setting up my first MDB. i had the exact same 2033 error, and ...
then, someone told me somewhere he had read that listener ports only work on server1 ... i gave it a try (with little hope), but it really worked.
give it a try - or did you find another solution in the meantime? |
|
| Back to top |
|
|
|
|
