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
Support running the gateway with other reactive containers besides netty #145
Comments
Not currently. |
I already have code for this that just needs to be formalized. The difficulty will be running all the tests with other containers. |
@spencergibb can u provide code ? |
This comment has been minimized.
This comment has been minimized.
@spencergibb How is the progress now? Thank you |
None so far |
This comment has been minimized.
This comment has been minimized.
@ghoddg this is likely not going to happen in 2.0.0. For now you have to use netty. |
This comment has been minimized.
This comment has been minimized.
No |
@spencergibb Thanks for update. |
@spencergibb , from above communication, i got understanding that, API Gateway Service with Spring Cloud Gateway will not work with Tomcat as well as Weblogic for now and it will work only with netty. |
This comment has been minimized.
This comment has been minimized.
I just noticed that this error occurs only in the testing mode. When run normally the gateway forwarding works fine. |
Another thing I noticed is that when I use |
It's not. It is used to test the gateway |
@spencergibb It is indeed. The source of my problem was using the |
are u open to pr's for tomcat support? for 2.0 or 2.1 |
@drdamour I already have code #145 (comment). The trouble is testing everything. |
yeah i assumed you meant unit test and thus PR. what type of testing are you referring to then? |
Basically all the integration tests. Anything that spins up a container then makes real network calls thru the gateway. |
k...how are you hoping to structure the tests...duality for every netty test have a tomcat test. or just abstract away the backing implementation in all the tests? or is there some prior art you are looking to follow? |
My guess is rerunning all the tests with some system properties. Copied tests is prohibitive. Most have a base class already. |
how will that work with your maven circle build? just 2+ surefire/failsafe executions? |
jenkins is our canonical build |
85193a0 may have fixed this functionality. The class cast exceptions mentioned here #145 (comment) are now gone. Remaining items:
|
Hmm those would be tests inside the gateway or some separate ones? Cause we could even embed running those tests inside the gateway build. |
Just all the tests already in gateway |
Adds webserver module to host auto-configuration for abover web servers. Adds profiles to core to run all tests with each webserver. fixes gh-145
See #1544 for progress |
@spencergibb Is it possible to use tomcat with gateway now? |
Hi @spencergibb |
@dlsrb6342 it's unrelated to this issue. There's no way to disable the netty beans at this moment. |
Hi @spencergibb Any update when tomcat support will be added to Spring cloud gateway please? |
New anomalies appear. java.lang.ClassCastException: org.springframework.http.server.reactive.TomcatHttpHandlerAdapter$TomcatServerHttpRequest cannot be cast to javax.servlet.http.HttpServletRequest |
I am trying to use tomcat instead netty. To achive this i have excluded netty from dependencies and included tomcat, so my build.gradle dependecies:
Hower it is not enough, i get ClassCastException:
Is it possible to use tomcat with gateway instead netty?
Thanks!
The text was updated successfully, but these errors were encountered: