|
Thanks, Jim! When I wrote my response, I hadn't seen yours yet... You hit the nail on the head: >It IS efficient because internally TCP support opens >pipes between the applications, not true TCP socket >connections ... Fascinating that you were able to see the "local sockets" optimization, albeit only as the result of an error. :-/ (I trust the error was treated as a bug, and fixed?) Thanks, again. -blair Blair Wyman -- iSeries JVM -- (507) 253-2891 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "I was born not knowing, and have had only a little time to change that here and there." -- Richard P. Feynman Jim Mason <jmason900@yahoo. To: java400-l@midrange.com com> cc: Sent by: Subject: RE: Communication between JVM's java400-l-admin@m idrange.com 04/23/2002 10:14 AM Please respond to java400-l Hi Blair. Running an IBM app ( WebFacing) on the same machine as WebSphere they communicate using standard sockets. When the app runs it was automatically optimized to open memory pipes instead. How do I know? The apps broke and the information was readily available in the log files ... Jim Mason --- Blair Wyman <blairw@us.ibm.com> wrote: > > Geert wrote: > > I see no difference using sockets to communicate > between > > two JVM's either on different machines or on the > same machine. > > Actually, there is (potentially) a big (performance) > difference when > sockets connect between two processes on the same > machine. > > When TCP/IP knows that both "ends" of a socket are > on the same machine > (i.e. the target address is 127.0.0.1 or > "loopback,"), it is able to use a > simple mutex'd shared memory segment as the IP > transport medium thingie... > As you can imagine, this can drastically improve > performance. > > AFAIK, this would be an "automatic" sort of > optimization -- embedded in the > sockets implementation, below the JVM, and > transparent to the JVM and user > alike -- so no code changes would be required to > exploit it. > > Having said all this, I'm not sure whether iSeries > sockets use this scheme > -- I'm not a sockets guy -- but I've got a couple of > feelers out. > > -blair > > Blair Wyman -- iSeries JVM -- (507) 253-2891 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > "I was born not knowing, and have had only a > little time to change that here and there." -- > Richard P. Feynman > > > > > Geert Van > Landeghem To: > "'java400-l@midrange.com'" > <java400-l@midrange.com> > <gvl@reynderseti. cc: > be> > Subject: RE: Communication between JVM's > Sent by: > java400-l-admin@m > idrange.com > > > 04/12/2002 09:24 > AM > Please respond to > java400-l > > > > > > How long do you estimate the duration of the > communication? > Have a look at the new Channel classes that allow > non-blocking > input from files, sockets, ... perhaps this will > benefit you. > > I see no difference using sockets to communicate > between > two JVM's either on different machines or on the > same machine. > > If you're afraid of to many socket communications > and response time > is not a problem you could implement a wait queue > which allows only > a maximum number of socket communications to be > active. > > Hope this helps. > > Geert > > -----Original Message----- > From: Price, Chris [mailto:chris_price@nsb.co.uk] > Sent: vendredi 12 avril 2002 14:08 > To: 'java400-l@midrange.com' > Subject: RE: Communication between JVM's > > > This message is in MIME format. Since your mail > reader does not understand > this format, some or all of this message may not be > legible. > -- > [ Picked text/plain from multipart/alternative ] > It's kind of a messaging system. > > My WAS needs to sends messages to some clients, via > a router. The router to > client part I'm happy to be socket based. > > If the WAS & the router are running on different > machines, then they will > have to use sockets to communicate. BUT if they are > the same machine, will > it be inefficient to communicate via sockets? > > I'm also nervous about large number of sockets being > opened in the WAS, as > each one is going to tie-up a TCP/IP port for the > duration of the > conversation. > > Chris. > > -----Original Message----- > From: Geert Van Landeghem > [mailto:gvl@reynderseti.be] > Sent: 12 April 2002 15:01 > To: 'java400-l@midrange.com' > Subject: RE: Communication between JVM's > > In my humble opinion, no. You could use File objects > on disk, an OODBMS, ... to share information. The > most low > level communication is always done by using sockets. > What kind of application do you want to write? > > Geert > > -----Original Message----- > From: Price, Chris [mailto:chris_price@nsb.co.uk] > Sent: vendredi 12 avril 2002 13:51 > To: 'java400-l@midrange.com' > Subject: RE: Communication between JVM's > > > This message is in MIME format. Since your mail > reader does not understand > this format, some or all of this message may not be > legible. > -- > [ Picked text/plain from multipart/alternative ] > Are there no more efficient solutions than sockets > (which all these > ultimately use)? > > -----Original Message----- > From: Geert Van Landeghem > [mailto:gvl@reynderseti.be] > Sent: 12 April 2002 14:45 > To: 'java400-l@midrange.com' > Subject: RE: Communication between JVM's > > There are several possibilities using: > - sockets > - RMI or Remote Method Invocation (serialized > objects over sockets) > - EJB (Application server) to clients > - Servlet/JSP (Application Server) to clients > ... > > Geert > -----Original Message----- > From: Price, Chris [mailto:chris_price@nsb.co.uk] > Sent: vendredi 12 avril 2002 13:25 > To: 'java400-l@midrange.com' > Subject: Communication between JVM's > > > This message is in MIME format. Since your mail > reader does not understand > this format, some or all of this message may not be > legible. > -- > [ Picked text/plain from multipart/alternative ] > All, > > What is the best way of communicating between two > different JVM's, running > on the same machine? > > > Chris. > > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) > mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > > > > > > > _______________________________________________ > This is the Java Programming on and around the > iSeries / AS400 (JAVA400-L) mailing list > To post a message email: JAVA400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/cgi-bin/listinfo/java400-l > or email: JAVA400-L-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/java400-l. > __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.