I've a hawtio 1.4.45 running in Jetty Server A where my camel application is also deployed. There is another camel application and jolokia web agent running on Jetty Server B. I'm able to get basic camel MBean details from both Server A and Server B. However I get to see the logs of only Server A and NOT Server B's. Is there any JMX settings to bring up the logs of Server B to hawtio Dashboard?
Related
Setting up a google cloud platform app with google cloud sql and for the life of me I cannot get a connection to the db when I run the code from google servers.
Following this example: https://cloud.google.com/appengine/docs/java/cloud-sql/?csw=1
I've gotten the non production url constructed properly and can connect with no issues to the cloud sql with this url
Class.forName("com.mysql.jdbc.Driver");
url = "jdbc:mysql://<ip-address>:3306/<database>?user=root";
So that's all good. This is the url I'm building for the prod connection.
Class.forName("com.mysql.jdbc.GoogleDriver");
url = "jdbc:google:mysql://<project-id>:<cloud sql instance name>/<database>?user=root";
I got the Project ID from the dashboard and the Instance ID SQL Instances List, database is the same as the non prod value and since non prod works I'm confident that's alright
Product and Instance ID locations I pulled them from
After deploying it all out I get the error message:
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
appengine-web.xml does have use-google-connector-j set to true and I saw that for the second generation cloud sql you do not need to specify your app on the authorization list in cloud SQL.
Any help would be appreciated
https://cloud.google.com/sql/docs/dev-access#gaev1-csqlv2-connect
You should look at "instance connection name" in "Instance details" of your instance. For second generation, it's "project-id:region-name:cloud-sql-instance-name", not "project-id:cloud-sql-instance-name" as in the first generation.
When trying to connect to GCP SQL from google cloud run, do not forget to enable connection to GCP SQL from the google cloud run service level settings.
Having the setting disabled (default) can also cause the communications link faulure error.
I am trying to setup SignalR for use in a load balanced environment with two web servers behind a load balancer and a separate database server.
I am using the SQL Server Backplane. As recommended in the official documentation, I at first turned on the Service Broker for the database. I observed that with the Service broker turned on Messages take much longer to get pushed from server to client. Why would this be the case ?
I am using Hawt.io to monitor my Apache Camel java app, but I have found that if I let it run I cannot use jvisualvm (and similar tools) to profile my app. It seems Hawt.io is using the connector that Camel exposes so jvisualvm cannot connect to the jvm.
What can I do to have Hawt.io and still be able to use jvisualvm?
Thank you!
Can JConsole connect to your JVM too?
Hawtio just connects to Jolokia on the server side; which just exposes JMX over HTTP/JSON; so the hawtio console doesn't itself change JMX in any way.
Incidentally are you using Local connector to connect from the hawtio web app into a separate JVM? Only that approach does add a jolokia agent dynamically to the JVM you are trying to connect to. If thats whats causing the issue - don't use it - and just configure your own Jolokia agent in your JVM?
I have a an admin and a managed server. A JMS server is targeting the admin server. The JMS Module which contains the Queue and the Connection Factory is targetting both the admin and the managed server.
When my application is deployed on the admin server everything works. But when is deployed on the managed server i get the following excpetion
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'CONNECTION_F'. Resolved ''; remaining name 'CONNECTION_F'
I can see from the JNDI tree of the managed that CONNECTION_F is not present...
Am I missing something? Something wrong configured on the domain?
I am using Weblogic 11g.
Please configure your JMS server on the managed server too.
I have 2 application servers, one is the real production server and another a "backup" server which can go live if the production app server is down. I want an apache webserver which will send incoming requests to both application servers. I do not expect the apache web server to crash, so am fine with "single point of failure".
I know that apache has a mod_proxy_balancer module, but can it be used for replication rather than load balancing? 99% of my http traffic is from some remote devices which do not need any kind of ui. UI is only used for maintenance and reports.