I am trying to deploy the hawtio-default-offline-1.3.1.war (into JBoss EAP 6.2) and I see this message in the logs:
10:16:07,988 WARN [io.hawt.jvm.local.JVMList] (ServerService Thread Pool -- 65) Local JVM discovery disabled as this JVM cannot access com.sun.tools.attach.VirtualMachine due to: com/sun/tools/attach/VirtualMachine
So I don't have a local tab when I start up hawtio. Is this OK? This is my local Windows laptop and I am deploying the hawtio WAR alongside my app WAR and I am launching it using the JBoss bat file. I do a jps and I can see the JBoss server running.
Appreciate any pointers, thanks!
Yes this is okay, the WARNING is only about the connect plugin, not being able to use the local discovery. You can always use remote discovery, also to connect to local.
But if you only need that hawtio application deployed in your EAP to manage and monitor whats running in the same JVM then this is no problem.
There is also a FAQ at hawtio about related to this.
http://hawt.io/faq/
Related
I got an issue with my environment I guess.
I use Eclipse Photon and WildFly 11 for Maven Projects.
The issue is when I start my WildFly server on Eclipse. I wait few seconds then I have the following message :
19:46:06,398 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) started in 24044ms - Started 674 of 900 services (355 services are lazy, passive or on-demand)
But my server seems to not work correctly. I'll explain:
After I start the server and the message is displayed, I can access to localhost:8080/myproject but, when the timeout setting to start server is reach (450 seconds by default) the server stops. Like it wasn't fully started.
Furthermore, if I go to -> Servers -> WildFly 11 -> Server Details, I see the mention Not Connected and nothing else while I should get some folder like Attributes, Core Services, Deployments, etc.
I tried reinstall Eclipse, WildFly 11 and 13, and I tried with project in the server and with an empty server, with a new workspace... The issue is still there.
Has anyone ever had this concern or has any leads to solve it?
I am using tomcat 7.0.8 in windows server 2008 remote machine(using it a server machine). Where I have hosted my java webapp running on port 80.
I start the tomcat server by running the startup.batch file. The issue is that the tomcat server shutdowns automatically whenever logoff from remote machine and not using the application for sometime like 30-40mins. I even disabled the tomcat shutdown 8005 but still the problem persists.
Please help me to solve this.
Thank you.
As you can see, there's the new instructions:
https://docs.jboss.org/author/display/AS71/JMX+subsystem+configuration
And the old RMI instructions:
https://docs.jboss.org/author/pages/viewpage.action?pageId=21627109
I can get the new instructions working, but we use nagios, which only allows checking JMX via RMI, so I need to get RMI JMX working.
Does anyone have a solution for this?
I can't use the old instructions because it says <jmx-connector> is no longer supported.
I've added the following to my JAVA_OPTS on JBoss startup:
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl -Djava.rmi.server.hostname=10.20.2.50
but i can't get jconsole to connect to service:jmx:rmi:///jndi/rmi://10.20.2.50:12345/jmxrmi
(PS. If anyone with redhat paywall access could report back on the answer here: https://access.redhat.com/solutions/263763 that would be swell :P)
To connect to JMX the URL entered should be in the format
service:jmx:remoting-jmx://{host_name}:{port}
Standalone mode
where {port} is the native management interface of the AS7 installation being monitored (default=9999).
Domain mode
where {port} is the JMX subsystem interface of the AS7 installation being monitored (first server=4447, port-offset=150 next server).
<subsystem xmlns="urn:jboss:domain:jmx:1.1">
<show-model value="true"/>
<remoting-connector use-management-endpoint="false"/>
</subsystem>
Both modes
Outside localhost you have to set -Djboss.bind.address.management or inside xml (standalone.xml / host.xml).
Once connected the capabilities provided by jconsole can be used as normal.
Authentication
The connector is making use of JBoss Remoting to communicate with the server, for this reason the exact same authentication mechanisms as are used by the CLI will apply here.
Local
For processes running local to the AS7 installation we support a local authentication mechanism which allows clients to verify their identity by sharing a token on the filesystem with the server - this mechanism runs silently without any further user interaction required.
Username / Password
Where local authentication is not possible such as if the client is running as a different user than the AS7 process or is running on a remote installation by default the next mechanism to be used is username / password based. Where this mechanism is used the username and password of a user in the ManagementRealm if using the default management connector (port 9999) or in the ApplicationRealm if using the remoting connector (port 4447) should be supplied in the boxes on the 'New Connection' screen before the 'Connect' button is clicked.
The $JBOSS_HOME/bin/add-user.sh (Linux) or $JBOSS_HOME/bin/add-user.bat (Windows) scripts can be used to add these users. Make sure to choose between Management User and ManagementRealm vs Application User and ApplicationRealm depending on whether you're using the default management connector or the remoting connector (usually used with domain mode or when connecting remotely).
Necessary libraries to connect JMX over JBoss Remoting
The JMX MBeanServer is accessible using JBoss Remoting through the management connection. Therefore, it is necessary to add the following libaries from the modules directory of the EAP6 / AS7 distribution to the classpath of the monitoring application:
org/jboss/remoting3/remoting-jmx
org/jboss/remoting3
org/jboss/logging
org/jboss/xnio
org/jboss/xnio/nio
org/jboss/sasl
org/jboss/marshalling
org/jboss/marshalling/river
Ref: Using jconsole to connect to JMX on AS7
Other resource: Connecting VisualVM with a remote JBoss AS 7 / EAP6 JVM process
EDIT:
JBoss EAP 5 supports JMX monitoring using RMI, where JBoss EAP 6 does not. EAP 6 uses “remoting-jmx” instead of “rmi”.
You should look for another solution, as SNMP, or proper plugin for nagios
See:
JVM monitoring via SNMP of JBoss EAP 6 worker nodes with pnp4nagios Template
Jboss SAR MBean and Perl plug-in for Nagios compatible with Jboss 7.1.1
I have an app deployed to my local WebLogic instance (10.3.6) on my Win7 laptop. It's creating Beans through Spring and registering them in the local MBeanServer. I can open up VisualVM, see the "WebLogic" process and see the mbeans that I've registered. This works fine.
I then wanted to set up my JVM for remote JMX access. I took the simple-minded approach for now and set the following properties:
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8888 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=true
I made sure the "jmxremote.access" and "jmxremote.password" file in my JRE was set appropriately.
I started it up, then opened up VisualVM on my Linux box and created a remote host entry for the IP address of my laptop, then a JMX connect to port 8888, and specified the name:pwd pair I set in the jmxremote.access and jmxremote.password files. This all worked fine. I could see all the same registered mbeans.
Then, I went back to my laptop and looked my local VisualVM, and I saw that there was no "WebLogic" process. It appears that enabling my JVM for remote JMX access has disabled local access. Is this supposed to happen? Is there a way to configure this? This isn't necessarily a big problem, I just need to understand it.
There is a Webservice written in Java (using jax-ws api's), already deployed on server. Suddenly, it has started giving wierd results, for some HTTP requests, that I could not reproduce on my local-box. Is it possible that I fire the HTTP request on the same server, and start debugging the code on eclipse installed on my local box.
Please help me with the steps for the same.
Thanks
On what application server are deployed your web service ?
You need to enable remote debug on your Tomcat, JBoss, Websphere, whatever application server, and just need to create a remote debug task in eclipse to connect on the right ip/port.
This is all you have to do.
To activate remote debugging for your application server, just add the following line to the JAVA_OPTS: -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
For eclipse you can follow this link