Thanks Eddie for your Ideas. We also think it is a weblogic BUG contacted our server vendor and reported about it.
But how Struts 1.0.2 making WEBLOGIC BUG hiding behind it. And how the BUG reappears even with STRUTS 1.0.2 when we just change our DTD reference to STRUTS 1.1. We are not running Weblogic as a service. We even heard that weblogic uses its own Socket Handling to support JDK 1.4.1 for future(Weblogic 6.1/7.0 not yet officially support) and they added some changes to the servlet implementation in 6.1. But how Struts 1.0.2 helping Weblogic 6.1 SP2 to free up the port? Is STRUTS 1.1 Action Servlet depends on the servlet container for any of these? We were thinking it might be some thing related with the Action Servlet in Destroying the applications cleanly. Because it should destroy all the Plug Ins also. Thanks, Vip. -----Original Message----- From: Eddie Bush [mailto:ekbush@;swbell.net] Sent: Tuesday, November 05, 2002 4:40 PM To: Struts Users Mailing List Subject: Re: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG?????????? I believe it's inconceivable that this is a Struts issue. Struts isn't causing any ports to be open - it just runs in your web container. I have heard that running WebLogic as a service can cause this behavior though. The suggestion I hear was "When the install asks if you'd like the server to run as a service - just say NO!" It *is* a WebLogic bug :-) I guarantee you. As I recall (and my memory is fuzzy) WebLogic built some custom socket-handling code (native C-language stuff), to use in their server, and, apparantly, they didn't do a good job of freeing them up. I find it odd that they don't show up under netstat -a, but the fact of the matter is that the server is the only animal in the zoo that will open that port :-) You asked for an idea: - complain *loudly* to your server vendor! (file a bug if there isn't one outstanding) - find other people having this problem - organize and lobby to have it fixed ... that's my idea. Nekkalapudi, Viplava wrote: >I already posted this some time back about the problem of server port >already in use. >We couldn't get away from this problem so we still use STRUTS 1.0.2 for our >application. > >We seen that by just modifying the DTD reference from STRUTS 1.0 to STRUTS >1.1 in the struts-config.xml, resulting the port bind error (at the end of >this mail). >We use Struts 1.0.2 with Weblogic Server 6.1 SP2. > >I wonder how Struts 1.1 DTD related with the Weblogic port bind error? > >If any one want to see this error with their application uses STRTUS 1.0.2, >Just modify the DTD reference in the struts-config.xml to STRUTS 1.1 DTD. >Start weblogic server, shutdown and restart the server again. >(The server binds the port correctly for the first time). > > Any Ideas??? > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
