Question
Wipro Limited
CA
Last activity: 14 Sep 2017 3:15 EDT
Encoded character gets converted to ASCII value while sending the message via JMS queue
Hi All,
We are trying to send XML message with Base 64 encoded text via JMS queue to an endpoint, but "+" character in the string gets translated to its ASCII value i.e + . All other characters are intact and we can see request getting posted correctly to the queue.
For e.g
Base 64 string -
Hi All,
We are trying to send XML message with Base 64 encoded text via JMS queue to an endpoint, but "+" character in the string gets translated to its ASCII value i.e + . All other characters are intact and we can see request getting posted correctly to the queue.
For e.g
Base 64 string -
PERhdGE+IDxDbGllbnRzPiA8cmVmZXJlbmN
lTnVtYmVyPmQ4Yzg3ZWE3LWI2OWQt
Translates to
PERhdGE+IDxDbGllbnRzPiA8cmVmZXJlbmN
lTnVtYmVyPmQ4Yzg3ZWE3LWI2OWQt
Anyone faced similar issue ? Is it related to Queue configuration or something additional required to post base 64 string via JMS.
TIA
Ashish
Pegasystems Inc.
IN
Hi Ashish,
I have faced same issue the thing we need to notice here is the XML you are sending is not encoded that is why the + is converted into + to overcome this issue please encode the request using Base64.encode(requestXML).
Thanks,
Narasimha
JPMorgan Chase & Company
US
HI Ashish,
Are you trying to use Property-Set-XML method to convert property data into XML format, if yes we have Hfix available for this issue. If yes please let us know the pega version.
CapGemini
IN
Hi Sudhakar,
I explained entire issue in below post, Please go through it once and let us know the hot-fix resolves the issue.
Regards,
SantoshKumar
CapGemini
IN
Hi Narasimha,
Let me explain the entire approach we are doing here
we are first encoding the message with Base64 method and passing it as string to one of the parameter in the request. Later we are doing the Property-set-XML to prepare the XML request and then sending it to External system via Connect-JMs Call
We traced the request from Pega tracer and also in JMS queue logs.
Pega Tracer shows the encoded string in the JMS request as like below:
Hi Narasimha,
Let me explain the entire approach we are doing here
we are first encoding the message with Base64 method and passing it as string to one of the parameter in the request. Later we are doing the Property-set-XML to prepare the XML request and then sending it to External system via Connect-JMs Call
We traced the request from Pega tracer and also in JMS queue logs.
Pega Tracer shows the encoded string in the JMS request as like below:
PERhdGE+IDxDbGllbnRzPiA8cmVmZXJlbmNlTnVtYmVyPmUzZThkZWIzLTUyOGItNDBkNi04M2Iz LTA5YzhhZjViN2FkYTwvcmVmZXJlbmNlTnVtYmVyPiA8RG9jdW1lbnRWZXJzaW9uTnVtYmVyPjwv RG9jdW1lbnRWZXJzaW9uTnVtYmVyPiA8TGFuZ3VhZ2U+PC9MYW5ndWFnZT4gPEJhcmNvZGVfVHJh bnNpdE5vPjUzMjwvQmFyY29kZV9UcmFuc2l0Tm8+IDxCYXJjb2RlX0FjY291bnRObz41MjwvQmFy Y29kZV9BY2NvdW50Tm8+IDxGb3JtRGF0ZT5BdWd1c3QgMTEsIDIwMTc8L0Zvcm1EYXRlPiA8TG9j YXRpb25JbmRpY2F0b3I+PC9Mb2NhdGlvbkluZGljYXRvcj4gPFByaW1hcnlDbGllbnQ+IDxQQ19j dXN0U1JGTm8+NTczMDQ2MzU2PC9QQ19jdXN0U1JGTm8+IDxQQ19jb21wYW55TmFtZT5SQk9MIEJV U0lORVNTNTU1PC9QQ19jb21wYW55TmFtZT4gPFBDX3RyYW5zaXRObz41MzI8L1BDX3RyYW5zaXRO bz4gPFBDX2FjY291bnRObz41MjwvUENfYWNjb3VudE5vPiA8L1ByaW1hcnlDbGllbnQ+IDxUcmFu c2l0QnVzaW5lc3NBY2NvdW50Tm8+NTMyLTUyPC9UcmFuc2l0QnVzaW5lc3NBY2NvdW50Tm8+IDxQ cm9kdWN0PlJCT0w8L1Byb2R1Y3Q+IDxNYXhBbW91bnQ+JDI1MDAwLjAwPC9NYXhBbW91bnQ+IDxN aW5SZXRhaW5lZEJhbGFuY2U+JDAuMDA8L01pblJldGFpbmVkQmFsYW5jZT4gPE1pblJldm9sdmVt ZW50QW1vdW50PiQyNTAuMDA8L01pblJldm9sdmVtZW50QW1vdW50PiA8T3BlcmF0aW5nTGluZVBs dXM+WWVzPC9PcGVyYXRpbmdMaW5lUGx1cz4gPFByZW1pdW1SYXRlPjMuMDwvUHJlbWl1bVJhdGU+ IDxQYXltZW50RGF0ZT4yMXN0PC9QYXltZW50RGF0ZT4gPFNldHVwRmVlPiQwLjAwPC9TZXR1cEZl ZT4gPE1vbnRobHlGZWU+JDI1LjAwPC9Nb250aGx5RmVlPiA8QW5udWFsRmVlPiQ3NS4wMDwvQW5u dWFsRmVlPiA8QkxJUD48L0JMSVA+IDxUZXJtcz48L1Rlcm1zPiA8QXV0aG9yaXplZFBlcnNvbl9M c3Q+IDxBdXRob3JpemVkUGVyc29uX1JlY29yZD4gPENsaWVudFNSRj41NzMwNDQ0MDE8L0NsaWVu dFNSRj4gPE5hbWU+UkJPTCBQRVJTT05BTDEwNTwvTmFtZT4gPC9BdXRob3JpemVkUGVyc29uX1Jl Y29yZD4gPC9BdXRob3JpemVkUGVyc29uX0xzdD4gPE93bmVyX0xzdD4gPE93bmVyX1JlY29yZD4g PE93bmVyU1JGPjU3MzA0NDQwMTwvT3duZXJTUkY+IDxOYW1lPlJCT0wgUEVSU09OQUwxMDU8L05h bWU+IDwvT3duZXJfUmVjb3JkPiA8L093bmVyX0xzdD4gPFNlY3VyaXR5SW5kaWNhdG9yPjwvU2Vj dXJpdHlJbmRpY2F0b3I+IDxNdWx0aWxpbmV0ZXh0PjwvTXVsdGlsaW5ldGV4dD4gPEd1YXJhbnRv cl9Mc3Q+IDxHdWFyYW50b3JfUmVjb3JkPiA8R3VhcmFudG9yU1JGPjwvR3VhcmFudG9yU1JGPiA8 TmFtZT48L05hbWU+IDwvR3VhcmFudG9yX1JlY29yZD4gPC9HdWFyYW50b3JfTHN0PiA8L0NsaWVu dHM+IDwvRGF0YT4g
JMS Queue logs(Piece of encoded line from request) :
PERhdGE+IDxDbGllbnRzPiA8cmVmZXJlbmN
lTnVtYmVyPmQ4Yzg3ZWE3LWI2OWQtNDUxZC1hNTc3
LTZhZjQ2MTA2YWJmNTwvcmVmZXJlbmNlTnVtYmVyPiA8RG9jdW1lbnRWZXJzaW9uTnVtYmVyPjwv
RG9jdW1lbnRWZXJzaW9uTnVtYmVyPiA8TGFuZ3VhZ2U+PC9MYW5ndWFnZT4gPEJhcmNvZGVfVHJh
bnNpdE5vPjUzMjwvQmFyY29kZV9UcmFuc2l0Tm8+IDxCYXJjb2RlX0FjY291bnRObz41MjwvQmFy
Y29kZV9BY2NvdW50Tm8+IDxGb3JtRGF0ZT5TZXB0
We found that in the request, in the encoded string "+" sign is replacing with "+" while reaching to JMS queue.
Hi Sudhakar,
Will the Hotfix resolves the above issue ??
Thanks & Regards,
SantoshKumar V
JPMorgan Chase & Company
US
Hi Santosh,
I am not understanding your statement, after encoding the property value. How you are setting the values to XML, this values are different with the encoded one ?
Pegasystems Inc.
IN
Hi Santhosh,
'we are first encoding the message with Base64 method and passing it as string to one of the parameter in the request. Later we are doing the Property-set-XML to prepare the XML request and then sending it to External system via Connect-JMs Call'
in the above statement first you are encoding the message and Later you are doing the Property-set-XML to prepare the XML request here the request will be decode by pega and you are sending actual message to Connect-JMS call as request so please add Base64.encode(requestXML) java step before sending the request to Connect-JMS.
I guess Hot fix not required here.
Thanks,
Narasimha