My company may not consider JBoss, because, that will be new skill set required for the system group. Tomcat is fine, Because They already manage tomcat with different other internal applications. My Application is simple transactional DB only web based application. I may not need full J2EE stack for this app. Any further insight will be helpful. Thanks Brijesh. Gregg Bolinger. I like Not sure what more insite someone could give you about your project that we know nothing about.
It really is as simple as Stefan says. Check out this list of all websites, systems and applications that run on Tomcat, refer to this page on Apache's website. You might need to clear some time out of your schedule, because it's about a mile long. Case closed! What they say : "Tomcat is not proven for use in your vertical - you should be running a Java EE app server.
There may be some special situations where a reliance on legacy applications forces you to use a legacy application server. However, in the majority of mainstream verticals, Tomcat has been proven more than a match for the job, and the proof is available across multiple industries - healthcare providers, auction houses, financial organizations, grocery stores, real estate It's simply not a matter of debate. Let's put this myth to rest. Tomcat is proven in the vertical. You do need to register with the Apache wiki system to edit this page: simply click the login or user preferences links at the top right of your screen to do so.
Don't worry if you don't think it fits here or into any particular category: we would like to see your application listed no matter how big, how small, or how miscategorized Some of these applications are simply compatible with, ship with, or run on Tomcat. Others are specifically designed or documented with Tomcat as the container in mind.
Please note that all the corporate logos and names used below are trademarked by their respective organizations. These organizations are not affiliated with this web site or with The Apache Software Foundation, and make no claims regarding The Foundation or its products. Further, in most cases the companies are not aware of their being listed on this site at all.
Any of the EJB server will be total overkill and the overhead will soak you. And Websphere at least the servlet side is based on Tomcat as is JBoss. Re:Use Resin if you care about performence Score: 3 , Informative. JBoss is certainly not based on Tomcat. We allow any servlet container to be plugged in to the server. Currently we support Jetty and Tomcat. Apache on the web tier and I'm no big fan of Apache or its configuration nightmare specifically.
What "Configuration nightmare"?! Really, there's just one well commented text file to edit, unless you intend to add user authentication to directories which itself isn't difficult - it's hardly brain surgery. Now sendmail. BEA is buggy as hell anyhow We use a BEA app server at work for our order processing system. Generally it works ok, but serious bugs in it cause us a lot of greif and downtime.
First off it has serious memory leaks in the performance pack trading speed for stability. We have to boot the BEA app server at least once a week least it runs out of memory and crashes. If you code smartly you can move the code back and forth so you really have nothing to loose Re:BEA is buggy as hell anyhow Score: 5 , Informative. I have been forced to run BEA and it has been agony.
Plenty of things that run under Tomcat won't under WebLogic. IMHO, this just plain wrong! Examples: 6. Why in the WAR? Score: 2 , Funny. Yes coroner, I did put methods in my Godzilla bean, is this the cause of death?
On to specifics, if you're hitting memory leaks with the performance pack enabled, you are using some old version - no question! The only problems I've hit with the perf pack on current releases are to do with relatively obscure things like HTTP pipelining the latter is a buggy spec if you want my opinion Turn on INFO level logging and check the report of java.
BTW Could be that now is exactly the wrong time moving an order management-type application from BEA to JBoss - WebLogic 7 has the Web Services and workflow management pulled together and when the Workshop tool caters for both end of year?
We use it Score: 2 , Informative. I don't know, but I archived this article [weblogs. Re:Is Tomcat crap? Bad developer productivity?!? Not at all. We develop using JBuilder, which comes with tomcat built in and allows for very effective development.
Since I like the development and production environment to be as much alike as possible, we also run tomcat for production on an important user intranet application for a large bank. We run it stand alone to avoid problems with the connectors.
Score: 4 , Insightful. There are issues with that article that he doesn't mention. For example, what is his test page? Is he serving static content? Does he have Tomcat in "reload" mode where it checks for updated code every time a servlet is executed? JBoss [jboss. They even offer consultancy if you cannot get it right the first time. Excellent award winning server, excellent support, what do you need more? It has Jetty integrated and gives you the full J2EE stack.
You can get it to work with Tomcat too: no problem. Check it out, the design is awesome for the techies. The support option is great for the management.
Everyone 's happy :. The servlet engine used in JBoss is Tomcat. JBoss 3. Check out the Jboss download page [jboss. Just make sure it's good hardware Score: 2 , Insightful. The last production box we got even for Msft 2K server was just a 1. Giving untrusted hw a weeks thrashing under simulated production conditions builds confidence immensely and avoids em-bareass-ment. Re:Just make sure it's good hardware Score: 2. If you don't need to scale to Sun's midrange then their stuff is insanely expensive, but for some things it is the only solution.
Apache is nice and fast for serving up static pages, and really nice with php pages. But in my own personal experience, and this was 2 years ago, Tomcat was really slow. It seemed to be just average with jsp pages, and then the more towards the j2ee route you went, the more worthless it was.
Tomcat Score: 4 , Insightful. It's been rock solid. If you're going to use it in conjunction with Apache, Apache2 will only work properly with the ajp13 connector. Choosing Tomcat over others Score: 5 , Insightful. I come from a similar situation and have managed to do what you want to do. To sound a little zen don't try to change their minds just show them the benefits.
In my case I drew on my knowledge on the lack of vendor lock-in combined with the economics of the situation and the inclusion of support in our seperate support contract really cheap support at that. As for support that was never really and issue with us so I have no argument there. Now Tomcat has some flaws most in the JSP compiler Jasper and their live redeploy area , but is otherwise a very sweet little servlet engine don't call it an appserver it isn't one in the J2EE sense of the word and that is the game you're playing when you use things like servlets.
Once it has compiled your JSPs it works just fine and the sweet things and the selling argument for our projects was redundancy of providers. You have a change of enviroments like going to another servlet engine. In fact we had some time one evening and switched between Tomcat, Resin and Jetty with only a few minutes spent making the configurations fit and the files unpack and install.
On a sidenote if you can delay any lock-in on a specific version of Tomcat, try and see if you can get your system over on the upcoming Tomcat 4. You should try to change his opinion on jBoss though. It is probably the most stable thing about this entire project with hot redeploy great for development , good performance and great ease of use and install on top. In fact the new 3. But enough about all this.
We build and deploy customized web apps for our growing client list. We have been running Tomcat for more than a year, and its performance has been superb. Of course, our clients don't have high volume web sites.
And we're not a large company. Tomcat is fine Score: 3 , Informative. We use Tomcat pretty extensively over here major league northeastern university. I have heard that Jetty and Resin are much faster. That said, Tomcat is perfectly adequate. Unless you are running Ebay or Amazon. Also, until 4. Like many Apache or maybe Open Source in general projects you pay for not having the depth of features a commercial product would, but you get in return breadth of features, and the comfort of a de facto standard with tons of inertia and support behind it.
Besides, the J2EE specs are written sufficiently well, that any servlet engine implementation is basically a dime a dozen. This is a web toolkit based on the Arsdigita of Phil Greenspun fame Community system. Tomcat does suck, avoid it. Score: 3 , Interesting. I've used Tomcat for testing against the Sun specs, and I find that it's slow and not worth the money you spend on it. Yes, I know it's free. Pay attention. Re:Tomcat does suck, avoid it. I had heard bad things about Tomcat's performance especially with a load - and that has improved over the last year or so , but not much about compatibility.
I personally have to deal with Websphere and Weblogic, and would take BEA's product over IBM's in a heartbeat that's my opinion, not my company's opinion, although many developers here share that opinion.
Truth be told, I haven't seen many compatibility problems, though. Usually something that doesn't work on Tomcat doesn't work on Weblogic or WebSphere, either. Most of our code just provides a client form-based interface, though, so I doubt we're pushing the limits of the J2EE spec.
Score: 5 , Insightful. What the hell are you talking about? I wonder what is your standard for poor but you can't get any better compliance than what you get with Tomcat namely it happens to be the official, Sub-blessed reference implementation of these very specs.
Thank you. Comparisons, plus some opinions Score: 3 , Interesting. From my experience, Tomcat 4. Not sure if this helps, but Primavera's [primavera. Jetty Web Server v3. I know of a few people that use it and have been happy with it. The only complaint that I've heard is that the pages take long to load. The person that said this thought it might have to do with the page being Java, but I think it might just be the database itself causing the slowdown. We have migrated to Linux, Apache, and Tomcat over the last year-and-a-half.
We use it both in development and in production, across or so boxes. As with everything, there are issues, but for the most part we are very happy. Even most commercial vendor's idea of a "big" site doesn't come close to what we do, so we have found very little difference between problem solving in the open-source and closed-source worlds.
For what we do, you can't beat the price And yes, that includes the price of our time. Rightworks used to use Tomcat Score: 2 , Interesting.
It wasn't serving up HTML per se:, but it was still used to run the application. Since the catalog server was a major piece of the procurement software, it had to perform. If people can't populate their cart, then what's the point? This software was sold to various 'largish' companies without any complaint on the performance of the catalog I'm not sure what they're using now, since I bailed just before the.
I'm not even sure if they're still selling the product, which would be a shame. If the performance isn't good enough, throw a few caching proxies in front of the web servers. You may want to do that regardless of what web server software you run in the back end Blogger Score: 3 , Informative.
According to some of the comments Evan Williams made recently, about " moving away from ASP [blogger. How I introduced free software into my big company Score: 3 , Informative. My former employer, a very large areospace company, was at one time very very much against any software that wasn't back by a "stable corporation". The excuse was that if something went wrong, my company could sue the pants off the software provider.
Of course, they almost never did that - instead, they just wouldn't pay the bills until the provider complied with company demands. Enter terminal emulator software. And with 10,'s of desktops, that was And the savings was amazing. We rolled out the product slowly. Everyone was happy.
0コメント