When I recently switched to Eclipse Galileo, I noticed that a Mule configuration file that had previously validated correctly now had validation errors. Since I did not change the file, something in Galileo’s validation of XML files must have changed.
The symptoms are these:
At MuleSoft we use Agile development to build and deliver all of our software products. One of the more challenging and potentially time consuming part of agile is story estimating. Recently we decided to take a new approach to this that has proven to be a lot of fun and amazingly accurate. I call it Bubble Sort Estimation.
Some time ago I wanted to do a Mule demo. I’m a Jabber fan so I wanted to use the XMPP transport for the demo.
I soon found out that the XMPP transport in its current form doesn’t work with real world Jabber servers any more. SSL connections are negotiated through TLS now and authentication seems to involve SASL – two things that the outdated smack version we’re using for the XMPP transport cannot currently do.
I often get questions about how to tune Tomcat for better performance. It is usually best to answer this only after first spending some time understanding the installation of Tomcat, the web site’s traffic level, and the web applications that it runs. But, there are some general performance tips that apply regardless of these important details. In general, Tomcat performs better when you:
Every so often, I would be answering some questions about Tomcat, and the person I’m speaking with would ask “where’s your blog?” or “do you have a blog somewhere?” I have always cringed at that question because I didn’t have one — until now. Mainly I had a few clever excuses for not putting time into a blog of my own:
The promise of a monitoring solution that will pinpoint application problems and give you exact steps to fix the problem has remained a dream. In addition, monitoring systems have become notorious for being expensive and difficult to maintain. Diagnosing application performance problems requires application-specific diagnostic information that general-purpose monitoring tools often do not provide.
While system monitoring products are useful in triaging a problem and assigning responsibility to a particular team (for ex: Application Server team),
While it has been commonplace (and well documented) for IT organizations to migrate Java EE applications initially developed on Apache Tomcat upward to commercial Java application servers, such as Oracle’s WebLogic, in recent years the trend has been reversing. There are a number of compelling reasons for creating new web applications using today’s deployment architectures on Tomcat instead of WebLogic, but perhaps even more interesting is the trend to migrate existing Java EE applications from WebLogic to Tomcat.
Finally, a way to develop and deploy Tomcat applications with ease! Are you developing applications on Apache Tomcat, or are you a Tomcat administrator? Have you been looking for ways to reduce tedious manual work as you deploy and manage your Tomcat applications, or are you seeking better visibility into your application’s performance metrics and faster resolution of problems?
Launching Tcat Server was a new type of challenge for MuleSoft. How do we take something that everyone knows — Apache Tomcat — and differentiate it with the enterprise features that our customers were asking for?
We started with a set of principles that would help us deliver this value. These included: