ebxmlms-general — General discussions

Re: [ebxmlms-general] time-to-live wrong format error

[Patrick Y. <kc...@ce...>]

Ronald,

We wanted to reuse as many error values defined in the spec as possible. And
of course the drawback is what you are suggesting: too general and the users
cannot figure out clearly what went wrong.

If the eb:Description can help, we suggest to keep the error value as
ValueNotRecognized, and reporting a more information description in the
eb:Description element, as you suggested.

For the checking of value before sending out, this is a good suggestion.
Currently a message even without correct schema could be sent out if the
wrong part is not necessary for sending. I guess we have to have a module to
validate the message before send.

Thanks for your suggestion. We have filed this in our TODO list. :-)

Regards, -Patrick


----- Original Message ----- 
From: "Ronald van Kuijk" <rv...@ab...>
To: <ebx...@li...>
Sent: Sunday, November 02, 2003 3:36 AM
Subject: [ebxmlms-general] time-to-live wrong format error


> Hi,
>
> I'm playing a little with time-to-live from the monitor application.
> When I send a message with a time-to-live of 1d (one day) which is of
> course in the wrong format. I get a nice error message back with a
> "ValueNotRecognized" error:
>
>     <eb:ErrorList
>
xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2
_0.xsd"
> soap-env:mustUnderstand="1" eb:version="2.0" eb:highestSeverity="Error">
>       <eb:Error eb:errorCode="ValueNotRecognized" eb:severity="Error">
>         <eb:Description xml:lang="en-US">
>           Value cannot be parsed / recognized
>         </eb:Description>
>       </eb:Error>
>     </eb:ErrorList>
>
> IMHO there are two things wrong with this error. The long description of
> "ValueNotRecognized"  according to the specs is:
>
> Although the document is well formed and valid, the element/ attribute
> contains a value that could not be recognized and therefore could not be
> used by the ebXML Message Service.
>
> According to the ebxml-ms schema type of TimeToLive is dateTime:
>
>     <element name="TimeToLive" type="dateTime"/>
>
> But... all the long descriptions in the ebxml specs mention "well formed
> and valid". Probably because they expect a schema-check to have taken
> place before the document will be parsed by an MSH.  So I do not know
> what is the correct error to return in a situation like this.  So making
> the error more specific and/or including the location in the form of an
> xpath statement.
>
> But shouldn't we also do a validation check before sending out the
> message? Since the error comes back from the MSH, the creation of the
> message in the Monitor probably does not include a validation of the
> message. I think we should include at least one of these (use the
> location in the error, or validate the message on creation) . The code
> that generates the message is in MessageServiceHandler.java:
>
>             if (ttlString != null) {
>                 final Date timestamp = Utility.fromUTCString(ttlString);
>                 EbxmlMessage errorMessage = null;
>
>                 if (timestamp == null) {
>                     String err = ErrorMessages.getMessage(
>                         ErrorMessages.ERR_HERMES_DATA_ERROR,
>                         "cannot recognize TTL value in message");
>                     logger.warn(err);
>                     errorMessage = generateErrorMessage
>                         (ebxmlMessage,
ErrorList.CODE_VALUE_NOT_RECOGNIZED,
>                          ErrorList.SEVERITY_ERROR,
>                          "Value cannot be parsed / recognized");
>                 }
>
> I think we should use the errorstring  (err, or at least the
> "cannot.....message" part) be used instead of the "Value cannot be
> parsed / recognized" or the other signature of generateErrorMessage
> which includes the location?
>
> Ronald
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

[ebxmlms-general] problem message: hermes throws exception on echo.

[Tripathi, A. (GXS) <Aji...@gx...>]

Ron,
 
    Here is the echo message that caused the problem (between echo lines)!
 
----------echo-------------------------
 
------=_Part_2_24749215.1068222593281
Content-Type: text/xml
Content-Id: <soappart>
 
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env="
http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> " xm
lns:xsi=" http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> " xmlns:xlink=" http://www.w3.o
<http://www.w3.o> 
rg/1999/xlink" xsi:schemaLocation="
http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/>  htt
p://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap-env:H
eade
r xsi:schemaLocation="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg> -
header-2_0.xsd
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header> -
2_0.xsd"><eb:MessageHeader xmlns:eb="
http://www.oasis-open.org/committees/ebxml
<http://www.oasis-open.org/committees/ebxml> -
msg/schema/msg-header-2_0.xsd" eb:version="2.0"
soap-env:mustUnderstand="1"><eb:
From><eb:PartyId
eb:type="fromPartyId">Sample</eb:PartyId></eb:From><eb:To><eb:P
artyId
eb:type="toPartyId">Sampola</eb:PartyId></eb:To><eb:CPAId>CPA_2003</eb:CP
AId><eb:ConversationId>Item_No_128</eb:ConversationId><eb:Service>http://loc
alho
st:9090/loopback</eb:Service><eb:Action>Order</eb:Action><eb:MessageData><eb
:Mes
sageId>20031107-162721578-CPA_2003.http://localhost:9090/loopback.Order.1@10
.24.
200.237</eb:MessageId><eb:Timestamp>2003-11-07T16:27:21Z</eb:Timestamp></eb:
Mess
ageData></eb:MessageHeader></soap-env:Header><soap-env:Body
xsi:schemaLocation="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd>
http://
 <http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd>
www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:Manif
est
xmlns:eb="
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x
<http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x> 
sd" eb:version="2.0"><eb:Reference eb:id="contentId" xlink:type="simple"
xlink:h
ref="cid:contentId"><eb:Description
xml:lang="en-US">description</eb:Description
></eb:Reference></eb:Manifest></soap-env:Body></soap-env:Envelope>
------=_Part_2_24749215.1068222593281
Content-Type: text/xml
Content-Transfer-Encoding: binary
Content-Id: <contentId>
 
<po/>
 
------=_Part_2_24749215.1068222593281--
 
----------echo-------------------------
 
regards,
Ajit

-----Original Message-----
From: Ronald van Kuijk [mailto:rv...@ab...]
Sent: Friday, November 07, 2003 9:33 PM
To: 'ebx...@li...'
Subject: RE: [ebxmlms-general] interesting hermes error


Do you get this message in hermes on receiving 'echo'?
 
This is caused by the servelet not detecting a multipart-mime header. Either
because it's not there or because the format is wrong. There has been
problems with the mail/activation libraries in Bea where they wew unable to
detect a boundary that spanned multiple lines. (spanning is done by having
the second line begin with a whitespace character, which bea failed to
detect). An plain html or a simple xml (including a echo of an ebxml
envelop!!) response also does not have the boundary set, and therefor leads
to the same error 
 
Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 16:38
Aan: 'ebx...@li...'
Onderwerp: [ebxmlms-general] interesting hermes error


Hi,
 
    I am using hermes to send a message from hermes to a JAXM servlet. If I
return the same ebXML message in reponse, this is what I am getting.
 
regards,
Ajit
 
javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)

RE: [ebxmlms-general] interesting hermes error

[Tripathi, A. (GXS) <Aji...@gx...>]

thanks Ronald! yes. i got this in hermes on receiving echo this is exactly
the same message that hermes understood coming in the first time...!

-----Original Message-----
From: Ronald van Kuijk [mailto:rv...@ab...]
Sent: Friday, November 07, 2003 9:33 PM
To: 'ebx...@li...'
Subject: RE: [ebxmlms-general] interesting hermes error


Do you get this message in hermes on receiving 'echo'?
 
This is caused by the servelet not detecting a multipart-mime header. Either
because it's not there or because the format is wrong. There has been
problems with the mail/activation libraries in Bea where they wew unable to
detect a boundary that spanned multiple lines. (spanning is done by having
the second line begin with a whitespace character, which bea failed to
detect). An plain html or a simple xml (including a echo of an ebxml
envelop!!) response also does not have the boundary set, and therefor leads
to the same error 
 
Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 16:38
Aan: 'ebx...@li...'
Onderwerp: [ebxmlms-general] interesting hermes error


Hi,
 
    I am using hermes to send a message from hermes to a JAXM servlet. If I
return the same ebXML message in reponse, this is what I am getting.
 
regards,
Ajit
 
javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)

RE: [ebxmlms-general] interesting hermes error

[Ronald v. K. <rv...@ab...>]

Do you get this message in hermes on receiving 'echo'?
 
This is caused by the servelet not detecting a multipart-mime header.
Either because it's not there or because the format is wrong. There has
been problems with the mail/activation libraries in Bea where they wew
unable to detect a boundary that spanned multiple lines. (spanning is
done by having the second line begin with a whitespace character, which
bea failed to detect). An plain html or a simple xml (including a echo
of an ebxml envelop!!) response also does not have the boundary set, and
therefor leads to the same error 
 
Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 16:38
Aan: 'ebx...@li...'
Onderwerp: [ebxmlms-general] interesting hermes error


Hi,
 
    I am using hermes to send a message from hermes to a JAXM servlet.
If I return the same ebXML message in reponse, this is what I am
getting.
 
regards,
Ajit
 
javax.mail.MessagingException: Missing start boundary
        at
javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
        at
javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)

[ebxmlms-general] interesting hermes error

[Tripathi, A. (GXS) <Aji...@gx...>]

Hi,
 
    I am using hermes to send a message from hermes to a JAXM servlet. If I
return the same ebXML message in reponse, this is what I am getting.
 
regards,
Ajit
 
javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
        at
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
        at java.security.AccessController.doPrivileged(Native Method)
        at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
        at
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
        at
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
        at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
        at
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
 
        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)

RE: [ebxmlms-general] hermes error

[Ronald v. K. <rv...@ab...>]

Probably the JAXM servlet you try to connect to sends something back
that cannot be converted to a soapmessage. We've had the same error when
e.g. a html response comes back. Dump the output of the response in the
jaxm servlet or generate a dump of the http request with e.g. ethereal.
 
Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 13:53
Aan: 'ebx...@li...'
Onderwerp: RE: [ebxmlms-general] hermes error


Hi,
 
    If I change the toMshUrl in the loopback client to one of my JAXM
servlets deployed elsewhere, the msh tries to send the msg to the
specified msh URL. This is the error I am getting on the sending side:
 
 
Exception: javax.xml.soap.SOAPException Message:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException:
Unable to internalize message
 
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <= MessageServer.retry
2003-11-07 18:22:55,734 DEBUG [Thread-20]: => Transaction.commit (txID:
#14)
2003-11-07 18:22:55,734 DEBUG [Thread-20]: =>
DbConnectionPool.freeConnection
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <=
DbConnectionPool.freeConnection
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <= Transaction.commit
2003-11-07 18:22:55,734 DEBUG [Thread-20]: MessageProcessor.wait[150000]
2003-11-07 18:22:55,734 DEBUG [Thread-21]: => HttpSender.run
2003-11-07 18:22:55,734 DEBUG [Thread-21]: =>
toMSHUrl[http://becajittripati:8080/loopback]
2003-11-07 18:22:55,734 DEBUG [Thread-21]: => HttpServlet.send
2003-11-07 18:22:55,734 INFO  [Thread-21]: Sending message to
<http://becajittripati:8080/loopback>
http://becajittripati:8080/loopback
2003-11-07 18:22:55,906 ERROR [Thread-21]: [10505] Cannot send SOAP
message
Exception: javax.xml.soap.SOAPException Message:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException:
Unable to internalize message
2003-11-07 18:22:55,906 DEBUG [Thread-21]: => MessageProcessor.wakeUp
2003-11-07 18:22:55,906 DEBUG [Thread-21]: <= MessageProcessor.wakeUp
2003-11-07 18:22:55,906 DEBUG [Thread-21]: <= HttpSender.run
2003-11-07 18:22:55,906 DEBUG [Thread-20]: =>
MessageServer.logSentMessage
2003-11-07 18:22:55,906 INFO  [Thread-20]: =>
DbConnectionPool.getConnection
2003-11-07 18:22:55,906 INFO  [Thread-20]: <=
DbConnectionPool.getConnection
 
regards,
Ajit
 
stacktrace
 
javax.servlet.ServletException: JAXM POST failed Unable to internalize
message
 at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:256)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241
5)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:171)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:172)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
 at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
 at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:59
4)
 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:392)
 at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:56
5)
 at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:619)
 at java.lang.Thread.run(Thread.java:536)

RE: [ebxmlms-general] hermes error

[Tripathi, A. (GXS) <Aji...@gx...>]

Hi,
 
    If I change the toMshUrl in the loopback client to one of my JAXM
servlets deployed elsewhere, the msh tries to send the msg to the specified
msh URL. This is the error I am getting on the sending side:
 
 
Exception: javax.xml.soap.SOAPException Message:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException:
Unable to internalize message
 
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <= MessageServer.retry
2003-11-07 18:22:55,734 DEBUG [Thread-20]: => Transaction.commit (txID: #14)
2003-11-07 18:22:55,734 DEBUG [Thread-20]: =>
DbConnectionPool.freeConnection
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <=
DbConnectionPool.freeConnection
2003-11-07 18:22:55,734 DEBUG [Thread-20]: <= Transaction.commit
2003-11-07 18:22:55,734 DEBUG [Thread-20]: MessageProcessor.wait[150000]
2003-11-07 18:22:55,734 DEBUG [Thread-21]: => HttpSender.run
2003-11-07 18:22:55,734 DEBUG [Thread-21]: =>
toMSHUrl[http://becajittripati:8080/loopback]
2003-11-07 18:22:55,734 DEBUG [Thread-21]: => HttpServlet.send
2003-11-07 18:22:55,734 INFO  [Thread-21]: Sending message to
<http://becajittripati:8080/loopback> http://becajittripati:8080/loopback
2003-11-07 18:22:55,906 ERROR [Thread-21]: [10505] Cannot send SOAP message
Exception: javax.xml.soap.SOAPException Message:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException:
Unable to internalize message
2003-11-07 18:22:55,906 DEBUG [Thread-21]: => MessageProcessor.wakeUp
2003-11-07 18:22:55,906 DEBUG [Thread-21]: <= MessageProcessor.wakeUp
2003-11-07 18:22:55,906 DEBUG [Thread-21]: <= HttpSender.run
2003-11-07 18:22:55,906 DEBUG [Thread-20]: => MessageServer.logSentMessage
2003-11-07 18:22:55,906 INFO  [Thread-20]: => DbConnectionPool.getConnection
2003-11-07 18:22:55,906 INFO  [Thread-20]: <= DbConnectionPool.getConnection
 
regards,
Ajit
 
stacktrace
 
javax.servlet.ServletException: JAXM POST failed Unable to internalize
message
 at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:171)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
 at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
 at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
 at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
 at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:392)
 at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
 at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:619)
 at java.lang.Thread.run(Thread.java:536)

RE: [ebxmlms-general] Hermes bug report

[Tripathi, A. (GXS) <Aji...@gx...>]

Mea culpa ... the bug was in my loopback client. I've verified the other
code to be correct.

-----Original Message-----
From: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Sent: Friday, November 07, 2003 3:15 PM
To: 'ebx...@li...';
'ebx...@li...'
Subject: [ebxmlms-general] Hermes bug report



Bob, Patrick,

I traced hermes a little bit more. 

This is what I am getting in the messages ... does it make sense?  I think
type and value of partyID elements are interchanged!!!!! Please confirm.

<eb:From><eb:PartyId
eb:type="Sample">fromPartyId</eb:PartyId></eb:From><eb:To><eb:PartyId
eb:type="Sampola">toPartyId</eb:PartyId></eb:To>

regards,

Ajit    

 

[ebxmlms-general] Hermes bug report

[Tripathi, A. (GXS) <Aji...@gx...>]

Bob, Patrick,

I traced hermes a little bit more. 

This is what I am getting in the messages ... does it make sense?  I think
type and value of partyID elements are interchanged!!!!! Please confirm.

<eb:From><eb:PartyId
eb:type="Sample">fromPartyId</eb:PartyId></eb:From><eb:To><eb:PartyId
eb:type="Sampola">toPartyId</eb:PartyId></eb:To>

regards,

Ajit    

---------------

The spec:

It is further recommended that these 783

values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12
I05 registries. 784

If the PartyId type attribute is not present, the content of the PartyId
element MUST be a URI 785

[RFC2396], otherwise the Receiving MSH SHOULD report an error (see section
4.1.5) with errorCode 786

 

3.1.1 From and To Elements 762

The REQUIRED From element identifies the Party that originated the message.
The REQUIRED To 763

element identifies the Party that is the intended recipient of the message.
Both To and From can contain 764

logical identifiers, such as a DUNS number, or identifiers that also imply a
physical location such as an 765

eMail address. 766

The From and the To elements each contains: 767

* PartyId elements - occurs one or more times 768

* Role element - occurs zero or one times. 769

If either the From or To elements contains multiple PartyId elements, all
members of the list MUST 770

identify the same organization. Unless a single type value refers to
multiple identification systems, the 771

value of any given type attribute MUST be unique within the list of PartyId
elements contained within 772

either the From or To element. 773

Note: This mechanism is particularly useful when transport of a message
between the parties may involve multiple 774

intermediaries. More generally, the From Party should provide identification
in all domains it knows in support of 775

intermediaries and destinations that may give preference to particular
identification systems. 776

The From and To elements contain zero or one Role child element that, if
present, SHALL immediately 777

follow the last PartyId child element. 778

3.1.1.1 PartyId Element 779

The PartyId element has a single attribute, type and the content is a string
value. The type attribute 780

indicates the domain of names to which the string in the content of the
PartyId element belongs. The 781

value of the type attribute MUST be mutually agreed and understood by each
of the Parties. It is 782

RECOMMENDED that the value of the type attribute be a URI. It is further
recommended that these 783

values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12
I05 registries. 784

If the PartyId type attribute is not present, the content of the PartyId
element MUST be a URI 785

[RFC2396], otherwise the Receiving MSH SHOULD report an error (see section
4.1.5) with errorCode 786

set to Inconsistent and severity set to Error. It is strongly RECOMMENDED
that the content of the 787

PartyId element be a URI. 788

3.1.1.2 Role Element 789

The Role element identifies the authorized role (fromAuthorizedRole or
toAuthorizedRole)

 

[ebxmlms-general] hermes basic question

[Tripathi, A. (GXS) <Aji...@gx...>]

Bob/Others,
 
    How does hermes decide whether the message is meant to be loopback?
 
    I changed the loopback client code to
 
            header.addFromPartyId("fromPartyId", "Sample");
            header.addToPartyId("toPartyId", "Sam");
 
    and 
 
            String cpaID = "CPA_2002";
            String conversationID = "Item_No_128";
            String service = " http://localhost:8080/loopback
<http://localhost:8080/loopback> ";
            String action = "Order";
 
That doesn't change anything... how do you make the msh forward a message to
another service?
 
regards,
Ajit        
 


-----Original Message-----
From: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Sent: Friday, November 07, 2003 10:35 AM
To: 'ebx...@li...'
Subject: [ebxmlms-general] ebXML sample client question


Hi,
 
    If I put the following in my loopback client...
 
            String cpaID = "CPA_2002";
            String conversationID = "Item_No_128";
            String service = "  <http://localhost:8080/loopback>
http://localhost:8080/loopback";
            String action = "Order";
 
   Shouldn't the msh forward the message to "
<http://localhost:8080/loopback> http://localhost:8080/loopback"? It doesn't
seem to.
 
    How do I make the msh forward the ebXML message to another JAXM servlet?
 
regards,
Ajit

[ebxmlms-general] ebXML sample client question

[Tripathi, A. (GXS) <Aji...@gx...>]

Hi,
 
    If I put the following in my loopback client...
 
            String cpaID = "CPA_2002";
            String conversationID = "Item_No_128";
            String service = "  <http://localhost:8080/loopback>
http://localhost:8080/loopback";
            String action = "Order";
 
   Shouldn't the msh forward the message to "
<http://localhost:8080/loopback> http://localhost:8080/loopback"? It doesn't
seem to.
 
    How do I make the msh forward the ebXML message to another JAXM servlet?
 
regards,
Ajit

RE: [ebxmlms-general] freebXML MSH Scalability

[Ronald v. K. <rv...@ab...>]

My  comments on 1 and 2:
 
1: Yes, Implementing such an interface would be great and that is just
what I did once before (but lost due to a system crash). I made an
interface DbConnectionPool and had both the original hermes
DbConnectionPool (renamed to DbConnectionPoolHermes) and a
DbConnectionPoolAppServer implement this interface. Via a property in de
config file I could switch from one to the other. Things I'd like to see
for this are:
- a DbConnectionPool interface
- a separate config file for the hermesconnectionpool
- Have the MessageServiceHandler not use the instance variables of the
connectionpool and generate an xml document or use it for debug output
but have the connectionpool generate such a document/output. 
 
In fact, I thinkh we should put all the persistency things in a nice
layer in it's own package, including the file persistency, transaction
things etc..Transaction handling btw could (should?) also be
standardized and so it uses the mechanisms available in app-servers and
Tomcat / Jetty plus (JTA/JTS)
 
2: The example DbConnectionPool that I have now (a little different than
the one I attached to one of the previous e-mails) works on both JBoss,
Tomcat, Bea and tonight I'll try Jetty plus. So there is no real
specific code in there. The app-server dependend issues will be in the
server specific deployment descriptos, if needed at all. 
 
Regarding the Weblogic cluster question. I have a cluster available and
could give it a try comming weekend. One of the (major) issues I expect
is locking. Hermes requires file access for persistency and thus both
servers need to have access to the same filesystem while locking is
implemented in a non-cluster aware transaction mechanism. 
 
Ronald

-----Oorspronkelijk bericht-----
Van: Bob Koon [mailto:py...@ce...]
Verzonden: donderdag 6 november 2003 7:25
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-general] freebXML MSH Scalability


No... I haven't tried it out... I just think about the followings:
1) If I get it right, I should make a interface for accessing resource,
like JDBC, JMS and files, and make this customizable to allow user to
implement it through JNDI? (I guess some non-enterprise people may just
use Hermes without JNDI instead)

2) Does the JNDI interface quite standardize for different app. server
like Tomcat, weblogic, etc? You know, although j2ee is quite standard,
developing j2ee will also be dependent to the app. server.
Regards,
Bob Koon

Tripathi, Ajit (GXS) wrote:


Bob,
 
    In an enterprise scale situation, not just connection pools, any
external resources - datasources (and JMS queues/connection factories in
the future... if JMS) should ideally be obtained via the app server's
JNDI enc. That will help developers use the app server's scalability
features.
 
    Has anyone experimented with deploying hermes in a weblogic cluster
yet?
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [ mailto:py...@ce... <mailto:py...@ce...>
]
Sent: Thursday, November 06, 2003 11:22 AM
To: ebx...@li...
<mailto:ebx...@li...> 
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


I am very sorry that I cannot understand the relation between using app
servers' database connection pool and scalability.
As I know, Hermes use its own database connection pooling and what's the
different of this with using app. server's database connection pool?
I can see that different app. server use different database connection
pool, and those interface are very different. So we need to provide
different "war" for different app. server, which make the deployment
difficult, isn't it?
I am very sorry that I don't have enough experience to make things
scalable, therefore if I have some mis-understandings, please point me
out.

Regards,
Bob Koon


Tripathi, Ajit (GXS) wrote:


Ronald,
 
I too am unfamiliar with administered db connections pools on tomcat
4.x. How does that work? 
 
If Hermes can use connection pools on app servers/weblogic, that would
help the eventual scalability objective.
 
BTW... why can't authentication also be managed by the server using
JAAS? Consider that.
 
However, in that case, the db connection pool will need to be
configurable in the deployment descriptor for hermes... wherever. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [ mailto:py...@ce... <mailto:py...@ce...>
]
Sent: Wednesday, November 05, 2003 3:04 PM
To: ebx...@li...
<mailto:ebx...@li...> 
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


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...
<mailto:Aji...@gx...> ]
Verzonden: maandag 3 november 2003 11:06
Aan: ' ebx...@li...
<mailto: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...
<mailto:kc...@ce...> ]
Sent: Thursday, October 30, 2003 7:47 PM
To: ebx...@li...
<mailto: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>
 

Re: [ebxmlms-general] freebXML MSH Scalability

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

Dear Ajit,
In fact I am thinking of it too. The problem of scalability is both 
discussed on mailing list and on our team. The question is more 
complicated when I think Reliable messaging, message order and even 
sync-reply on Business Document (although it is not implemented yet, but 
should be thought on design phase). Probably there are share on states 
and even messages. I have no idea on the interfaces design for such 
mechanism yet.
Regards,
Bob Koon

Tripathi, Ajit (GXS) wrote:

> something like that...
>  
> another concern: assuming a clustered environment, what state would 
> be maintained in hermes MSH instance running in one weblogic instance?
>  
> for example ... Does the msh check the persistent store for a message 
> being duplicate or not? This datastore will need to be shared between 
> MSHs and so - they should probably be using the same resource?  Can 
> the client send a message to any MSH instance in a cluster or will it 
> need to send subsequent messages to the same MSH...? I think we need 
> to think about such scenarios.
>  
> The question of state here is relevant for load balancing 
> and especially relevant for failover.
>  
> regards,
> Ajit
>
>     -----Original Message-----
>     From: Bob Koon [mailto:py...@ce...]
>     Sent: Thursday, November 06, 2003 11:55 AM
>     To: ebx...@li...
>     Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>
>     No... I haven't tried it out... I just think about the followings:
>     1) If I get it right, I should make a interface for accessing
>     resource, like JDBC, JMS and files, and make this customizable to
>     allow user to implement it through JNDI? (I guess some
>     non-enterprise people may just use Hermes without JNDI instead)
>     2) Does the JNDI interface quite standardize for different app.
>     server like Tomcat, weblogic, etc? You know, although j2ee is
>     quite standard, developing j2ee will also be dependent to the app.
>     server.
>     Regards,
>     Bob Koon
>
>     Tripathi, Ajit (GXS) wrote:
>
>>     Bob,
>>      
>>         In an enterprise scale situation, not just connection
>>     pools, any external resources - datasources (and JMS
>>     queues/connection factories in the future... if
>>     JMS) should ideally be obtained via the app server's JNDI enc.
>>     That will help developers use the app server's scalability features.
>>      
>>         Has anyone experimented with deploying hermes in a
>>     weblogic cluster yet?
>>      
>>     regards,
>>     Ajit
>>
>>         -----Original Message-----
>>         From: Bob Koon [mailto:py...@ce...]
>>         Sent: Thursday, November 06, 2003 11:22 AM
>>         To: ebx...@li...
>>         Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>>
>>         I am very sorry that I cannot understand the relation between
>>         using app servers' database connection pool and scalability.
>>         As I know, Hermes use its own database connection pooling and
>>         what's the different of this with using app. server's
>>         database connection pool?
>>         I can see that different app. server use different database
>>         connection pool, and those interface are very different. So
>>         we need to provide different "war" for different app. server,
>>         which make the deployment difficult, isn't it?
>>         I am very sorry that I don't have enough experience to make
>>         things scalable, therefore if I have some mis-understandings,
>>         please point me out.
>>
>>         Regards,
>>         Bob Koon
>>
>>
>>         Tripathi, Ajit (GXS) wrote:
>>
>>>         Ronald,
>>>          
>>>         I too am unfamiliar with administered db connections pools
>>>         on tomcat 4.x. How does that work?
>>>          
>>>         If Hermes can use connection pools on app servers/weblogic,
>>>         that would help the eventual scalability objective.
>>>          
>>>         BTW... why can't authentication also be managed by the
>>>         server using JAAS? Consider that.
>>>          
>>>         However, in that case, the db connection pool will need to
>>>         be configurable in the deployment descriptor for hermes...
>>>         wherever.
>>>          
>>>         regards,
>>>         Ajit
>>>
>>>             -----Original Message-----
>>>             From: Bob Koon [mailto:py...@ce...]
>>>             Sent: Wednesday, November 05, 2003 3:04 PM
>>>             To: ebx...@li...
>>>             Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>>>
>>>             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>
>>>>                          
>>>>

RE: [ebxmlms-general] freebXML MSH Scalability

[Tripathi, A. (GXS) <Aji...@gx...>]

something like that... 
 
another concern: assuming a clustered environment, what state would be
maintained in hermes MSH instance running in one weblogic instance? 
 
for example ... Does the msh check the persistent store for a message being
duplicate or not? This datastore will need to be shared between MSHs and so
- they should probably be using the same resource?  Can the client send a
message to any MSH instance in a cluster or will it need to send subsequent
messages to the same MSH...? I think we need to think about such scenarios.
 
The question of state here is relevant for load balancing and especially
relevant for failover. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [mailto:py...@ce...]
Sent: Thursday, November 06, 2003 11:55 AM
To: ebx...@li...
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


No... I haven't tried it out... I just think about the followings:
1) If I get it right, I should make a interface for accessing resource, like
JDBC, JMS and files, and make this customizable to allow user to implement
it through JNDI? (I guess some non-enterprise people may just use Hermes
without JNDI instead)
2) Does the JNDI interface quite standardize for different app. server like
Tomcat, weblogic, etc? You know, although j2ee is quite standard, developing
j2ee will also be dependent to the app. server.
Regards,
Bob Koon

Tripathi, Ajit (GXS) wrote:


Bob,
 
    In an enterprise scale situation, not just connection pools, any
external resources - datasources (and JMS queues/connection factories in the
future... if JMS) should ideally be obtained via the app server's JNDI enc.
That will help developers use the app server's scalability features.
 
    Has anyone experimented with deploying hermes in a weblogic cluster yet?
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [ mailto:py...@ce... <mailto:py...@ce...> ]
Sent: Thursday, November 06, 2003 11:22 AM
To: ebx...@li...
<mailto:ebx...@li...> 
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


I am very sorry that I cannot understand the relation between using app
servers' database connection pool and scalability.
As I know, Hermes use its own database connection pooling and what's the
different of this with using app. server's database connection pool?
I can see that different app. server use different database connection pool,
and those interface are very different. So we need to provide different
"war" for different app. server, which make the deployment difficult, isn't
it?
I am very sorry that I don't have enough experience to make things scalable,
therefore if I have some mis-understandings, please point me out.

Regards,
Bob Koon


Tripathi, Ajit (GXS) wrote:


Ronald,
 
I too am unfamiliar with administered db connections pools on tomcat 4.x.
How does that work? 
 
If Hermes can use connection pools on app servers/weblogic, that would help
the eventual scalability objective.
 
BTW... why can't authentication also be managed by the server using JAAS?
Consider that.
 
However, in that case, the db connection pool will need to be configurable
in the deployment descriptor for hermes... wherever. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [ mailto:py...@ce... <mailto:py...@ce...> ]
Sent: Wednesday, November 05, 2003 3:04 PM
To: ebx...@li...
<mailto:ebx...@li...> 
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


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...
<mailto:Aji...@gx...> ]
Verzonden: maandag 3 november 2003 11:06
Aan: ' ebx...@li...
<mailto: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... <mailto:kc...@ce...> ]
Sent: Thursday, October 30, 2003 7:47 PM
To: ebx...@li...
<mailto: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>
 

Re: [ebxmlms-general] freebXML MSH Scalability

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

No... I haven't tried it out... I just think about the followings:
1) If I get it right, I should make a interface for accessing resource, 
like JDBC, JMS and files, and make this customizable to allow user to 
implement it through JNDI? (I guess some non-enterprise people may just 
use Hermes without JNDI instead)
2) Does the JNDI interface quite standardize for different app. server 
like Tomcat, weblogic, etc? You know, although j2ee is quite standard, 
developing j2ee will also be dependent to the app. server.
Regards,
Bob Koon

Tripathi, Ajit (GXS) wrote:

> Bob,
>  
>     In an enterprise scale situation, not just connection 
> pools, any external resources - datasources (and JMS queues/connection 
> factories in the future... if JMS) should ideally be obtained via the 
> app server's JNDI enc. That will help developers use the app 
> server's scalability features.
>  
>     Has anyone experimented with deploying hermes in a 
> weblogic cluster yet?
>  
> regards,
> Ajit
>
>     -----Original Message-----
>     From: Bob Koon [mailto:py...@ce...]
>     Sent: Thursday, November 06, 2003 11:22 AM
>     To: ebx...@li...
>     Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>
>     I am very sorry that I cannot understand the relation between
>     using app servers' database connection pool and scalability.
>     As I know, Hermes use its own database connection pooling and
>     what's the different of this with using app. server's database
>     connection pool?
>     I can see that different app. server use different database
>     connection pool, and those interface are very different. So we
>     need to provide different "war" for different app. server, which
>     make the deployment difficult, isn't it?
>     I am very sorry that I don't have enough experience to make things
>     scalable, therefore if I have some mis-understandings, please
>     point me out.
>
>     Regards,
>     Bob Koon
>
>
>     Tripathi, Ajit (GXS) wrote:
>
>>     Ronald,
>>      
>>     I too am unfamiliar with administered db connections pools on
>>     tomcat 4.x. How does that work?
>>      
>>     If Hermes can use connection pools on app servers/weblogic, that
>>     would help the eventual scalability objective.
>>      
>>     BTW... why can't authentication also be managed by the server
>>     using JAAS? Consider that.
>>      
>>     However, in that case, the db connection pool will need to be
>>     configurable in the deployment descriptor for hermes... wherever.
>>      
>>     regards,
>>     Ajit
>>
>>         -----Original Message-----
>>         From: Bob Koon [mailto:py...@ce...]
>>         Sent: Wednesday, November 05, 2003 3:04 PM
>>         To: ebx...@li...
>>         Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>>
>>         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>
>>>                      
>>>

RE: [ebxmlms-general] freebXML MSH Scalability

[Tripathi, A. (GXS) <Aji...@gx...>]

Bob,
 
    In an enterprise scale situation, not just connection pools, any
external resources - datasources (and JMS queues/connection factories in the
future... if JMS) should ideally be obtained via the app server's JNDI enc.
That will help developers use the app server's scalability features.
 
    Has anyone experimented with deploying hermes in a weblogic cluster yet?
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [mailto:py...@ce...]
Sent: Thursday, November 06, 2003 11:22 AM
To: ebx...@li...
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


I am very sorry that I cannot understand the relation between using app
servers' database connection pool and scalability.
As I know, Hermes use its own database connection pooling and what's the
different of this with using app. server's database connection pool?
I can see that different app. server use different database connection pool,
and those interface are very different. So we need to provide different
"war" for different app. server, which make the deployment difficult, isn't
it?
I am very sorry that I don't have enough experience to make things scalable,
therefore if I have some mis-understandings, please point me out.

Regards,
Bob Koon


Tripathi, Ajit (GXS) wrote:


Ronald,
 
I too am unfamiliar with administered db connections pools on tomcat 4.x.
How does that work? 
 
If Hermes can use connection pools on app servers/weblogic, that would help
the eventual scalability objective.
 
BTW... why can't authentication also be managed by the server using JAAS?
Consider that.
 
However, in that case, the db connection pool will need to be configurable
in the deployment descriptor for hermes... wherever. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [ mailto:py...@ce... <mailto:py...@ce...> ]
Sent: Wednesday, November 05, 2003 3:04 PM
To: ebx...@li...
<mailto:ebx...@li...> 
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


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...
<mailto:Aji...@gx...> ]
Verzonden: maandag 3 november 2003 11:06
Aan: ' ebx...@li...
<mailto: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... <mailto:kc...@ce...> ]
Sent: Thursday, October 30, 2003 7:47 PM
To: ebx...@li...
<mailto: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>
 

Re: [ebxmlms-general] freebXML MSH Scalability

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

I am very sorry that I cannot understand the relation between using app 
servers' database connection pool and scalability.
As I know, Hermes use its own database connection pooling and what's the 
different of this with using app. server's database connection pool?
I can see that different app. server use different database connection 
pool, and those interface are very different. So we need to provide 
different "war" for different app. server, which make the deployment 
difficult, isn't it?
I am very sorry that I don't have enough experience to make things 
scalable, therefore if I have some mis-understandings, please point me out.

Regards,
Bob Koon


Tripathi, Ajit (GXS) wrote:

> Ronald,
>  
> I too am unfamiliar with administered db connections pools on tomcat 
> 4.x. How does that work?
>  
> If Hermes can use connection pools on app servers/weblogic, that would 
> help the eventual scalability objective.
>  
> BTW... why can't authentication also be managed by the server using 
> JAAS? Consider that.
>  
> However, in that case, the db connection pool will need to be 
> configurable in the deployment descriptor for hermes... wherever.
>  
> regards,
> Ajit
>
>     -----Original Message-----
>     From: Bob Koon [mailto:py...@ce...]
>     Sent: Wednesday, November 05, 2003 3:04 PM
>     To: ebx...@li...
>     Subject: Re: [ebxmlms-general] freebXML MSH Scalability
>
>     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>
>>                  
>>

[ebxmlms-general] Re: native connectionpools

[Ronald v. K. <rv...@ab...>]

I got it working in tomcat 4.1.29LE as well. I'll draw up a little 
how-to regarding the connection pool tomorrow and will post a new 
DbConnectionPool as well since there is a small change for jndi lookups.

btw. Can somebody explain why there is a normal and a raw connection?

Ronald


Ronald van Kuijk wrote:

> As promised:
>
> Connectionpools on tomcat :
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html 
>
>
> Connectionpools on Jetty:
> http://jetty.mortbay.org/jetty/plus/index.html
>
> Connectionpools on JBoss:
> http://prdownloads.sourceforge.net/jboss/JCAConfig322.pdf?download
>
> Attached you wil find a DbConnectioPool.java that is a real 
> stripped-down version of the original hermes DbConnectioPool class. 
> It's really stripped even the comment is gone ;-). I think 90% of the 
> code is now logging and error handling.
>
> It works on JBoss 3.2.2 with the attached mysql-ds.xml datasource and 
> the web.xml.
>
> I'll try to install Tomcat 4.1.x and 4.0.x in a moment and try to get 
> it working there as wel.
>
> Ronald
>
> Tripathi, Ajit (GXS) wrote:
>
>> Ronald,
>>  
>> I too am unfamiliar with administered db connections pools on tomcat 
>> 4.x. How does that work?
>>  
>> If Hermes can use connection pools on app servers/weblogic, that 
>> would help the eventual scalability objective.
>>  
>> BTW... why can't authentication also be managed by the server using 
>> JAAS? Consider that.
>>  
>> However, in that case, the db connection pool will need to be 
>> configurable in the deployment descriptor for hermes... wherever.
>>  
>> regards,
>> Ajit
>>
>>  
>

native connectionpools (was: Re: [ebxmlms-general] freebXML MSH Scalability)

[Ronald v. K. <rv...@ab...>]

As promised:

Connectionpools on tomcat :
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html

Connectionpools on Jetty:
http://jetty.mortbay.org/jetty/plus/index.html

Connectionpools on JBoss:
http://prdownloads.sourceforge.net/jboss/JCAConfig322.pdf?download

Attached you wil find a DbConnectioPool.java that is a real 
stripped-down version of the original hermes DbConnectioPool class. It's 
really stripped even the comment is gone ;-). I think 90% of the code is 
now logging and error handling.

It works on JBoss 3.2.2 with the attached mysql-ds.xml datasource and 
the web.xml.

I'll try to install Tomcat 4.1.x and 4.0.x in a moment and try to get it 
working there as wel.

Ronald

Tripathi, Ajit (GXS) wrote:

> Ronald,
>  
> I too am unfamiliar with administered db connections pools on tomcat 
> 4.x. How does that work?
>  
> If Hermes can use connection pools on app servers/weblogic, that would 
> help the eventual scalability objective.
>  
> BTW... why can't authentication also be managed by the server using 
> JAAS? Consider that.
>  
> However, in that case, the db connection pool will need to be 
> configurable in the deployment descriptor for hermes... wherever.
>  
> regards,
> Ajit
>
>     -----Original Message-----
>     *From:* Bob Koon [mailto:py...@ce...]
>     *Sent:* Wednesday, November 05, 2003 3:04 PM
>     *To:* ebx...@li...
>     *Subject:* Re: [ebxmlms-general] freebXML MSH Scalability
>
>     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>
>>                  
>>

RE: [ebxmlms-general] freebXML MSH Scalability

[Ronald v. K. <rv...@ab...>]

All,
 
I'll try to look-up some relevant links tonight (central european time,
it's 17:17 now) and try to recreate a connection-pool class that uses
the pools provided by the app-server afterwards.
 
Ronald

-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: woensdag 5 november 2003 11:28
Aan: 'ebx...@li...'
Onderwerp: RE: [ebxmlms-general] freebXML MSH Scalability


Ronald,
 
I too am unfamiliar with administered db connections pools on tomcat
4.x. How does that work? 

If Hermes can use connection pools on app servers/weblogic, that would
help the eventual scalability objective.
 
BTW... why can't authentication also be managed by the server using
JAAS? Consider that.
 
However, in that case, the db connection pool will need to be
configurable in the deployment descriptor for hermes... wherever. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [mailto:py...@ce...]
Sent: Wednesday, November 05, 2003 3:04 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


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...
<mailto:Aji...@gx...> ]
Verzonden: maandag 3 november 2003 11:06
Aan: ' ebx...@li...
<mailto: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...
<mailto:kc...@ce...> ]
Sent: Thursday, October 30, 2003 7:47 PM
To: ebx...@li...
<mailto: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>
 

RE: [ebxmlms-general] freebXML MSH Scalability

[Tripathi, A. (GXS) <Aji...@gx...>]

Ronald,
 
I too am unfamiliar with administered db connections pools on tomcat 4.x.
How does that work? 
 
If Hermes can use connection pools on app servers/weblogic, that would help
the eventual scalability objective.
 
BTW... why can't authentication also be managed by the server using JAAS?
Consider that.
 
However, in that case, the db connection pool will need to be configurable
in the deployment descriptor for hermes... wherever. 
 
regards,
Ajit

-----Original Message-----
From: Bob Koon [mailto:py...@ce...]
Sent: Wednesday, November 05, 2003 3:04 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] freebXML MSH Scalability


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...
<mailto:Aji...@gx...> ]
Verzonden: maandag 3 november 2003 11:06
Aan: ' ebx...@li...
<mailto: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... <mailto:kc...@ce...> ]
Sent: Thursday, October 30, 2003 7:47 PM
To: ebx...@li...
<mailto: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>
 

RE: [ebxmlms-general] URLResolverLDAP finished

[Ronald v. K. <rv...@ab...>]

Great, that would be my suggestion as well

I'll send something tonight

Ronald

> -----Oorspronkelijk bericht-----
> Van: Bob Koon [mailto:py...@ce...]
> Verzonden: woensdag 5 november 2003 10:47
> Aan: ebx...@li...
> Onderwerp: Re: [ebxmlms-general] URLResolverLDAP finished
> 
> 
> Dear Ronald,
> 
> I am glad to hear you that you have implemented the url 
> resolver for ldap.
> I think you can add the configuration to another properties 
> file rather 
> than msh.properties.xml. The reason is that user may not 
> choose to use 
> your URLResolver. If you like, you can use the Property provided on 
> hk.hku.phoenix.common.util. for your properties.
> 
> Regards
> Bob Koon
> 
> Ronald van Kuijk wrote:
> 
> > Hi,
> >
> > I finally implemented my ldap url resolver based on the 
> mozilla ldap 
> > sdk so It does not require jndi or any thing. It supports 
> > connectionpooling and caching. All the parameters, 
> including the ldap 
> > server, port and credentials, search base, filter etc.. are 
> currently 
> > hardcoded in the resolver as they suit my environment. I'd like to 
> > make it configurable however and send it as a contribution to this 
> > project.
> >
> > Any suggestions on how to make it configuranle in a hermes 
> compliant 
> > way? I could add several attributes on the resolver 
> element, but that 
> > probably leads to schema changes of the config file.
> >
> > Ronald
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?   SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > ebxmlms-general mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> 

Re: [ebxmlms-general] URLResolverLDAP finished

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

Dear Ronald,

I am glad to hear you that you have implemented the url resolver for ldap.
I think you can add the configuration to another properties file rather 
than msh.properties.xml. The reason is that user may not choose to use 
your URLResolver. If you like, you can use the Property provided on 
hk.hku.phoenix.common.util. for your properties.

Regards
Bob Koon

Ronald van Kuijk wrote:

> Hi,
>
> I finally implemented my ldap url resolver based on the mozilla ldap 
> sdk so It does not require jndi or any thing. It supports 
> connectionpooling and caching. All the parameters, including the ldap 
> server, port and credentials, search base, filter etc.. are currently 
> hardcoded in the resolver as they suit my environment. I'd like to 
> make it configurable however and send it as a contribution to this 
> project.
>
> Any suggestions on how to make it configuranle in a hermes compliant 
> way? I could add several attributes on the resolver element, but that 
> probably leads to schema changes of the config file.
>
> Ronald
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>

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>
>              
>

[ebxmlms-general] URLResolverLDAP finished

[Ronald v. K. <rv...@ab...>]

Hi,

I finally implemented my ldap url resolver based on the mozilla ldap sdk 
so It does not require jndi or any thing. It supports connectionpooling 
and caching. All the parameters, including the ldap server, port and 
credentials, search base, filter etc.. are currently hardcoded in the 
resolver as they suit my environment. I'd like to make it configurable 
however and send it as a contribution to this project.

Any suggestions on how to make it configuranle in a hermes compliant 
way? I could add several attributes on the resolver element, but that 
probably leads to schema changes of the config file.

Ronald