Author |
Message |
Topic: MQRC_UOW_ENLISTMENT_ERROR, ServicedComponent(COM+), |
RikBaeten
Replies: 8 Views: 35394
|
Forum: Multiphase Commit Posted: Mon Aug 08, 2011 6:23 am Subject: MQRC_UOW_ENLISTMENT_ERROR, ServicedComponent(COM+), |
Do you have an APAR reference? I don't see it on:
http://www-01.ibm.com/support/docview.wss?uid=swg27014224
We have a very similar error.
Thanks. |
Topic: MQ7 server installation fails |
RikBaeten
Replies: 20 Views: 25072
|
Forum: IBM MQ Installation/Configuration Support Posted: Wed Mar 30, 2011 9:38 am Subject: MQ7 server installation fails |
## Verifying package <mqm> dependencies in global zone
## Processing package information.
pkgrm: ERROR: bad read of contents file
pkgrm: ERROR: pathname=/usr/bin/addmqinf
pkgrm: ERROR: pro ... |
Topic: New MQ Security Hole Found - Part 2 |
RikBaeten
Replies: 3 Views: 5627
|
Forum: IBM MQ Security Posted: Wed Mar 16, 2011 2:35 am Subject: New MQ Security Hole Found - Part 2 |
This is correctly working from a client-application v7 in C to a WMQ v5.3 server.
However connecting the same client-application v7 in C to a WMQ v7 server it no longer works. At the same time it c ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Tue Jan 04, 2011 5:46 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
Thanks everyone for your help . The issue is solved. I'm adding my findings as future reference for other people.
I've done some testing on Solaris UNIX with different queue managers: one with de ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Wed Dec 15, 2010 4:31 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
The KeepAlive parameter means: Advise the operating system, to send IP packages through an IP connection - and so "keep it alive".
If the sending of this package fails, the operating sys ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Wed Dec 15, 2010 3:19 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
TCP Keep Alive only cleans up orphaned connections where there is nothing left on the client side on that socket. True orphans.
ClientIdle kills both orphaned and dormant but otherwise perfectly ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Wed Dec 15, 2010 3:13 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
if i want to get rid of an old svrconn connection, i use
stop channel(..) conname(...) mode(force)
then its gone from the list of "active" channels.
The problem is that there are bo ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Fri Dec 10, 2010 5:04 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
I'm a bit hesitant on using the ClientIdle parameter
- it seems to be listed here: http://www-01.ibm.com/support/docview.wss?uid=swg21376219, but it's not officially documented in the infocenter. I r ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Fri Dec 10, 2010 4:31 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
Thank you very much both for your comments.
@Mr Butcher:
Interesting info. So if I understand it correctly:
- on one side the MCA accepts TCP/IP connection from client applications => this c ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Thu Dec 09, 2010 8:51 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
In fact I wanted to post this as a question/comment on topic 37647, but somehow it was made a separate topic:
http://mqseries.net/phpBB2/viewtopic.php?t=37647&start=0&postdays=0&postorder ... |
Topic: [SOLVED] stop conn(*) not fully cleaning up the connection |
RikBaeten
Replies: 21 Views: 27095
|
Forum: General IBM MQ Support Posted: Thu Dec 09, 2010 6:30 am Subject: [SOLVED] stop conn(*) not fully cleaning up the connection |
After I issue the stop conn(id) command, the connection is not visible anymore via dis conn(*). However via the netstat command I see the corresponding sockets are still open and via t ... |
Topic: Message Flow Syntax Error after Migration WMQI 2.1 --> WB |
RikBaeten
Replies: 4 Views: 3090
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jul 26, 2010 6:35 am Subject: Message Flow Syntax Error after Migration WMQI 2.1 --> WB |
I had a similar problem, and for me vmcgloin's suggestion IS a solution.
You probably need something like:
SET ErrorType = EVAL( 'FIELDNAME(''' || Path || ''')'); |
Topic: [SOLVED] Err while deploying msg flow |
RikBaeten
Replies: 9 Views: 12527
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Dec 29, 2009 8:40 am Subject: [SOLVED] Err while deploying msg flow |
I had a similar problem implementing UsernameToken basic authentication (WS-Security) from the SoapRequest nodes. I got a similar error:
BIP3701E: A Java exception was thrown whilst calling t ... |
Topic: Losing XML Attributes in Environment.Variables |
RikBaeten
Replies: 17 Views: 33611
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 28, 2009 12:36 am Subject: Losing XML Attributes in Environment.Variables |
Thanks, indeed reparsing was not necessary. This is the adapted code:
CREATE LASTCHILD OF Environment.Variables.xmlMsg DOMAIN('XMLNSC');
SET Environment.Variables.xmlMsg.XMLNSC = ... |
Topic: Losing XML Attributes in Environment.Variables |
RikBaeten
Replies: 17 Views: 33611
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 24, 2009 7:38 am Subject: Literal code that fixes the problem |
For future reference: I'm adding some code that I literally used to fix the problem that XML attributes are changed into XML nodes when assigning an XML tree to the Environment.
The pieces of code ... |