| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| A problem in WebSphere Custom Service |
« View previous topic :: View next topic » |
| Author |
Message
|
| draculax |
 Posted: Mon May 13, 2002 12:23 am Post subject: A problem in WebSphere Custom Service |
 |
|
Newbie
Joined: 13 May 2002
Posts: 3
|
Hi all,
My system uses tools like WebSphere Advanced Edition 4.0, MQSeries for Java (ma88) and JMS. The system has to collect MQ messages from a (IBM MQSeries) queue and the messages would then be processed by EJBs which is deployed inside the WebSphere Advanced Edition 4.0. In order to achieve the design, I wrote a MessageListener program and register it under WebSphere Custom Services, so that the MessageListener program would start listening to the incoming message queue once the WebSphere starts running.
However, I encounter a problem with the above design. The WebSphere Custom Service triggers my MessageListener program before JNDI services and EJBs are in running status. Therefore, it would fail to retrieve the EJBs from the JNDI service at a moment that message arrives at the incoming queue but the JNDI service is not ready for calling.
I would like to ask any solution to force MessageListener not to start working before the JNDI service is in ready status?
I know WebSphere Enterprise Edition 4.0 provide this service as a built-in function, but I don't have enough budget to update my WebSphere to that version.
Regards,
Dennis |
|
| Back to top |
|
 |
| kolban |
| Posted: Mon May 13, 2002 6:13 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
This looks very, very much like a WebSphere app server question relating to the order and requirements of startup of the services.
As you pointed out, WebSphere 4.0 EE has an inherent MDB listener. As part of J2EE 1.3 which will be WebSphere 5.0, JMS becomes a mandatory part of the spec along with MDB. I don't think you will be able to achieve what you want by "user coding" a MDB listener. I think you must wait/use the vendor supplied mechanism for dispatching messages. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
