synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Created: (SYNAPSE-493) Synapse sets the HttpCoreRequestResponseTransport status value to INITIAL
Date Tue, 23 Dec 2008 17:48:46 GMT
Synapse sets the HttpCoreRequestResponseTransport status value to INITIAL

                 Key: SYNAPSE-493
             Project: Synapse
          Issue Type: Bug
            Reporter: Amila Chinthaka Suriarachchi

ServletRequestResponseTransport and SimpleHTTPRequestResponseTranspor set this value to WAITING.

This gives a problem with sandesah2. Sandesha2 has this code.

if((toEPR==null || toEPR.hasAnonymousAddress()) &&
			   (makeConnection == null || !makeConnection.booleanValue()) &&
			   (t == null || !t.getStatus().equals(RequestResponseTransportStatus.WAITING))) {
				// Mark this sender bean so that we know that the transport is unavailable, if the
				// bean is still stored.
				SenderBean bean = senderBeanMgr.retrieve(senderBean.getMessageID());
				if(bean != null && bean.isTransportAvailable()) {
				// Commit the update
				if(transaction != null && transaction.isActive()) transaction.commit();
				transaction = null;
				if (log.isDebugEnabled())
					log.debug("Exit: SenderWorker::run, no response transport for anonymous message");

it does not send the response back if the status of the RequestResponseTransport is WAITING.

Setting this initial value to WAITING makes the Sandesha2 works with the synapse.

is it possible to change this initial value to WAITING?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message