1
我正在使用AMQP将Jasure服务总线与Java qpid客户端一起连接到Spring JMS。Spring jms ListenerContainer与使用Qpid客户端的AMQP抛出异常连接到Azure服务总线分区时主题
我将服务总线扩展到高级层，因为主题是默认分区的，无法从门户或Azure服务总线管理库修改我在SimpleMessageListenerContainer的开始处遇到以下问题。
的javax.jms.JMSException：无法打开一个主题客户端的实体类型用户。 TrackingId：74bcb8d5-5d05-4239-9dad-cb2133015c29_B19，SystemTracker：servicebus-topic：topic：dumb-pipe〜127 | sink-alpha-test-processing-subscription，时间戳：2017/5/22 2:40:45 TrackingId ：f572fcfb24dc47bf9ef3968bdfa99666_G17，SystemTracker：网关2，时间戳：2017年5月22日下午二时40分44秒[状态= AMQP：不被允许]
依次为： -
2017-05-22 16:40:44.772 INFO 14268 --- [windows.net:-1]] o.a.q.j.s.SaslMechanismFinder : Best match for SASL auth was: SASL-PLAIN
2017-05-22 16:40:45.376 INFO 14268 --- [windows.net:-1]] o.a.q.j.JmsConnection : Connection ID:c27375bc-e3e2-41a9-90a4-8e1bb1e17f8a:1 connected to remote Broker: amqps://servicebus-topic.servicebus.windows.net?amqp.idleTimeout=500000
2017-05-22 16:40:45.377 INFO 14268 --- [ main] o.s.j.c.CachingConnectionFactory : Established shared JMS Connection: [email protected]
2017-05-22 16:40:46.499 WARN 14268 --- [windows.net:-1]] o.a.q.j.p.a.b.AmqpResourceBuilder : Open of resource:(JmsConsumerInfo: { ID:c27375bc-e3e2-41a9-90a4-8e1bb1e17f8a:1:1:1, destination = dumb-pipe }) failed: Cannot open a Topic client for entity type Subscriber. TrackingId:74bcb8d5-5d05-4239-9dad-cb2133015c29_B19, SystemTracker:servicebus-topic:topic:dumb-pipe~127|sink-alpha-test-processing-subscription, Timestamp:5/22/2017 2:40:45 PM TrackingId:f572fcfb24dc47bf9ef3968bdfa99666_G17, SystemTracker:gateway2, Timestamp:5/22/2017 2:40:44 PM [condition = amqp:not-allowed]
2017-05-22 16:40:46.520 WARN 14268 --- [ main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'domainListenerContainer' defined in class path resource [ServiceBusConfig.class]: Invocation of init method failed; nested exception is org.springframework.jms.UncategorizedJmsException: Uncategorized exception occurred during JMS processing; nested exception is javax.jms.JMSException: Cannot open a Topic client for entity type Subscriber. TrackingId:74bcb8d5-5d05-4239-9dad-cb2133015c29_B19, SystemTracker:servicebus-topic:topic:dumb-pipe~127|sink-alpha-test-processing-subscription, Timestamp:5/22/2017 2:40:45 PM TrackingId:f572fcfb24dc47bf9ef3968bdfa99666_G17, SystemTracker:gateway2, Timestamp:5/22/2017 2:40:44 PM [condition = amqp:not-allowed]
请注意，一切当使用未分区主题时似乎很好（生产者以及消费者）。
我发现现在使用Azure服务总线check Latest added features from service bus documentation的AMQP协议支持分区实体。