jeremydmiller on master
Apply configurations when updat… Pulsar allows native scheduled … Rename classes to be specific t… and 5 more (compare)
jeremydmiller on master
Make exception_message and exce… Prepend all jasper tables with … Fix typo (compare)
JarrodJ83 on pulsar-cleanup
Add Kafka readme and example (compare)
JarrodJ83 on pulsar-cleanup
Ignore tests not applicabale to… Implement KafkaCallbackChannel (compare)
JarrodJ83 on pulsar-cleanup
Update pkg details Implement DotPulsar channel cal… (compare)
JarrodJ83 on pulsar-cleanup
Apply configurations when updat… Pulsar allows native scheduled … Rename classes to be specific t… (compare)
jeremydmiller on master
Optional Parallel Rabbit MQ lis… (compare)
Even when it only runs one time it always says:
Jasper.Messages:Information: Successfully processed message UpdateFeatureSubscriptions#016cbb46-b9f5-433d-86d0-23eaedc9e5e9 from loopback://retries/
Jasper.Transports:Information: Recovered 1 incoming envelopes from storage
Processing: $Envelope #016cd0d2-9646-4d42-8579-f9c698867afb (UpdateFeatureSubscriptions) from Api@CGPC to loopback://durable/ on default
[... snipped noise ...]
Jasper.Transports:Information: Recovered 1 incoming envelopes from storage
Processing: $Envelope #016cd0d2-9646-4d42-8579-f9c698867afb from Api@CGPC to loopback://durable/ on default
[... snipped more noise ...]
Jasper.Messages:Information: Successfully processed message UpdateFeatureSubscriptions#016cd0d2-9646-4d42-8579-f9c698867afb from loopback://retries/
[... snipped more noise ...]
Jasper.Messages:Information: Successfully processed message UpdateFeatureSubscriptions#016cd0d2-9646-4d42-8579-f9c698867afb from loopback://retries/
RecoverIncomingMessages
kicks in and grabs it also? But I'll be damned to hell if I can figure out where that's happening.
First, this message:
Jasper.Messages:Information: Successfully processed message UpdateFeatureSubscriptions#016cd11a-6c35-483d-a028-fbfe4a5535f4 from loopback://retries/
MessageLogger.MessageSucceeded()
which is hard coded to report the "loopback://retries/" URL (which is called ReplyUri??), no matter what. The other logging I added seems to indicate it's actually coming from "loopback://durable/"
JasperOptions.ScheduledJobs.FirstExecution
and JasperOptions.ScheduledJobs.PollingTime
, which seems to control the durability agent's queue processing. I set them both to 2 minutes (default of 0 seconds and 5 seconds respectively), and the problem seems to go away.