You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Nekkalapudi, Viplava" <VN...@erac.com> on 2002/11/05 22:01:36 UTC
Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
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???
[java] <Oct 8, 2002 9:46:58 AM CDT> <Emergency> <WebLogicServer>
> <Unable to create a server socket for port: 51300.
java.net.BindException:
> Address in use: JVM_Bind Perhaps another process is usi ng port 51300.>
>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Emergency> <WebLogicServer>
> <The WebLogic Server is no longer listening for connections. You should
> probably restart it.>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Alert> <WebLogicServer> <Server
> shutdown has been requested by system>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Alert> <WebLogicServer> <The
> shutdown sequence has been initiated.>
--- Viplava.
-----Original Message-----
From: s.frank@vierundsechzig.de [mailto:s.frank@vierundsechzig.de]
Sent: Tuesday, October 15, 2002 11:19 AM
To: Nekkalapudi, Viplava
Subject: AW: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
neither nor, i suppose: we are using the same combination and it works
fine. Do you have some startup-logs, that show exactly where weblogic
stops?! You're sure this is not some other stuff that prevents wls from
booting?!
greetings
stf
--- Ursprüngliche Nachricht ---
Datum: 15.10.2002 18:13
Von: "Nekkalapudi, Viplava" <VN...@erac.com>
An: Struts Users Mailing List <st...@jakarta.apache.org>
Betreff: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
>
> We are trying to update a web application based on
Struts1.0.2
to
> Struts 1.1 B2. We use Weblogic 6.1 SP2 on Win 2000.
> It used to work fine with Struts 1.0.2 and with Struts 1.1
B2,
> weblogic server fails to start properly using the port and shut down
> initialized automatically (Complaining port is already used). It works
some
> times if we reboot our machines OR wait 5/10 minutes before restart the
App
> server. By issuing the command "netstat -a", the port doesn't show up.
>
> Any one has an idea what will be the problem? It happened only when
> we migrate to Struts1.1 from Struts 1.0.2. Is it a bug of Struts 1.1 OR
> Weblogic 6.1?
>
> Thanks in advance.
>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Emergency> <WebLogicServer>
> <Unable to create a server socket for port: 51300.
java.net.BindException:
> Address in use: JVM_Bind Perhaps another process is usi ng port 51300.>
>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Emergency> <WebLogicServer>
> <The WebLogic Server is no longer listening for connections. You should
> probably restart it.>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Alert> <WebLogicServer> <Server
> shutdown has been requested by system>
> [java] <Oct 8, 2002 9:46:58 AM CDT> <Alert> <WebLogicServer> <The
> shutdown sequence has been initiated.>
>
>
> -- Vip.
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
Posted by Daniel Jaffa <ja...@courtinnovation.org>.
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" <ek...@swbell.net>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
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:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Struts1.1 B2 BUG OR Weblogic 6.1 SP2 BUG??????????
Posted by Eddie Bush <ek...@swbell.net>.
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>