devinbost commented on issue #6332: (Flaky-test) Intermittent failure of 
ProxyParserTest.testRegexSubscription
URL: https://github.com/apache/pulsar/issues/6332#issuecomment-590554046
 
 
   Here's the chain of events in the logs during the success-case around when 
the problem occurs:
   
   ```
   20:49:21.322 
[pulsar-client-io-5029-1:org.apache.pulsar.client.impl.ConsumerImpl@550] INFO  
org.apache.pulsar.client.impl.ConsumerImpl - 
[persistent://sample/test/local/topic2][ignored] Subscribing to topic on cnx 
[id: 0x6b207b92, L:/10.1.0.4:38008 - 
R:fv-az59.sa2tkz14bfaudpy2zzhb034ywc.cx.internal.cloudapp.net/10.1.0.4:34623]
   20:49:21.322 
[pulsar-proxy-io-39-1:org.apache.pulsar.proxy.server.ParserProxyHandler@78] 
INFO  org.apache.pulsar.proxy.server.ParserProxyHandler - 
frontendconn:[/10.1.0.4:38008/10.1.0.4:34623] cmd:SUBSCRIBE 
msg:{consumer:0486d,topic:persistent://sample/test/local/topic2}
   20:49:21.323 [pulsar-io-15-4:org.apache.pulsar.broker.service.ServerCnx@760] 
INFO  org.apache.pulsar.broker.service.ServerCnx - [/127.0.0.1:51438] 
Subscribing on topic persistent://sample/test/local/topic2 / ignored
   ```
   
   Here's what it looks like in the failure case:
   
   ```
   20:49:21.343 
[pulsar-client-io-5029-1:org.apache.pulsar.client.impl.ConsumerImpl@550] INFO  
org.apache.pulsar.client.impl.ConsumerImpl - 
[persistent://sample/test/local/topic1][regex-sub-proxy-parser-test-1582577361325]
 Subscribing to topic on cnx [id: 0x604df1da, L:/10.1.0.4:38026 - 
R:fv-az59.sa2tkz14bfaudpy2zzhb034ywc.cx.internal.cloudapp.net/10.1.0.4:34623]
   20:49:21.343 
[pulsar-proxy-io-39-1:io.netty.channel.DefaultChannelPipeline@1164] WARN  
io.netty.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, 
and it reached at the tail of the pipeline. It usually means the last handler 
in the pipeline did not handle the exception.
   java.lang.UnsupportedOperationException: null
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to