[JBoss-user] Re: Multiple Remote EJB Requests Bombs JBoss

2001-05-21 Thread Bob Cober

FYI - The error was caused by the bean.  It was using Minerva JDBC 
connection pooling with a pool limit of 10 connections.  The bean did not 
release the connection, so it bombed as soon as 10 rapid requests came 
in.

Long live Open-Source

From: "Bob Cober" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Mon, 21 May 2001 09:27:05 -0700
Subject: [JBoss-user] Multiple Remote EJB Requests Bombs JBoss
Reply-To: [EMAIL PROTECTED]

We are using Tomcat 3.1.1 on one machine and JBoss 2.2.1 on another.  When
calling EJBs from a remote JSP page, everything works fine...until we
quickly submit 10 or so refresh requests from the browser.  At this point
JBoss hangs and we cannot browse that JSP page.  Other pages are still
accessible from Tomcat.

Are there any documented issues regarding locking up JBoss with multiple
request from the same machine?  It seems that there are quite a few
connections open to JBoss from the Tomcat machine - is this the problem?

Thanks in advance for any help you can provide

_
Get your FREE download of MSN Explorer at http://explorer.msn.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] Multiple Remote EJB Requests Bombs JBoss

2001-05-21 Thread Bob Cober

We are using Tomcat 3.1.1 on one machine and JBoss 2.2.1 on another.  When 
calling EJBs from a remote JSP page, everything works fine...until we 
quickly submit 10 or so refresh requests from the browser.  At this point 
JBoss hangs and we cannot browse that JSP page.  Other pages are still 
accessible from Tomcat.

Are there any documented issues regarding locking up JBoss with multiple 
request from the same machine?  It seems that there are quite a few 
connections open to JBoss from the Tomcat machine - is this the problem?

Thanks in advance for any help you can provide

_
Get your FREE download of MSN Explorer at http://explorer.msn.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Firewall and JBoss

2001-05-11 Thread Bob Cober

OK I Found my problem

If you are interested read on:

The port I was missing was the RMI Port in the Naming Service.

In the server log I found
[Configuration] RmiPort set to 0 in DefaultDomain:service=Naming

So I edited jboss.jcml and added the line with **added**:

  
1099
4499**Added**
  

On restart, this led to
[Configuration] RmiPort set to 4499 in DefaultDomain:service=Naming

And sure enoungh all packets on every request are either 1099, , or 
4499


Linux, Open Source and JBoss Rule!!!

_
Get your FREE download of MSN Explorer at http://explorer.msn.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Firewall and JBoss

2001-05-11 Thread Bob Cober


Yes I read about the JMX connector port.  But I think I am encountering 
something else.  I am using TCPDump to spy on the packets when I make a 
request to JBoss.

First I see a couple of packets on port 1099(JNDI Lookup)
Then a few on 2694? (Don't know this one)
Then alot on  (RMI Object Port)
Then a few on 2694? (Again don't know this one)
Then a few on  (RMI Object Port)

If I restart the server the above is the same except all 2694 packets are on 
some randomly assigned port...

Any ideas on how to lock down these ports to a consistent value?
Thanks again


>From: "Filip Hanik" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] Firewall and JBoss
>Date: Fri, 11 May 2001 16:58:49 -0700
>
>you also have the JMX HTTPConnector port - I believe this one is 8082
>
>Filip
>
>~
>Namaste - I bow to the divine in you
>~
>Filip Hanik
>Software Architect
>[EMAIL PROTECTED]
>www.filip.net
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Bob Cober
> > Sent: Friday, May 11, 2001 4:45 PM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-user] Firewall and JBoss
> >
> >
> > Help!
> > I am interested in locking the ports JBoss uses.
> > 1099 if the default JNDI lookup that is fine.
> >  is the default RMI Object Port that can be controlled in jboss.xml.
> > There is a third port that seems to be randomly assigned everytime the
> > server is started.  I have seen 1591, 2291, etc.
> > I believe this port may be part of the default RMI Socket Factory or
> > something.  How can I control it?
> >
> > Thanks for any help you can provide
> >
> >
> > _
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
>
>___
>JBoss-user mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-user

_
Get your FREE download of MSN Explorer at http://explorer.msn.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] Firewall and JBoss

2001-05-11 Thread Bob Cober

Help!
I am interested in locking the ports JBoss uses.
1099 if the default JNDI lookup that is fine.
 is the default RMI Object Port that can be controlled in jboss.xml.
There is a third port that seems to be randomly assigned everytime the 
server is started.  I have seen 1591, 2291, etc.
I believe this port may be part of the default RMI Socket Factory or 
something.  How can I control it?

Thanks for any help you can provide


_
Get your FREE download of MSN Explorer at http://explorer.msn.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user