in storm 1.2.2 deployment, ui is stuck in "loading summary" - deployment

I tried to deploy apache storm for a streaming program development. 4 servers for 1 nimbus/ui and 3 supervisors. After all setup, nimbus/ui/supervisors are launched without errors/exceptions reported in logs. But when access to ui via browser, the page is stuck in a spinning prompted "loading summary" like for ever.
All processes are killed and zookeeper node "/storm" and storm data folder are cleared. Still stuck on ui after restart the cluster.
Also switched to lower rev 1.1.3, still same problem, looks like not a bug specific to rev, more like a bug relevant to my setting. But really confusing to figure out. Anyone familiar with storm can help me on this?

Related

Why wont the Zed Attack Proxy (ZAP) start

I have ZAP installed on a build server (Windows 2008 R2) and on my Windows 7 desktop, and Zap only occasionally starts. I click on the program and my cursor shows it is waiting for a second or 2 and then nothing. Attempting to run from the command line will also not show any signs of running.
Then just out of the blue the program may launch.
Is it possible it just takes forever to start. I left my computer running and the next day when I came to work there was the UI.
I get the same results if I try to run the program in the headless state. with the -daemon flag. it never starts, it never shows up in the task manager, as an application or a process
thanks Noel
Turns out there were 2 issues. The first was that the tool was taking 4-5 minutes to start (I timed it several times at around 4m 30s). I did not have the patience to wait, so I would try to start it again. Attempting to start the application when one had started, but no UI was showing invariable caused the application to hang.
Secondly if you start it as a headless application there is no way to stop it. So if you have it headless and then try to start the application it will cause it to hang. THe easiest way to tell if it is running is to follow the log information being written out as suggested by Psiion above in his link.
To kill the process, look in the task manager for the java process and kill it.
Just in case anyone stumbles across this post, my problem was I didn't have Java installed. I had removed it a few months ago due to security considerations.
You can stop your browsesr using Java easily by using the Java control panel http://www.java.com/en/download/help/disable_browser.xml
I was facing a similar issue, the ZAP tool was working fine on my local machine but was displaying erratic behavior on the Virtual Machine. I tried all the previously mentioned suggestions but none of them could mitigate the issue. Upon checking the log files i found out that the HSQLDB files were being locked even after closing the tool or even if the tool did not start. I eventually figured out that the difference between the 2 environments was just the operating system. My local had Windows 10 pro while the VM had Windows 10 enterprise. So in case if any one else is facing similar, kindly check the operating system.

Running zookeeper from within application

I'd like to use zookeeper in one of my applications for distributed configuration management. The application is currently running in distributed environment and having to restart nodes for configuration files changes is a headache.
However, we want the zookeeper process to be started from within the application. The point is to reduced startup dependency and reduce operational cost. We've already have startup/shutdown scripts for the application and we need to reduce impact for operations team.
Has any one done something similar? Is this setup recommended or there are better solutions? Any tip or feedback is appreciated.
I have a blog post that describes how to embed Zookeeper in an application. The Zookeeper developers don't recommend it, though, and I would tend to agree now, though I had the same rationale for embedding it that you do - to reduce the number of moving parts.
You want to keep your ZK cluster stable but you will need to restart your app to do code updates, etc, impacting the ZK cluster stability.
Ultimately you will end up using your ZK cluster for multiple apps and those extra moving parts will be amortized over a number of projects.

Apache won't start in MAMP Pro

I’ve tried several ways to get MAMP PRO to work for me. The main issue is that Apache keeps conking out, not sure why.
Apache starts when i don’t have any servers other than local. But when i start to create new servers Apache won’t run.
Here is my setup per screen shots:
shot 1: http://kualitydesign.com/css-tricks/mamp-1.png
shot 2: http://kualitydesign.com/css-tricks/mamp-2.png
I’ve googled, but all i’ve been able to find is how to start a new server, which i know how to do when MP starts normally.
What i don’t know how to do is troubleshoot MP when it Apache doesn’t start. Really need to work locally for a new WP build and would love to get this up and running.
If anyone has had this same issue, can spot my error, or has other ways to fix the issue and cares to share, that would rule!
My hunch, and it’s a very noob hunch, is that Apache on MAC is running and it’s conflicting with MP’s apache, if that’s even possible. I just re-call reading that somewhere.
Thank you.

Problem with embedding activemq to jboss application server

I'm totally a newbie in Java Enterprise and I have a lot stuff yet to learn. Right now I'm working which involves JMS using JBoss and ActiveMQ. An application sends messages to queues in JBoss and my goal is to access those messages using any message broker (in this case I tried to use ActiveMQ). So I think it's better for me to embed ActiveMQ to JBoss. I used the link below as the guidance :
http://activemq.apache.org/integrating-apache-activemq-with-jboss.html
I followed every single steps in the guide except that I used JBoss 4.2.3 and ActiveMQ 5.1.1. If this problem results from the different version of the tools, I think I can't help it out because other versions seem does not work on my machine. When I run JBoss to test whether the embedding is working or not, I can't see anything running on port localhost:61616 which is the default port for ActiveMQ, although JBoss seems run well. My question is :
Is any one know how to fix this? Or has anyone ever experienced such problem?
Is there any way to access queue in Jboss?
If this question is pretty ambiguous or need more details, let me know. Thanks in advance for any help.
I'm quite sure the embedded broker is started (transport vm://localhost) which results in a working JMS broker for that VM. But this broker isn't reachable from outside (via tcp or anything else)
Do you see any error in the log when launching jboss? I managed to make it work with Jboss 4.2 and ActiveMQ 5.4, and once integrated it only gives you a small hint that is working correctly with some info message saying "broker started in port ..." .
Also you can try to use the sample producers and receivers in ActiveMQ to test if the queue is working correctly.
If you still have problems I can try to help

jboss-4.2.3.GA-jdk6.zip is it stable?

It seems as if the jboss teams doesn't want to say that the Java 6 compile of Jboss AS 4.2.3 is a GA, they write that it shouyld be considered expiremental.
Anyone using it in production? we're using it in test and plan to move it to prod as it hasn't shown any problems.
We've been running that same distribution (jboss-4.2.3.GA-jdk6.zip) in production for several months now and it's been working like a champ. However be aware of this issue in particular, it bit us in testing and would have killed us in production: (Add http://) jira.jboss.org/jira/browse/JBWEB-82 . We've installed JBoss Native as a work around and it's been running great.
We have now been running it for a quarter of a year. Seems stable, apart from some strange logs from the transaction manager for unreceverable XA transactions, but we havn't been able to connect those log entries to any application errors.
So it seems stable.