Tomcat Log:
REST Servlet (GET) called
Connecting to server localhost at port 9002
Successfully created a connection to the server
Setting session timeout to 30000 seconds.
This process is on repeat until CPU usage reaches 100% and I have to manually kill server processes.
The Service is reachable via the Aware IM Rest URL, but it does not like the GET verb.
The same Tomcat log message appears when using POST & HEAD verbs, also consumes memory and CPU.
The OPTIONS verb returns a successful code 200 response instantly.
Here is the result of this using OPTIONS:
TIMELINE:
- Preparing request to http://192.168.0.17:8081/AwareIM/REST/CR/SI_REST_Service
- Using libcurl/7.51.0-DEV OpenSSL/1.0.2j zlib/1.2.8 libssh2/1.6.1_DEV
- Enable automatic URL encoding
- Enable SSL validation
- Enable cookie sending with jar of 10 cookies
- Connection 8 seems to be dead!
- Closing connection 8
- Trying 192.168.0.17...
- TCP_NODELAY set
- Connected to 192.168.0.17 (192.168.0.17) port 8081 (#9)
OPTIONS /AwareIM/REST/CR/SI_REST_Service HTTP/1.1
Host: 192.168.0.17:8081
User-Agent: insomnia/5.16.6
Accept: /
< HTTP/1.1 200
< Allow: GET, HEAD, POST, OPTIONS
< Content-Length: 0
< Date: Thu, 12 Jul 2018 05:16:01 GMT
- Curl_http_done: called premature == 0
- Connection #9 to host 192.168.0.17 left intact
=== end timeline ===
I have set up the process to initiate the service within Aware IM, but it's the same behaviour as above, for GET, POST and HEAD verbs.