Does WireMock support mocking TCP (Java Socket API) calls or can that be achieved via WireMock? Thanks
We are using WireMock already for mocking HTTP calls
Related
A new project consider use Spring Cloud build micro service. But we have many inner RPC call within services.
For performance, how to upgrade Feign support http2?
There are gRPC has give a great example for high performance by http2 but our project based on JVM and Feign and relative annotation is good enough for interface definition.
So, I'm first consider Feign support http2 without SSL to speed up RPC.
Hope there are benchmark on http2 if someone has done.
Thanks.
To use http/2 with feign you just need to replace the Http client Bean with a client that prefers http/2.
With default HttpClient (as opposed to OkHttp), you can just add this as a bean, and feign should use it, or you can build it into the feignClient:
HttpClient client = HttpClient.newBuilder()
.version(Version.HTTP_2)
.build();
ref: https://openjdk.java.net/groups/net/httpclient/intro.html
The OkHttp Client may have http/2
I think you would also have to enable http/2 on the server with:
server.http2.enabled: true
This should allow it to receive incoming requests with http/2.
https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#application-properties.server.server.http2.enabled
What is the difference between using socket to connect to a site, and simply making an HTTP request?
Does the connection established by the sockets make it possible not to authenticate during the request?
What is the difference between using socket to connect to a site, and simply making an HTTP request?
The act of using socket to connect to a site is more basic than making an HTTP request — the former is required by the latter, since a HTTP/TCP request cannot be sent without an established connection.
Does the connection established by the sockets make it possible not to authenticate during the request?
HTTP neither implies authentication.
I refer to this tutorial
: http://seleniumparadise.blogspot.com/2015/07/jmeter-web-socket-testing.html
I am trying to test web socket but it cannot run HTTP Request.
My WebSocket :
ws://localhost:3000/socket.io/?EIO=3&transport=websocket&sid=DemHDCauiFttdm0WAAA9
How to get Socket ID in my web socket ?
I don't think you can test WebSocket protocol using HTTP Request sampler and would recommend using WebSocket Sampler plugin instead. The easiest way to install the plugin is using JMeter Plugins Manager
I am using groovy wslite library(https://github.com/jwagenleitner/groovy-wslite) for consuming SOAP service, it is so simple and very effective but i didn't see any connection pooling while creating http conections under the hood.
Isn't creating a new connection everytime is expensive? trying understand whether it is good practice or not?
What is the default port number that the SOAP protocol works on?
There is no such thing as "SOAP protocol". SOAP is an XML schema.
It usually runs over HTTP (port 80), however.
SOAP (Simple Object Access Protocol) is the communication protocol in the web service scenario.
One benefit of SOAP is that it allowas RPC to execute through a firewall. But to pass through a firewall, you will probably want to use 80.
it uses port no.8084
To the firewall, a SOAP conversation on 80 looks like a POST to a web page. However, there are extensions in SOAP which are specifically aimed at the firewall. In the future, it may be that firewalls will be configured to filter SOAP messages. But as of today, most firewalls are SOAP ignorant.
so exclusively open SOAP Port in Firewalls
SOAP (communication protocol) for communication between applications.
Uses HTTP (port 80) or SMTP ( port 25 or 2525 ), for message negotiation and transmission.