As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've taken part in a project where we have recently changed the application server to Jboss AS 7 (EAP 6). The system is a Jboss installation running in Domain Mode with one server (Server A) containing EJB's connecting to a relational database and the other (Server B) being a front-end node primaraly with JSP's connecting to Server A.
Before starting our load and performance testing I though I would ask here.
Question:
What are the major pitfalls and performance tweaks needed on a Jboss
AS 7 (EAP 6) in Domain Mode running a mix of transactional EJB's and JSP
web-interfaces?
The top performance problem is typically separating EJB beans and UI code on separate servers.
This pattern was advocated in 2001 because the concept "distributed objects" just sounded cool at the time.
After many failed and dog slow IT projects, people started thinking: why on earth do we put a slow network between two arbitrary pieces of code? What do we win?
The answer was invariably; nothing much if anything at all.
Long story short; don't put Servlets, JSP pages and JSF Servlets on a different server. Put your EJBs in the same EAR or even consider just putting them in the same war (just create a package "business").
One of top performance contributors in our JBoss 7 project was the fact that the server was not fine tuned, i.e. by default it runs many unused and unneeded service. These services affect almost all aspects of application life cycle, such as deployment speed, responsiveness, memory and disk footprint.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I need to add some SIP based functionality to my company's Windows based software, allowing the user to call extensions and receive calls from extensions registered with a SIP server. Essentially I'll be creating a simple soft-phone. The software might be running on separate networks, so NAT, firewalls and STUN servers are considerations.
I'm wondering if others have done this sort of thing and if so do you have any recommendations on how to get started.
Should I write my own SIP stack from scratch?
Should I consider using OPAL? It looks ideal, but they only list a single company that they know of using their library, which concerns me.
Should I consider other 3rd party libraries?
You should avoid to write your own implementation because this voip is a huge and complex topic. I would also not recommend OPAL (that is already outdated).
Just search for "SIP SDK" and you will see a lot of ready to use working solutions then just choose whichever seems better for your needs.
Opal has been around for years - and the code has been provided to various commercial users.
The code has been tested in many harsh environments.
Good software is like wine - it matures with age. Opal has matured well.
The library is extreme C++ - I hope you know C++ well.
Use Opal - cause when they ask for h.323, it will be easy.
The code has been tested on many compilers - (win, gcc, mac) and each compiler can be regarded
as a new pair of eyes, or another CPP quality check system.
http://www.opensips.org/ is a good choice in working for a server side implementation.
If you are to make a SIP client, try searching for webphones.Things with javascripts are cool.
here is a list:
http://www.voip-info.org/wiki/view/Open+Source+VOIP+Software
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Which is the best Operation System suited for web application development in various platforms like JAVAEE, PHP, Ruby-On-Rails, Perl, Python, if I have missed out anything then that too etc. including testing front end and business logics, version control system like svn/git etc, planning, reporting, life cycle management etc etc? In short, need to cover all aspects for web application engineering.
I have used both Windows and Linux and have felt Linux is better for its great command line capability. I have no idea about development in Mac. My experience in web application development is limited to 3 years and I just need expert opinion.
Linux is great option because of the following:
Software/Tools availability
Relatively easy troubleshooting
Easy to find answers on any question/error code you get
Great package management (Debian/Ubuntu and derivatives)
Friendly community
and many more
About the machine configuration more RAM, more HDD space, better CPU, ... :). In the company I work, every in-house developed piece of software is developed and hosted on Linux. I really can not remember of any issues we've had, except minor hardware related ones.
Linux is always a best bet on development, but of course you'll want available testing platforms with Windows and Macintosh, as well as other Unix bases for testing to make sure that your product functions appropriately under all configurations.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Did someone have succeed stressing a GWT app?
Any recommended tool?
I wrote a blog post about this topic a little while ago.
http://blog.oio.de/2011/04/19/load-testing-gwt-applications-with-selenium-2-and-gradle
There I published a Selenium 2 test script written in Groovy and a Gradle script for the parallel execution.
But with this solution and no accessibility from the outside its quite difficult to put a heavy load on your GWT application. Except you have many free test clients available in your work/dev environment.
We are successfully using http://loadui.org to test our GWT app. To test the GUI we input directly JSON HTTP requests to our RPC servlet. It's also useful to test SOAP/REST web services.
http://loadstorm.com/ is a great tool which lives in the cloud and supports Javascript. Fairly powerful and easy to setup and use.
We use NeoLoad for our GWT load tests campaigns. They provide an easy way to describe the JSON calls in the GUI.
You should check this out here to see if it can help you as well!
My Company (UBIK-INGENIERIE) distributes a commercial Apache JMeter plugin to load test GWT and GWT RPC applications.
You can easily record, variabilize and replay GWT and GWT RPC based application with standard knowledge of Apache JMeter.
See:
http://www.ubik-ingenierie.com/blog/load-testing-gwt-rpc-applications-with-ubik-load-pack-plugin-for-jmeter/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I finally decided it was time to write that "killer web app" we all dream about. :-) I've been a programmer for almost as long as I can remember so I'm not scared of technology, but I haven't been active in the web world for about a decade. Looking for some help on the direction I should go.
The app I'm considering: (in order of importance)
1) will need to charge my customers securely using someone else's service
2) must scale easily
3) must be cheap to deploy
4) must be reasonably responsive (much of it will be client side
javascript, but there is some server interaction)
5) will need a database on the back end (not a huge database, but it will
need to scale with the customer base)
I'm thinking of using the following:
Technology: mySQL, PHP, Javascript
Deployment: Amazon Cloud
Payment: Paypal
Is this the right direction?? (Any tutorial links would be greatly appreciated)
Use what you know best.
Don't worry too much about technology choices. The technologies you list are "safe" choices in the sense that many successful web apps have been built with them, so you know it can be done. I'd suggest sticking with mainstream technologies for that reason.
Also, don't worry too much about particular techniques and architectures. If your app really takes off, you're going to end up constantly redesigning the internal architecture anyway to keep up with traffic. Just keep it flexible.
If you could use Java or Python instead of PHP, check out Google App Engine: http://code.google.com/appengine/
Use paypal or Chargify or amazon
Check
Check (free until a high limit)
Check (google servers)
As long as you don't require a relational database
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
On the web side we are working on getting source control. Now, I want to see what can be done for the iSeries side. What is your favorite source control application for iSeries and why? I am looking for low-cost if possible.
The two most common source control packages for the iSeries are Turnover and Aldon. Neither are low cost but integrate well with the iSeries.
I prefer Turnover. It flawlessly handles production installs to both a local and remote iSeries.
Don't forget about MKS Implementer ;)
If you're using the WebSphere Development Studio or Rational from a PC then any source control system that will play nicely with that is an option if you don't want to shell out for the native iSeries one.
We use Aldon for our COBOL, CL, DDS code and it does a really good job. I don't know about the cost of it. There's a plug-in for the WebSphere Development Studio. Just about any source control option could handle archiving/versioning the source code, but Aldon excels at handling the compilation and deployment from dev to QA to production environments. It can keep different library lists for each, for example, and change them dynamically for compiling in different environments. It will even push code to other LPARs, if your dev and prod environments are not on the same LPAR.