I am setting up federation on one rabbitmq broker (B), with another broker as the upstream broker (A).
I'm getting this error on trying to run the command to set up the upstream broker.
localhost:$ sbin/rabbitmq-plugins enable rabbitmq_federation
The following plugins have been enabled:
rabbitmq_federation
Plugin configuration has changed. Restart RabbitMQ for changes to take effect.
localhost:$ sbin/rabbitmq-plugins enable rabbitmq_federation_management
The following plugins have been enabled:
rabbitmq_federation_management
localhost:$ sbin/rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://localhost:5672","expires":3600000}'
Setting runtime parameter "my-upstream" for component "federation-upstream" to "{\"uri\":\"amqp://localhost:5672\",\"expires\":3600000}" ...
Error: Validation failed
component federation-upstream not found
I did restart the broker after enabling the federation plugins. Why am I getting this error "component federation-upstream not found" ?
I could set up the upstream broker and policy through the Management UI, but federation is still not working.
I got the same error:
"validation failed component federation-upstream not found"
which went away after I installed the rabbitmq_federation plugin.
Here's my sequence:
Installing rabbitmq_federation_management
getting error
Installing rabbitmq_federation and that cleared the error
Related
I have started the jboss server by copying the war to deploy folder in jboss. But it was throwing the error as the artifact not deployed. Is there any particular configuration to be followed to make the artifact deployed.
09:25:00,894 ERROR [ProfileServiceBootstrap] Failed to load profile:
Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS)
DEPLOYMENTS IN ERROR:
Deployment "vfszip:
<>../webapp-war-1.14.0-SNAPSHOT.war/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI=http://java.sun.com/xml/ns/javaee location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd
We are setting up a new DSE 5.1.0 cluster from opscenterd but keep facing this error.
ERROR: Received error from node event-subtype="MeldError" job-id="127e28d3-1b1c-4d63-8f65-f33bb3b100e0" name="Cassandra-4" ssh-management-address="192.168.150.209" node-id="7d946773-13ec-4ca7-9855-0cd032dd4a9b" event-type="error" message="OS platform (CentOS Linux, 7.4.1708, Core) is not supported for DSE 5.1.0. If absolutely necessary, this check can be turned off with the disable_platform_check configuration setting." (opscd-pool-0)
ERROR: Install job 127e28d3-1b1c-4d63-8f65-f33bb3b100e0 failed! (async-thread-macro-11)
INFO: Install job finished for node name="Cassandra-4" ssh-management-address="192.168.150.209" node-id="7d946773-13ec-4ca7-9855-0cd032dd4a9b" (async-thread-macro-10)
Also, we've disabled disable_platform_check and set the value to False (with capital F). But same error.
The flag should be "true". Try adding this line in the opscenter.conf
[lifecycle_manager]
disable_platform_check = True
When I'm starting the MobileFirst Server in debug mode, it fails loading with the following error message:
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
Error occurred during initialization of VM
agent library failed to init: jdwp
How Can I solve this?
The MobileFirst Development Server is by default in debug mode... so when you try to start the server using the "debug mode" icon, it fails in doing so because the debug definition cannot be set twice, which is what the error message says.
To start the server in debug mode, simply start it as you would normally do it, by clicking on the "play" button.
After doing so, you can spot the following line: "Listening for transport dt_socket at address: 10777".
This means the server started in debug mode.
I have install latest version of IBM Worklight on Marketplace of eclipse juno. I have create a new project and then run my project Run As > Run on Worklight Development Server. then i have face an error on the server. Please Help me.
Thanks
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
objc[42627]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
/Users/apple/Downloads/eclipse 2/plugins/com.worklight.studio.plugin_6.2.0.00-20140904-1709/liberty/wlp/bin/server: line 710: 42627 Abort trap: 6 "${JAVA_CMD}" "$#"
Your Log says Address Already in use. Restart your eclipse. Make sure process is killed.
Either your eclipse did not exit gracefully or some other application is using the port.
If some application is using the port go to server view of eclipse, expand "worklight development server" and change port in "server.xml" file. Hope that helps
According to your error message it is clearly saying that address already in use , this means the port number id using java.exe in background process.so this time if you stop server also this will not release.For this please do the following.
1.Download TCPView from http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx for windows.
2.Install TcpView , after that you will find the port number say 10080.Right click on port number and end process.Now Clean the project and run the server.
Hope this helps.
I am running 'mvn clean install -Dmaven.test.skip=true' command for a web application. but it gives following error. I set the catalina home as an environment variable. i am using maven 3.1.1 version. Please help me
FATAL ERROR in native method: JDWP No transports i
nitialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[WARNING] [talledLocalContainer] ERROR: transport error 202: bind failed: Addres
s already in use
[ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:star
t (start-container) on project RCMigrationWebApp: Execution start-container of g
oal org.codehaus.cargo:cargo-maven2-plugin:1.2.4:start failed: Failed to start t
he Tomcat 7.x container. Deployable [http://localhost:8080/cargocpc/index.html]
failed to finish deploying within the timeout period [120000]. The Deployable st
ate is thus unknown. -> [Help 1]
Probably you have to kill any process running at 8080, looks like the port is already in use..
ERROR: transport error 202: bind failed: Address already in use
Port in use. Run netstat -bv if you are using Windows. You will get to know which process is holding up the port. With your stackTrace, it looks very obvious.
Let me know if it helps.