13 Replies Latest reply on Aug 14, 2003 5:06 AM by Vishal Sharma

    Strange Problem

    Pushpendra Newbie

      Hi:
      I am using Jboss 3.2.1 on Win98 with 200MHz processor and 128 MB Ram for development purpose. But when i start jboss after some time the browser fails to connect to localhost and also fails to connect toany website. It happens both in Netscape and IE.
      It gives me dns error. After I switch off jboss server then browser connects to websites. Is it because my computer RAM Is less?

      What is the configuration requirement for Jboss 3.2.1?

      Any solutions available.

      Regards,

      Pushpendra

        • 1. Re: Strange Problem
          Adrian Brock Master

          Can you run
          netstat -a
          on win98?

          Regards,
          Adrian

          • 2. Re: Strange Problem
            Pushpendra Newbie

            Hi,

            I did netstat -an and found that when I use my application deployed on Jboss there is proliferation of local addresses.

            Why are local addresses multiplying. So there is definately error connected with my application or Jboss. I have made very sure to close database connections. What could be the reason?

            Regards,

            Pushpendra

            • 3. Re: Strange Problem
              Adrian Brock Master

              What is your application using?

              Regards,
              Adrian

              • 4. Re: Strange Problem
                Pushpendra Newbie

                Hi,

                My application architechture is as follows:
                I have Servlet talking to Java Bean and Java Bean doing data access via BMP Entity Bean. The database server here is MySQL. I am using Jboss 3.2.1.

                Regards,

                Pushpendra Raval

                • 5. Re: Strange Problem
                  Pushpendra Newbie

                  Hi,

                  I further found that when the Jboss server is laying idle and you have message: "Passivation ejb method called"
                  After this message the local and foreign addressess in netstat -a increases. Then browser would start giving dns error and would not connect to any IP address.

                  Also one more question: Is there any freeware software available to test Distributed application on jboss? Like checking web-load capacity, database transaction speed, number of open database connections etc.

                  Regards,

                  Pushpendra

                  • 6. Re: Strange Problem
                    Adrian Brock Master

                    That sounds screwy.
                    Are you doing some networking
                    (including local sockets) from your EJB?

                    Can you get a diff of the netstat -a output
                    before and after.

                    I'm not aware of open source solutions for this.
                    You can get some statistics specific to what jboss
                    implements by looking at the jsr77 mbeans or
                    jmx mbeans.

                    Try http://localhost:8080/web-console

                    Regards,
                    Adrian

                    • 7. Re: Strange Problem
                      Pushpendra Newbie

                      Hi,

                      This is my netstat -a before values:

                      Active Connections

                      Proto Local Address Foreign Address State
                      TCP sraval9:1025 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1027 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1283 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1284 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1285 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1031 PUSHPENDRA:0 LISTENING
                      TCP sraval9:8009 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1099 PUSHPENDRA:0 LISTENING
                      TCP sraval9:8080 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1191 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1192 PUSHPENDRA:0 LISTENING
                      TCP sraval9:3306 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1027 localhost:3306 ESTABLISHED
                      TCP sraval9:1032 PUSHPENDRA:0 LISTENING
                      TCP sraval9:3306 localhost:1027 ESTABLISHED
                      TCP sraval9:1031 baym-cs65.msgr.hotmail.com:1863 ESTABLISHED
                      TCP sraval9:137 PUSHPENDRA:0 LISTENING
                      TCP sraval9:138 PUSHPENDRA:0 LISTENING
                      TCP sraval9:nbsession PUSHPENDRA:0 LISTENING
                      TCP sraval9:8083 PUSHPENDRA:0 LISTENING
                      UDP sraval9:1025 *:*
                      UDP sraval9:1191 *:*
                      UDP sraval9:1192 *:*
                      UDP sraval9:1032 *:*
                      UDP sraval9:nbname *:*
                      UDP sraval9:nbdatagram *:*

                      and netstat -a after values (i.e. after I use database connections and do database operation with mysql server):


                      Active Connections

                      Proto Local Address Foreign Address State
                      TCP sraval9:1025 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1027 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1283 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1284 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1285 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1031 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1333 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1334 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1335 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1336 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1337 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1338 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1339 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1340 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1341 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1342 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1343 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1344 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1345 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1346 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1347 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1348 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1349 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1350 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1351 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1352 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1353 PUSHPENDRA:0 LISTENING
                      TCP sraval9:8009 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1354 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1099 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1355 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1356 PUSHPENDRA:0 LISTENING
                      TCP sraval9:8080 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1191 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1192 PUSHPENDRA:0 LISTENING
                      TCP sraval9:3306 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1027 localhost:3306 ESTABLISHED
                      TCP sraval9:1032 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1326 PUSHPENDRA:0 LISTENING
                      TCP sraval9:1333 localhost:3306 ESTABLISHED
                      TCP sraval9:1334 localhost:3306 ESTABLISHED
                      TCP sraval9:1335 localhost:3306 ESTABLISHED
                      TCP sraval9:1336 localhost:3306 ESTABLISHED
                      TCP sraval9:1337 localhost:3306 ESTABLISHED
                      TCP sraval9:1338 localhost:3306 ESTABLISHED
                      TCP sraval9:1339 localhost:3306 ESTABLISHED
                      TCP sraval9:1340 localhost:3306 ESTABLISHED
                      TCP sraval9:1341 localhost:3306 ESTABLISHED
                      TCP sraval9:1342 localhost:3306 ESTABLISHED
                      TCP sraval9:1343 localhost:3306 ESTABLISHED
                      TCP sraval9:1344 localhost:3306 ESTABLISHED
                      TCP sraval9:1345 localhost:3306 ESTABLISHED
                      TCP sraval9:1346 localhost:3306 ESTABLISHED
                      TCP sraval9:1347 localhost:3306 ESTABLISHED
                      TCP sraval9:1348 localhost:3306 ESTABLISHED
                      TCP sraval9:1349 localhost:3306 ESTABLISHED
                      TCP sraval9:1350 localhost:3306 ESTABLISHED
                      TCP sraval9:1351 localhost:3306 ESTABLISHED
                      TCP sraval9:1352 localhost:3306 ESTABLISHED
                      TCP sraval9:1353 localhost:3306 ESTABLISHED
                      TCP sraval9:1354 localhost:3306 ESTABLISHED
                      TCP sraval9:1355 localhost:3306 ESTABLISHED
                      TCP sraval9:1356 localhost:3306 ESTABLISHED
                      TCP sraval9:3306 localhost:1027 ESTABLISHED
                      TCP sraval9:3306 localhost:1333 ESTABLISHED
                      TCP sraval9:3306 localhost:1334 ESTABLISHED
                      TCP sraval9:3306 localhost:1335 ESTABLISHED
                      TCP sraval9:3306 localhost:1336 ESTABLISHED
                      TCP sraval9:3306 localhost:1337 ESTABLISHED
                      TCP sraval9:3306 localhost:1338 ESTABLISHED
                      TCP sraval9:3306 localhost:1339 ESTABLISHED
                      TCP sraval9:3306 localhost:1340 ESTABLISHED
                      TCP sraval9:3306 localhost:1341 ESTABLISHED
                      TCP sraval9:3306 localhost:1342 ESTABLISHED
                      TCP sraval9:3306 localhost:1343 ESTABLISHED
                      TCP sraval9:3306 localhost:1344 ESTABLISHED
                      TCP sraval9:3306 localhost:1345 ESTABLISHED
                      TCP sraval9:3306 localhost:1346 ESTABLISHED
                      TCP sraval9:3306 localhost:1347 ESTABLISHED
                      TCP sraval9:3306 localhost:1348 ESTABLISHED
                      TCP sraval9:3306 localhost:1349 ESTABLISHED
                      TCP sraval9:3306 localhost:1350 ESTABLISHED
                      TCP sraval9:3306 localhost:1351 ESTABLISHED
                      TCP sraval9:3306 localhost:1352 ESTABLISHED
                      TCP sraval9:3306 localhost:1353 ESTABLISHED
                      TCP sraval9:3306 localhost:1354 ESTABLISHED
                      TCP sraval9:3306 localhost:1355 ESTABLISHED
                      TCP sraval9:3306 localhost:1356 ESTABLISHED
                      TCP sraval9:1031 baym-cs65.msgr.hotmail.com:1863 ESTABLISHED
                      TCP sraval9:137 PUSHPENDRA:0 LISTENING
                      TCP sraval9:138 PUSHPENDRA:0 LISTENING
                      TCP sraval9:nbsession PUSHPENDRA:0 LISTENING
                      TCP sraval9:8083 PUSHPENDRA:0 LISTENING
                      UDP sraval9:1025 *:*
                      UDP sraval9:1191 *:*
                      UDP sraval9:1192 *:*
                      UDP sraval9:1032 *:*
                      UDP sraval9:1326 *:*
                      UDP sraval9:nbname *:*
                      UDP sraval9:nbdatagram *:*

                      Note port : 3306 is MySQL Server port, while port: 8080,8083, and 1099 is jboss webserver, webservices and jndi server ports.

                      I checked connection pool count and it shows around 25 open connections which matches observed values.

                      Since my server is on local machine and I am the only person using the j2ee application why then it should open many mysql ports and why is it not closing connections which i do it in my code.

                      I am attaching sample EJB file: AutoBean.java for review. Earlier I was getting No Managed Connections error which I solved by closing connections in method and then that message went away, so what could be the reason that afte ejb passivates you get dns error in browser.

                      Regards,

                      Pushpendra

                      • 8. Re: Strange Problem
                        Pushpendra Newbie

                        Here: is my java EJB file: AutoBean.java

                        • 9. Re: Strange Problem
                          Pushpendra Newbie

                          Hi:

                          Anybody with ideas as to why I am getting dns error?

                          Pushpendra

                          • 10. Re: Strange Problem
                            Adrian Brock Master

                            The 25 open connections are the pooled jdbc
                            connections, closing a connection in your ejb
                            just returns it to the pool.

                            I don't know why 25 open connections should
                            stop you connecting to the web server, maybe
                            there is some limit in Win98?

                            Regards,
                            Adrian

                            • 11. SOLUTION
                              Pushpendra Newbie

                              Hi,
                              Finally I got the solution. It had to do with limitation of RAM on my machine. 128MB RAM on 200MHz Computer cannot handle 25 connection pool so it gave me dns error and browser was not able to open any website. So when I made max connection pool to just 1 everything worked fine and also even if EJB Passivates the browser still worked.

                              Does any body have any figure as to how much should be the connection pool for an deployed application serving polpulation of 5 milliion. And hardware requirements?

                              Regards,

                              Pushpendra Raval

                              • 12. Re: SOLUTION
                                scoob Newbie

                                Hi there,

                                I have been looking through the text of this thread and I am having exactly the same symptoms with my Win 98 machine using JBoss 3.2.2.

                                I am very new to JBoss, so could you let me know how you changed the max connection pool size.

                                Thanks in advance,

                                Scoob.

                                • 13. Re: SOLUTION
                                  Vishal Sharma Expert

                                  Go to JBOSS_HOME/server/all/conf/standardjboss.xml

                                  Look for this for yr respectibve bean.

                                  </container-pool-conf>
                                  100
                                  </container-pool-conf>


                                  Try this...