You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(20) |
Nov
(11) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(11) |
Feb
(8) |
Mar
(17) |
Apr
(11) |
May
(9) |
Jun
(30) |
Jul
(18) |
Aug
|
Sep
(4) |
Oct
(34) |
Nov
(83) |
Dec
(28) |
| 2004 |
Jan
(4) |
Feb
|
Mar
(13) |
Apr
(20) |
May
(4) |
Jun
(26) |
Jul
(5) |
Aug
(2) |
Sep
(3) |
Oct
(7) |
Nov
(10) |
Dec
(24) |
| 2005 |
Jan
(7) |
Feb
(44) |
Mar
(9) |
Apr
(16) |
May
(9) |
Jun
(64) |
Jul
(48) |
Aug
(36) |
Sep
(27) |
Oct
(24) |
Nov
(20) |
Dec
(11) |
| 2006 |
Jan
(12) |
Feb
(13) |
Mar
(7) |
Apr
|
May
(16) |
Jun
(5) |
Jul
(2) |
Aug
(7) |
Sep
(19) |
Oct
(5) |
Nov
(9) |
Dec
(13) |
| 2007 |
Jan
(21) |
Feb
(12) |
Mar
(6) |
Apr
|
May
(2) |
Jun
(14) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(5) |
May
(2) |
Jun
(1) |
Jul
(6) |
Aug
|
Sep
(9) |
Oct
(3) |
Nov
(25) |
Dec
(32) |
| 2009 |
Jan
(11) |
Feb
(12) |
Mar
(18) |
Apr
(19) |
May
(31) |
Jun
(23) |
Jul
(35) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
(8) |
| 2010 |
Jan
(3) |
Feb
(3) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Robert A. S. <ro...@no...> - 2005-08-10 16:36:16
|
I am able to connect to the Cyclone server using the simple HTTPSClient below. I am almost positive that the handshaking problem - it isn't a problem with Hermes, more like with the HttpsURLConnection class which Hermes utilizes. I would file a bug report with Sun - but unless I can give them access to our trading partner's development environment - I have no way to replicate the issue for them. So I am pretty much out of luck. If anybody comes up with a work-around - I would LOVE to hear about it. Thanks, -Rob -----Original Message----- From: ebx...@li... [mailto:ebx...@li...] On Behalf Of ebx...@li... Sent: Tuesday, August 02, 2005 8:15 PM To: ebx...@li... Subject: ebxmlms-general digest, Vol 1 #276 - 3 msgs Send ebxmlms-general mailing list submissions to ebx...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/ebxmlms-general or, via email, send a message with subject or body 'help' to ebx...@li... You can reach the person managing the list at ebx...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of ebxmlms-general digest..." Today's Topics: 1. RE: SSLHandshakeException (SSL PROBLEM) (Robert A. Stockfleth) 2. RE: RE: SSLHandshakeException (SSL PROBLEM) (Pattiarachi, Mal) 3. Re: RE: SSLHandshakeException (SSL PROBLEM) (David Webber (XML)) --__--__-- Message: 1 From: "Robert A. Stockfleth" <ro...@no...> To: <ebx...@li...> Date: Tue, 2 Aug 2005 15:05:00 -0700 Subject: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) Reply-To: ebx...@li... This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C59773.8DC924D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit A few weeks ago I figured out where my SSL Handshake problem is coming from. It seems that by default Hermes uses the HttpsURLConnection class to connect (when you're accessing a HTTPS URL). I rewrote the SSL connection portion of Http.java to use the Socket class instead of the HttpsURLConnection class. When I connected using the exact same keystore - the handshaking process worked properly. It seems like something inside the HttpsURLConnection class was not compatible with the Cyclone server, my private key or both. Anyone have any ideas (that don't involve hacking the source apart)?? PS Any chance future versions of Hermes will undergo Drummond's "EBXML" certification. Many large companies will not allow outside vendors to connect, unless they are using an officially EBXML certified application. Message: 2 From: "Pattiarachi, Mal" <Mal...@ro...> To: <ebx...@li...> Subject: RE: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) Date: Wed, 3 Aug 2005 09:30:57 +1000 Reply-To: ebx...@li... This is a multi-part message in MIME format. ------_=_NextPart_001_01C597BA.3BDDD192 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hi Robert, I'm getting a similar error (javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake) at random occassions (some connections get through), when connecting to Tibco Business Connect in = our partners test environment. Oddly enough, in production, where our = partner uses an external clustered HTTPS web server, the connections appear to = work fine. The thing is, the problem is replicable outside of Hermes... i.e. I used = a simple HTTPS client (consisting of just a few lines of code) which uses = the socket method of connecting, and I still got the same error I'm getting = with Hermes ... and this was duplicated no matter the version of Java I was using, be it 1.4.2_01 or 1.4.2_08 or 1.5! I figured this was a problem = to do with Tibco's internal SSL handler which wasn't behaving correctly and requested our partner try to see what's going on with Tibco. We use Hermes 0.9.3.1 and Java 1.4.2, I examined Http.java - most if it appears to be commented out? Perhaps it's changed between versions. I've attached the source code I was using for the simple HTTPS client, = see if you can connect to your partners Cyclone using it.=20 import java.net.*; import java.io.*; import java.security.*; import javax.net.ssl.*; public class HTTPSClient { public static void main(String[] args) { int port =3D 6707; String host =3D "HOST_URL"; try { Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider()); SSLSocketFactory factory =3D (SSLSocketFactory) SSLSocketFactory.getDefault(); SSLSocket socket =3D (SSLSocket) factory.createSocket(host, port); Writer out =3D new OutputStreamWriter(socket.getOutputStream()); // https requires the full URL in the GET line out.write("GET http://" + host + "/ HTTP/1.1\r\n"); out.write("\r\n"); out.flush(); // read response BufferedReader in =3D new BufferedReader( new InputStreamReader(socket.getInputStream())); int c; while ((c =3D in.read()) !=3D -1) { System.out.write(c); } out.close(); in.close(); socket.close(); } catch (Exception e) { System.out.println(e); } } } -----Original Message----- From: ebx...@li... [mailto:ebx...@li...] On Behalf Of Robert = A. Stockfleth Sent: Wednesday, 3 August 2005 8:05 AM To: ebx...@li... Subject: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) A few weeks ago I figured out where my SSL Handshake problem is coming = from. =20 It seems that by default Hermes uses the HttpsURLConnection class to = connect (when you're accessing a HTTPS URL). =20 I rewrote the SSL connection portion of Http.java to use the Socket = class instead of the HttpsURLConnection class. When I connected using the = exact same keystore - the handshaking process worked properly. =20 It seems like something inside the HttpsURLConnection class was not compatible with the Cyclone server, my private key or both. =20 Anyone have any ideas (that don't involve hacking the source apart)?? =20 PS Any chance future versions of Hermes will undergo Drummond's "EBXML" certification. Many large companies will not allow outside vendors to connect, unless they are using an officially EBXML certified = application. =20 The information contained in this email and any attachments to it: =20 (a) may be confidential and if you are not the intended recipient, any = interference with,=20 use, disclosure or copying of this material is unauthorised and = prohibited; and =20 (b) may contain personal information of the recipient and/or the sender = as defined under the Privacy Act 1988 (Cth). Consent is hereby given by the = recipient(s) to=20 collect, hold and use such information and any personal information = contained in a=20 response to this email, for any reasonable purpose in the ordinary = course of=20 Ross Human Directions Limited business (including all of it=92s = subsidiaries), including=20 forwarding this email internally or disclosing it to a third party.=20 All personal information collected by Ross Human Directions Limited will = be handled in=20 accordance with Ross Human Directions Limited Privacy Policy. If you = have received this=20 email in error, please notify the sender and delete it.=20 (c) you agree not to employ or arrange employment for any candidate(s) = supplied in=20 this email and any attachments without first entering into a contractual = agreement with=20 Ross Human Directions Limited. You further agree not to divulge any = information contained=20 in this document to any person(s) or entities without the express = permission of=20 Ross Human Directions Limited.=20 Message: 3 From: "David Webber \(XML\)" <da...@dr...> To: <ebx...@li...> Subject: Re: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) Date: Tue, 2 Aug 2005 22:25:25 -0400 Organization: XML eBusiness Reply-To: ebx...@li... This is a multi-part message in MIME format. ------=_NextPart_000_00F1_01C597B1.145CD180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Robert, Good catch. On the certification front. I've done the Drummond testing with a = commercial product. I would venture that if Hermes can freely interchange with the target = server (say Cyclone - which BTW has probably the most complete = implementation) - that is exactly like completing the Drummond testing = anyway. Of course Drummond makes you perform a range of tests with four or more = other vendors - but you can easily verify that Hermes matches those = needs. BTW - the CPA handling in current Hermes is not all it should be. My = understanding that is being enhanced - along the lines we did in the = code here - http://ebxmlbook.com/interop/=20 All this is about verifying the operation. For example - Oracle now has = a ebMS compatible server to for iHub - but its not "certified" - and = I'll wager that your management would happily use it, eh? Hope that helps your decision making. Thanks, DW _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general End of ebxmlms-general Digest |
|
From: Michal P. <pl...@nc...> - 2005-08-10 01:16:02
|
Dnia 2005-08-10 02:57, Michal Postupalski napisa=B3(a):
> Hi !
>=20
> I've got problem with deleting attached file as payload after
> successfully sent message. Seems that attached file is lock'ed. Doing
> something like this:
>=20
> <stub>
> File payload =3D new File("payload.xml");
> ...
> ...
> AttachmentDataSource ads =3D new AttachmentDataSource( payload,
> "application/xml" );
> DataHandler dataHandler =3D new DataHandler( ads );
> message.addPayloadContainer( dataHandler, payload.getName(),
> "description" );
> ....
> ....
> message.saveChanges();
> mshRequest.send( message );
>=20
> if ( !payload.delete() ) {
> //and can't delete file
> System.out.println( "always return false" );
> }
> </stub>
>=20
> I was checking read/write rights and always returned true.
>=20
> Can anybody help me with it???
ok, problem solved ;) I should load attachment to memory:
AttachmentDataSource ads =3D new AttachmentDataSource( payload,
"application/xml", true );
|
|
From: Michal P. <pl...@nc...> - 2005-08-10 00:58:45
|
Hi !
I've got problem with deleting attached file as payload after
successfully sent message. Seems that attached file is lock'ed. Doing
something like this:
<stub>
File payload = new File("payload.xml");
...
...
AttachmentDataSource ads = new AttachmentDataSource( payload,
"application/xml" );
DataHandler dataHandler = new DataHandler( ads );
message.addPayloadContainer( dataHandler, payload.getName(),
"description" );
....
....
message.saveChanges();
mshRequest.send( message );
if ( !payload.delete() ) {
//and can't delete file
System.out.println( "always return false" );
}
</stub>
I was checking read/write rights and always returned true.
Can anybody help me with it???
|
|
From: David W. \(XML\) <da...@dr...> - 2005-08-03 17:36:14
|
A plug is a good thing! TV presenters "plug" things all the time - as do commercials of course. Now you have me thinking about the origins of this saying - maybe that it is the solution - the plug they want you to connect to...? Or that they hold something up and it is the plug for you - like putting a plug into something to turn it on.....? From programming to linguistic origins in one seamless leap! http://www.answers.com/topic/plug ; -) DW ----- Original Message ----- From: "Sacha Schlegel" <sa...@sc...> To: <ebx...@li...> Sent: Wednesday, August 03, 2005 1:18 PM Subject: Re: [ebxmlms-general] Best book/resources on explaining ebXML/ebMS from the ground up? > Hi David > > Sorry I do not understand this saying. > > Are you happy or upset? > > Sacha > > On Wed, 2005-08-03 at 12:44 -0400, David Webber (XML) wrote: > > > > Thanks for the plug! > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > |
|
From: Sacha S. <sa...@sc...> - 2005-08-03 17:19:27
|
Hi David Sorry I do not understand this saying. Are you happy or upset? Sacha On Wed, 2005-08-03 at 12:44 -0400, David Webber (XML) wrote: > > Thanks for the plug! |
|
From: David W. \(XML\) <da...@dr...> - 2005-08-03 16:44:20
|
Sacha, Thanks for the plug! BTW - a we have a quick primer PDF that people may like to read: http://ebxmlbook.com/benefits/ and there is also a ton more "stuff" at http://ebxmlforum.org DW ----- Original Message ----- From: "Sacha Schlegel" <sa...@sc...> To: <ebx...@li...> Sent: Wednesday, August 03, 2005 2:56 AM Subject: Re: [ebxmlms-general] Best book/resources on explaining ebXML/ebMS from the ground up? > Hi Steven > > I can suggest "Professional ebXML Foundations" by Duane Nickull, et al by > Wrox Press. Several of the authors were and still are active members of > the ebXML project. > > Also, ebXML: The New Global Standard for Doing Business on the Internet by > Alan Kotok, et al by New Riders may be interesting for you as the > co-author David Webber is active in this mailinglist ;) so maybe a very > good contact to ask direct questions. > > Book resellers have other books on ebXML, just search for them. > > Also do not be afraid of reading the ebXML specifications, they are not so > hard to read after all. Maybe a good starting point is the "ebXML > Technical Architecture". Then it depends on where you interest is, if it > is messaging the ebXML Message Service specification may be of value. > > Regards > > Sacha > > > The subject says it all... > > > > Can anybody point me at the best book/resources on explaining ebXML/ebMS > > from the ground up? > > > > Thanks > > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > |
|
From: David W. \(XML\) <da...@dr...> - 2005-08-03 14:41:04
|
Patrick, OK - understood. I'm forwarding your request to the program team so I can get a good answer. I think the documentation doc contains descriptions - but I'll find out exactly where... Thanks, DW ----- Original Message ----- From: "Patrick Yee" <kc...@ce...> To: <ebx...@li...> Sent: Wednesday, August 03, 2005 4:07 AM Subject: Re: To DW, was [ebxmlms-general] Out of memory error in the MSH monitor > > http://ebxmlbook.com/interop/ > > Dear DW, > > We are going to package the patches we have made in > the last six months and release hermes 1.0.0.1 next > week. > > I just tried to download the patches you have > contributed and see if I can get it into the main > trunk. Unfortunately, I found that it quite difficult > to diff your updated source code and the current > source code we have in the CVS (somehow there are > some whitespace addition/deletion so that many > lines look different to diff). Do you have a > summary of the changes so that I can refer to? > > Thanks a lot for your help and contribution. > > Regards, -Patrick > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > |
|
From: David W. \(XML\) <da...@dr...> - 2005-08-03 13:40:28
|
http://ebxmlbook.com=20 DW ----- Original Message -----=20 From: Steven Herod=20 To: ebx...@li...=20 Sent: Wednesday, August 03, 2005 1:11 AM Subject: [ebxmlms-general] Best book/resources on explaining = ebXML/ebMS from the ground up? The subject says it all... Can anybody point me at the best book/resources on explaining = ebXML/ebMS from the ground up? Thanks |
|
From: Patrick Y. <kc...@ce...> - 2005-08-03 08:07:49
|
> http://ebxmlbook.com/interop/ Dear DW, We are going to package the patches we have made in the last six months and release hermes 1.0.0.1 next week. I just tried to download the patches you have contributed and see if I can get it into the main trunk. Unfortunately, I found that it quite difficult to diff your updated source code and the current source code we have in the CVS (somehow there are some whitespace addition/deletion so that many lines look different to diff). Do you have a summary of the changes so that I can refer to? Thanks a lot for your help and contribution. Regards, -Patrick |
|
From: Ted <ts...@fr...> - 2005-08-03 06:39:55
|
Publisher wrox "Professional ebXML Foundations" ISBN 1-861005-90-3 Piblisher Wiley " ebXML Concepts and Applications" ISBN 0-76-7645-4960-X These are helpful Ted _____ From: ebx...@li... [mailto:ebx...@li...] On Behalf Of Steven Herod Sent: Wednesday, 3 August 2005 1:12 PM To: ebx...@li... Subject: [ebxmlms-general] Best book/resources on explaining ebXML/ebMS from the ground up? The subject says it all... Can anybody point me at the best book/resources on explaining ebXML/ebMS from the ground up? Thanks |
|
From: Sacha S. <sa...@sc...> - 2005-08-03 06:31:56
|
Hi Steven I can suggest "Professional ebXML Foundations" by Duane Nickull, et al by Wrox Press. Several of the authors were and still are active members of the ebXML project. Also, ebXML: The New Global Standard for Doing Business on the Internet by Alan Kotok, et al by New Riders may be interesting for you as the co-author David Webber is active in this mailinglist ;) so maybe a very good contact to ask direct questions. Book resellers have other books on ebXML, just search for them. Also do not be afraid of reading the ebXML specifications, they are not so hard to read after all. Maybe a good starting point is the "ebXML Technical Architecture". Then it depends on where you interest is, if it is messaging the ebXML Message Service specification may be of value. Regards Sacha > The subject says it all... > > Can anybody point me at the best book/resources on explaining ebXML/ebMS > from the ground up? > > Thanks > |
|
From: Steven H. <sh...@te...> - 2005-08-03 05:12:07
|
The subject says it all... Can anybody point me at the best book/resources on explaining ebXML/ebMS from the ground up? Thanks |
|
From: David W. \(XML\) <da...@dr...> - 2005-08-03 02:25:39
|
Robert, Good catch. On the certification front. I've done the Drummond testing with a = commercial product. I would venture that if Hermes can freely interchange with the target = server (say Cyclone - which BTW has probably the most complete = implementation) - that is exactly like completing the Drummond testing = anyway. Of course Drummond makes you perform a range of tests with four or more = other vendors - but you can easily verify that Hermes matches those = needs. BTW - the CPA handling in current Hermes is not all it should be. My = understanding that is being enhanced - along the lines we did in the = code here - http://ebxmlbook.com/interop/=20 All this is about verifying the operation. For example - Oracle now has = a ebMS compatible server to for iHub - but its not "certified" - and = I'll wager that your management would happily use it, eh? Hope that helps your decision making. Thanks, DW ----- Original Message -----=20 From: Robert A. Stockfleth=20 To: ebx...@li...=20 Sent: Tuesday, August 02, 2005 6:05 PM Subject: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) A few weeks ago I figured out where my SSL Handshake problem is coming = from. =20 It seems that by default Hermes uses the HttpsURLConnection class to = connect (when you're accessing a HTTPS URL). =20 I rewrote the SSL connection portion of Http.java to use the Socket = class instead of the HttpsURLConnection class. When I connected using = the exact same keystore - the handshaking process worked properly. =20 It seems like something inside the HttpsURLConnection class was not = compatible with the Cyclone server, my private key or both. =20 Anyone have any ideas (that don't involve hacking the source apart)?? =20 PS Any chance future versions of Hermes will undergo Drummond's = "EBXML" certification. Many large companies will not allow outside = vendors to connect, unless they are using an officially EBXML certified = application. =20 |
|
From: Pattiarachi, M. <Mal...@ro...> - 2005-08-02 23:30:45
|
Hi Robert, I'm getting a similar error (javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake) at random occassions (some connections get through), when connecting to Tibco Business Connect in = our partners test environment. Oddly enough, in production, where our = partner uses an external clustered HTTPS web server, the connections appear to = work fine. The thing is, the problem is replicable outside of Hermes... i.e. I used = a simple HTTPS client (consisting of just a few lines of code) which uses = the socket method of connecting, and I still got the same error I'm getting = with Hermes ... and this was duplicated no matter the version of Java I was using, be it 1.4.2_01 or 1.4.2_08 or 1.5! I figured this was a problem = to do with Tibco's internal SSL handler which wasn't behaving correctly and requested our partner try to see what's going on with Tibco. We use Hermes 0.9.3.1 and Java 1.4.2, I examined Http.java - most if it appears to be commented out? Perhaps it's changed between versions. I've attached the source code I was using for the simple HTTPS client, = see if you can connect to your partners Cyclone using it.=20 import java.net.*; import java.io.*; import java.security.*; import javax.net.ssl.*; public class HTTPSClient { public static void main(String[] args) { int port =3D 6707; String host =3D "HOST_URL"; try { Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider()); SSLSocketFactory factory =3D (SSLSocketFactory) SSLSocketFactory.getDefault(); SSLSocket socket =3D (SSLSocket) factory.createSocket(host, port); Writer out =3D new OutputStreamWriter(socket.getOutputStream()); // https requires the full URL in the GET line out.write("GET http://" + host + "/ HTTP/1.1\r\n"); out.write("\r\n"); out.flush(); // read response BufferedReader in =3D new BufferedReader( new InputStreamReader(socket.getInputStream())); int c; while ((c =3D in.read()) !=3D -1) { System.out.write(c); } out.close(); in.close(); socket.close(); } catch (Exception e) { System.out.println(e); } } } -----Original Message----- From: ebx...@li... [mailto:ebx...@li...] On Behalf Of Robert = A. Stockfleth Sent: Wednesday, 3 August 2005 8:05 AM To: ebx...@li... Subject: [ebxmlms-general] RE: SSLHandshakeException (SSL PROBLEM) A few weeks ago I figured out where my SSL Handshake problem is coming = from. =20 It seems that by default Hermes uses the HttpsURLConnection class to = connect (when you're accessing a HTTPS URL). =20 I rewrote the SSL connection portion of Http.java to use the Socket = class instead of the HttpsURLConnection class. When I connected using the = exact same keystore - the handshaking process worked properly. =20 It seems like something inside the HttpsURLConnection class was not compatible with the Cyclone server, my private key or both. =20 Anyone have any ideas (that don't involve hacking the source apart)?? =20 PS Any chance future versions of Hermes will undergo Drummond's "EBXML" certification. Many large companies will not allow outside vendors to connect, unless they are using an officially EBXML certified = application. =20 The information contained in this email and any attachments to it: =20 (a) may be confidential and if you are not the intended recipient, any = interference with,=20 use, disclosure or copying of this material is unauthorised and = prohibited; and =20 (b) may contain personal information of the recipient and/or the sender = as defined under the Privacy Act 1988 (Cth). Consent is hereby given by the = recipient(s) to=20 collect, hold and use such information and any personal information = contained in a=20 response to this email, for any reasonable purpose in the ordinary = course of=20 Ross Human Directions Limited business (including all of it=92s = subsidiaries), including=20 forwarding this email internally or disclosing it to a third party.=20 All personal information collected by Ross Human Directions Limited will = be handled in=20 accordance with Ross Human Directions Limited Privacy Policy. If you = have received this=20 email in error, please notify the sender and delete it.=20 (c) you agree not to employ or arrange employment for any candidate(s) = supplied in=20 this email and any attachments without first entering into a contractual = agreement with=20 Ross Human Directions Limited. You further agree not to divulge any = information contained=20 in this document to any person(s) or entities without the express = permission of=20 Ross Human Directions Limited.=20 |
|
From: Robert A. S. <ro...@no...> - 2005-08-02 22:05:29
|
A few weeks ago I figured out where my SSL Handshake problem is coming from. It seems that by default Hermes uses the HttpsURLConnection class to connect (when you're accessing a HTTPS URL). I rewrote the SSL connection portion of Http.java to use the Socket class instead of the HttpsURLConnection class. When I connected using the exact same keystore - the handshaking process worked properly. It seems like something inside the HttpsURLConnection class was not compatible with the Cyclone server, my private key or both. Anyone have any ideas (that don't involve hacking the source apart)?? PS Any chance future versions of Hermes will undergo Drummond's "EBXML" certification. Many large companies will not allow outside vendors to connect, unless they are using an officially EBXML certified application. |
|
From: Patrick Y. <kc...@ce...> - 2005-08-02 03:04:59
|
Basically, you will need two pairs of keys. One for sender and one for receiver. Let's say they are named pkey_sender.p12 and pkey_receiver.p12. You need to put the name of keystore under the AckSign properties, your example is correct in specifying this. Next, you need to import the public cert of the issuing CA to the both Hermes. You need to import the .crt file to a keystore, typically in JKS or PKCS format. And then specify the file name of the keystore in the TrustedAnchor. Please do not specify the .crt file directly. Hope this helps. Regards, Patrick Yee Center for E-Commerce Infrastructure Development Making E-Commerce Everyday Commerce em...@og... wrote: > > Grateful if anyone successfully configuring Hermes to adopt the > digital signature could share the experience. > > When I performed a demo using MSH Monitor, the "Cannot receive > acknowledgement" error message was logged in Error History after a > message was sent with the "Require Signed Acknowledgement" selected. > When I sent a message with appropriate information specified in the > "Digital Signature" section in the MSH Monitor, no any result/error > message was received in Send/Receive/Error History. > > The private key used for signing the message itself or its > acknowledgement is named "pkey.p12" while the certificate of the > issuing CA was "SubCA.crt". > > <DigitalSignature> in msh.properties.xml for both the sending Hermes > and receiving Hermes was configured as follows: > > *-* <file://c:/program/#> <DigitalSignature> > *-* <file://c:/program/#> <TrustedAnchor> > *-* <file://c:/program/#> <KeyStore> > * * <Path>*/hermes*</Path> > * * <File>*SubCA.crt*</File> > * * <Password></Password> > * * </KeyStore> > * * </TrustedAnchor> > *-* <file://c:/program/#> <AckSign> > *-* <file://c:/program/#> <KeyStore> > * * <Path>*/hermes*</Path> > * * <File>*pkey.p12*</File> > * * <Algorithm>*dsa-sha1*</Algorithm> > * * <Alias>*ackkey*</Alias> > * * <Password>*XXXXXXXXXXXXXXX*</Password> > * * </KeyStore> > * * </AckSign> > * * </DigitalSignature> |
|
From: <em...@og...> - 2005-07-28 07:05:26
|
Grateful if anyone successfully configuring Hermes to adopt the digital signature could share the experience. When I performed a demo using MSH Monitor, the "Cannot receive acknowledgement" error message was logged in Error History after a message was sent with the "Require Signed Acknowledgement" selected. When I sent a message with appropriate information specified in the "Digital Signature" section in the MSH Monitor, no any result/error message was received in Send/Receive/Error History. The private key used for signing the message itself or its acknowledgement is named "pkey.p12" while the certificate of the issuing CA was "SubCA.crt". <DigitalSignature> in msh.properties.xml for both the sending Hermes and receiving Hermes was configured as follows: - <DigitalSignature> - <TrustedAnchor> - <KeyStore> <Path>/hermes</Path> <File>SubCA.crt</File> <Password></Password> </KeyStore> </TrustedAnchor> - <AckSign> - <KeyStore> <Path>/hermes</Path> <File>pkey.p12</File> <Algorithm>dsa-sha1</Algorithm> <Alias>ackkey</Alias> <Password>XXXXXXXXXXXXXXX</Password> </KeyStore> </AckSign> </DigitalSignature> |
|
From: Patrick Y. <kc...@ce...> - 2005-07-25 03:03:25
|
Hi MC, I am sorry that Hermes Monitor client is designed for demonstration purpose only. Everytime it receives a message, it stores the messages in the memory. Therefore, Monitor is suitable for testing the connectivity and parameters only. You are recommended to write your own Hermes client for serious applications. Hermes server is using another approach (storing the sent/received messages at database and file repository), so this problem only occurs in the Monitor. Regards, Patrick Yee Center for E-Commerce Infrastructure Development Making E-Commerce Everyday Commerce em...@og... wrote: > > When I repeatedly sent a message with one attachment of size 600KB 100 > times from the MSH monitor in one Windows PC (call it A) to the MSH > monitor in another Windows PC (call it B), the monitor in B showed the > java.lang.OutOfMemoryError after displaying the first 66 messages > received in the "Receive History" (the remaining 34 messages could be > displayed after OutOfMemoryError occurred), while the monitor in A > revealed all 100 messages sent with the state "Sent and > Acknowledgement Received" when right-clicking the messages in the > "Sent History" in A. > > The OutOfMemoryError still occurred until the MSH monitor in B was > restarted. Right after the restart, the remaining 34 messages were > displayed in the "Receive History". > > The default MaxPayloadSize (1000000) in msh_client.properties.xml is > used. PC A has 512MB RAM and paging file size allocated is 768MB, > while PC B has 768MB RAM and paging file size allocated is 1152MB. > > I have some questions based on the above incident: > > 1. Although PC B did not reveals all messages, PC A reveals that all > mesages "Sent and Acknowledgement Received", I wonder whether PC B > successfully receive all 100 messages? > 2. Any recommendation on the hardware requirements on running Hermes, > especially a large volume of messages need to be processed? > 3. Although PC B has more RAM and virtual memory than PC A, but the > out of memory error did not occur in A. Is there any difference in the > memory or other hardware requirement for sending messages and > receiving messages. > 4. Any other experience sharing is welcomed. > > > Regards, > MC |
|
From: Ronald v. K. <rtv...@xs...> - 2005-07-22 23:52:05
|
I'm not the real expert, but ebMS 1.3? I know 1.092 and 2.0 but 1.3? Besides that the full document you show are business signals, not transport signals. This doesn't have anything to do with ebMS, so not with hermes. If I mis something I'd like to hear it. Ronald Steven Herod probeerde me het volgende duidelijk te maken: > Hi > > Our partner is upgrading their ebms MSH and now requires a more 'strict' compliance with Ebms 1.3 > > Specifically, they would like the NonRepudiationInformation Digitially signed, below is what we > are currently sending, and below > that sample, what they require: > > Note the replacement of > > <bpsrcptack:MessagePartIdentifier>cid:16119404.1121897154483.EBMSConnection@192.128.83.36</bpsrcptack:MessagePartIdentifier> > > with: > > <dsig:Reference URI="cid:20392570.1121310610175.EBMSConnection@192.128.83.100"> > <dsig:DigestMethod Algorithm=" <http://www.w3.org/2000/09/xmldsig#sha1> > http://www.w3.org/2000/09/xmldsig#sha1"/> > <dsig:DigestValue>4B2uoJR8lcgJX9iHB3q524egTeg=</dsig:DigestValue> > </dsig:Reference> > > They haven't been more specific, apart from pointing us to section 6.3.2.5 of the ebMS spec from > OASIS > > http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0.pdf > > Any suggestions on getting this to happen in Hermes? > > Current: > > <?xml version="1.0" encoding="UTF-8"?> > <bpsrcptack:ReceiptAcknowledgment xmlns:bpsrcptack=" > <http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS> > http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS" xmlns:dsig=" > <http://www.w3.org/2000/09/xmldsig> > http://www.w3.org/2000/09/xmldsig#" xmlns:xlink=" <http://www.w3.org/1999/xlink> > http://www.w3.org/1999/xlink" xmlns:xsi=" > <http://www.w3.org/2001/XMLSchema-instance> http://www.w3.org/2001/XMLSchema-instance"> > <bpsrcptack:OriginalMessageIdentifier>BC.I0000000011351931-T64561296</bpsrcptack:OriginalMessageIdentifier> > <bpsrcptack:NonRepudiationInformation> > <bpsrcptack:MessagePartNRInformation> > <bpsrcptack:MessagePartIdentifier>cid:16119404.1121897154483.EBMSConnection@192.128.83.36</bpsrcptack:MessagePartIdentifier> > </bpsrcptack:MessagePartNRInformation> > </bpsrcptack:NonRepudiationInformation> > <bpsrcptack:FromPartyInfo bpsrcptack:type="TPID">672178</bpsrcptack:FromPartyInfo> > <bpsrcptack:ToPartyInfo bpsrcptack:type="TPID">625046</bpsrcptack:ToPartyInfo> > <bpsrcptack:FromRole bpsrcptack:name="Seller" xlink:href="urn:CompanyA:Procurement$1.0#Seller" > xlink:type="simple"/> > <bpsrcptack:ToRole bpsrcptack:name="Buyer" xlink:href="urn:CompanyA:Procurement$1.0#Buyer" > xlink:type="simple"/> > <bpsrcptack:OriginalMessageDateTime>2005-07-20T22:05:54.505Z</bpsrcptack:OriginalMessageDateTime> > <bpsrcptack:ThisMessageDateTime>2005-07-21T08:08:19Z</bpsrcptack:ThisMessageDateTime> > <bpsrcptack:ProcessSpecificationInfo bpsrcptack:name="Procurement" > bpsrcptack:uuid="urn:CompanyA:Procurement$1.0" > bpsrcptack:version="1.0" xlink:href="urn:CompanyA:Procurement$1.0" xlink:type="simple"/> > </bpsrcptack:ReceiptAcknowledgment> > > Requested: > > <?xml version="1.0" encoding="UTF-8"?> > <bpsrcptack:ReceiptAcknowledgment xmlns:xsi=" <http://www.w3.org/2001/XMLSchema-instance> > http://www.w3.org/2001/XMLSchema-instance" > xmlns:xlink=" <http://www.w3.org/1999/xlink> http://www.w3.org/1999/xlink" xmlns:dsig=" > <http://www.w3.org/2000/09/xmldsig> > http://www.w3.org/2000/09/xmldsig#" xmlns:bpsrcptack=" > <http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS> > http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS"> > <bpsrcptack:OriginalMessageIdentifier>I0000000009719001-T65047388</bpsrcptack:OriginalMessageIdentifier> > <bpsrcptack:NonRepudiationInformation> > <bpsrcptack:MessagePartNRInformation> > <dsig:Reference URI="cid:20392570.1121310610175.EBMSConnection@192.128.83.100"> > <dsig:DigestMethod Algorithm=" <http://www.w3.org/2000/09/xmldsig#sha1> > http://www.w3.org/2000/09/xmldsig#sha1"/> > <dsig:DigestValue>4B2uoJR8lcgJX9iHB3q524egTeg=</dsig:DigestValue> > </dsig:Reference> > </bpsrcptack:MessagePartNRInformation> > </bpsrcptack:NonRepudiationInformation> > <bpsrcptack:FromPartyInfo bpsrcptack:type="TPID">613974</bpsrcptack:FromPartyInfo> > <bpsrcptack:ToPartyInfo bpsrcptack:type="TPID">625046</bpsrcptack:ToPartyInfo> > <bpsrcptack:FromRole bpsrcptack:name="Seller" xlink:href="urn:CompanyA:Procurement$1.0#Seller" > xlink:type="simple"/> > <bpsrcptack:ToRole bpsrcptack:name="Buyer" xlink:href="urn:CompanyA:Procurement$1.0#Buyer" > xlink:type="simple"/> > <bpsrcptack:OriginalMessageDateTime>2005-07-14T03:10:12.020Z</bpsrcptack:OriginalMessageDateTime> > <bpsrcptack:ThisMessageDateTime>2005-07-14T03:12:53.282Z</bpsrcptack:ThisMessageDateTime> > <bpsrcptack:ProcessSpecificationInfo bpsrcptack:name="Procurement" > bpsrcptack:uuid="urn:CompanyA:Procurement$1.0" > bpsrcptack:version="1.0" xlink:href="urn:CompanyA:Procurement$1.0" xlink:type="simple"/> > </bpsrcptack:ReceiptAcknowledgment> > -- Kijk niet terug, maar kijk naar mij Against all odds |
|
From: Steven H. <sh...@te...> - 2005-07-22 23:25:24
|
Hi
Our partner is upgrading their ebms MSH and now requires a more 'strict' compliance with Ebms 1.3
Specifically, they would like the NonRepudiationInformation Digitially signed, below is what we are currently sending, and below
that sample, what they require:
Note the replacement of
<bpsrcptack:MessagePartIdentifier>cid:16119404.1121897154483.EBMSConnection@192.128.83.36</bpsrcptack:MessagePartIdentifier>
with:
<dsig:Reference URI="cid:20392570.1121310610175.EBMSConnection@192.128.83.100">
<dsig:DigestMethod Algorithm=" <http://www.w3.org/2000/09/xmldsig#sha1> http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>4B2uoJR8lcgJX9iHB3q524egTeg=</dsig:DigestValue>
</dsig:Reference>
They haven't been more specific, apart from pointing us to section 6.3.2.5 of the ebMS spec from OASIS
http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0.pdf
Any suggestions on getting this to happen in Hermes?
Current:
<?xml version="1.0" encoding="UTF-8"?>
<bpsrcptack:ReceiptAcknowledgment xmlns:bpsrcptack=" <http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS>
http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS" xmlns:dsig=" <http://www.w3.org/2000/09/xmldsig>
http://www.w3.org/2000/09/xmldsig#" xmlns:xlink=" <http://www.w3.org/1999/xlink> http://www.w3.org/1999/xlink" xmlns:xsi="
<http://www.w3.org/2001/XMLSchema-instance> http://www.w3.org/2001/XMLSchema-instance">
<bpsrcptack:OriginalMessageIdentifier>BC.I0000000011351931-T64561296</bpsrcptack:OriginalMessageIdentifier>
<bpsrcptack:NonRepudiationInformation>
<bpsrcptack:MessagePartNRInformation>
<bpsrcptack:MessagePartIdentifier>cid:16119404.1121897154483.EBMSConnection@192.128.83.36</bpsrcptack:MessagePartIdentifier>
</bpsrcptack:MessagePartNRInformation>
</bpsrcptack:NonRepudiationInformation>
<bpsrcptack:FromPartyInfo bpsrcptack:type="TPID">672178</bpsrcptack:FromPartyInfo>
<bpsrcptack:ToPartyInfo bpsrcptack:type="TPID">625046</bpsrcptack:ToPartyInfo>
<bpsrcptack:FromRole bpsrcptack:name="Seller" xlink:href="urn:CompanyA:Procurement$1.0#Seller" xlink:type="simple"/>
<bpsrcptack:ToRole bpsrcptack:name="Buyer" xlink:href="urn:CompanyA:Procurement$1.0#Buyer" xlink:type="simple"/>
<bpsrcptack:OriginalMessageDateTime>2005-07-20T22:05:54.505Z</bpsrcptack:OriginalMessageDateTime>
<bpsrcptack:ThisMessageDateTime>2005-07-21T08:08:19Z</bpsrcptack:ThisMessageDateTime>
<bpsrcptack:ProcessSpecificationInfo bpsrcptack:name="Procurement" bpsrcptack:uuid="urn:CompanyA:Procurement$1.0"
bpsrcptack:version="1.0" xlink:href="urn:CompanyA:Procurement$1.0" xlink:type="simple"/>
</bpsrcptack:ReceiptAcknowledgment>
Requested:
<?xml version="1.0" encoding="UTF-8"?>
<bpsrcptack:ReceiptAcknowledgment xmlns:xsi=" <http://www.w3.org/2001/XMLSchema-instance> http://www.w3.org/2001/XMLSchema-instance"
xmlns:xlink=" <http://www.w3.org/1999/xlink> http://www.w3.org/1999/xlink" xmlns:dsig=" <http://www.w3.org/2000/09/xmldsig>
http://www.w3.org/2000/09/xmldsig#" xmlns:bpsrcptack=" <http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS>
http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS">
<bpsrcptack:OriginalMessageIdentifier>I0000000009719001-T65047388</bpsrcptack:OriginalMessageIdentifier>
<bpsrcptack:NonRepudiationInformation>
<bpsrcptack:MessagePartNRInformation>
<dsig:Reference URI="cid:20392570.1121310610175.EBMSConnection@192.128.83.100">
<dsig:DigestMethod Algorithm=" <http://www.w3.org/2000/09/xmldsig#sha1> http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>4B2uoJR8lcgJX9iHB3q524egTeg=</dsig:DigestValue>
</dsig:Reference>
</bpsrcptack:MessagePartNRInformation>
</bpsrcptack:NonRepudiationInformation>
<bpsrcptack:FromPartyInfo bpsrcptack:type="TPID">613974</bpsrcptack:FromPartyInfo>
<bpsrcptack:ToPartyInfo bpsrcptack:type="TPID">625046</bpsrcptack:ToPartyInfo>
<bpsrcptack:FromRole bpsrcptack:name="Seller" xlink:href="urn:CompanyA:Procurement$1.0#Seller" xlink:type="simple"/>
<bpsrcptack:ToRole bpsrcptack:name="Buyer" xlink:href="urn:CompanyA:Procurement$1.0#Buyer" xlink:type="simple"/>
<bpsrcptack:OriginalMessageDateTime>2005-07-14T03:10:12.020Z</bpsrcptack:OriginalMessageDateTime>
<bpsrcptack:ThisMessageDateTime>2005-07-14T03:12:53.282Z</bpsrcptack:ThisMessageDateTime>
<bpsrcptack:ProcessSpecificationInfo bpsrcptack:name="Procurement" bpsrcptack:uuid="urn:CompanyA:Procurement$1.0"
bpsrcptack:version="1.0" xlink:href="urn:CompanyA:Procurement$1.0" xlink:type="simple"/>
</bpsrcptack:ReceiptAcknowledgment>
|
|
From: <em...@og...> - 2005-07-22 02:47:59
|
The hermes config of A and B are the same (except the MSH/Config/URL which
points to A & B respectively).
Thank you!
"Ronald van Kuijk" <rtv...@xs...>
Sent by: ebx...@li...
21.07.2005 21:32
Please respond to ebxmlms-general
To: ebx...@li...
cc:
Subject: Re: [ebxmlms-general] Out of memory error in the MSH monitor
Where is hermes itself running? You mention to monitors (PC A and PC B)
but not where hermes
itself is running. So unless we know where exactely the error occured
(monitor <-> hermes <->
monitor) it is difficult to answer your questions.
Ronald
em...@og... probeerde me het volgende duidelijk te maken:
> When I repeatedly sent a message with one attachment of size 600KB 100
> times from the MSH monitor in one Windows PC (call it A) to the MSH
> monitor in another Windows PC (call it B), the monitor in B showed the
> java.lang.OutOfMemoryError after displaying the first 66 messages
received
> in the "Receive History" (the remaining 34 messages could be displayed
> after OutOfMemoryError occurred), while the monitor in A revealed all
100
> messages sent with the state "Sent and Acknowledgement Received" when
> right-clicking the messages in the "Sent History" in A.
>
> The OutOfMemoryError still occurred until the MSH monitor in B was
> restarted. Right after the restart, the remaining 34 messages were
> displayed in the "Receive History".
>
> The default MaxPayloadSize (1000000) in msh_client.properties.xml is
used.
> PC A has 512MB RAM and paging file size allocated is 768MB, while PC B
has
> 768MB RAM and paging file size allocated is 1152MB.
>
> I have some questions based on the above incident:
>
> 1. Although PC B did not reveals all messages, PC A reveals that all
> mesages "Sent and Acknowledgement Received", I wonder whether PC B
> successfully receive all 100 messages?
> 2. Any recommendation on the hardware requirements on running Hermes,
> especially a large volume of messages need to be processed?
Since PC B (the monitor) gave an oom exception, I think your current
hermes config (PC A) can
handle it nicely
> 3. Although PC B has more RAM and virtual memory than PC A, but the out
of
> memory error did not occur in A. Is there any difference in the memory
or
> other hardware requirement for sending messages and receiving messages.
> 4. Any other experience sharing is welcomed.
>
>
> Regards,
> MC
--
Kijk niet terug, maar kijk naar mij
Against all odds
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
|
|
From: <em...@og...> - 2005-07-22 02:17:59
|
The hermes runs in the same PC as the MSH montior application. i.e.
monitor A <-> hermes A <-> hermes B <-> monitor B.
Thank you!
"Ronald van Kuijk" <rtv...@xs...>
Sent by: ebx...@li...
21.07.2005 21:32
Please respond to ebxmlms-general
To: ebx...@li...
cc:
Subject: Re: [ebxmlms-general] Out of memory error in the MSH monitor
Where is hermes itself running? You mention to monitors (PC A and PC B)
but not where hermes
itself is running. So unless we know where exactely the error occured
(monitor <-> hermes <->
monitor) it is difficult to answer your questions.
Ronald
em...@og... probeerde me het volgende duidelijk te maken:
> When I repeatedly sent a message with one attachment of size 600KB 100
> times from the MSH monitor in one Windows PC (call it A) to the MSH
> monitor in another Windows PC (call it B), the monitor in B showed the
> java.lang.OutOfMemoryError after displaying the first 66 messages
received
> in the "Receive History" (the remaining 34 messages could be displayed
> after OutOfMemoryError occurred), while the monitor in A revealed all
100
> messages sent with the state "Sent and Acknowledgement Received" when
> right-clicking the messages in the "Sent History" in A.
>
> The OutOfMemoryError still occurred until the MSH monitor in B was
> restarted. Right after the restart, the remaining 34 messages were
> displayed in the "Receive History".
>
> The default MaxPayloadSize (1000000) in msh_client.properties.xml is
used.
> PC A has 512MB RAM and paging file size allocated is 768MB, while PC B
has
> 768MB RAM and paging file size allocated is 1152MB.
>
> I have some questions based on the above incident:
>
> 1. Although PC B did not reveals all messages, PC A reveals that all
> mesages "Sent and Acknowledgement Received", I wonder whether PC B
> successfully receive all 100 messages?
> 2. Any recommendation on the hardware requirements on running Hermes,
> especially a large volume of messages need to be processed?
Since PC B (the monitor) gave an oom exception, I think your current
hermes config (PC A) can
handle it nicely
> 3. Although PC B has more RAM and virtual memory than PC A, but the out
of
> memory error did not occur in A. Is there any difference in the memory
or
> other hardware requirement for sending messages and receiving messages.
> 4. Any other experience sharing is welcomed.
>
>
> Regards,
> MC
--
Kijk niet terug, maar kijk naar mij
Against all odds
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ebxmlms-general mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
|
|
From: David W. \(XML\) <da...@dr...> - 2005-07-22 00:29:15
|
Normal.DOTRonald, Yes - all the source code at the site is open source and has no = licensing requirements and was developed as part of a US government = funded project - you may freely incorporate it as you need. Thanks, DW ----- Original Message -----=20 From: R. van Kuijk (Ronald)=20 To: ebx...@li...=20 Sent: Thursday, July 21, 2005 8:17 PM Subject: RE: [ebxmlms-general] Out of memory error in the MSH monitor David,=20 I'm currently refactoring hermes. Is it allowed to include these = patches to since I think they are not in the main codebase. Besides = that, there are some extentions like working with CPA's Can they be = included to? Ronald -------------------------------------------------------------------------= ----- Van: ebx...@li... = [mailto:ebx...@li...] Namens David Webber = (XML) Verzonden: donderdag 21 juli 2005 16:42 Aan: ebx...@li... Onderwerp: Re: [ebxmlms-general] Out of memory error in the MSH = monitor Mattias, The patches and fixes to allow sending of any size message (we tested = up to 150MB) are in the source code ZIP downloadable from: http://ebxmlbook.com/interop/=20 Included in that is the fixes to the error in the mimetype handling = that corrupts the first 16 bytes of a binary file. I'm not sure if any of these corrections made it into the main trunk = codebase. Basically you need these fixes to send files larger than 10Mb. DW ----- Original Message -----=20 From: Mattias J=20 To: ebx...@li...=20 Sent: Thursday, July 21, 2005 7:37 AM Subject: Re: [ebxmlms-general] Out of memory error in the MSH = monitor At 2005-07-21 12:48, you wrote: When I repeatedly sent a message with one attachment of size 600KB = 100 times from the MSH monitor in one Windows PC (call it A) to the MSH = monitor in another Windows PC (call it B), the monitor in B showed the = java.lang.OutOfMemoryError after displaying the first 66 messages = received in the "Receive History" (the remaining 34 messages could be = displayed after OutOfMemoryError occurred), while the monitor in A = revealed all 100 messages sent with the state "Sent and Acknowledgement = Received" when right-clicking the messages in the "Sent History" in A.=20 The OutOfMemoryError still occurred until the MSH monitor in B was = restarted. Right after the restart, the remaining 34 messages were = displayed in the "Receive History".=20 The default MaxPayloadSize (1000000) in msh_client.properties.xml is = used. PC A has 512MB RAM and paging file size allocated is 768MB, while = PC B has 768MB RAM and paging file size allocated is 1152MB. Well, how much memory did you assign to the JVM? Check out -Xmn, -Xms and -Xmx |
|
From: R. v. K. \(Ronald\) <rv...@ab...> - 2005-07-22 00:17:22
|
David, I'm currently refactoring hermes. Is it allowed to include these patches to since I think they are not in the main codebase. Besides that, there are some extentions like working with CPA's Can they be included to? Ronald ________________________________ Van: ebx...@li... [mailto:ebx...@li...] Namens David Webber (XML) Verzonden: donderdag 21 juli 2005 16:42 Aan: ebx...@li... Onderwerp: Re: [ebxmlms-general] Out of memory error in the MSH monitor Mattias, The patches and fixes to allow sending of any size message (we tested up to 150MB) are in the source code ZIP downloadable from: http://ebxmlbook.com/interop/ Included in that is the fixes to the error in the mimetype handling that corrupts the first 16 bytes of a binary file. I'm not sure if any of these corrections made it into the main trunk codebase. Basically you need these fixes to send files larger than 10Mb. DW ----- Original Message ----- From: Mattias J <mailto:mj...@ex...> To: ebx...@li... Sent: Thursday, July 21, 2005 7:37 AM Subject: Re: [ebxmlms-general] Out of memory error in the MSH monitor At 2005-07-21 12:48, you wrote: When I repeatedly sent a message with one attachment of size 600KB 100 times from the MSH monitor in one Windows PC (call it A) to the MSH monitor in another Windows PC (call it B), the monitor in B showed the java.lang.OutOfMemoryError after displaying the first 66 messages received in the "Receive History" (the remaining 34 messages could be displayed after OutOfMemoryError occurred), while the monitor in A revealed all 100 messages sent with the state "Sent and Acknowledgement Received" when right-clicking the messages in the "Sent History" in A. The OutOfMemoryError still occurred until the MSH monitor in B was restarted. Right after the restart, the remaining 34 messages were displayed in the "Receive History". The default MaxPayloadSize (1000000) in msh_client.properties.xml is used. PC A has 512MB RAM and paging file size allocated is 768MB, while PC B has 768MB RAM and paging file size allocated is 1152MB. Well, how much memory did you assign to the JVM? Check out -Xmn, -Xms and -Xmx |
|
From: Patrick Y. <pat...@gm...> - 2005-07-21 16:14:41
|
Ronald, I agree with you. It should be ok to refactor those inner classes= =20 too. ..p On 7/21/05, Ronald van Kuijk <rtv...@xs...> wrote: >=20 > Patrick, >=20 > I'm totally aware of the security reasons, but for the other changes it i= s=20 > easier to split it > first. I can allways make innerclasses of it afterwards. But on the other= =20 > hand, I'd solve the > security issue by using a java.policy file. Isn't that what is was for=20 > originally? Not many > developers know it and try to solve it in another way. One can even sign= =20 > all hermes classes and > have the important ones only be accessed by code that is also signed. Thi= s=20 > keeps the classes much > more clean imo. >=20 > Ronald >=20 > |