I installed multiple rabbitmq Services on our dev environment and enabled the management plugin and gave them different ports. This works fine, now I installed 3 rabbit MQ nodes on another machine and installed the management plugin. Of course I adjusted the configs and gave the management tools different ports. Unfortunately I can only access the management plugin from rabbitmq 1, 2 and 3 are not working.
I checked and see that some folders are missing in the setup.
C:\Users\myuser\AppData\Roaming\RabbitMQ1\db
inside of this folder I am missing the plugins folder which I have in the rabbitmq1 setup. I tried to cheat and copy the folders and rename them, but as soon as I start the service it recognizes this and delete the folder.
Re-installing the management plugin does not work, whenever I try to install I get the message that I already have it.
Any idea?
I finally found the issue. When you create the rabbit-mq and you don't have a config in the AppData\Roaming/YourRabbitInstance than there will be no config parameter created in the registry. Meaning your config will never be picked up, whatever details you provide. I have added the config parameter to the registry and the queue immediately started listing on the ports defined in the cfg.
-config "C:\\Users\\myuser\\AppData\\Roaming\\myrabbit\\myrabbit"
Related
I have deployed my application running on my local server # http://localhost:8048/myservice?day=xx&month=yy&year=zzzz , it works succesfully on my local machine, in that it downloads a file from the http site. However when I deploy to Mule Management console . I understand that the default port is 8585. When I change the URL to MMC & give the default port with the same path, it does not download the file . Am I missingsomething
The MMC is a utility for managing and monitoring Mule Standalone Runtimes.
One of its functions is to deploy apps to a Runtime. You are not actually deploying to the MMC.
Does this help clarify the situation or do you want any further help on want The MMC is used for and how to do it?
Please check the logs inside MMC.It stores the logfiles date wise.See if your application has been deployed in MMC successfully and if yes then do the following things:
1)If you are using any path to download the file then cross check the path details.You can put a logger to crosscheck that.
2)Put a logger before the business logic and after the business logic and follow what it is logging in the log file.
3)In case your server is Linux then check the path separator pattern
MMC is a Mule Management Console which is used (provides provision) to deploy, undeploy, manage, monitor application and server both. From the statement you mentioned in your query it seems you are trying to deploy the app in the MMC - MMC is not a server its a console where you can register your ESB Runtimes -or- API Gateways (on-Prem) servers so that you can deploy the applications to the server/runtimes (which will go to the runtimes location $MULE_HOME/apps).
Please check if you have registered the server under MMC's Server tab - if not then you have to do this first and then it will allow you to perform application deployment using the MMC's APplication tab where you can upload your deployment archive/artifacts/build to the mmc repo and then you can deploy through the deployment options by selecting your server (which you have registered).
If I am missing something from your statement then please clarify more and will try to help you out here.
I am using Openfire server with Strophe and it has the Monitoring Plugin installed. It archives my messages, and I use strophe to load them. But there is a 30seconds-1min delay for the messages to be put into the database.
I am wondering, if I use Ejabberd to archive messages, and the messages get put into the database, is there a delay as well?
There will be no delay on the ejabberd. As I was working on retrieving the messages using ejabberd, I didn't found any delay while retrieving the messages and even while putting in the database. It might take some nano or micro seconds to put in database but while retrieving I am sure there is no delay in my POC app.
I worked with Ejabberd and its pretty awesome. I don't know much about openfire and I really suggest you to switch over to Ejabberd.
Ejabberd has an Admin panel which shows online users, virtual hosts, nodes, modules and lots of stuff which admin can access atmost. Its pretty much easier for Installation and Configuration. Ejabberd is actively developed and widely used.
Ejabberd supports all the messaging features. While installation all the modules will be installed. If you want to install some external module (not developed by Ejabberd Official people), then go through with that module installation docs. Some of the modules which are developed by Ejabberd wont get installed while ejabberd setup. Take a look here for those modules. You can install these modules as:
ejabberdctl module_update_specs
ejabberdctl module_install <module_name>
After installing the module, just enable that module at modules section in the ejabberd configuration file.
I have installed WebLogic 10.3.6 in Production mode and I have deployed an EAR application in my Managed Server. How can I make sure that when I restart my Managed server then WebLogic will re-deploy my application once again?
There are a couple ways you can verify a deployment...
Click the deployments link in the admin console, find your deployment, click it, and verify the path, staging mode, and targets are correct. You can also click on the monitoring tab to verify it is in the Active state.
You can verify the same by opening the config.xml file in your /config directory. Look for the tags
Once you've deployed, you don't need to worry about it disappearing when you restart. It will be there until you choose to remove it OR you delete the .ear file.
Multiple TFS 2010 MSBuilds are not triggering Web Deploy to publish the web application to the IIS website.
This is for multiple different software products, multiple different build configurations, 2 different build agents (on 2 different servers), multiple IIS web site instances on multiple different servers.
3 different continuous deployment setups were previously working.
So hopefully this rules out miss-configuration of the build/build servers/hosting servers/web deploy and IIS.
According to the network manager nothing has changed on the network (all servers are local), and port 8172 is not blocked by any security configurations.
All builds succeed, web deploy fails silently (no error, nothing in the logs). It appears that web deploy is no longer being triggered.
Are there any other ports that are used here?
What else could be blocking the communication between MSBuild and Web Deploy?
Would you expect it to fail silently (nothing in the logs or passed back to MSBuild)?
UPDATE
This is a similar question How to determine if MSBUILD Arguments were executed for TFS Build Definition
Assuming you are using vs2012, on your build server make sure the following two folders exist: Web & WebApplications in
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0
If these dont exist then need to be copied from a machine your do development on. This worked for me, and solved all of my problems with the Deployment of projects.
I have installed YouTrack as a windows service, on the same box as TeamCity. TeamCity works fine, but the YouTrack windows service stops as soon as it is started.
Can anyone point me towards log files for youTrack, or has anyone expreienced this before? I have been unable to find anything on google.
I set up YouTrack using this article:
http://blog.endjin.com/2010/11/a-step-by-step-guide-to-hosting-youtrack-in-iis-7/
though I have not even got to the IIS part. I have tried both the stable release and the latest EAP build.
Thanks in advance
Most likely the port you've chosen is already used by some other application, check YouTrack logs for more details, they are located under the installation directory, for example:
c:\Program Files (x86)\YouTrack\logs
Note that if you run TeamCity on the same machine, at least one more port (except the default HTTP port) could conflict, edit conf\server.xml:
<Server port="8005" shutdown="SHUTDOWN">
TeamCity Tomcat is most likely using the same shutdown port, so you need to change it. Change other conflicting ports if you find them reported in the logs.