I created gemfire instance and started a locator, and I was also able to access the HTTP application from browser. Another day when I logged again and start gfsh to connect gemfire install using following command,
gfsh>connect
it gave following output,
gfsh>connect
Connecting to Locator at [host=localhost, port=10334] ..
Exception caused JMX Manager startup to fail because: 'HTTP service failed to start'
Even on connecting to locator,
gfsh>connect --locator=localhost[40405]
Connecting to Locator at [host=localhost, port=40405] ..
Exception caused JMX Manager startup to fail because: 'HTTP service failed to start'
Related
I had Apache Geode cluster running and I was connected to it using gfsh client. In order to test something, I stopped the Cache Server using, "stop server --name=xxxxserver" command. The Cache server stopped successfully.
Further, I stopped the locator using the "stop locator --name=xxxxlocator" command. The locator stopped successfully. However, my gfsh client connection was also disconnected.
Now, I am trying to reconnect my gfsh client to the locator, but it always gives me a 502 bad gateway error. I have tried accessing the pulse url, I get the same error:
"502 Bad Gateway: Registered endpoint failed to handle the request."
What I am missing and how can this be fixed?
If you stopped your locator, it's expected for gfsh and PULSE to be disconnected as there's no JMX Manager they can talk to. You should start your locator again and re-connect, then everything should be fine.
Cheers.
Right. But, the problem is I am unable to start the locator due to the error I have mentioned. I created another cache instance to verify, but don't see this problem. Stopped/started locator with no issues and able to access the pulse as well.
I want to delpoy the Execution Server in follwing environment:
Wildfly17.0.0.Final
JVM memory, min:64m, max:1024m
Execution Server WAR package: kie-server-7.22.0.Final-ee7.war
A message shows in deployment page of Wildfly's HAL Management Console:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kie-server-7.22.0.Final-ee7.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"kie-server-7.22.0.Final-ee7.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
can someone help? thanks in advance!
It seems that you started WildFly with default standalone profile. However Kie server requires standalone-full profile as it uses JMS queues.
Please try to start WildFly with standalone-full profile. For linux based system you can achieve that using command:
./standalone.sh -c standalone-full.xml
I am trying to run a jmeter test script which has a single websocket sampler.It works fine when i run it from single machine through java GUI or command line.
But , When i try to run it on remote host (by running jmeter-server on other machine) then following exception is thrown.
ERROR
- jmeter.engine.ClientJMeterEngine: Error in rconfigure() method java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.lang.ClassNotFoundException: JMeter.plugins.functional.samplers.websocket.WebSocketSampler (no security manager: RMI class loader disabled)
2016/10/06 07:03:20 INFO - jmeter.engine.ClientJMeterEngine: Interrupting RMI Reaper
Both Master/slave jmeter installations are having same version of jmeter(v3.0) and websocket plugin(v1.0.2).
Any other http distributed test runs fine when it is run in same setup.
According to the error message, it looks like the WebSocket plugin is missing on the remote slave. The main pre-requisite of distributed JMeter tests execution is having the same JMeter version with the same config, plugins, 3rd-party libraries, etc. on remove slaves as on the master.
So make sure you have identical setup on master and all the slaves, i.e. install the WebSocket Sampler to all the slaves.
JMeter restart will be required to pick the plugins up
The easiest way of installing JMeter Plugins and keeping them up-to-date is using JMeter Plugins Manager
I'm GlassFish 3.1.2, ActiveMQ 5.1.1 and ActiveMQ 5.8 resource adapter (activemq-rar-5.1.1) I have created a GlassFish cluster with 2 instances. I reference http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/ to assist with the initial deployment/configuration of activemq resource adapter After configuring the Connector Connection Pool via GlassFish Admin Console and enable Ping. When Ping is executed an error occurs: Ping Connection Pool for jms/ActiveMQConnectionFactory is Failed. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details. Ping failed Exception - This pool is not registered with the runtime environment : jms/ActiveMQConnectionFactory Please check the server.log for more details.
appreciate for your replay
by any chance is your glassfish instance in a cluster?. In our case it was failing with the same error message, and we figured out that if the instance is in a cluster, it doesn´t work. Though it works if it is not in a cluster.
We verified this also by checking in the activemq admin console the the consumers were active and receiving message, even if the ping command was failing.
I have a message-driven EJB deployed to a Glassfish 2.x system. When I get a message that causes an exception or isn't able to be sent or consumed, I would like to do one of the following things:
Pause the EJB's subscription to the Topic/Queue
Shut down the EJB itself
Cease consuming messages until I give an 'all clear' or something equivalent
This is all so that I can stop repeatedly throwing exceptions after calling context.setRollbackOnly() on the message.
I've tried connecting to the server via JMX, but from what I've looked at in documentation says that I'd have to persist:
username
password
jmx url
in my EJB somewhere. Can't I access the JMX server from within the EJB in Glassfish without having to know that?