Regarding setting JMSMessageID with solclient C api
Hi,
Is it possible to call / set JMSMessageId with the help of solclient C api?
Or can i intgerate JMS api in C code to set JMS realted headers when sending message (via solclient C api)?
Need help on this urgently.
Regards
Amol
Best Answer
-
Interesting. I would have expected that to work. Can you share your C code?
Also an interesting exercise would be to use sdkperf to give us a message dump. This will give us more info about what the JMS app is actually receiving before the headers/properties are translated.
You can download sdkperf at the bottom of solace.com/downloads
And usesdkperf_java.sh -cip localhost:55555 -cu username@vpn -cp password -stl topic -q -md5
Answers
-
Hi @amol_p81,
You sure can! TheJMSMessageIDheader field on a JMS Message maps to theApplicationMessageIDfield in the Solace APIs so in the C API you would just get/set theApplicationMessageIDheaderYou can also see how other header fields map in a table in the docs here: https://docs.solace.com/Solace-JMS-API/Message-Components.htm#Header
Hope that helps
1 -
Interesting. I would have expected that to work. Can you share your C code?
Also an interesting exercise would be to use sdkperf to give us a message dump. This will give us more info about what the JMS app is actually receiving before the headers/properties are translated.
You can download sdkperf at the bottom of solace.com/downloads
And usesdkperf_java.sh -cip localhost:55555 -cu username@vpn -cp password -stl topic -q -md5 -
Marc,
Had a query, when i run the soclient C api example in Intro folder HelloWorldQueuePub process, i dont see any error and able to see Acknowledgement received.
However when executing the sdkperf_java.sh (sdkperf_java.sh -cip localhost:55555 -cu username@vpn -cp password -stl topic -q -md, modifying the parameters accordingly as used for HelloWorldQueuePub), i see ****Error response (403) - Subscription ACL Denied - Topic '........', subscription additions failed.
Error response (400) - Subscription Not Found - Topic ****
Topic used is same as one for HelloWorldQueuePub.
sdkperf version is 7.1.2.33.
solclient version - 7.3.0.3.Please let me know if there is any issue with topic as when executing HelloWorld processes i dont get any errors.
0 -
Need a quick help over here, using solclient C api, the message has the following properties
SolTextMessage={ JMSDeliveryMode:1,JMSDestination:Topic 't.rfds.ds.notify.int5',JMSExpiration:0,JMSMessageID:2,JMSPriority:0,JMSRedelivered,JMSTimestamp:0,JMSProperties:{JMS_Solace_isXML:true,JMS_Solace_DeliverToOne:false,JMS_Solace_DeadMsgQueueEligible:false,JMS_Solace_ElidingEligible:false,Solace_JMS_Prop_IS_Reply_Message:false},SolPayload:{XML:len=295} }
However the JMSProperties is seen as NULL.The format required is
SolTextMessage={ JMSDeliveryMode:2,JMSDestination:Topic 't.rfds.ds.notify.int5',JMSExpiration:1588958554273,JMSMessageID:ID:fe80:0:0:0:250:56ff:fea2:2a21%eth0dff5171eb010b570:4,JMSPriority:0,JMSRedelivered,JMSTimestamp:1588785753229,JMSProperties:
{cobdate:04-MAY-2020,snapshotid:41,valuationcontextid:1b_VAR-1d,statusremarks:,brds_dsloadid:1,rowcount:331,confidence_level:.99,dsloadid:103103087,scenario_context:VaR,package_type:FINAL,horizon:1d,measure_type:VaR,feedid:65,timetaken:6431,ds_wf_status:COMPLETED,datasource:RFDS,dsname:PA HISTSIM HYBRID VAR,runtype:HISTSIM_VAR_RFG,notificationtype:DATASET,grainids:[11b54131428443c9899974420d113cf5],taskid:164,snaptype:VaR_1d_FINAL,JMS_Solace_isXML:true,JMS_Solace_DeliverToOne:false,JMS_Solace_DeadMsgQueueEligible:false,JMS_Solace_ElidingEligible:false,Solace_JMS_Prop_IS_Reply_Message:false}
,SolPayload:{XML:len=438} }
How can i see above with solclient C api?0
