GlassFish : it works!
One of the clear benefit of Open Source is that smart people can easily contribute by tracking down issues, by proposing fixes. Here is an abstract of a mail I received yesterday from a partner (Excutive summary version - technical gorry details skipped)David, I think I ran into a bug that is in glassfish. As I told you previously, we had problems with binding the HTTP-listener ... Using the source of glassfish, I could trace the problem to the following: upon startup, the appserver will call ASLazyKernel.setupSocketListeners()... The problem is that only the port-information is used here ... As a consequence, the HTTP-services are started at port 80 of 0.0.0.0 When the HTTP-service itself is initialized later ... Since the given address now contains a specific address, the check returns false, and a new ServerSocket will be created ... which results in an error since 0.0.0.0:80 is already bound. I fixed this in my tree by removing the lazy startup and it works fine now. I assume other people have this problem too (I'm running on Linux), so maybe this can help?so less than 2 weeks after the annoucement, it seems that GlassFish (Sun's Open Source Java EE 5 Application Server) is on track and people start contributing! Tags : OSS J2EE Sun ( juil. 12 2005, 12:08:07 AM PDT ) Permalink Comments [0]
Trackback URL: http://blogs.sun.com/delabassee/entry/glassfish_it_works
Comments:
Post a Comment:




