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.

Similar Messages

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.

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

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

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 get syslog messages from Remote SA520 over VPN

I'm trying to set up a central logging server on a debian system running rsyslog.
The syslog server is local & I have a branch office connected via a VPN. Both buildings have SA520 routers.
I have set up both firewalls to allow ANY from each network 192.168.150.X & 19.168.160.X
(also tried to add a rule for UDP514 but that didn't help)
The debian system is new & has no iptables set up
I've entered the syslog server IP in remote logging.
I've set up facilities in Send to syslog for both routers.
I am logging messages from the local router but don't see anything from the remote.
I've checked with wireshark & see no syslog packages from the remote (I do see SSL negotiation & others when using the web admin and of course the functioning vpn)
I rebooted the router to see if that mae a difference but no luck.
Any ideas why I can't get the syslog traffic across the VPN?

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 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?

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

JMS: can I access SAP messages from extenal Java

- Can I access SAP Messages from an external (non-SAP) java program?
- Do I use JNDI or can I call using a jar file from my java invocation?
- Do I have to define a queue (or does SAP JMS have queues)
- What port do I use?
Thanks

Hi John,
> - Can I access SAP Messages from an external
> (non-SAP) java program?
>
Yes, you can use the JMS provider on the Web AS from a standalone java program.
> - Do I use JNDI or can I call using a jar file from
> my java invocation?
You connect your remote java client to the server by getting an InitialContext. The you lookup the JMS resources (such as Topic- or Queue ConnectionFactory, etc.) from the JNDI. You can have a look at <a href="http://help.sap.com/saphelp_nw04/helpdata/en/25/bf8f44540c469abc19fb6ac3ac7885/frameset.htm">this</a> page for more info.
>
> - Do I have to define a queue (or does SAP JMS have
> queues)
>
The JMS Provider on the Web AS provides default connection factories that you can use to create a topic ot queue. The lookup strings you have to use are
jmsfactory/default/TopicConnectionFactory
for topics and
jmsfactory/default/QueueConnectionFactory
for queues.
> - What port do I use?
>
You use the P4 port (50004 by default for instance number 00) when obtaining the InitialContext with this code:
java.util.Properties properties = new Properties();
// set the properties of the connection
properties.put("Context.INITIAL_CONTEXT_FACTORY", "com.sap.engine.services.jndi.InitialContextFactoryImpl");
properties.put(Context.PROVIDER_URL, "<Server_Host>:<p4_port>");
properties.put("Context.SECURITY_PRINCIPAL", "Administrator");
properties.put("Context SECURITY_CREDENTIALS", "admin_password");
// start initial context with the properties specified
InitialContext context = new InitialContext(properties);
Hope that helps!

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

How to handle failure when sending messages to remote queues from OAS10.1.3

Hi,
Here is my problem. IN my project, I have a MDB which is looking for message in a queue and once a message arrived, it supposed to send the message to remote queues.
Assume that there are 3 remote queues, and my mdb is trying to send the message to all the 3 remote queues,
1) My problem is, If one of the remote queue is not reachable or down, then the MDB should be able to resend it several times until it reaches the failed remote queue.
2) At the same time, I dont want to resend the messages(duplicate) to the queues which are successful ones.
Please suggest me some solution for this in JMS.
My MDB deployed at 10.1.3 and assume that remote queue can be in either another 10.1.3 or WAS 6.0(Optional).
Thanks and regards,
SS.

Hi,
1) My problem is, If one of the remote queue is not reachable or down, then the MDB should be able to resend it several times until it reaches the failed remote queue.
Not very sure what is your question, depending on if you want to resend the message if one of three queues is down.
If the message has to arrive to a certain destination while mdb received it, you may try to reconnnect and resend the message in a couple of times. Perhaps you need a couter or timeout to limit the number of time to retry or the period to retry.
Is that what you are asking.
2) At the same time, I dont want to resend the messages(duplicate) to the queues which are successful ones.
While sending message to a queue, those implementation is within the exception try/catch block, so any resend failure (JMSException) will fall into the catch block I guess. And we can probably use that exception to determine if the message is able to send to remote queue, if not, keep resending util it is over the limit of retries. For example:
onMessage(Message){
resend(message, counter);
public void resend(message, counter) {
try{
if (counter <= retryLimit){
.... // do the reconnect or/and resend operation
}catch(exception e){
resend(message, counter++);
If the above is not what you are asking, please clarify a bit.
Rocky

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.

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

Count the number of message in remote queue.

Does any method in MQSeries or JMS, can count the number of message in remote queue.
I try to use QueueBrowser to browser, but got exception when browse the remote queue.
thanks.

You cannot read from, browse or query a remote MQ Queue, only write to it. Try www.mqseries.net or ibm website for any ways around this...

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

Can' t consume JMS messages from remote queue

Similar Messages

Maybe you are looking for