F
Fuelfire
Guest
Hi, Anand! I have problems with receiving messages :-( I modified test_get.p this way: /*------------------------------------------------------------------------ File : Get.p Purpose : Syntax : Description : Author(s) : Created : Wed Mar 22 17:06:44 MSK 2017 Notes : ----------------------------------------------------------------------*/ /* *************************** Definitions ************************** */ BLOCK-LEVEL ON ERROR UNDO, THROW. /* ******************** Preprocessor Definitions ******************** */ /* *************************** Main Block *************************** */ DEFINE VAR QueueManager AS CHAR NO-UNDO. DEFINE VAR QueueName AS CHAR NO-UNDO. DEFINE VAR CMessage AS CHAR NO-UNDO. DEFINE VARIABLE ptpsession AS HANDLE. DEFINE VARIABLE consumerH AS HANDLE. DEFINE VARIABLE stillWaiting AS LOGICAL NO-UNDO INITIAL TRUE. ASSIGN QueueManager = "RemoteCF" QueueName = "TEST.Q". /* Creates a session object. */ RUN jms/jmssession.p PERSISTENT SET ptpsession ("-H localhost -S 3620 -AppService AD.sonicMQ1 -DirectConnect"). RUN setBrokerURL IN ptpsession (INPUT QueueManager). /* Set user credentials. */ RUN setUser IN ptpsession (INPUT "swiftmq"). RUN setPassword IN ptpsession (INPUT "swiftmq"). /* Connect to the broker. */ RUN beginSession IN ptpsession. /* Subscribe to the Sample.Q1 queue. Messages are handled by the "messageHandler" internal procedure. */ RUN createMessageConsumer IN ptpsession (THIS-PROCEDURE, /* This proc will handle it */ "messageHandler", /* name of internal procedure */ OUTPUT consumerH). /* Do not create a new message for each received message */ RUN setReuseMessage IN consumerH. RUN receiveFromQueue IN ptpsession (QueueName, /* name of queue */ ?, /* No message selector */ consumerH) NO-ERROR. /* Handles incoming messages*/ /* Start receiving messages */ RUN startReceiveMessages IN ptpsession. RUN waitForMessages IN ptpsession ("inWait", THIS-PROCEDURE, ?). RUN deleteSession IN ptpsession. /* Wait forever to receive messages since "u1" is never applied. WAIT-FOR u1 OF THIS-PROCEDURE.*/ MESSAGE cMessage VIEW-AS ALERT-BOX. RETURN "0". PROCEDURE messageHandler: DEFINE INPUT PARAMETER messageH AS HANDLE. DEFINE INPUT PARAMETER msgConsumerH AS HANDLE. DEFINE OUTPUT PARAMETER replyH AS HANDLE. /* Creates a reply message. The reply is published automatically when control returns to the ABL-JMS implementation. */ ASSIGN CMessage = DYNAMIC-FUNCTION('getText':U IN messageH). RUN deleteMessage IN messageH. ASSIGN stillWaiting = FALSE. END. FUNCTION inWait RETURNS LOGICAL: RETURN stillWaiting. END. But when I run the program - it hangs. I do not understand where I made a mistake. Let me remind you that I want to call the program for receiving messages from the application server (PASOE). When I interrupt execution of program I see in sonicMQ1.server.log: S-0011>(Mar 31, 2017 10:16:29:436) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: Startup Parameters: jmsServerName: Point-To-Point brokerURL: RemoteCF user: swiftmq password: swiftmq clientID: null pingInterval: transactedPublish: false transactedReceive: false singleMessageAck: false symbiontAdapter: false jmsDomain: true S-0011>(Mar 31, 2017 10:16:29:436) S-0011: receive message queue size set to 10 S-0011>(Mar 31, 2017 10:16:29:437) S-0011: browse message queue size set to 500 S-0011>(Mar 31, 2017 10:16:29:437) : In SessionContainer() S-0011>(Mar 31, 2017 10:16:29:441) : Looking up ConnectionFactory in JNDI Object Store S-0011>(Mar 31, 2017 10:16:29:442) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: Using connection values: 26,null,true,,true,false,-1,-1,false,0,false,false,,10000,0,30,false,60,0,20,0,,swiftmq,swiftmq,depotest2,localhost S-0011>(Mar 31, 2017 10:16:29:628) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: A JMS session has been created. (9291) Thread-30>(Mar 31, 2017 10:16:29:636) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: receive(): Request to receive from: TEST.Q. Thread-31>(Mar 31, 2017 10:16:29:636) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: getNextMessage(): Client requests next message. Thread-30>(Mar 31, 2017 10:16:29:640) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: createListener(): Message listener is set. Thread-30>(Mar 31, 2017 10:16:29:641) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: start(): Starting message reception. Thread-30>(Mar 31, 2017 10:16:29:642) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: start(): Message reception started. S-0019>(Mar 31, 2017 10:30:33:797) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: stop(): Stopping message reception. S-0019>(Mar 31, 2017 10:30:33:802) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: stop(): Message reception stopped. S-0019>(Mar 31, 2017 10:30:33:802) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: Client was disconnected without calling deleteSession()! (9294) Thread-31>(Mar 31, 2017 10:30:33:802) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: getNextMessage(): Sending SHUTDOWN message to the client. S-0019>(Mar 31, 2017 10:30:33:805) 172.25.197.193::sonicMQ1::3620::2a52856389d3b6a3:-6eb6a82c:15b23327852:-7fdc: The JMS session has been closed. (9295)
Continue reading...
Continue reading...