• Post Reply Bookmark Topic Watch Topic
  • New Topic

Advice in using Linux and J2EE as a server  RSS feed

 
william christensen
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I hope this is the proper forum in asking anyone who uses Linux (preferably Debian) to run a J2EE server. Could you pass along: the machine type, memory needed, diskspace used, the JVM used and the J2EE framework used. Also could you pass on the amount of trouble in getting all the software and hardware to work together.

P.S. I am only interested in machines used as a servers only..so no graphics loaded on the machine (ie X or Swing etc).

Thanks for your time
Regards
William
 
Joe Ess
Bartender
Posts: 9439
12
Linux Mac OS X Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's a pretty vague question. The most important information, like what you intend to use the server for, is left out. For example, I have a Gentoo Linux PC with an AMD 1400XP processor and 512Mb RAM and a 200 GB HD running Tomcat on a DSL line with a static IP running my private web site. All it does is display pictures of my kid, so it doesn't need much horsepower or throughput. I also use it as my main home PC, so it is running X/KDE and it has all the trimmings like OpenOffice and Mplayer and so on.
Now, for the public web site I maintain for my employer we use dual-processor SPARC systems in a failover arrangement. Both boxes run Solaris 9 on dual processors, 4GB of RAM and 5 4GB disk partitions hosted on a seperate disk array. We use Weblogic 6.1 in our production environment and are in the process of moving to 8.1.
So what are you trying to accomplish with your server?
 
Tim Holloway
Saloon Keeper
Posts: 18789
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you use Sun's JVM, Swing's already part of the package and if you render client-displayed graphics, you'll end up using parts of the X system and probably parts of Swing as well.

My general recommendation fo J2EE is at least 512MB RAM for J2EE + a 600_MHz CPU, regardless of Linux or Windows or which of the several J2EE containers out there you like. How much above that lower limit you need depends on the workload and everyone's workload has its own peculiarities so in the end, only real application benchmarks can help.

You'll find vendors aren't too interested in Debian. It's a good place to find leading-edge stuff, but the stodgier Red Hat and Suse are the ones that get the best support. Some versions of RHEL come ready out-of-the box with J2EE pre-installed. Come to think of it, I think so did my copy of Fedora Core 4.

Stock server hardware is rarely a problem with a Linux. Most issues have to to with nonstandard hardware like HP's motherboard-bases SCSI controllers or the odd Dell appendage.
 
dema rogatkin
Ranch Hand
Posts: 294
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have j2ee web up running under Xbuntu. I use TJWS as app and web server. Machine is Pentium III 700MHz with 700MB memory. It runs for years without stopping. However it's private web app with relatively low demand. I use also with success Xbuntu to debug very complex web app using the same app/web server combination. Oracle DB is running on Sun box though. If you need more advanced app server, then you can consider Tomcat.

Edit: I use stock Sun's JVM, version 1.5.0_6 I think. You can get filling about how responsive it is playing with 7bee.j2ee.us
[ February 15, 2006: Message edited by: dema rogatkin ]
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!