0.5 0 0 27 2 1 196 191 green 0.00 5.1 0.0 40 32 3.80 1287 717.01 4 Queens 071701 4071701 I QN18 Rego Park 4108 1172 568 4 Queens 056800 4056800 I QN34 Queens Village 4105 3389285 1 2014-03-21 12:38:03 2014-03-21 12:54:58 N 1 -73.861373901367188 40.72998046875 -73.851463317871094 40.69384765625 1 3.60 15.5 0 0.5 0 0 16 2 196 258 green 0.00 0.0 0.0 51 39 7.61 1287 717.01 4 Queens 071701 4071701 I QN18 Rego Park 4108 806 20 4 Queens 002000 4002000 E QN53 Woodhaven 4111 3389286 1 2014-03-29 16:54:00...

	select {
	case <-ctx.Done():
		// Returning error here is too noisy.
		return nil
	case c.outQueue <- msg:
		return nil
	}
}

// queueMsg queues a message, with an optional payload.
// sender should not reference msg.Payload
func (c *Connection) queueMsg(msg message, payload sender) error {
	// Add baseflags.
	msg.Flags.Set(c.baseFlags)

### Existing object replication

MinIO also sends with the notifications two headers: `minio-bucket` and `minio-event`. An exchange using the type "headers" can use this information to route the notifications to proper queues.

Note that, you can add as many AMQP server endpoint configurations as needed by providing an identifier (like "1" in the example above) for the AMQP instance and an object of per-server configuration parameters.

	if err = config.Validate(globalSite.Region, globalEventNotifier.targetList); err != nil {
		arnErr, ok := err.(*event.ErrARNNotFound)
		if ok {
			for i, queue := range config.QueueList {
				// Remove ARN not found queues, because we previously allowed
				// adding unexpected entries into the config.
				//
				// With newer config disallowing changing / turning off
				// notification targets without removing ARN in notification