Lost connection with cluster3.eu.messagelabs.com[46.226.53.54] while performing the EHLO handshake

I need a solution

Hello, we cannot send emails to any of your customers located on cluster3.eu.messagelabs.com.  Messages queue at our side with the error: lost connection with cluster3.eu.messagelabs.com[46.226.53.54] while performing the EHLO handshake.

I have checked the RBL lists and we appear to be clear for spam activity. Would you please investigate why this would be the case?

Thank you.

0

Related:

  • No Related Posts

7021536: Verastream Host Integrator Event Handler Examples: Writing Data to JMS Message Queue

About this Event Handlers Example

This event handler is to generate an XML document using data from a table procedure, which is then sent to a JMS (SonicMQ) message queue.

The following sample shows output from all procedures in the CCSDemo model. The same event handler could work with all procedures; however, parameters vary according to the procedure.

<?xml version="1.0" encoding="UTF-8"?>

<Transactions>

<GetAccount Table="Accounts">

<FilterParameters>

<AcctNumber>167439459</AcctNumber>

</FilterParameters>

<InputParameters/>

</GetAccount>

<AccountSearch Table="Accounts">

<FilterParameters>

<MiddleInitial>c</MiddleInitial>

<State>ri</State>

<LastName>smith</LastName>

</FilterParameters>

<InputParameters/>

</AccountSearch>

<GetTransactions Table="Transactions">

<FilterParameters>

<AcctNumber>167439459</AcctNumber>

</FilterParameters>

<InputParameters/>

</GetTransactions>

</Transactions>

It is undesirable for an exception to interfere with procedure execution (unless this is the intended behavior), so log any XML-related exceptions and continue processing.

Parameters for connecting to the JMS queue can be hard coded or read from the Verastream properties files script.properties (server) or dt_script.properties (Design Tool).

Event Handler Code

This Verastream Event Handler example has 3 steps:

  1. Generate an XML document from procedure filter and data parameters.
  2. Convert the XML document to a string or a file.
  3. Connect to a (SonicMQ) JMS queue and submit the XML string .

The first two steps are functions called from the main handler method. generateXMLdocument() generates an XML document from input parameters, filter and data parameters, appending each key/value parameter pair as an element node to either a FilterParameter or InputParameter parent node. outputDoc2String() serializes the XML document to a string, transactionXML.

public ProcedureRecordSet

executeProcedure(ExecuteProcedureEvent event)

throws ApptrieveException {

try {

generateXMLdocument(event);

outputDoc2String(transactionXML);



} catch (Exception e) {

//throw new ApptrieveException(e.getMessage());

}

}

The remaining steps continue within executeProcedure(), prior to executing the actual table procedure. Parameters for connecting to the JMS queue are read from script.properties (server only) or dt_script.properties (Design Tool only):

broker = event.getHandlerProperty("broker");

queueName = event.getHandlerProperty("queue");

uname = event.getHandlerProperty("user");

password = event.getHandlerProperty("password");

Next, a transaction queue is opened, the XML string is sent to the appropriate queue, and the queue is closed.

try {

queueTransactionData(broker, uname, password);

sendMessage(queueName, transactionXML);

closeQueueConnection();

} catch (Exception e) {

//System.out.println("Caught exception: " + e.getMessage());

}

Finally, the table procedure is executed, returning the recordset.

return event.defaultProcedure();

Downloading the Example

The zipped Java file and ReadMe, can be downloaded from the Download Library at logTransactionToQueue.zip.

Installing the Event Handler

To install the event handler, follow these steps.

  1. Copy logTransactionToXML.java to the models<your model>scriptssrc directory.
  2. In Design Tool, click Events > Rebuild.
  3. Assuming the build is successful, click Model > Tables, select any procedure, and then click Advanced Properties.
  4. Under Event handler, select logTransactionToXML, and then click Properties and note the description.
  5. Save the changes.

To set the classpath, follow these steps, where <JMS> is the directory that contains the SonicMQ jar files:

vhi.script.classpath=<JMS>\sonic_Client.jar;<JMS>\broker.jar;<JMS>\

gnu-regexp-1.0.6.jar; <JMS>\javax.jms.jar;<JMS>\jaxp.jar;<JMS>\

xercesImpl.jar;<JMS>\xmlParserAPIs.jar;

For use by Design Tool, dt_script.properties in <VHI>etc needs to be edited in a similar manner.

Parameters for connecting to the JMS queue can either be hard-coded or (as here) read from the Verastream properties file: script.properties (server) or dt_script.properties (Design Tool). To use properties, copy the following to the appropriate .properties file.

queue=SampleQ1

user=

broker=<SonicMQ server>:2506

password=

To test the event handler, be sure that the necessary SonicMQ broker is running. The default queues in SonicMQ are SampleQ1, SampleQ2, SampleQ3 and SampleQ4; be sure that the expected queue is availabe. In Design Tool, choose "Procedure test..." from the "Debug" menu. Select table and procedure desired. Enter Procedure filters or data parameters, click "Execute". Some messages are written to the Debug Console. A new message has been added to the desired queue. XML data is readable in the body of the message using a browser.

Related:

Seeing AMQ9456: Update not received for queue QUEUE1, queue manager QMGR_NAME from full repository for cluster CLUSTER_NAME in queue manager error logs.

AMQ9456: Update not received for queue QUEUE1, queue manager QMGR_NAME from full repository for cluster CLUSTER_NAME in queue manager error logs. The repository manager detected a cluster queue that had been used sometime in the last 30 days for which updated information should have been sent from a full repository. However, this has not occurred.

Related:

How to make event when the some message flow sent data to queue?(WebSphere MQ)

Hello team,

Maybe someone know if:
There are 2 message flows(A and B) which are sending the data to 2 queues.
If it possible to see the events when message flow A sent to Queue A and where Flow B sent to Queue B?

PS the installed agents: IBM Integration Bus, WebSphere MQ.

Related: