-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
salem alaykom brother #9
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i have a problem when i sending request to the notification microservice , rabbitmq didnt receive the request and i got this message
2022-05-08 10:03:34.390 INFO [customer,eafc83ec63be9b99,dbcbc950693251ce] 18336 --- [nio-8080-exec-2] com.bramli.amqp.RabbitMQMessageProducer : Publishing to internal.exchange using routingKey internal.notification.routing-key. Payload: NotificationRequest[toCustomerId=1, toCustomerName=bramli@gmail.com, message=Hi Mohamed, welcome to Amigoscode...]
2022-05-08 10:03:34.399 INFO [customer,eafc83ec63be9b99,dbcbc950693251ce] 18336 --- [nio-8080-exec-2] o.s.a.r.c.CachingConnectionFactory : Attempting to connect to: [localhost:5672]
2022-05-08 10:03:34.553 INFO [customer,eafc83ec63be9b99,dbcbc950693251ce] 18336 --- [nio-8080-exec-2] o.s.a.r.c.CachingConnectionFactory : Created new connection: rabbitConnectionFactory#62f3ad90:0/SimpleConnection@55adccf1 [delegate=amqp://guest@127.0.0.1:5672/, localPort= 64503]
2022-05-08 10:03:34.630 INFO [customer,eafc83ec63be9b99,dbcbc950693251ce] 18336 --- [nio-8080-exec-2] com.bramli.amqp.RabbitMQMessageProducer : Published to internal.exchange using routingKey internal.notification.routing-key. Payload: NotificationRequest[toCustomerId=1, toCustomerName=bramli@gmail.com, message=Hi Mohamed, welcome to Amigoscode...]
2022-05-08 10:03:34.641 ERROR [customer,,] 18336 --- [ 127.0.0.1:5672] o.s.a.r.c.CachingConnectionFactory : Shutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no exchange 'internal.exchange' in vhost '/', class-id=60, method-id=40)
The text was updated successfully, but these errors were encountered: