-
Notifications
You must be signed in to change notification settings - Fork 184
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
My Apache Camel application in Quarkus exits through 2 different ports when calling 2 SOAP WebServices in the same logic #5907
Comments
Maybe due to HTTP connection pooling, keep-alive etc? What are you using as the HTTP client to interact with the SOAP services? |
@jamesnetherton As an http client I am using POSTMAN to test SOAP interfaces |
I mean in your Camel application. What's sending the SOAP request? |
This is what I sent in the 2 requests COMANDO LGI
COMANDO LST_DYNSUB https://10.160.12.181:8001/sessionId
@jamesnetherton Do you require more details? |
@cesarjv I understand that you are writing a SOAP client application calling two external SOAP endpoints. From what you have shown, it is not clear, how you send the request to those endpoints. |
With these classes I send the application The ConfigureSSL class is used to configure the call using SSL:
The udbUrl variable refers to the IP variable that is called and is found in the properties: ResRoute
application.properties
No, the SOAP external IP is not governed by a LoadBalancer, it is a unique IP |
I am currently working on a service using Apache Camel and Quarkus, in which I must call 2 SOAP Webservices, one that allows me to obtain a session id (called LGI Command) and the next allows me to consult the information from a mobile number. associated with it (Called LST_DYNSUB Command), passing the session id previously obtained with the LGI Command. The question is that these 2 calls must be made through the same port due to the policies of the application to be called where the aforementioned SOAP interfaces are located, called UDB, the UDB only admits a valid session id in the LST_DYNSUB command if the same port through which the LGI Command.
Testing in Postman does not give me problems and it can be seen that when testing both SOAP interfaces there are no problems, however, when I come to develop my waterfall logic in my Apache Camel and Quarkus development, it can be observed at the destination log level (UDB) that is being sent through different ports.
Called in postman and where it is observed that both interfaces arrive through the same ports:
Called from my microservice with Apache Camel and Quarkus where it is evident that it is arriving through a different port, even though it is within the same logic:
I attach the logic of my Red Route in Apache Camel:
Class Rest Route
UdbLgiCommandProcessorReq
UdbLstDynsubCommandProcessorReq
pom.xml
Does this have any logical explanation as to why it could be happening in Apache Camel and Quarkus?
The text was updated successfully, but these errors were encountered: