Message Queue Blocking / MSGMNI Setting
Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.
Malcolm,
Your information and explanations behind these error messages are very useful.
It allow me to further understand Tuxedo internal processing and at the same time
give me a chance to start analysing these fields.
I am reluctant to ask further questions at the mean time. I will use your suggestions
as a starting point.
I will certainly keep you posted of the outcome when I have made the changes in
my UBB config and machine parameters.
Many thanks with your help/explanations Malcolm. It helps alot!
Cheers.
David.
"Malcolm Freeman" <[email protected]> wrote:
>
Hi David,
The MSGTQL reference you give (Solution S-00488) refers to the BEA MessageQ
product
and is not relevant to Tuxedo.
The error messages indicate that the queue buildup is probably due to
a restartable
server failing. What happens is this:
When a restartable server fails its IPC queue remains in place and continues
to
receive messages (which will be processed when the server restarts).
Depending
on the time taken to restart, the queue could become full and unable
to receive
any more messages, and this is probably why you got the message CMDTUX_CAT:1380
indicating that the BRIDGE process was unable to put a message on the
server's
queue.
A server is only restarted when the BBL does a SANITYSCAN check. If,
for example,
your SANITYSCAN interval is 300 seconds and your server fails immediately
after
the previous scan, then there will be a delay of almost 5 minutes before
the failure
is detected and the server restarted - plenty of time for the queue to
fill up.
There are a few things you could do:
The key thing would be to find out why the server is failing, and fix
the problem.
If this is not possible immediately, consider some of the other ideas
below.
Have several servers form an MSSQ to service this queue; then if one
fails the
others will continue processing the messages while the failed server
restarts
(this assumes, of course, that your application does not require the
messages
to be processed in strict order through the server).
Reduce the SANITYSCAN interval (but don't make it too small). This would
reduce
the average time taken to restart the server.
Increase the size of the IPC queue (MSGMNB) so that it can hold more
messages.
I'm not sure why you got a LIBTUX_CAT:1485 message, but this could be
due to a
BRIDGE failure as a result of the congestion.
The NETLOAD parameter would reduce the number of messages going to the
remote
machine, but only if the local machine offers the same service. If the
remote
machine is the only source of the service then NETLOAD will have no effect.
I
recommend you do a search of this newsgroup for postings on "load balancing"
there's some good stuff which will explain how load balancing works.
Depending how things go, it might not be a bad idea to open a case with
BEA Support
and ask for guidance (remember to submit your ubbconfig (or preferably
do a tmunloadcf)
together with the complete ULOGs from both the master and the slave machine).
Hope this helps some.
Regards,
Malcolm.
"Dave" <[email protected]> wrote:
Hi Malcolm,
Thank you for your reply. Interesting point you have made about theMSGTQL
value.
Based on your suggestion I went hunting around the BEA site and found
the following
snipplet:
"- The MSGTQL parameter must be set to a value greater than or
equal to the MSGMNI setting."
(http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_solution&answerpage=solution&page=msq/S-00488.htm)
If the above point is valid, then my MSGTQL is definitely way too low.
IF this
be the case, would you know of a method to work out what my MSGTQL bytes
value
should be?
Additionally, I have looked at other parameters which I could tune,and
would
adding a NETLOAD parameter in the *MACHINES section will reduce remote
servers
call? Which potentially, maybe reduce message queue blocking?
FYI:
The error messages I am seeing in my ULOG file are:
"LIBTUX_CAT: 1477 : ERROR .SysServerDied
LIBTUX_CAT: 1476 : ERROR: .SysServerRestarting"
Which then leads to message queue blocking
"CMDTUX_CAT: 1380 : ERROR: Message queue blocking prevented delivery,
Qaddr=..."
and potentially "LIBTUX_CAT: 1485 .SysNetworkDropped."
Many Thanks. Hope to hear from you (Malcolm) or other parties out there
that can
assists.
Thanks.
David
Similar Messages
-
Message Queue Blocking/MSGMNI Confirmations
Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated.Hi All,
Firstly, many thanks to all that can assists. I am currently getting Message Queue
Blocking messages in my ULOG files in my Tuxedo Application. (Tux ver 7.1 in Unix).
I am not sure what is causing this, but started to look into the Tux Config (UBB.MP)
and System message queue setting. Detailed as follows:
1)
Listed below is the system message queue setting:
set msgsys:msginfo_msgmni=2000
set msgsys:msginfo_msgmax=128000
set msgsys:msginfo_msgmnb=100000
set msgsys:msginfo_msgssz=256
set msgsys:msginfo_msgseg=25088
set msgsys:msginfo_msgtql=1550
set msgsys:msginfo_msgmap=1000
According to the BEA site, the MSGMNI is determined by this formula:
MSGMNI = MAXACCESSERS + 7 + (no. of servers with REPLYQ) + (no. MSSQ sets) - (no.
of servers with MSSQ sets)
The following is my current Tux. Config (UBB.MP) is set as :
- MAXACCESSERS = 2300
- Each servers (4 types in total) has its own REPLYQ and RQADDR.
- The same type of servers are set the same across 4 application servers.
Hence, my MSGMNI should be a minimum 2339 (ie. MSGMNI = 2300 + 16 + 16 - 0 = 2339).
But my current MSGMNI is 2000.
Would this contribute to my Message Queue Blocking?
Is my understanding correct and is this something I should change to avoid Message
Queue Blocking? Any helps and advice is much appreciated. -
CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery
Today, I changed a Tuxedo application (server) to the product systems(One master and two slaves). Only a small changes in code. But after a period of running, there are many errors in ULOG:
CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery, Qaddr = 583902
And then, the server is died. After restart the server, this will happen again later.
I don't know why this happens? Thx.Hi Bill,
This is happening because the BRIDGE process received a message from the network and was unable to place the message on the intended IPC queue. This could be because the server handling that message is backed up, or the system IPC resource settings are too low. Please check the recommended actions in:
http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/messages/cdtux/cdtux013.html
Regards,
Todd Little
Oracle Tuxedo Chief Architect -
.SysMachineMsgq: message queue blocking
Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq: hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service is causing the blocking?
Thank you,
IvanIvan,
You can look in the userlog for a "LIBTUX_CAT:672 ERROR: Message operation
failed because the message queue or the system is full" message. That will
tell you the process in which the msgsnd() failed, although it will not tell
you the specific queue that was full. If the queue full condition is not
something transient, you can use the "ipcs -q -a" command to examine the
number of bytes currently on each queue on the machine.
If you need to automate the process of searching the ULOG, the T_ULOG class
in TM_MIB(5) can be used.
The event message for the SysMachineMsgq event deliberatly contains very few
details, since the process where msgsnd() failed uses a message to inform
the event server of the failure and if a message queue is full, then there
might be a problem with sending a large message to the TMSYSEVT server.
(There is a check to prevent looping if the message send to TMSYSEVT fails.)
Ed
<Ivan Novick> wrote in message news:[email protected]..
Hi,
I am getting the following error message:
064222.hostname!TMSYSEVT.14351.3071440608.0: WARN: .SysMachineMsgq:
hostname message queue blocking
Is there anyway to pinpoint exactly which application and or which service
is causing the blocking?
Thank you,
Ivan -
LIBTUX_CAT:681Failure ro create message queue
Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024And just to add to $0.02,
Oracle doesn't use message queues, only shared memory and semaphores. Here is the
/etc/system I use on my Solaris 7 system for development work:
* IPC Tunables - Shared memory
* max shared memory segment size (SHMMAX)
set shmsys:shminfo_shmmax=4294967295
* min shared memory segment size (SHMMIN)
set shmsys:shminfo_shmmin=1
* max attached shm segments per process (SHMSEG)
set shmsys:shminfo_shmseg=100
* shared memory identifiers (SHMMNI)
set shmsys:shminfo_shmmni=100
* IPC Tunables - Semaphores
* semaphores in system (SEMMNS)
set semsys:seminfo_semmns=4096
* semaphore identifiers (SEMMNI)
set semsys:seminfo_semmni=128
* entries in semaphore map (SEMMAP)
set semsys:seminfo_semmap=4096
* undo structures in system (SEMMNU)
set semsys:seminfo_semmnu=4096
* max semaphores per id (SEMMSL)
set semsys:seminfo_semmsl=2048
* max operations per semop call (SEMOPM)
set semsys:seminfo_semopm=256
* max undo entries per process (SEMUME)
set semsys:seminfo_semume=1024
* semaphore maximum value (SEMVMX)
set semsys:seminfo_semvmx=32767
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
* set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
* set msgsys:msginfo_msgmax=262144
* max bytes on queue (MSGMNB)
* set msgsys:msginfo_msgmnb=262144
* message queue identifiers (MSGMNI)
* set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
* set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
* set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
* set msgsys:msginfo_msgseg=2048
* Workstation Settings
* IPC Tunables - Messages - For Tuxedo
* entries in msg map (MSGMAP)
set msgsys:msginfo_msgmap=2048
* max message size (MSGMAX)
set msgsys:msginfo_msgmax=65535
* max bytes on queue (MSGMNB)
set msgsys:msginfo_msgmnb=512000
* message queue identifiers (MSGMNI)
set msgsys:msginfo_msgmni=1024
* message segment size (MSGSSZ)
set msgsys:msginfo_msgssz=1024
* system message headers (MSGTQL)
set msgsys:msginfo_msgtql=2048
* message segments (MSGSEG)
set msgsys:msginfo_msgseg=2048
Mervin Calverley wrote:
Fabrice:
The error implies that msgmni is set too low. msgmni is the total number of message
queues allowed in the system. Getting an error here implies that oracle or some
other process is consuming them.
For Tuxedo Classes we use the listed values as minimum for the kernel parameters
to perform the labs. In these classes the machine is only running Tuxedo. This
means the values are probably lower than those required by a production system or
one hosting Oracle as well as Tuxedo.
Message Queue Parameters:
MSGMAP 800
MSGMAX 32769
MSGMNB 42000
MSGMNI 400
MSGSSZ 64
MSGTQL 400
MSGSEG 2048
Semaphore Parameters:
SEMMAP 800
SEMMNI 800
SEMMNS 800
SEMMNU 800
SEMMSL 800
SEMOPM 64
SEMUME 64
SEMVMX 32769
SEMAEM 16384
Shared Memory Parameters:
SHMMAX 2097152
SHMMIN 1
SHMMNI 100
SHMSEG 64
SHMALL 2048
**Note: Some UNIX kernels do not support all of the above parameters or have additional
parameters not listed.
Hope this helps!
mervin
"Fabrice Poulard" <[email protected]> wrote:
Hi,
We get this error when we start more than 3 Appserver.
(Solaris 8 + Oracle)
Any information would be appreciated. Thanks.
It's my /etc/system file...
set maxusers=80
set shmsys:shminfo_shmmax=8589934590
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=15
set semsys:seminfo_semume=500
set semsys:seminfo_semmns=500
set semsys:seminfo_semmnu=500
set semsys:seminfo_semmsl=70
set semsys:seminfo_semmap=500
set semsys:seminfo_semmni=32
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set semsys:seminfo_msgmap=780
set semsys:seminfo_msgmax=4096
set semsys:seminfo_msgmnb=8192
set semsys:seminfo_msgmni=500
set semsys:seminfo_msgssz=8
set semsys:seminfo_msgtql=40
set semsys:seminfo_msgseg=1024
Brian Douglass
Transaction Processing Solutions, Inc.
8555 W. Sahara
Suite 112
Las Vegas, NV 89117
Voice: 702-254-5485
Fax: 702-254-9449
e-mail: [email protected] -
Get/set message Queue ID in PI 7.1 Adapter module
Hello,
I have a special requirment to get and set message Queue ID in PI 7.1 adapter module.
I tried to use the method setConversationID for the Message Class, but this doest seem to available any more.
Any pointers to which class and method can be used.
Thanks in advance
Regards,
AbhishekHi, try [setSequenceId|http://help.sap.com/javadocs/pi/pi711sp03/com/sap/engine/interfaces/messaging/api/Message.html#setSequenceId(java.lang.String)]. Maybe you have to use setDeliverySemantics before in order to set EOIO.
regards, Martin -
Queue Blocking and File picked Partially Problem ?
Hi All,
The File which is placed in FTP server having more 50000 to 65000 rows .
when XI picks the File the Partial Data is processed.
In SXMB_MONI if we check the message we are able to see some rows not full Data which was in file.
it's also blocking the Large message QUEUE -XBTM0000
while processing.
In QUEUE monitoring(SMQ2) the STATUS message is "Connnection CLosed No DATA" .
what could the reason here and also we are not able see any error related information(If it is having error) in SXMB_MONI.
it's urgent because of Production issue.
Regards
NandanHi Indira,
In our scenario the Modification Check is set 5000 .
To resolve this problem what should i must do ?
Whether to decrease the present value or increase the present set value.
what will be the timing parameter Actually in Additional Parameter Tab?( SECONDS or MILLI SECONDS) -
App Server Install fails - due to incompatible Message Queue
I had JES 2005 q1 installed in one of the test machines...now I am trying to set up JES 2005q4 on that. I cud install a Web Server on that ut when I tried to set up the App Server it throws up a msg stating that there is an incompatible version of Message Queue installed and hence installation cannot go ahead.
I am not able to find any instance of Message Queu setup....how do I detect and uninstall old versions of Message Queue??
thx
anandI assume you are talking about appserver install on Solaris. Message Queue on Solaris is a package based install. The easiest way to uninstall the old version of MQ is: "pkginfo -i | grep Message" ---> "pkgrm all MQ packages".
-
Message Queue 4.4 doesn't know "jms.properties" ?
Sun JMS Tutorial illustrates using a properties file to supply context properties. You define a System property "jms.properties" to point to the location of the properties file:
java -Djms.properties=%J2EE_HOME%\config\jms_client.propertiesInside of said file is the properties in question (these are a surmise; the contents are nowhere documented).
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:///C:/TempThen a call to InitialContext() will succeed.
But the Tutorial assumes you're running under J2EE, and I'm not. I'm using the stand-alone Message Queue 4.4. If I define the properties on the command line,
java -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Djava.naming.provider.url=file:///C:/Tempthen InitialContext() succeeds.
If I explicitly dump the contents of the file into System.properties,
String
prop = System.getProperty( "jms.properties" );
Properties props = System.getProperties();
try {
java.io.File pf = new java.io.File( prop );
props.load( new java.io.FileInputStream(pf) );
catch( Exception ex ) { ex.printStackTrace(); }Then they get defined and InitialContext() tries to use them. But if I don't then they never get defined. Obviously the Tutorial expects that someone will do that, but who? AFAIK, both environments use the same naming library.
Has the behavior of MQ changed since version 1.3 of the tutorial? Or is J2EE doing something that the standalone product doesn't?This is all about JNDI configuration. Before you can look up an object in a JNDI repository you need to tell the JNDI runtime which JNDI provider to use. This means you need to set the system properties java.naming.factory.initial and java.naming.provider.url to specify which JNDI provider to use and where the data is located. There's a bit about this in the JNDI tutorial [http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html|http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html] .
The tutorial you are running uses the simple file-based JNDI provider known as "fscontext" and included in fscontext.jar.
That tutorial seems to be reading the jms.properties property and importing its contents, though I can't see where that is supposed to happen and so am not surprised it doesn't work. jms.properties is not, as far as I can see, a standard property name.
The MQ 4.4 documentation describes how to configure an InitialContext to use fscontext by configuring those properties directly. This would definitely work!
[http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view|http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view]
Note that your JNDI datastore (which you've defined to be in C:\Temp) will start off empty, so any lookups will fail unless you've inserted connection factories or destinations in there yourself. I see that is covered elsewhere in the JMS tutorial you were following. There's also a simple MQ GUI tool that can do this. [http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view|http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view]
Finally, if you're simply trying to learn about JMS and MQ you can skip the use of JNDI completely and simply instantiate the underlying connection factories explicitly. This wouldn't be appropriate in a production environment (where it is recommended to store such objects in a central store) but for developmeht purposes would work just fine.
Nigel
http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view -
I had iconnection problems between one of the POA and MTA and I restored this connection after a couple days.
now I can see the poa open on the MTA bus the message between the post-offices are not working.
I thinking the delete the message queue because I believe that there is possible problem with the queue ( any bad message that blocked it).
How can I clean the POA queue ?
Tks.* ffernandesv,
down the MTA, under the MTA directory, rename the MSLOCAL\MSHOLD\<postoffice>\ folder of the troubling PO. The folder will get recreated when you restart the MTA.
Also down the POA and rename the WPCSIn and WPCSOUT directory under the POA's directory structure.
HTH
Uwe -
Howto config msg policies for dead message queue (dmq) outside Glassfish?
The one thing I really love about OpenMQ is that I can have a centralized message store with a cluster of JMS nodes interacting with it.
I'm now at a contract gig which is pretty much a Tomcat/Spring only shop. I've setup OpenMQ 4.3 w/ MySQL message store and am using Bitronix Transaction Manager (BTM) to pool my XA connections and manage the transactions that are instrumented via AspectJ from the Spring configuration.
I have two issues really ...
1) The Spring DefaultMessageListenerContainer does not seem to think it needs to pull messages off the queue unless there is more than one message in the queue. It behaves as if it needs to be primed with messages. I would blame it on DefaultMessageListenerContainer if not for the fact that when I do the same thing with ActiveMQ it works fine.
2) ActiveMQ has this cool [RedeliveryPolicy object|http://activemq.apache.org/redelivery-policy.html] that you can associate with the connection factory. The com.sun.messaging.XAQueueConnectionFactory has no such settings. What limited amount of similar setting exist in OpenMQ seem to be associated with the ActivationSpec which seems to be more related to resource adapters as run from within an app server like Glassfish. My guess that it is outside the realm of configuration for OpenMQ is based on the fact that the default for endpointExceptionRedeliveryAttempts is 6 and when I enable transactions for my queue the messages will thrash indefinitely when they start hitting exceptions.
So, how do I configure a message delivery policy for OpenMQ outside of Glassfish? Or is the notion of a dead message queue (dmq) completely useless for OpenMQ without Glassfish?
Thanks,
Steve MaringOpenMQ does not have such a feature. The only thing you can do is to disable or enable DMQ delivery per destination. There is no way of configuring the number of redeliveries before message gets moved to DMQ.
Tom -
Limiting the message queue size
I am currently trying to run the message broker so that each queue has a maximum size on the messages that are contained within it. However, when setting this value by the administration console, it is completely ignored and more messages are successfully added to the queue.
I have also tried limiting the number of message in a particular queue, my problem is that when this limit is reached more messages are added and stored in the brokers memory, but not persisted. An error is still thrown by the broker, although this is a generic error which means there is no way of knowing if the message is in the queue or not which leads to duplicate messages being sent to the queue.
Any help on configuring the size of a message queue via either method will be greatly appreciated.
Thanks,
James.Hello,
Yes it is possible .
From the ICM script and before you send the call to the queue , make a IF statement :
SkillGroup.(Skill group Name).RouterCallsQNow<=15
ABout the threshold i am not sure but the above if the calls in queue reached 16 you can send it to a play prompt then drop it.
Amer -
Intial information:
SUN MQ 4.3
Local installation
Purpose: use dead message queue.
As per refered in SUN MQ admin guide have updated the broker
imqcmd update dst -t q -n TestQueue1 -o useDMQ=true
imqcmd update dst -t q -n TestQueue1 -o MaxBytesPerMsg=150000
Also java program sending message to the queue and data is of size 171KB(171000)
With above setting I expect the message to go to mq.sys.dmq, however its not? Any one have answer?
Or any one have used dead message queue with SUN MQ?
Any help will be appreciated.
Madhav
Edited by: user10111912 on Jan 20, 2011 4:18 PMIn this case, the message will be rejected, that is it does not get into the destination, which is different from a message in the destination becomes "dead" - dead message.
-
HTTP transport and Sun ONE Message Queue
How do I get the HTTP transport to work? The docs don't seem to be correct.
There are a couple of errors in the Sun ONE Message Queue docs that shipped with
the product.
The following are corrections for those errors.
Servlet configuration
Please note the following correction in the Sun ONE Message Queue 2.0
Administration Guide, Appendix B -
The class name of the HTTP Servlet in Step 4 of the "Configuring the Tunnel Servlet"
section is given as:
com.sun.messging.jmq.transport.httptunnel.servlet.HTTPTunnelServlet
The correct class name is :
com.sun.messaging.jmq.transport.httptunnel.servlet.HttpTunnelServlet
Client setup for HTTP support
1.The following connection factory attributes must be specified to use the HTTP
tunnel connection support.
JMQConnectionType :
Set this attribute to "HTTP".
JMQConnectionURL :
Set this attribute to the URL that will be used to connect to the Sun ONE
Message Queue message service (i.e. the URL for the HTTP tunnel servlet).
Note that there is no need to specify the JMQConnectionHandler attribute as
mentioned in the Sun ONE Message Queue 2.0 Administration Guide -
Appendix B.
2.Before running the client application, set the CLASSPATH variable to include
jmqutil.jar in addition to the standard Sun ONE Message Queue jar files.
This file is located at "/opt/SUNWjmq/lib/jmqutil.jar".
If the "jmqutil.jar" file is not included in the CLASSPATH, the client will get a
"java.lang.NoClassDefFoundError" exception for the class
"com/sun/messaging/jmq/util/JMQTimerTask".
3.If you are using an HTTP proxy, set "http.proxyHost" to the proxy server host
name, and "http.proxyPort" to the proxy server port number using the -D
command line option.
An example command line would look like this:
java -classpath
/opt/SUNWjmq/lib/jms.jar:/opt/SUNWjmq/lib/jmq.jar:
/opt/SUNWjmq/lib/jndi.jar:.:/opt/SUNWjmq/lib/jmqutil.jar
-DJMQConnectionType=HTTP
-DJMQConnectionURL=http://webserver:80/imq/servlet ClientApplicaiton -
Hi Experts,
The BASIS team has configured the CCMS alert for XBTI* and XBTO* queues in development system.
Hence we need to test the same.
Possibilities tried:
1. Huge payload
2. Stop and start of BPE this blocks the XBQ which is not needed as of now
3. Deregistering the specific queues. The queus is set to ready state until we register the same. Once registered the queue block is cleared. Hence this option is not helpful.
Kindly let us know the various ways to block the queues in PI.
Thanks
Suganya.Hi,
If you have any interfaces using EOIO queues then try failing the same at mapping level and check...
Another option is try failing the interface at mapping level by sending some invalid data for normal interfaces (EO) only and check...but in this case runtime may not block the queues all the times only few times and few circumstances it will block the queues...
HTH
Rajesh
Maybe you are looking for
-
How to avoid displaying empty rows in a table?
The situation is as follows: I have got a set of questions under a particular category say marketing category. The user will be displayed with a table consisting of a set of questions from a particular category with four radio buttons for each questi
-
Exception is thrown "mydb is not bound"(needs urgent help)
We r three students and our final project is a BPM(Business peocess Management)system. BPM is actually a workflow system(managing the business processes)and all the rules and constraints are applied from the Rule Management System. we have started th
-
HT204150 I have lost contacts in my icloud!! How do i get them back?
I have lost contacts in my icloud!! How do i get them back?
-
Hi... I have Oracle 8i installed on a Linux server. Now I installed 9i in another server and upgraded an Oracle 8i database. But there are some queries that I have performance problems. For example, when I run in SQL Navigator a simple select that re
-
Hi, if i try to watch a streaming quick time movie on the net like a demo it works fine. But if i try to play a quicktime file thats on my PC i get instant reboot. Every time i try to play any file on quicktime from my computer it reboots instantly.