Drop jms messages from distributed queue

hello
i am searching info for making one script (wlst?) for deleting messages from one jms distributed queue and i dont find it.
can you help me?
thanks

You can use the wlst scripts described in How to list total number of message in specific Topic/queue using wlst comm to find the right destination runtime MBean. Then call deleteMessages('true') on the destination runtime MBean. The method deleteMesages() takes a selector expression.
Hope this helps.
Dongbo
Edited by: Dongbo on Mar 14, 2012 10:44 AM

Similar Messages

Routing JMS message from same queue to different channels.

From a given adapter module, is there a way of calling different communication channels?
The scenario: The sender of the data is JMS. One single queue contains desperate text format. Based on the content of the first 4 characters , PI has to parse it differently in its own corresponding MT. The target IDoc structure remains the same. I have multiple messageTransformBeans set up, one for each MT assuming that the data would arrive in different JMS queues. However since the data is now all heaped on to a single queue, the challenge of routing the data now lies in SAP PI.
HowTo - Send Test Messages to the Adapter Engine (to an Integrated Configuration) - This solution does send message directly to the IE (using 7,1), but not to the adapter engine where the messageTransformBeans exist.
Any solid pointers in the direction will be really helpful.
Regards,
Keerti

Hi,
you can go for end to end testing.
if jms not available use file adapter in the sender side and fetch the text file and test it.
Regards,
Muni

Error reading jms message from MQ-queue

Hi,
To be able to use async-sync bridge in JMS adapter, we recently patched XI 3.0 from SP 15 to SP21. But the jms sender adapter has problem reading the message from the MQ-queue, see detail of error-message at the end of this message.
I did change the adapter to use modules use RequstResponseBean and ResponseOneWayBean as explaned on help.sap.com.
The async-sync bridge worked once and the it started failing.
Detailed error message in communication channel monitoring:
Error while processing message '3c5a0640-9c03-11dc-82f2-000255d3bbf7'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ...
/Maria Lande

Hi,
I fixed it myself. I hade to do a Xi Data Cahe Refresh.
Navigate to Administration section on the SAP Exchange Infrestructure start page. On the Directory tab page, choose Cache overview under the heading Administration of Locks and Caches. Do a Full Cache Refresh on the adapter engine.
/Maria Lande

Can' t consume JMS messages from remote queue

Hello.
We are using Tibco JMS Server as Foreign JMS server from WL server. And WebLoigic (8.1 SP 3) MDBs are receivers. Everything works fine until there is a restart of the Tibco server. Once the queues become unavailabe, we see in the WL log that the destination is unreachable. And also once the Tibco server comes back up, WL log says that the Foreign queues have been re-connected. But still, we don't see any messages being received by the MDB. The MDBs are configured to poll for messages evey 1 second. Still we don't see it happening after the foreign server restart.
But if we re-start the WL server, it begins to work just fine.
Any pointers?
Thanks

I do have the correct IP address of the syslog server set up. I do not want email logs so have not enabled that.
My setup is
remote lan > SA520-remote (192.168.160.1) > [ site to site IPSec VPN over WAN ] > SA520-local (192.168.150.1) > syslog server (192.168.150.25) & local lan
Firewall is set up to allow ANY IN & OUT to local lan on both routers.
I have also set up specific rules for UDP 514 Syslog traffic (no difference, currently disabled)
syslog server has -no- firewall at the moment.
Syslog server is receiving messages from the local router with no issues.
Log Severity is set to Information & Log Facility is set up to send to Syslog.
I have also setup a SNMP trap on the syslog server & pointed the remote router to it in hopes of diagnosing the issue.
Both routers have the latest firmware applied.
Using wireshark on the syslog server I see no traffic on UDP 514 (syslog) or UDP 162 (snmp)
I can use the WUI for the remote & ping the 160.1 with no problem. Both ping & TLS/TCP traffic show up in wireshark on the syslog server when I do so.
It looks to me like there is a problem routing the syslog messages out of the router & then back through the VPN.
Worst case I'll set up another syslog server on an old machine at the remote location & then cron the logs to the central syslog server but it really seems I shouldn't have to.

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

If you want to use JMS with AQ as datastore then there is some configuration you need to do to enable this. This is outside SOA Suite per sa, e.g. no adapter required.
If you want to connect to the AQ direct then use the AQ adapter.
this blog may be of some help understand the configuration
http://biemond.blogspot.com/2008/01/oracle-jms-with-esb-and-bpel.html
cheers
James

Discarding JMS messages from queue

Hi,
I have some Weblogic JMS queues, and some OSB SOAP based JMS Proxy Services listening to those queues.
Sometimes, the source application puts a message in the JMS queue, which is not a valid SOAP XML, or sometimes is a simple text. For such cases, the Proxy service is not able to receive the message from the JMS, and the OSB logs keep on piling up with the error messages.
Is there any way to discard such messages, which the proxy is unable to read, automatically ?

Hello buddies,
I have the same problem. The scenario is the following:
On request:
WS Client -> FrontRequestQueue -> Proxy Service -> Business Service -> BackRequestQueue -> WS Server JMS
On response:
WS Client <- FrontRequestQueue <- Proxy Service <- Business Service <- BackResponseQueue <- WS Server JMS
1st Case: WS Client send a correct & valid Soap Message with all request info OK. Result OK
2nd Case: WS Client send a Soap Message with KO info. Result: Error handled on Proxy Service and error message is returned, OK.
3rd Case: WS Client send a "HelloWorld" String.
Result:
An *<Error> +<OSB Kernel> <BEA-380003> <Excepción en TransportManagerImpl.receiveMessage, com.bea.wli.sb.context.BindingLayerException: Failed to parse XML text+*
com.bea.wli.sb.context.BindingLayerException: Fallo al anular la canalización del mensaje: Failed to parse XML text*
+ at com.bea.wli.sb.context.ContextUtils.newException(ContextUtils.java:933)+
etc...
Proxy Service tries to read the messages from the queue infinitely producing many errors on server, so I have to stop the queue and delete the message to force stop it.
I've changed all the JMS Transport "retry" params on Proxy and Biz services and the behaviour is the same, any suggestions?
Thanks to all.

How to send JMS Message from a BPM Process

Hi All
I have small query regarding sending JMS Message from a bpm process. Is it possible to send JMS message from one bpm process to another bpm process.
I have a scenario in which I need to send a JMS message to a queue where another process is listening on that queue and as soon as the message is received on the queue the process instance is created.
I know how to listen for the JMS message on the queue, but I don't how to send a JMS message from a process.
Also Can I create process by sending the Notification to the process instead of a JMS message. But the process to be created is not a subprocess i.e. Can notification be send accross different processes.
Any information or example in this regard would be helpful.
Thanks in advance
Edited by: user9945154 on Apr 22, 2009 7:46 PM

Hi,
Here's one approach to sending JMS messages from an Oracle BPM process. If you're doing this just to send a message into another process, do not take this approach. It's far easier and quicker if you do this using the OOTB "send notification" logic.
These steps describe how to do this using WebLogic. The steps would be different if you're using another ap server / JMS provider.
1. Guessing you've already done this, but first expose the two required WebLogic jar files for JMS messaging as Java components in the External Resources. The two files for WebLogic are weblogic.jar and wljmsclient.jar” (located in the < WebLogic home directory > /weblogic/server/lib” directory).
AquaLogic BPM JMS Queue Listener for WebLogic 8.1
2. You've probably already done this, but add an External Resource to represent the J2EE container:
• Name: “weblogicJ2EE” - this is important and will be used in the next step
• Supported Type: “GENERIC_J2EE”
• Initial Context Factory: “weblogic.jndi.WLInitialContextFactory”
• URL: “t3://localhost:7001”
• Principal: and Credentials: whatever userid and password you defined to access theWebLogic administrative console.
3. Create the External Resource that represents the send queue configuration. In this example, I'm calling it “WebLogic Send Queue”. This is important - remember what you named it because you will use this name in the logic that sends the JMS message. This new External Resource is configured as:
• J2EE: “weblogicJ2EE” (same name as the second External Resource you created)
• Destination Type: “QUEUE”
• Lookup Name: “weblogic.examples.jms.exampleQueue”
• Connection Factory Lookup Name: “weblogic.examples.jms.QueueConnectionFactory”
4. Here's the logic to send a Message to the Queue
<pre class="jive-pre"><p />msg as String = "Hello World"
jmsMsg as Fuego.Msg.JmsMessage
msg = "<?xml version=\"1.0\"?><Msg>" + msg + "</Msg></xml>"
jmsMsg = JmsMessage(type : JmsMessageType.TEXT)
jmsMsg.textValue = msg
sendMessage DynamicJMS
using configuration = "WebLogic Send Queue",
message = jmsMsg</pre>
Note that the “sendMessage” method uses the configuration parameter “WebLogic Send Queue”. You previously created a JMS messaging service External Resource with this name in the third step.
Again, please don't go this route if you're just using it to send notifications between processes,
Dan

MQ Adapter does not clear the rejected message from the queue

Hi All,
I'm using a MQ Adapter to fetch the message from the queue without any Backout queue configured. However, whenever there is any bad structured message found in the queue, MQ adapter rejects the message and moves the message to the rejmsg folder but does not clear it off the queue, as a result of which it keeps retrying the same hence, filling the logs and the physical memory. Somehow we do not have any backout queue configured so I can move the message to blackout queue. I have tried configuring the jca retry properties and global jca retry as well but to no avail.
- Is it not the default behaviour of MQ Adapter to remove the rejected message from the queue irrespective of Backout queue is configured or not? The same behaviour working well with the JMS and File Adapter though.
- Is there any way I can make MQ Adapter delete the message from that queue once it is rejected?
Regards,
Neeraj Sehgal

Hi Jayson,
Check this URL which answers a problem with com.sap.engine.boot.loader.ResourceMultiParentClassLoader problem:
http://209.85.175.132/search?q=cache:RnFZ9viwuKkJ:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fcom.sap.sdn.folder.application!2fcom.sap.sdn.folder.roles!2fcom.sap.sdn.folder.navigationroles!2fcom.sap.sdn.role.anonymous!2fcom.sap.sdn.tln.workset.forums!2fforumtest!2fcom.sap.sdn.app.iview.forumthread%3FQuickLink%3Dthread%26tstart%3D45%26threadID%3D1020700+com.sap.engine.boot.loader.ResourceMultiParentClassLoader&hl=en&ct=clnk&cd=3&gl=in&client=firefox-a
Please check that the JDK compliance level is at 5.0
Window->Preferences->Java->Compiler->Compiler compliance level set this to 5.0
Set the installed JRE to the one you have mentioned JDK 5.0 update 16
Window->Preferences->Java->Installed JRE's->
Click on the add button to select the path of your JDK.
once completed click on the check box next to it.
regards,
AKD

How can I send and receive a message from a queue using standalone program

Hi,
I want to write a standalone Java program which has to post a message to a queue and receive a message from a queue thats specified as a replyto queue.I want to have my application to be completely standalone without the need of a Application server.What all the Jars do I need to include in the application.My aim is to have the application standalone and portable so that the application runs on any machine that has a JRE.
Thanks in advance,
Prathima

Hi,
You can get quite simple standalone MQ Java programs from this site http://www.capitalware.biz/mq_code_java.html.
Also regarding the jars required for your application depends on the API being used. If you use MQI API few jars are required and if you decide to use JMS API you'll require few other jars. But you got to either install Websphere MQ Java Client, which will copy the jars to the respective location, or you can choose to copy the jars from some other machine manually.
Eventually, all the jars related to MQI and JMS API will reside under /usr/mqm/java/lib/ or /var/mqm/java/lib/ UNIX Environment. And in case of WINTEL, you should find the jars under C:\Program Files\IBM\WebSphere MQ\Java\lib.
Trust it clarifies...
Naren

DefaultMessageListenerContainer Does receive message from remote Queue

I am developing an application where I need to consume JMS messages from JMS Queue on remote weblogic server 10.3.3.0. My application is deployed WLS 10.3.2.0 and I using Spring 2.5.6. In my spring configuration, I have used Springframework's DefaultMessageListenerContainer to listen to the Queue on remote server.
Now I have two scenarios in which DMLC does not consumer messages without server restart.
Scenario 1: When the Remote server on which the JMS queue resides is restarted. DMLC stops consuming message from the Queue on remote server. After I restart my server, it starts consuming messages. But I want that DMLC starts consuming messages without the restarting server at my end.
Scenario 2: When the remote server is running and I update/Redploy my application on WLS at my end. In this case also, DMLC stops receiving messages and I have to restart server at my end.
Could anyone please help sorting out this issue?

This seems like a Spring question, you might want to ty the Spring forums. I'm not sure why you would get the behaviour you see.

JMS message from one application to the another appl in the same container?

I have a question.
Can I send JMS message from one application to the another application in the same container?
If yes ...can you provide me info.
I want to know in regards of EJB2.0 and EJB3.0.
Thanks,
Rahul

So the receiver application is a Message Driven Bean, right?
In your container, do you have a mean to ensure that it is correctly configured to listen the desired destination? Like an administrative console that would show the destinations, the number of pending messages, the number of active consummers...?
btw what is the destination type? A queue or a topic?

ALDSP 3.2 - How to create JMS message from ALDSP

Is there a way to write a jms message from ALDSP?
I want to be able to perform database updates to a database and also write a message to queue in a transaction.
Thanks

As per my understanding only one resource can be non-transactional. In this case it would be the Web Service.If you have n data sources and the first n-1 are transactional and the nth one is not - if you update the first n-1 successfully, and the nth one fails - then you just throw an exception and the updates to the n-1 data sources get rolled back. If an update to one of the n-1 data sources fails you throw an exception and the update to the nth data source never happens. In your case, it's up to you to ensure the updates are executed in the correct order (how you write your XQSE procedure).
Will the call to write a jms message from a Java function in ALDSP participate in the database transaction? DSP doesn't suspend the current transaction when calling a Java function. So yes, the JMS call would participate in the same transaction as the database call.
If you want to dump out the transactionId in your java function in the same format as it appears in the DSP Audit, you can use :
public String byteArrayToHexString(byte in[]) {
StringBuffer out = new StringBuffer(in.length * 2 + 2);
out.append("0x");
for(int i = 0; i < in.length; i++) {
byte ch = 0x00;
ch = (byte) (in[i] & 0xF0);
ch = (byte) (ch >>> 4);
ch = (byte) (ch & 0x0F);
out.append(HEX[(int) ch]);
ch = (byte) (in[i] & 0x0F);
out.append(HEX[(int) ch]);
return out.toString();
}

Sending a jms message from one server to another in a cluster fails..

Hi,
          My platform is wl6.1 sp7 two servers in a cluster...
          I have problems sending jms messages from one server to the other. When sending to a destination on the same server it works fine, but sending to the other server do not work. I get no exceptions when I send the message. The "Monitor all Active JMS Destinations..."->"Messages Received" column increase number of received messages for the remote server. But the onMessage method in the bean is not called(I am logging all calls to a file...)
          Any suggestions?
          And..
          My understanding is that the JNDINameReplicated default value is set to true? But when I don't set this value to true the jndi name is not replicated too the other server.
          (The state for both servers are Running in the admin console and listed servers in the cluster is 2....
          Server names:
          * bluej, biztalk-lab
          JMS connection factory:
          * xlink.jms.factory.commerceFactory, deplyed on both servers and for the cluster
          Destinations:
          * xlink.jms.service.report.biztalk-lab.Report for the biztalk-lab server active on 'biztalk-labJMSServer' JMS-server
          * xlink.jms.service.report.bluej.Report for the bluej server active on 'bluejJMSServer' JMS-server)
          ~b

Deployed to the bluej server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.bluej.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.bluej.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.bluej.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>
          Deployed to the biztalk-lab server:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <message-driven-descriptor>
          <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
          </message-driven-descriptor>
          <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
          <ejb-class>no.xlink.server.service.report.engine.jms.ReportBean</ejb-class>
          <transaction-type>Bean</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          </ejb-jar>

Removing superseded messages from the queue

Does JSMQ provide any way for a producer to remove a message from the queue which it queued some time ago but which it no longer wishes to send?
I am investigating the use of JSMQ in a military battlemap application connecting nodes over low bandwidth/unreliable connections. The reason we want to be able to remove messages is as follows: Say a producer sends a low priority message to the queue regarding a unit's position. Later on the same producer sends an update regarding the same unit to the queue. If the first message is still present in the queue (ie has not been sent yet) then we want the producer to be able to remove it as it is now superseded by the new message and we don't want to waste bandwidth sending the old message first.
I know we can set an expiry time on messages, but this doesn't really solve our problem. We want the original message to stay in the queue indefinately (until it is read by the consumer) unless it is superseded by a new message in which case we want to remove it.
Thanks
Roger

Hi Roger,
JMS does not support the removal of messages from a queue
as you described. I can't think of a way to not deliver the old
message once it was already sent.
Alternatives I can think of:
- Adjust the interval at which the consumer reads the messages
off the queue and/or the number of messages that are read;
so that the consumer will see the old and new messages
and can decide which one to use. This does not address the
bandwidth issue but allows the consumer to behave smarter.
- Similar to above, but on the producer side. The producer waits
for some interval before sending a message, in case an
updated position of a unit arrives at the producer. This might not
be good if a consumer needs to know the location of a unit as
soon as it is available.
- Use a topic instead of a queue. When using queues, old
messages (containing old positions) sent to a queue are kept
until the consumer reads it. With topics, if no consumers are
around, the message is tossed. However, if you really need old
messages to lie around (e.g. need to know last position of
unit), this won't suit your needs.
Sorry I don't have a straight answer for you, hope this helps
somewhat.
-i
http://wwws.sun.com/software/products/message_queue/index.html

Drop jms messages from distributed queue

Similar Messages

Maybe you are looking for