I have deployed an hawtio enabled spring-boot application in an openshift environment. But I am facing issue in accessing Jolokia endpoint through hawtio.
I noticed On the pod logs of my application, that set of actuator endpoints are exposed during startup where the Jolokia endpoint is not listed in that.
But I also could observe the below information in the startup logs
Jolokia: Agent started with URL https://ipaddress:8778/jolokia/
Bascially I suspect a conflict between the Jolokia endpoint that comes with spring-actuator and Openshift default Jolokia capabilities causing this issue.
Any Idea or Suggestion about the issue and fix?
This issue is resolved now
Solution: Disable the default Jolokia in openshift.
This issue has been resolved by disabling the default Jolokia through environment variable in openshift as per the documentation . Added the below Env variable:
AB_JOLOKIA_OFF: true
Related
We have a camel application integrated with hawtio and deployed in openshift environment. This application has been scaled into two pod and exposed to the outside world through openshift route.
So through hawtio actuator url, when we changed the camel routes on runtime, it has been reflected on either of the pods and not in both. We are looking for a solution, where we can update the camel route on both the pods through hawtio url.
Anybody faced a similar sort of issue? please advice.
Hawtio online is the solution for OpenShift:
https://github.com/hawtio/hawtio-online
That said, generally it's not recommended to change Camel routes on the fly on each pod. You can instead redeply the changed deployment and then let it replicate the pods on OpenShift.
I have spring boot admin server deployed in openshift with the help of fabric8 maven plugin
And also i have several applications deployed in openshift.
Spring boot admin server (SBAS) use spring cloud kubernetes discovery to discover services (applications) registered / running in namespace / cluster, which is automatic client discovery.
SBAS discovered as expected, its fine but some applications shown / registered in SBAS use http and some use https to check the health as like below
I have no idea, why SBAS use http for some apps and for https for some apps to check the health.
Since SBAS use https and port 8443 it shows applications are offline but those applications are exposed in http 8080 only
I have compared applications code and openshift configurations but i don't see any difference and how to fix this issue.
I am new to all above concepts could some one help me ?
I didn't find solution for this issue, but i did work around which helped me.
Since i am using only one port 8080, i have deleted other ports such as 8443 and 8778 via openshif yml as shown below. but you have you have to expose more ports this won't help.
Using the last version of ngsi-proxy to make Orion related wirecloud components work I get the following error when configuring my Orion Source component:
2fb0de97f49a.js:1737 GET http://localhost:3000/eventsource/12caae10-30eb-11e7-95ac-d72bca8f4488 net::ERR_CONNECTION_REFUSED
My configuration of the component is the following:
And I am running both Orion Context Broker (v1.7) and Wirecloud (v1.0) running locally. Version of the Orion Source operator is the latest I have found (3.0.7). No security is configured.
Could anyone help me to figure out what I am doing wrong?
The problem was that the ngsi-proxy didn't answer properly. I solved by using the public ngsi-proxy: https://ngsiproxy.lab.fiware.org (as it comes by default).
I have created instance on google cloud platform (allowed http traffic). Used Ubuntu 14.04 OS. Installed oracle java8 and apache-tomcat.Placed war file in tomcat webapps and started server. Server started successfully.
Question is how to access my application, tried accessing external ip of instance from web browser but no response.
Can anyone tell me the process or missing things I have not done.
Thanks in advance.
I had the same issue and eventually solved it
In my case the solution was simple.Check the firewall rule is really tcp:8080 and not tcp:80 as created by default.
Changed this and finally saw my tomcat welcome page.
1)Added http port (8080) in firewall rules in Networking section
2)Refreshing VM instance by click refresh option before accessing with external ip followed by http server port(8080)
I hope after following first step, need to refresh VM instance to access web serve with external IP
I can not configure the proxy to download the dependencies:
Initially when I tried to build the project. received the message timeout. Now gotta find a configuration file that solved my problem in parts.
the file is net.properties which is inside the directory of the jdk, it is where I can specify the proxy server but can not get past the User and password for authentication.
any idea what to do?
You could try setting the following additional parameters in your net.properties file.
http.proxyUser=xxxxx
http.proxyPassword=xxxxx
Else, you can setup a local proxy server (with no authentication) which supports authentication to the proxy server you are using and point your net.properties to it.
Cheers.