Re: [ebxmlms-general] freebXML MSH Scalability

[Bob K. <py...@ce...>]

see comment inline.

Ronald van Kuijk wrote:

> Ajit,
>  
> Regarding point 2, I've already tried once to implement this and it 
> works. Since all j2ee servers support this and even tomcat and jetty 
> have connectionpool mechanisms, I'm all in favour of using that what 
> is provided with the appserver/servlet enginge. What I did not try is 
> to make it configurable to be able to use both solutions. This would 
> require a DBConnectionPoolInterface. Since hermes uses a combination 
> of a connection pool and some direct connections, 
> getRawConnection(), I mapped the implementation of these methods to 
> the connectionpool.

I am sorry that I am not familar with it. I would like to ask the use on 
using connection pool on tomcat/jetty. Is this connection pool just a db 
connection pool or it is another thing?

>  
> Another thing I was looking at was a real persistency layer (in it's 
> own package?) as interfaces which would make it possible to also store 
> the messages in the database as blobs (our ASP does not allow us to 
> store 'things' in a filesystem).

In fact on the design work on Hermes 1.0, we are trying to make a 
generalize flow of receiving messages and send messages. Then for each 
items on the flow, customization can be done (so persistence part can 
also be customized).  However the design is in very early stage and I 
cannot provide more information on it yet (I can only say that there are 
many changes on 1.0)

>  
> Unfortunately I had a major system crash and lost all of this code and 
> did not start over again...
>  
> Failover is also not possible (i think) since the message sending 
> threads (for retries etc) are created on a restart of the server, so 
> if one crashes you have to restart the other to have it pick up the 
> messages.
>  
> One of the other things (for us) is centralized authentication using 
> an ldap server where we can manage all users/clients/systems that have 
> access to the server. I'd like an abstraction layer for this to so we 
> can implement something that uses the authentication of the 
> application server / servelet engine (e.g. through jaas)

For this one, I have to do some investigation, because I am also not 
familiar with it too.

>  
>  
> Ronald
>
>     -----Oorspronkelijk bericht-----
>     Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
>     Verzonden: maandag 3 november 2003 11:06
>     Aan: 'ebx...@li...'
>     Onderwerp: [ebxmlms-general] freebXML MSH Scalability
>
>     Hi,
>      
>         Hermes MSH is essentially a JAXM servlet with a lot more
>     behind it.
>      
>         My question is - how does/would hermes scale w.r.t messaging
>     requirements?
>      
>         1. Can hermes use administered components such as datasources,
>     connection pools etc (other than hermes' native connection pools).
>         2. What conversational state is preserved in a servlet
>     instance of hermes MSH? Can different instances of Hermes MSH
>     share the same underlying resources?
>         3. What are the other key considerations w.r.t deploying
>     hermes MSH in an app server ( e.g. weblogic) cluster?
>      
>         Has someone experimented with this?
>      
>     regards,
>     Ajit
>      
>
>         -----Original Message-----
>         From: Patrick Yee [mailto:kc...@ce...]
>         Sent: Thursday, October 30, 2003 7:47 PM
>         To: ebx...@li...
>         Subject: Re: [ebxmlms-general] SMTP Port not configurable
>
>         Ajit,
>         Ooops.. you are right. We will include it in our next release.
>         Thanks for your suggestion.
>         Regards, -Patrick
>          
>
>                 By the way, why is the SMTP port not configurable in
>             msh.properties.xml?
>              
>                   <SMTP>
>                     <Host>localhost</Host>
>                     <User>ajitkt</User>
>                     <Password>nainital</Password>
>                   </SMTP>
>              
>