[JBoss Messaging] - Is Jboss Messaging ready for Mission Critical Application?
by deadrow
Hi Everybody,
I am not writing to report a bug or a problem. Actually I was able to install a Jboss 4.2.1 cluster with Jboss Messaging 1.4 GA.
I am writing bc I am interested in unsing Jboss Messaging in my production enviroment but I am actually wondering the stability/performance of Jboss Messaging compared with other MQ systems. I haven't found much on the internet.
Right now, I have a java stand alone application (mission critical indeed) that uses Sun MQ 3.6. My application deals with 500K messages per day. Message's size is btw 2k and 2 MB.
The JMS provider I use, is also a java stand alone application. My architecture works fine but I would like to move my queues inside an application server so that eventually I will be able to deploy a new version of my application inside a J2EE container. In this way I would be able to run my application in a cluster.
My manager wants me to suggest the application server/JMS provider. Basically, I have to choose btw BEA Weblogic and Jboss Messaging. BEA JMS Provider has been tested successfully within my company and is definitively a save solution. I like Jboss cluster better as BEA realizes a "fake" cluster of JMS destinations.
Is there any document regarding Jboss Messaging performance/stability, some benchmark where jboss Messaging is compared to other JMS Provider? some successful study-case? I need some doc to help my proposed solution to be sure that JMSG can deal with my traffic and it is a stable product.
Correct me if I am wrong, but at the moment it is not possible to buy a support service for Jboss messaging, right?
PLEASE HELP
Regards
Davide
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092627#4092627
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092627
18Â years, 7Â months
[JBoss Tools (users)] - JBossTools 2.0.0.beta3 released (Repost)
by mculpepperï¼ jboss.com
Today we are officially announcing the release of JBossTools 2.0.0.beta3, the long-awaited follow up to JBossIDE 2.0.0.beta2, and the sister release of RHDS 1.0.0.beta1.
Firstly, here are all the pertinent links:
Sourceforge release area:
http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=24...
Update site:
http://download.jboss.org/jbosstools/updates/development
This release includes our new JBossAS Server Adapter, new Archives tools, new SeamTools, RichFaces Visual Page Editor from Exadel, and new releases of all the favorites: Hibernate Tols, jBPM Designer, FreemarkerIDE, and more.
We'll be posting more links soon, stay tuned!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074216#4074216
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074216
18Â years, 7Â months
[JBossWS] - Web service parameters are always null
by ppollard
I have a web service running on JBoss 4.2.1.GA. I have two different clients consuming the service. The 1st client is Remedy, a 3rd party service management application. Using tcpmon, I captured the SOAP document coming across. Here it is:
POST /remedyAbstractService/remedyAbstractService_1_0 HTTP/1.0
| Content-Type: text/xml; charset=utf-8
| Accept: application/soap+xml, application/dime, multipart/related, text/*
| User-Agent: Axis/1.1
| Host: phpoll0905:8666
| Cache-Control: no-cache
| Pragma: no-cache
| SOAPAction: ""
| Content-Length: 1065
|
| <?xml version="1.0" encoding="UTF-8"?>
| <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <soapenv:Body><sendTicketRequestToPartner xmlns="http://MY_COMPANY.com/remedyAbstractService_1_0/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <remedyUserID>MY_USER</remedyUserID>
| <remedyPassword>MY_PASS</remedyPassword>
| <remedyTransactionCode>60</remedyTransactionCode>
| <remedyTPSID>00000002600</remedyTPSID>
| <remedyTicketNumber>ATS01994267</remedyTicketNumber>
| <partner>Initech</partne>
| <partnerTicketNumber>ats11111</partnerTicketNumber>
| <technicalNotes>2/19/2007 4:58:28 PM
| 2/19/2007 4:50:33 PM asdfasdfasdfasdf 2/17/2006 3:15:24 PM iswebsvc tech notes
| </technicalNotes>
| <closedCode>my closed code</closedCode>
| <resolvedBy>guy who fixed it</resolvedBy>
| <solution>my solution</solution>
| </sendTicketRequestToPartner> </soapenv:Body>
| </soapenv:Envelope>
With this request, all of the parameters of the web service are null. The client calls the web service successfully, but the parms are always null, even though values are being specified for each field, as you can see in the document above.
I've also created a standard .NET client to consume the same service. When running it, the values from the client do reach the web service. The request SOAP document looks like this:
| POST /remedyAbstractService/remedyAbstractService_1_0 HTTP/1.1
| User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407)
| Content-Type: text/xml; charset=utf-8
| SOAPAction: ""
| Content-Length: 1014
| Expect: 100-continue
| Connection: Keep-Alive
| Host: phpoll0905:8666
|
| <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><sendTicketRequestToPartner xmlns="http://MY_COMPANY.com/remedyAbstractService_1_0/types"><remedyUserID xmlns="">MY_USER</remedyUserID><remedyPassword xmlns="">MY_PASS</remedyPassword><remedyTransactionCode xmlns="">60</remedyTransactionCode><remedyTPSID xmlns="">00000002600</remedyTPSID><remedyTicketNumber xmlns="">ATS01994267</remedyTicketNumber><partner xmlns="">Initech</partner><partnerTicketNumber xmlns="">ats11111</partnerTicketNumber><technicalNotes xmlns="">2/19/2007 4:58:28 PM 2/19/2007 4:50:33 PM asdfasdfasdfasdf 2/17/2006 3:15:24 PM iswebsvc tech notes</technicalNotes><closedCode xmlns="">my closed code</closedCode><resolvedBy xmlns="">guy who fixed it</resolvedBy><solution xmlns="">my solution</solution></sendTicketRequestToPartner></soap:Body></soap:Envelope>
Why does the 2nd document work, yet the 1st one does not?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092615#4092615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092615
18Â years, 7Â months