I have a Spring Boot application running on Google cloud container engine.
I have created containers, service and load balancer using kubernetes templates. The load balancer is ingress resource.
When I try to connect to the app using webscoket it does not work on iPad, iPhone.
It works in local environment, when iPad and the Spring Boot server is in the same network.
It works when connecting from Chrome running on PC.
The only combination that fails is from iPad, iPhone to Google Cloud.
I do not have the SSL setup.
Is there any reason why this should not work?
I have finally found the solution. I have replaced the Tomcat with Undertow server in the Spring Boot and it started working correctly.
Basically the issue is that following setup does not work:
WebSocket on iOS --> Google cloud load balancer --> Spring Boot on Tomcat
Maybe I am missing some configuration to make tomcat work.
Related
I have deployed my Rest web services based SpringBoot java application in AWS EC2 server. Its deployed in Apache Tomcat server.
Client-side Angular4 application also deployed on the same server.
When I use a web browser from my desktop it works fine. I can see the logs are writing immediately in the server console.
But when I hit from a mobile browser I don't see any hit and logs in the server console for few minutes. But after a few seconds/minutes, I can see the logs writing on the server.
So what is wrong why it is getting delayed to reach my server from mobile browser?
I wanted to check if somebody has explored the option of deploying Kitura compiled project on TomCat? Basically, is it possible to deploy the build outside IBM cloud environment?
Please note that you can run Kitura instead of Tomcat. Kitura is an embedded web server, you do not need other web server to run a Kitura application. So you can build a Kitura application on macOS/Linux and run the compiled executable on macOS/Linux. It will listen to the port you specify, receive HTTP requests and route them to the request handling code of your application.
Have created Webservice and deployed in weblogic admin sever its working as expected. But customer wants this to be deployed in weblogic managed server and in the deployment there is no error. But not able to access service. Anyone assists on what should be done to make this working in managed server.
You can use the WebLogic admin console to deploy and target your application to the managed server. If the application is already deployed, just update the targetng mode to include the managed server.
We are developing an application using Spring Boot plus Spring web starter. We use Go Pipeline and Parallel Deployment feature of Apache Tomcat 7 to deploy war file to a standalone Tomcat Server. ref
When running the application we can see the logs loading controllers, services and requests, etc.
Once the container is up, the initial requests occasionally lead to an ugly 404.
However, this is an intermittent behavior. Once you refresh browser, subsequent request works.
We wonder what could be the root cause of the intermittent 404 response.
I want to run my WSO2 CEP on IBM Bluemix. Is it possible to host it as a Liberty application or any other option is available there ?
WSO2 CEP is a Java Web application including Tomcat as application server, so you may have to build it from source and push the war on Bluemix to try it working on liberty application server. Anyway between WSO2 CEP prerequisites there is Java Oracle jdk, and Bluemix is running on IBM jdk, so you could have some other problems.
So maybe it could be better to run it on a (group of) Bluemix Container: these are based on Docker containers, so you could create a custom docker image from the (really) several images available, and then you can push it to a Bluemix container on cloud.
Bluemix/Docker containers are fully portable so you can very easily create your one and take it everywhere and also make it scaling very simply on Bluemix cloud environment.
You can start from here
https://www.ng.bluemix.net/docs/containers/container_index.html
https://docs.docker.com/docker/userguide/