You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Arun Dsouza (JIRA)" <ji...@apache.org> on 2013/03/21 22:59:15 UTC
[jira] [Created] (PROTON-274) Proton-C Sending a message to an non
existant Service Bus entity suceeds
Arun Dsouza created PROTON-274:
----------------------------------
Summary: Proton-C Sending a message to an non existant Service Bus entity suceeds
Key: PROTON-274
URL: https://issues.apache.org/jira/browse/PROTON-274
Project: Qpid Proton
Issue Type: Bug
Affects Versions: 0.4
Reporter: Arun Dsouza
Priority: Minor
########## Background ######################
I am using Proton-C to communicate with a queue in Windows Azure Service Bus.
According to the Proton-C Samples the way to check if an operation suceeded is use the pn_messenger_errno function. Its declaration is as follows
/** Returns the error code for the Messenger.
*
* @param[in] messenger the messenger to check for errors
*
* @return an error code or zero if there is no error
* @see error.h
*/
PN_EXTERN int pn_messenger_errno(pn_messenger_t *messenger);
############ Bug ################
Now If I try to send to a SB queue that DOES NOT exist. pn_messenger_errno returns 0.
However if I try to send to an entity in an NON EXISTANT SB namespace. pn_messenger_errno correctly returns a non 0 error code
########### Relavent Proton Traces #############
Connected to INT7-27689-0-2.servicebus.int7.windows-int.net:5671
-> SASL
[0x9871400:0] -> SASL-INIT @65 [:PLAIN, b"\x00owner\x00dexww###########################"]
<- SASL
[0x9871400:0] <- SASL-MECHANISMS @64 [@PN_SYMBOL[:PLAIN, :EXTERNAL]]
[0x9871400:0] <- SASL-OUTCOME @68 [0, b"Welcome!"]
-> AMQP
[0x986c740:0] -> OPEN @16 ["1fcb1ed4-67a6-42d8-aaef-7e8aed0d5977", "INT7-27689-0-2.servicebus.int7.windows-int.net", null, null, null, null, null, null, null]
[0x986c740:1] -> BEGIN @17 [null, 0, 1024, 1024]
[0x986c740:1] -> ATTACH @18 ["sender-xxx", 1, false, null, null, @40 ["zgflsmhbbfyle1", 0, null, 0, false, null, null, null, null, null, null], @41 ["zgflsmhbbfyle1", 0, null, 0, false, null, null], null, null, 0]
<- AMQP
[0x986c740:0] <- OPEN @16 ["305ab36b6dba436a9c0b58546df87c7b_G1", null, 65536, 4999, 60000, null, null, null, null, null]
[0x986c740:0] <- BEGIN @17 [1, 1, 1024, 1024, 7, null, null, null]
[0x986c740:0] <- ATTACH @18 ["sender-xxx", 1, true, null, null, @40 ["zgflsmhbbfyle1", 0, null, 0, false, null, null, null, null, null, null], null, null, null, 0, null, null, null, null]
[0x986c740:0] <- DETACH @22 [1, true, @29 [:"amqp:not-found", "The messaging entity 'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could not be found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013 9:44:53 PM", {:"com.microsoft:stack-trace"="\x0d\x0aServer stack trace: \x0d\x0a\x0d\x0a\x0d\x0aException rethrown at [0]: \x0d\x0a at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) in d:\bt\109356\private\source\ServiceBus\Clients\Microsoft.ServiceBus.Messaging\Common\AsyncResult.cs:line 411\x0d\x0a at Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewayProvider.Microsoft.Cloud.ServiceBus.Gateway.Runtime.IAmqpGatewayProvider.EndResolveAndAuthorize(IAsyncResult result, Int64& containerId, Int32& partitionId, String& entityName, DateTime& authorizationValidToUtc) in d:\bt\109356\private\source\ServiceBus\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Amqp\AmqpGatewayProvider.cs:line 89\x0d\x0a at Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewa
LINK ERROR (amqp:not-found) The messaging entity 'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could not be found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013 9:44:53 PM
[0x986c740:1] -> DETACH @22 [1, true, null]
[0x986c740:0] -> CLOSE @24 [null]
[0x986c740:0] <- END @23 [@29 [:"amqp:not-found", "The messaging entity 'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could not be found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013 9:44:53 PM", {:"com.microsoft:stack-trace"="\x0d\x0aServer stack trace: \x0d\x0a\x0d\x0a\x0d\x0aException rethrown at [0]: \x0d\x0a at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) in d:\bt\109356\private\source\ServiceBus\Clients\Microsoft.ServiceBus.Messaging\Common\AsyncResult.cs:line 411\x0d\x0a at Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewayProvider.Microsoft.Cloud.ServiceBus.Gateway.Runtime.IAmqpGatewayProvider.EndResolveAndAuthorize(IAsyncResult result, Int64& containerId, Int32& partitionId, String& entityName, DateTime& authorizationValidToUtc) in d:\bt\109356\private\source\ServiceBus\Service\Messaging\Microsoft.Cloud.ServiceBus.Messaging\Amqp\AmqpGatewayProvider.cs:line 89\x0d\x0a at Microsoft.Cloud.ServiceBus.Gateway.Runtime.AmqpGatewayListener
SESSION ERROR (amqp:not-found) The messaging entity 'sb://int7-27689-0-2.servicebus.int7.windows-int.net/zgflsmhbbfyle1' could not be found..TrackingId:305ab36b6dba436a9c0b58546df87c7b_G1,TimeStamp:3/21/2013 9:44:53 PM
[0x986c740:0] <- CLOSE @24 [null]
[0x986c740:0] <- EOS
[0x986c740:0] -> EOS
Closed INT7-27689-0-2.servicebus.int7.windows-int.net:5671
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira