can you try it with tomcat and reproduce?
.V
Nekkalapudi, Viplava wrote:
Hi Daniel,
Did you have a chance to read my last mail which I sent around 4:00PM.
If there are 3 instances running for WEBLOGIC 6.1 SP2, then why it is
not an issue with STRTUS 1.0.2?
Our STRUTS 1.1 application also works fine with the Validatior Frame
work, but only problem is with the port issue. We need to wait a minimum of
5/10 minutes.
(May be to stop all these instances).
But today we just modified the the DOC-TYPE in struts-config.xml file to
refer STRUTS 1.1 DTD in our web application developed based on STRUTS 1.0.2.
We started seeing this error.
Thanks for your time.
-----Original Message-----
From: Daniel Jaffa [mailto:jaffad@;courtinnovation.org]
Sent: Tuesday, November 05, 2002 4:28 PM
To: Struts Users Mailing List
Subject: Re: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
netstat -a returns
TCP proliant-ml370:82 proliant-ml370:0 LISTENING
TCP proliant-ml370:90 proliant-ml370:0 LISTENING
TCP proliant-ml370:94 proliant-ml370:0 LISTENING
Which are the 3 instances of Weblogic Server 6.1 SP2.
Eddie, this is not a Struts error and it is also not a BEA Weblogic error.
I have configured Weblogic 6.1 with struts 1.1 b1 and b2. This is a config
error not a
application or framework error.
Viplava, please look at what your configuration is, I assure you that you
have one small
error that is snowballing you right now.
Daniel Jaffa
Sa' right
Sa' write
----- Original Message -----
From: "Eddie Bush" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 05, 2002 5:40 PM
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>
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
