[JBoss jBPM] - Error handling in GPD process deployment
by alf_dave
GPD 3.0.11, JBPM 3.1.2
I've noticed the error handling to be erratic when deployment of a process archive from the GPD fails. Often, a dialog is presented stating the deployment succeeded when in fact it hasn't. Other times, a dialog is presented due to an unexpected error. Two extremes.
The deploy servlet returns arbitrary messages in the response for certain exceptions e.g. FileUploadException, IOException, but for others, just leaves the exception to propagate, presumably forcing an HTTP error response. However, for valid HTTP responses, it seems the content is completely ignored by the GPD.
Obviously, an improvement would be to present the cause of the error in the GPD and to also catch all errors.
However, I raise this as I'm developing my own deploy servlet to fit the setup of our server, but it's not clear what the protocol is for reporting an error. For now, I've kept as close as I can to the error handling in UploadServlet.
David Caruana
Alfresco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964151#3964151
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964151
19 years, 9 months
[Beginners Corner] - Reasons not to use Jboss? Is this true?
by pani_rd
All:
I'm trying to pursue the folks @ work to use JBoss for our next projet. But, I was hit with the following reasons for not going with JBoss. I can validate the reasons by doing a little investigation. But, thought of throwing this up in the forum to see others response as well.
Here are the reason - BTW, folks came up with this reasons want to go with WebLogic.
1. Jboss uses multicast for replication in a cluster .This does not provide scalability and generates network traffic. This wont impact the application servers, but if there are multiple applications in the netwrok, they will be impacted. Currently we are using Jboss in a loadbalanced configuration. This is not an application cluster, therefore performance and failover are poor, the session is not shared among the cluster.
2. Jboss has poor quality, the JCA and transaction manager are not J2EE compliant (at least this was the case with Jboss 3.x).
3. Jboss does not have good EJB pooling capabilities. For instance for a pool size of 500, the pool cannot be incremented by 20. This is something that is provided by weblogic, and therefore providing better memory utilization. Also the pool sizes cannot be decremented within Jboss. If the pool size reaches the max, it stays at the max.
4. Jboss lacks add on utilities and programs for clustering, performance tuning and server monitoring. Weblogic includes good profiling tools as well. Jboss does not have a nice way to create and populate domains, or handling creation/management/deploy of queue's and topics
Any response validating the above reasonings will be appreciated!
Thanks,
RD
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964149#3964149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964149
19 years, 9 months