| Author |
Message
|
| pigicam |
 Posted: Tue Feb 28, 2006 4:09 am Post subject: Using services in not sherable mode |
 |
|
Newbie
Joined: 28 Feb 2006
Posts: 3
Location: Rome, Italy
|
I configured some services in WAS 6.0.
All worked well untill the queue was set:
DEFSOPT (not exlusive)
SHARED.
Unfortunately in the production environment I must keep the queue:
DEFSOPT (exlusive)
NOT SHARED.
But now the onMessage does not work.
From client side we have no problems, but from the server side (MQ log error) i have this message:
02/27/2006 02:36:12 PM - Process(15816.49) User(mqm) Program(amqrmppa)
AMQ9208: Error on receive from host 10 (10.158.31.161).
EXPLANATION:
An error occurred receiving data from 10 (10.158.31.161) over TCP/IP. This may
be due to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 104 (X'68'). Record these
values and tell the systems administrator.
Does anybody know what should I do?
Tnx in advance for your replay.
Bye
Pierluigi |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Feb 28, 2006 7:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Remember that an MDB has usually 2 processes on the queue. One doing browse to see if there is any message and one doing the get.
Now you have a problem.... You cannot define the default open as exclusive...
Was this an attempt to limit the number of MDB instances to 1 despite the WAS config ?
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pigicam |
| Posted: Wed Mar 01, 2006 1:45 am Post subject: |
|
|
Newbie
Joined: 28 Feb 2006
Posts: 3
Location: Rome, Italy
|
Mamma mia!!!! Maybe I'm in trouble.
Using the mq trigger to get message from the queue coud it be a walkaround ?
If this is a possible way out, do you happen to know how to do this in java?
Tnx a lot
Pierluigi |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 01, 2006 3:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
It is quite easy but maybe not the prefered / needed way.
Can you describe in more detail what you want to do?
Unless there is a good business reason to force the queue into exclusive mode, you really should keep it shared as well as the defopen...
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pigicam |
| Posted: Wed Mar 01, 2006 5:43 am Post subject: |
|
|
Newbie
Joined: 28 Feb 2006
Posts: 3
Location: Rome, Italy
|
At present for business rules I must garantee that only one application at time is connected to the queue and that only one message is being processed at time as well.
Can I achieve this goal in any other way?
Such as setting "Maximum sessions" at 1 or/and some other settings?
And what about using "Service integration"? Does it make any difference from jms?
I have little experience on those.
Thanks you a lot for reply.
Pierluigi |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 01, 2006 11:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Looking at JMS ---
To guarantee only one application -- Do only give out access rights to said application.
To guarantee only one message being processed at a time... that is more or less a given with the std MDB setting. Now the question is really a little bit different: does one message at a time mean FIFO serial processing or does it just mean one message per LUW (parallel processing allowed)?
You can ensure both by setting the right config on the MDB.
1 msg per LUW is the default on the MDB
Serial processing is ensured by setting the maxinstances (sessions) to 1 on the MDB.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rpera |
| Posted: Fri Mar 03, 2006 4:42 am Post subject: |
|
|
Newbie
Joined: 03 Mar 2006
Posts: 1
|
Hi everybody
sorry to butt in, but I found this thread very intersting, as I have the same problem, God knows why users are so concerned in setting the parameter into "shared", anyway, I'm not sure I thoroughly understand when Mr Spider Man says "Do only give out access rights to said application", is it something that one can set on the MQ side or WAS side ?
thanks for your reply
Roberto |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 03, 2006 4:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Roberto
Give MQ rights at group level using setmqaut to said queue. Have the WAS User passed for authentication be in the right group.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
