xsocket-develop — xSocket Support Forum

Re: [xSocket-develop] Multiplex echo server and echo client

[Bhatnagar, V. (Ved) <vbh...@av...>]

Hi,

 

How do I keep pipelines from disconnecting in multiplexed scenario?

 

 

Do I need to create  pipelines every time I need to send data across the multiplexed connection?

 

Thank you,

Ved

 

From: Gregor Roth [mailto:gre...@gm...] 
Sent: Tuesday, March 10, 2009 10:07 PM
To: Bhatnagar, Ved (Ved)
Cc: xso...@li...
Subject: Re: [xSocket-develop] Multiplex echo server and echo client

 

Hello ved,

 

the xsocket-multiplexed tutorial (http://xsocket.sourceforge.net/multiplexed/tutorial/V2/TutorialMultiplexed.htm) contains some examples. Additional take a look into the junit tests of xsocket-multiplexed (http://xsocket.svn.sourceforge.net/viewvc/xsocket/xsocket/multiplexed/trunk/src/test/java/org/xsocket/connection/multiplexed/)

 

gregor 

 

	----- Original Message -----

	From: Bhatnagar, Ved (Ved)

	Sent: 11/03/09 01:20 am

	To: xso...@li...

	Subject: [xSocket-develop] Multiplex echo server and echo client

	 

	Hi,

	Can someone please point me to a simple multiplex client and server sample?

	 

	Thank you,

	ved

 

 

Re: [xSocket-develop] Multiplex echo server and echo client

[Gregor R. <gre...@gm...>]

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com

[xSocket-develop] Multiplex echo server and echo client

[Bhatnagar, V. (Ved) <vbh...@av...>]

Hi,

Can someone please point me to a simple multiplex client and server
sample?

 

Thank you,

ved

Re: [xSocket-develop] Question about xSocket

[Sven E. <eis...@sy...>]

Hello gregor,

thank you for your comments.
I implemented an DB Connection Manager class, based on apache commons 
dbcp, which holds a connection pool with an prepared statement cache.
Now the DB access method in my Handler allocates an exclusive connection 
from this pool.
With this I could get rid of all synchronization. This pushed the 
performance from ~ 300 ms per message (with sync) to ~ 50-100 ms per 
message.
Fair enough in my opinion.
xSocket convinced me, again I have to state great work.

Sven

Gregor Roth schrieb:
>
> Hi Sven,
>
>
> please see my comments
>
>
> gregor
>
>
>
>> ----- Original Message -----
>>
>> From: Sven Eisenhauer
>>
>> Sent: 05/03/09 10:23 am
>>
>> To: xso...@li...
>>
>> Subject: [xSocket-develop] Question about xSocket
>>
>>  
>>
>> Hello *,
>> I am new to xSocket, but up to now I am very happy with it, great work.
>> I have implement my first server using non-blocking connections for a
>> custom protocol based on tcp.
>> Everything works fine up to now.
>>
>> But I have one question open, perhaps somebody here on the list could
>> clarify this:
>> I have written a Handler for my protocol, which I pass to the server
>> according to the tutorial:
>>
>> IServer srv = new Server(PORT,new MyHandler());
>>
>> Am I right that there only exists one instance of a MyHandler object and
>>
>> there are new Handler-Threads created always using this object?
>>
>>
>> >> Yes, this is true.
>>
>>
>>
>> MyHandler receives one message per minute on every non-blocking
>> connection. This message is converted and must be inserted in a database
>> table.
>> For this MyHandler has a jdbc database connection object with several
>> prepared statements as an attribute.
>> During my tests I have observed, that there occur database exceptions. I
>> assumed that different Handler-Threads operate on the same prepared
>> statement so that it becomes corrupted. After putting the hole database
>> access in a synchronized method of MyHandler this phenomenon disappeared.
>>
>> Now my question:
>> Am I right, that in this situation only one Handler thread can access
>>
>> the database at one time and all others are blocked?
>>
>>
>> >> Yes, if you synchronize the onRequestMethod all conncurrent 
>> requests will be blocked. As already mentioned, only one instance of 
>> the Handler exists
>>
>>
>> If this is right, I assume that the database access could become a
>> bottleneck. There is only one database connection for all 
>> Handler-Threads.
>> How could I open this bottleneck?
>> One alternative I thought off is that I open up a database connection
>> for every non-blocking connection to a client and attach it to the
>> non-blocking connection. But this seems a little bit as an overkill to
>> open up 1000 database connections for 1000 client connections and every
>>
>> connection is used only once per minute.
>>
>>
>> In my opinion it would be much better to have a database connection for
>>
>> every Handler-Thread. What's your opinion about this?
>>
>>
>> And how could I implement it? Setting up a database connection pool with
>> apache-commons dbcp or something else should be no rocket science.
>> But how to implement a Handler, that always asks for a db-connection
>> from the pool? And would I have to prepare the statements every time a
>>
>> Handler runs?
>>
>>
>> >> I would recomend this solution. I my option the handler 
>> implementation could hold the pool.
>>
>>
>>
>>
>> Best regards and thanks in advance,
>> Sven
>>
>> -- 
>> Sven Eisenhauer, B.Sc.
>> SYNERVA GmbH
>> Mergenthalerallee 55
>> 65760 Eschborn
>> Deutschland
>> Fon: +49 [069] 33 99 66 99
>> Fax: +49 [069] 33 99 66 98
>> mailto:eis...@sy...
>> http://www.synerva.de
>>
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San 
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the 
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source 
>> participation
>> -Receive a $600 discount off the registration fee with the source 
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> xSocket-develop mailing list
>> xSo...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>
>  
>
>


-- 
Sven Eisenhauer, B.Sc.
SYNERVA GmbH
Mergenthalerallee 55
65760 Eschborn
Deutschland
Fon: +49 [069] 33 99 66 99
Fax: +49 [069] 33 99 66 98
mailto:eis...@sy...
http://www.synerva.de

Re: [xSocket-develop] Question about xSocket

[Gregor R. <gre...@gm...>]

[xSocket-develop] Question about xSocket

[Sven E. <eis...@sy...>]

Hello *,
I am new to xSocket, but up to now I am very happy with it, great work.
I have implement my first server using non-blocking connections for a 
custom protocol based on tcp.
Everything works fine up to now.

But I have one question open, perhaps somebody here on the list could 
clarify this:
I have written a Handler for my protocol, which I pass to the server 
according to the tutorial:

    IServer srv = new Server(PORT,new MyHandler());

Am I right that there only exists one instance of a MyHandler object and 
there are new Handler-Threads created always using this object?

MyHandler receives one message per minute on every non-blocking 
connection. This message is converted and must be inserted in a database 
table.
For this MyHandler has a jdbc database connection object with several 
prepared statements as an attribute.
During my tests I have observed, that there occur database exceptions. I 
assumed that different Handler-Threads operate on the same prepared 
statement so that it becomes corrupted. After putting the hole database 
access in a synchronized method of MyHandler this phenomenon disappeared.

Now my question:
Am I right, that in this situation only one Handler thread can access 
the database at one time and all others are blocked?
If this is right, I assume that the database access could become a 
bottleneck. There is only one database connection for all Handler-Threads.
How could I open this bottleneck?
One alternative I thought off is that I open up a database connection 
for every non-blocking connection to a client and attach it to the 
non-blocking connection. But this seems a little bit as an overkill to 
open up 1000 database connections for 1000 client connections and every 
connection is used only once per minute.

In my opinion it would be much better to have a database connection for 
every Handler-Thread. What's your opinion about this?
And how could I implement it? Setting up a database connection pool with 
apache-commons dbcp or something else should be no rocket science.
But how to implement a Handler, that always asks for a db-connection 
from the pool? And would I have to prepare the statements every time a 
Handler runs?

Best regards and thanks in advance,
Sven

-- 
Sven Eisenhauer, B.Sc.
SYNERVA GmbH
Mergenthalerallee 55
65760 Eschborn
Deutschland
Fon: +49 [069] 33 99 66 99
Fax: +49 [069] 33 99 66 98
mailto:eis...@sy...
http://www.synerva.de

Re: [xSocket-develop] WARNING: [xDispatcherClientGlb#0] exception occured while processing. Reason java.io.IOException: File exists

[Michael S. <se...@in...>]

Great :-) I will upgrade and try again.

Thanks,
Michael



El vie, 27-02-2009 a las 08:09 +0100, Gregor Roth escribió:
> Hi Michael,
> 
>  
> 
> this (confusing) errormessage should not longer occur with the new
> xSocket-Version 2.4.4. It is caused bythe SelectorKey-Handling.
> 
>  
> 
> Regards
> 
> Gregor 
> 
> 
> 
> > ----- Original Message -----
> > 
> > From: Michael Seibold
> > 
> > Sent: 26/02/09 12:02 pm
> > 
> > To: xso...@li...
> > 
> > Subject: [xSocket-develop] WARNING: [xDispatcherClientGlb#0]
> > exception occured while processing. Reason java.io.IOException: File
> > exists
> > 
> >  
> > 
> > Hi,
> > 
> > I'm using xsocket 2.4.2.
> > 
> > Sometimes I see the following warning on the client. What does that
> > mean? will the request still be processed?
> > 
> > [INFO] WARNING: [xDispatcherClientGlb#0] exception occured while
> > processing. Reason java.io.IOException: File exists
> > [INFO] at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
> > [INFO] at
> > sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:233)
> > [INFO] at
> > sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:214)
> > [INFO] at
> > sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
> > [INFO] at
> > sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
> > [INFO] at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
> > [INFO] at
> > org.xsocket.connection.IoSocketDispatcher.run(IoSocketDispatcher.java:229)
> > [INFO] at java.lang.Thread.run(Thread.java:619)
> > [INFO] 
> > [INFO] Feb 26, 2009 11:52:59 AM
> > org.xsocket.connection.IoSocketDispatcher run
> > [INFO] WARNING: [xDispatcherClientGlb#0] exception occured while
> > processing. Reason java.io.IOException: File exists
> > [INFO] at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
> > [INFO] at
> > sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:233)
> > [INFO] at
> > sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:214)
> > [INFO] at
> > sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
> > [INFO] at
> > sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
> > [INFO] at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
> > [INFO] at
> > org.xsocket.connection.IoSocketDispatcher.run(IoSocketDispatcher.java:229)
> > [INFO] at java.lang.Thread.run(Thread.java:619)
> > 
> > Kind regards,
> > Michael
> > 
> > 
> > ------------------------------------------------------------------------------
> > Open Source Business Conference (OSBC), March 24-25, 2009, San
> > Francisco, CA
> > -OSBC tackles the biggest issue in open source: Open Sourcing the
> > Enterprise
> > -Strategies to boost innovation and cut costs with open source
> > participation
> > -Receive a $600 discount off the registration fee with the source
> > code: SFAD
> > http://p.sf.net/sfu/XcvMzF8H
> > _______________________________________________
> > xSocket-develop mailing list
> > xSo...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsocket-develop
> 
>  
> 
> 
> 

Re: [xSocket-develop] WARNING: [xDispatcherClientGlb#0] exception occured while processing. Reason java.io.IOException: File exists

[Gregor R. <gre...@gm...>]

[xSocket-develop] WARNING: [xDispatcherClientGlb#0] exception occured while processing. Reason java.io.IOException: File exists

[Michael S. <se...@in...>]

Hi,

I'm using xsocket 2.4.2.

Sometimes I see the following warning on the client. What does that
mean? will the request still be processed?

[INFO] WARNING: [xDispatcherClientGlb#0] exception occured while
processing. Reason java.io.IOException: File exists
[INFO] 	at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
[INFO] 	at
sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:233)
[INFO] 	at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:214)
[INFO] 	at
sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
[INFO] 	at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
[INFO] 	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
[INFO] 	at
org.xsocket.connection.IoSocketDispatcher.run(IoSocketDispatcher.java:229)
[INFO] 	at java.lang.Thread.run(Thread.java:619)
[INFO] 
[INFO] Feb 26, 2009 11:52:59 AM
org.xsocket.connection.IoSocketDispatcher run
[INFO] WARNING: [xDispatcherClientGlb#0] exception occured while
processing. Reason java.io.IOException: File exists
[INFO] 	at sun.nio.ch.EPollArrayWrapper.epollCtl(Native Method)
[INFO] 	at
sun.nio.ch.EPollArrayWrapper.updateRegistrations(EPollArrayWrapper.java:233)
[INFO] 	at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:214)
[INFO] 	at
sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
[INFO] 	at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
[INFO] 	at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
[INFO] 	at
org.xsocket.connection.IoSocketDispatcher.run(IoSocketDispatcher.java:229)
[INFO] 	at java.lang.Thread.run(Thread.java:619)

Kind regards,
Michael

Re: [xSocket-develop] Performance issue

[Gregor R. <gre...@gm...>]

Re: [xSocket-develop] Performance issue

[Betten, T. <tho...@op...>]

Hello,

thanks for quick reply.

Does it mean that NIO approach is actually (always) slower, but more robust
regarding tons of socket connections?

In my tests the common approach was about twice as fast.

Are there any programming pitfalls that I am in since performance
is so bad? Maybe a bad code section outsmarts the NIO benefit.

I cannot believe that xSocket-based implementation is so slow since
it states being appropriate for building high performce and high scalable
servers.

Maybe inefficient usage of NonBlockingConnection, wrong flush-mode or
inappropriate write-transfer-rate... *sigh*


Gregor Roth <gre...@gm...> hat am 25. Februar 2009 um 11:57 geschrieben:


>  
> Hi Thorben,
> 
> 
> in general the non-blocking I/O-approach addresses scalability. If you have only to support a few connections currently, you will reach a better response time by using blocking IO. By running blocking IO a dedicated thread listens for incoming data. The non-blocking approach is based on the NIO Selector (Java 1.7 will introduce true async IO) which adds indirection by reading and writing. 
> 
> 
> By flushing data, the xSocket-internal out buffer will be written into the OS socket buffer. If you are using the sync flush mode, the flush method will block until the data is written into the OS socket buffer. By using the async flush mode xSocket will write the out data into the OS socket buffer in async mode. This means the flush method returns immediately. In contrast to the sync flush mode no internal thread synchronization is required. For this reason setting the flush mode to async can improve the performance. Unfortunately some restrictions exist for the async flushmode. See http://xsocket.sourceforge.net/core/apidocs/2_4_3/org/xsocket/connection/INonBlockingConnection.html#setFlushmode(org.xsocket.connection.IConnection.FlushMode)
> 
> 
> Regards
> Gregor
> 
> 
>  
>  
> 
> > ----- Original Message -----
> > From: "Betten, Thorben"
> > Sent: 24/02/09 05:35 pm
> > To: xso...@li...
> > Subject: [xSocket-develop] Performance issue
> >  
> > 
> > Dear mailing list,
> > 
> > I've written an AJP server using xSocket v2.4.3 library since I read many articles
> > stating that NIO is a must-have to build a high-performance and scalable web application.
> > 
> > 
> > So I started to implement an alternative to my common thread-per-socket approach, but
> > the test results (using JMeter) showed that the xSocket implementation is slower than
> > the old approach.
> > 
> > Is this a "normal" behavior? Meaning "Of course your application is slower, but more
> > scalable and robust regarding many, many socket connections"
> > 
> > I guess I'm using wrong or even missing necessary tuning parameters, but the performace
> > section in the online documentation does not give me a hint. Currently server runs in
> > SYNC mode.
> > 
> > Here's a list of options/properties I use:
> > - On server creation:
> >    sysprops.put("org.xsocket.connection.server.readbuffer.usedirect", "true");
> > - onConnect():
> >    connection.setAutoflush(false);
> >    connection.setOption(INonBlockingConnection.TCP_NODELAY, "true");
> > 
> > 
> > Is the ASYNC flush-mode generally preferable to SYNC mode?
> > What is an appropriate value for write transfer rate if package size is limited to 8192 bytes?
> > Are there any other tuning options that I am missing?
> > 
> > Any help would be appreciated...
> > 
> > 
> > --
> > Thorben Betten
> > 
> > 
 
>  
> 
> 
>  
>  
>  
>  
> 






--
Thorben Betten
Engineering - Back-End-Team
Open-Xchange AG

Phone: +49 2761 8385-16, Fax: +49 2761 838530

-------------------------------------------------------------------------------
Open-Xchange AG,  Maxfeldstr. 9, 90409 Nürnberg, Amtsgericht Nürnberg HRB 24738
Vorstand: Rafael Laguna de la Vera, Aufsichtsratsvorsitzender: Richard Seibt

European Office: Open-Xchange GmbH, Martinstr. 41, D-57462 Olpe, Germany
Amtsgericht Siegen, HRB 8718, Geschäftsführer: Frank Hoberg, Martin Kauss

US Office: Open-Xchange, Inc., 303 South Broadway, Tarrytown, New York 10591
-------------------------------------------------------------------------------

Re: [xSocket-develop] Performance issue

[Gregor R. <gre...@gm...>]

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

Re: [xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..

[Timothy Schm. <tim...@we...>]

Hi Gregor.

> bymoving xSocket-httpto xLightweb most parts of xSocket-http have 
> beenreimplemented and code hasbeen cleaned heavily. TheremoveHopByHopHe
> aders() has not been implemented by xLightweb yet.Should xLightweb 
> support this method?

Not sure, probably not. It was just not clear to me it was fully removed. 
 
> Ihavetested heise.de with the expermintal HttpProxy implemention and 
> didnot get a404. If you send me your proxy (snippest), I will re-run 
> thetest based on yourimplementation.

In the meantime I took a deeper look at HttpProxy, in particular establishTunnel() and TcpProxyHandler, and this was the missing link for me. Things seem to work really well now.
Thank you very much.
Tim

____________________________________________________________________
Psssst! Schon vom neuen WEB.DE MultiMessenger gehört? 
Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123

[xSocket-develop] Performance issue

[Betten, T. <tho...@op...>]

Dear mailing list,

I've written an AJP server using xSocket v2.4.3 library since I read many articles
stating that NIO is a must-have to build a high-performance and scalable web application.


So I started to implement an alternative to my common thread-per-socket approach, but
the test results (using JMeter) showed that the xSocket implementation is slower than
the old approach.

Is this a "normal" behavior? Meaning "Of course your application is slower, but more
scalable and robust regarding many, many socket connections"

I guess I'm using wrong or even missing necessary tuning parameters, but the performace
section in the online documentation does not give me a hint. Currently server runs in
SYNC mode.

Here's a list of options/properties I use:
- On server creation:
   sysprops.put("org.xsocket.connection.server.readbuffer.usedirect", "true");
- onConnect():
   connection.setAutoflush(false);
   connection.setOption(INonBlockingConnection.TCP_NODELAY, "true");


Is the ASYNC flush-mode generally preferable to SYNC mode?
What is an appropriate value for write transfer rate if package size is limited to 8192 bytes?
Are there any other tuning options that I am missing?

Any help would be appreciated...


--
Thorben Betten

Re: [xSocket-develop] Fw: Re: Maybe Problem with ACK

[Gregor R. <gre...@gm...>]

Re: [xSocket-develop] Maybe Problem with ACK

[Gregor R. <gre...@gm...>]

[xSocket-develop] Maybe Problem with ACK

[Johann H. <ho...@in...>]

Hello,
My goal is to write a xSocketClient which can connect to a Script 
written in Python using the Twisted Framework.
So I started experimenting and now I have a Problem.
I wrote a simple xSocketServer and from Python I was able to connect to 
it and to receive and send lines. Everything worked perfectly.
BUT: Then I tried it the other way round and it didn't work.
I tried to open a NonBlockingConnection to my Server running in Python. 
The Python Server recognized, that there is a incoming connection, but 
it seems, that a kind of ACK is missing, because the 
NonBlockingConnection runs into a timeout (well, I think it's a timeout, 
because it appears after the defined timeout):
Exception in thread "main" java.lang.NullPointerException
   at 
org.xsocket.connection.NonBlockingConnection.isDataWriteable(NonBlockingConnection.java:943)
   at 
org.xsocket.connection.AbstractNonBlockingStream.ensureStreamIsOpenAndWritable(AbstractNonBlockingStream.java:1533)
   at 
org.xsocket.connection.AbstractNonBlockingStream.write(AbstractNonBlockingStream.java:1043)
   at 
org.xsocket.connection.AbstractNonBlockingStream.write(AbstractNonBlockingStream.java:1028)
   at ConnectToTwisted.main(ConnectToTwisted.java:54)

So: What kind of answer do I have to send to the client, that he 
recognizes, that the connection is established?

Greetings
Joe

Re: [xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..

[Gregor R. <gre...@gm...>]

Re: [xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..

[Timothy Schm. <tim...@we...>]

Hi Gregor.

> yes this is true, the method removeHopByHopHeaders() had only been 
> supported in eraly version of xLightweb.

Can you try to explain the rational for this?

> Do you use the older version 
> xSocket-http or xLightweb (http://xlightweb.sourceforge.net/) which 
> replaces xSocket-http?

My classpath is set to: xlightweb-2.5.jar:xSocket-2.4.3.jar:.
Without xSocket-2.4.3.jar in there, I get NoClassDefFoundError: org/xsocket/ILifeCycle. 

> Could you send me some links which causes 404? I would like to cross-
> checks the links

Sure, for instance http://www.heise.de/ gives me a 404 with 'Connection: close' on the root document. What is a bit strange is that the browser still (successfully) fetches ico, css, gif, js and other fragments. And the 404 is actually printed in the body of the browser. So the webserver is indeed aware that there is some issue.

> By the way there is a experimental implementation of a HttpProxy in 
> the sandbox branch. See http://xlightweb.svn.sourceforge.net/viewvc/
> xlightweb/xlightweb/sandbox/HttpProxy/trunk/

Hmm, this code also doesn't seem to have any special (hop-by-hop) header treatment. (Except for setting "Via" if I'm not mistaken.) 
Thanks,
Tim (apologies for double delivery)

_______________________________________________________________________
Jetzt 1 Monat kostenlos! WEB.DE FreeDSL - Telefonanschluss + DSL
für nur 17,95 EURO/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a

Re: [xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..

[Gregor R. <gre...@go...>]

Hi Timothy,

yes this is true, the method removeHopByHopHeaders() had only been supported
in eraly version of xLightweb. Do you use the older version xSocket-http or
xLightweb (http://xlightweb.sourceforge.net/) which replaces xSocket-http?

Could you send me some links which causes 404? I would like to cross-checks
the links

By the way there is a experimental implementation of a HttpProxy in the
sandbox branch. See
http://xlightweb.svn.sourceforge.net/viewvc/xlightweb/xlightweb/sandbox/HttpProxy/trunk/

Regards
Gregor



2009/2/22 Timothy Schm. <tim...@we...>

> Hi. I'm not quite sure how to perform the proxy issues mentioned in several
> code samples, like ForwardHandler and ReverseHandler.
>
> http://xsocket.sourceforge.net/http/tutorial/V2/TutorialHttp.htm mentions
> a removeHopByHopHeaders() method for handling hob-by-hop headers
> automatically. But it does not seem to be supported anymore. Is this
> correct?
>
> I got a truly fast Java HTTP proxy running now based on xSocket. But so
> far, it works only with _some_ web servers. In other cases, replied content
> gets stucked and somethimes I receive 404's where the remote webserver is
> clearly running fine. It would be really good, if that header handling for
> proxies could be exlained somewhere.
>
> Thank you.
> Tim
>
> _______________________________________________________________________
> DSL zum Nulltarif + 20 Euro Extraprämie bei Online-Bestellung über die
> DSL Freundschaftswerbung! http://dsl.web.de/?ac=OM.AD.AD008K15279B7069a
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> xSocket-develop mailing list
> xSo...@li...
> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>

[xSocket-develop] further proxy issues, header, cache, remove hop-by-hop headers..

[Timothy Schm. <tim...@we...>]

Hi. I'm not quite sure how to perform the proxy issues mentioned in several code samples, like ForwardHandler and ReverseHandler. 

http://xsocket.sourceforge.net/http/tutorial/V2/TutorialHttp.htm mentions a removeHopByHopHeaders() method for handling hob-by-hop headers automatically. But it does not seem to be supported anymore. Is this correct?

I got a truly fast Java HTTP proxy running now based on xSocket. But so far, it works only with _some_ web servers. In other cases, replied content gets stucked and somethimes I receive 404's where the remote webserver is clearly running fine. It would be really good, if that header handling for proxies could be exlained somewhere.

Thank you.
Tim

_______________________________________________________________________
DSL zum Nulltarif + 20 Euro Extraprämie bei Online-Bestellung über die
DSL Freundschaftswerbung! http://dsl.web.de/?ac=OM.AD.AD008K15279B7069a

Re: [xSocket-develop] java.lang.ExceptionInInitializerError

[Gregor R. <gre...@go...>]

Hi Andrew,

xLightweb 2.4 does not work with xSocket-2.4.x (I fixed the the requirement
section in the download page) . xLightweb 2.4 requires 2.3.x. The next
Version xLightweb 2.5 which is based on xSocket-2.4.x will be released next
week.

Gregor

2009/2/5 Andrew <and...@gm...>

> Hello,
>
> I'm trying to start example from
> /http://xlightweb.sourceforge.net/core/tutorial/V2/TutorialCore.htm /but
> get an exception in the line  /IHttpClientEndpoint client = new
> HttpClient(); /:
>
> java.lang.ExceptionInInitializerError
>    at
> org.xlightweb.RequestHandlerChain.computePath(RequestHandlerChain.java:214)
>    at
> org.xlightweb.RequestHandlerChain.addFirst(RequestHandlerChain.java:134)
>    at org.xlightweb.client.HttpClient.resetChain(HttpClient.java:392)
>    at org.xlightweb.client.HttpClient.<init>(HttpClient.java:196)
>    at org.xlightweb.client.HttpClient.<init>(HttpClient.java:147)
>    at demo.DemoApp.init(DemoApp.java:29)
>    at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
>    at
> org.xsocket.connection.ConnectionUtils.isSmaller(ConnectionUtils.java:462)
>    at
>
> org.xsocket.connection.ConnectionUtils.matchVersion(ConnectionUtils.java:419)
>    at org.xlightweb.HttpUtils.<clinit>(HttpUtils.java:161)
>    ... 8 more
>
> I use xSocket-2.4.1.jar, xSocket-multiplexed-2.1.2.jar and
> xlightweb-2.4.jar from xSocket download page. Is this a bug or I do
> something wrong?
>
> Thanks
>
>
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code
> to
> build responsive, highly engaging applications that combine the power of
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK
> and
> Ajax docs to start building applications today-
> http://p.sf.net/sfu/adobe-com
> _______________________________________________
> xSocket-develop mailing list
> xSo...@li...
> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>

[xSocket-develop] java.lang.ExceptionInInitializerError

[Andrew <and...@gm...>]

Hello,

I'm trying to start example from 
/http://xlightweb.sourceforge.net/core/tutorial/V2/TutorialCore.htm /but 
get an exception in the line  /IHttpClientEndpoint client = new 
HttpClient(); /:

java.lang.ExceptionInInitializerError
    at 
org.xlightweb.RequestHandlerChain.computePath(RequestHandlerChain.java:214)
    at 
org.xlightweb.RequestHandlerChain.addFirst(RequestHandlerChain.java:134)
    at org.xlightweb.client.HttpClient.resetChain(HttpClient.java:392)
    at org.xlightweb.client.HttpClient.<init>(HttpClient.java:196)
    at org.xlightweb.client.HttpClient.<init>(HttpClient.java:147)
    at demo.DemoApp.init(DemoApp.java:29)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
    at 
org.xsocket.connection.ConnectionUtils.isSmaller(ConnectionUtils.java:462)
    at 
org.xsocket.connection.ConnectionUtils.matchVersion(ConnectionUtils.java:419)
    at org.xlightweb.HttpUtils.<clinit>(HttpUtils.java:161)
    ... 8 more

I use xSocket-2.4.1.jar, xSocket-multiplexed-2.1.2.jar and 
xlightweb-2.4.jar from xSocket download page. Is this a bug or I do 
something wrong?

Thanks

Re: [xSocket-develop] Too many open files exception

[Gregor R. <gre...@go...>]

...  thanks, I'm going to fix this

Gregor

2009/1/19 gk <gk...@ph...>

> Hi...
>
> there is a minor error in your test. It outputs to have tested 200
> concurrent servers, but opens only 100.
> I don't think it was intended this way...
>
> gk
>
> Zitat von Gregor Roth <gre...@go...>:
>
> > Hi Armine,
> >
> > have you already took a look into chapter 28 of the tutorial?
> > Regarding to the Too many open files behaviour some documents a
> > referred. On some window configurations it has been observed that the
> > underlying selector of a Dispatcher accepts only a small number of
> > concurrent connections. This is a JRE/OS behaviour. As a workaround
> > you can set the number of the dispatchers with a higher value ->
> > org.xsocket.connection.dispatcher.initialCount. Or you can set
> > org.xsocket.connection.dispatcher.maxHandles.
> >  I also added a new JUnit-Test based on your test (see
> >
>
> http://xsocket.svn.sourceforge.net/viewvc/xsocket/xsocket/core/trunk/src/test/java/org/xsocket/connection/ManyConcurrentServerTest.java?view=markup[1]<http://xsocket.svn.sourceforge.net/viewvc/xsocket/xsocket/core/trunk/src/test/java/org/xsocket/connection/ManyConcurrentServerTest.java?view=markup%5B1%5D>
> ).
> > Within the continuous integration xSocket's tests runs on a Windows
> > XP professional/SP3 as well as on a RedHed (centos) multicore
> > platform.  Gregor
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> xSocket-develop mailing list
> xSo...@li...
> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>

Re: [xSocket-develop] Too many open files exception

[gk <gk...@ph...>]

Hi...

there is a minor error in your test. It outputs to have tested 200
concurrent servers, but opens only 100.
I don't think it was intended this way...

gk

Zitat von Gregor Roth <gre...@go...>:

> Hi Armine,
>
> have you already took a look into chapter 28 of the tutorial?
> Regarding to the Too many open files behaviour some documents a
> referred. On some window configurations it has been observed that the
> underlying selector of a Dispatcher accepts only a small number of
> concurrent connections. This is a JRE/OS behaviour. As a workaround
> you can set the number of the dispatchers with a higher value ->
> org.xsocket.connection.dispatcher.initialCount. Or you can set
> org.xsocket.connection.dispatcher.maxHandles.
>  I also added a new JUnit-Test based on your test (see
>
http://xsocket.svn.sourceforge.net/viewvc/xsocket/xsocket/core/trunk/src/test/java/org/xsocket/connection/ManyConcurrentServerTest.java?view=markup[1]).
> Within the continuous integration xSocket's tests runs on a Windows
> XP professional/SP3 as well as on a RedHed (centos) multicore
> platform.  Gregor