jms - MQ 7.0.1.9 selector JMSCorrelationID Mistaken Msg -


we developed java application in multiple java jms clients connect server, both websphere mq 7.0.1.9. each client has consumer selector on application specific client id eg. jmscorrelationid='050_14133431' on shared queues, in server set application specific client id on messages setjmscorrelationid( ) sent particular client. application specifi client ids unique. works fine of time. however, found messages client sessionid consumed client b surprisingly. checked logs , confirmed each client create consumer selector on sessionid. in understanding, consumer consume messages match selector criteria. 1 thing note used read ahead feature our application use non persistent messages. happened rarely, once month. idea why happen? syntax error in jmscorrelationid='050_14133431', should must start letter instead of digit? hints appreciated. in advance.

please find below jms documentation (emphasis mine):

the delivery modes supported jms api persistent , non_persistent.

a client marks message persistent if feels application have problems if message lost in transit. client marks message non-persistent if occasional lost message tolerable. clients use delivery mode tell jms provider how balance message transport reliability throughput.

delivery mode covers transport of message destination. retention of message @ destination until receipt acknowledged not guaranteed persistent delivery mode. clients should assume message retention policies set administratively. message retention policy governs reliability of message delivery destination message consumer. example, if client's message storage space exhausted, messages may dropped in accordance site-specific message retention policy.

a message guaranteed delivered once , once jms provider if delivery mode of message persistent , if destination has sufficient message retention policy.

https://docs.oracle.com/javaee/6/api/javax/jms/deliverymode.html

in summary, if message marked non_persistent, jms provider can't guarantee once , once delivery. if not acceptable, should change persistent mode.

also, should perform resilience (non-functional) tests (with scenarios broker fail overs, etc..) production volumes of messages, find out average number of duplicate messages.


Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more