Hi,
it's difficult to say what's wrong w/ the code.
1.9.5 is pretty old version, can you pls. try to use 1.9.43? I'd even
recommend to use 2.2.1, but may be it wouldn't be that easy because of
API changes.
Thanks.
WBR,
Alexey.
On 01/11/2012 04:50 PM, maryjane wrote:
> Hi guys,
>
> I'm using grizzly-http 1.9.5 in our project.
> We deploied our war packet inside Jboss application server.
> We launched a ServiceController (see attached class) class inside a
> Servlet throw loadOnStartup parameter equals 1 in web.xml file.
> ServiceController class contains start, stop and load
> configuration (such as core.threads, max.threads ecc...) methods.
> In the start method we instantiate a server grizzly web server custom
> class (MyGrizzlyWebServer see attached class), and we configure the
> adapter class.
> We have performance problem.
> We can achieve just few requests at same time, the other http get
> request like this one
> ('http://10.6.137.100?cod=XX0000&ter=1&tte=M3453&act=BEGIN&vis=001&rel=121&nob=3&ttl=BG
> <http://10.6.137.100/?cod=PA0552&ter=1&tte=M370E&act=BEGIN&vis=001&rel=121&nob=3&ttl=BG>')
> are ignored, we can't read any request on the logs.
> The configuration of threads for the selector thread is maxThread 150.
> There is just one selector thread, it could be a problem??
> The application should be download large files (1-2 Mb) via http in a
> concurrent way.
> We have to manage at least 500-700 concurrent request.
> We have six jboss server.
> We can't understand why with grizzly we can't achieve this result,
> maybe it's a configuration and tuning problem.
>
> It will appreciate any help, if you need more information don't
> hesitate to ask me.
> Thank you so much.
>
> Mariateresa Piselli.
>
>
>