1 2 Previous Next 22 Replies Latest reply on Sep 25, 2008 12:37 PM by Peter Johnson

    Jboss Server Crashed ! ! !

    Milan Gothe Newbie

      Hi,

      Is there any one who can support to resolve the issue?
      This is really stucking my life using Jboss server 4.0.3 SP 1. We've the application using JAVA/JSP and Jboss server to serve. And MSSQL server 2000 as a backend database server and MERLIA.jar to connect.

      Here, what we are experiencing is; we need to send more than 100,000 emails a week and after sending out all emails (100,000 emails (email size is about 45kb per email)) the jboss server automaticall down and we will need to restart the jboss.

      We've the file named mssql-ds.xml to for database connetion:
      ------------------------------------------------------------------

      <local-tx-datasource>
      <jndi-name>MerliaDS</jndi-name>
      <connection-url>jdbc:inetdae7:192.168.1.11:1433?database=TPR</connection-url>
      <driver-class>com.inet.tds.TdsDataSource</driver-class>
      <user-name>sa</user-name>
      pxgTGK23
      <min-pool-size>300</min-pool-size>
      <max-pool-size>500</max-pool-size>
      <blocking-timeout-millis>30000</blocking-timeout-millis>
      <idle-timeout-minutes>10</idle-timeout-minutes>
      <check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
      <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->

      <type-mapping>MS SQLSERVER2000</type-mapping>

      </local-tx-datasource>

      --------------------------------------------------------------------------------------
      What could be the possible cause of jboss crash again again!!!!

      Any Information and solution would be greatly appreciated.

      Thanks in Advance. This is really emergency.

      Regards,
      Milan Gothe

        • 1. Re: Jboss Server Crashed ! ! !
          jaikiran pai Master

          How do you send the emails? What does the server.log contain when the server is shutting down?

          • 2. Re: Jboss Server Crashed ! ! !
            Milan Gothe Newbie

            Hi,

            Thanks atleast someone replied. well, we are using linux machine RHEL4AS.

            And, we are sending email using Windows 2003 server SMTP server,no exchange server.And ofcourse, sending email using JAVA. is this anything has to do with.

            The jboss is throwing the following error in the log file "server.log"

            -----------------------------------------------------------------------------------
            INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)\par
            2008-09-04 16:14:11,558 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)\par
            2008-09-04 16:14:11,558 INFO [STDOUT] \tab at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)\par
            2008-09-04 16:14:11,558 INFO [STDOUT] \tab at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at java.lang.Thread.run(Thread.java:595)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )\par2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:246)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)\par
            2008-09-04 16:14:11,559 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)\par
            2008-09-04 16:14:11,560 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:73)\par
            2008-09-04 16:14:11,560 INFO [STDOUT] \tab ... 26 more\par
            2008-09-04 16:14:11,560 WARN [org.apache.jk.common.ChannelSocket] processCallbacks status 2\par
            2008-09-04 16:14:12,961 INFO [STDOUT] Exception Caught at GETPOOLED Connection.\par2008-09-04 16:14:12,961 INFO [STDOUT] org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout (30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))\par
            2008-09-04 16:14:12,961 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:79)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getPooledConnection(TPRConnection.java:179)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getConnection(TPRConnection.java:57)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at com.tpr.model.facility.EmailCampaignTracker.doGet(EmailCampaignTracker.java:42)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:12,962 INFO [STDOUT] \tab at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)\par
            2008-09-04 16:14:12,963 INFO [STDOUT] \tab at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)\par
            2008-09-04 16:14:12,964 INFO [STDOUT] \tab at java.lang.Thread.run(Thread.java:595)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:246)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)\par
            2008-09-04 16:14:12,965 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:73)\par
            2008-09-04 16:14:12,966 INFO [STDOUT] \tab ... 26 more\par
            2008-09-04 16:14:12,966 WARN [org.apache.jk.common.ChannelSocket] processCallbacks status 2\par
            2008-09-04 16:14:15,341 INFO [STDOUT] Exception Caught at GETPOOLED Connection.\par
            2008-09-04 16:14:15,341 INFO [STDOUT] org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))\par
            2008-09-04 16:14:15,341 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:79)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getPooledConnection(TPRConnection.java:179)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getConnection(TPRConnection.java:57)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at com.tpr.model.facility.EmailCampaignTracker.doGet(EmailCampaignTracker.java:42)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)\par
            2008-09-04 16:14:15,342 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)\par
            2008-09-04 16:14:15,343 INFO [STDOUT] \tab at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)\par
            2008-09-04 16:14:15,344 INFO [STDOUT] \tab at java.lang.Thread.run(Thread.java:595)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )\par2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:246)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:73)\par
            2008-09-04 16:14:15,345 INFO [STDOUT] \tab ... 26 more\par
            2008-09-04 16:14:15,346 WARN [org.apache.jk.common.ChannelSocket] processCallbacks status 2\par
            2008-09-04 16:14:15,399 INFO [STDOUT] Exception Caught at GETPOOLED Connection.\par
            2008-09-04 16:14:15,399 INFO [STDOUT] org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))\par
            2008-09-04 16:14:15,399 INFO [STDOUT] \tab at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:79)\par
            2008-09-04 16:14:15,399 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getPooledConnection(TPRConnection.java:179)\par
            2008-09-04 16:14:15,399 INFO [STDOUT] \tab at com.tpr.connection.TPRConnection.getConnection(TPRConnection.java:57)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at com.tpr.model.facility.EmailCampaignTracker.doGet(EmailCampaignTracker.java:42)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)\par
            2008-09-04 16:14:15,400 INFO [STDOUT] \tab at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)\par
            2008-09-04 16:14:15,401 INFO [STDOUT] \tab at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)\par
            2008-09-04 16:14:15,402 INFO [STDOUT] \tab at java.lang.Thread.run(Thread.java:595)\par
            ----------------------------------------------------------------------------------
            Any help and support to resolve would be greatly appriciated. If you need any further information plz let me know

            Thanks
            Milan Gothe

            • 3. Re: Jboss Server Crashed ! ! !
              jaikiran pai Master

              When you say JBoss crashes, do you actually mean the java.exe process is killed?

              As for this exception:

              2008-09-04 16:14:11,559 INFO [STDOUT] Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )


              See this wiki http://wiki.jboss.org/wiki/WhatDoesTheMessageNoManagedConnectionsAvailableMean

              • 4. Re: Jboss Server Crashed ! ! !
                Milan Gothe Newbie

                Hi,

                Well, i'm not sure but i think so. It is happening after that 100,000 emails are sent. And also, it won't happen at the moment of email sent out. It will happen after 2/3 days of email send out.

                As i already give you the min pool and block time out above,can we increase over that i mean we already have 300 min pool size, is there the limitation.

                Thanks.
                Milan Gothe

                • 5. Re: Jboss Server Crashed ! ! !
                  Milan Gothe Newbie

                  Hi Jaikiran,

                  Sorry,I don't know your name.Thanks you so much for keep on responding.

                  Do you have any idea how can we see the concurrent access in the jboss or any tools. And does it have to with the connection pool and all.

                  Thanks.
                  Milan Gothe.

                  • 6. Re: Jboss Server Crashed ! ! !
                    jaikiran pai Master

                     

                    "gothemilan" wrote:
                    Hi,


                    As i already give you the min pool and block time out above,can we increase over that i mean we already have 300 min pool size, is there the limitation.



                    You will have to check whether your application is leaking connections. See this wiki http://wiki.jboss.org/wiki/CanJBossTellMeWhenIDontCloseAConnection.

                    Also, you can access the jmx-console at http://localhost:8080/jmx-console and you will find a MBean named "name=MerliaDS,service=ManagedConnectionPool" under the jboss.jca section. Click on that link which will lead you to a page which shows the various attributes of the connection pool. One of them is the InUseConnectionCount. Check out the value of this.

                    • 7. Re: Jboss Server Crashed ! ! !
                      jaikiran pai Master

                       

                      "gothemilan" wrote:


                      Well, i'm not sure but i think so. It is happening after that 100,000 emails are sent. And also, it won't happen at the moment of email sent out. It will happen after 2/3 days of email send out.



                      If you get hold of the server.log when this actually happens, then it might provide some hint.

                      • 8. Re: Jboss Server Crashed ! ! !
                        Milan Gothe Newbie

                        Hi,

                        Thanks for your response.

                        Can we increase min pool size to 400 and does this have anything to do with RAM(Memory) in the system. Currently we have 2GB of RAM in the system. Is this RAM enough to manupulate data for more than 250 users concurrent connection.Is this causing the issue?

                        The value for InUseConnectionCount is long.I don't understand this.

                        Thanks.
                        Milan Gothe[/img]

                        • 9. Re: Jboss Server Crashed ! ! !
                          Milan Gothe Newbie

                          Hi Friend,

                          May be this information could help us to find the solutions. we only have 100 Max connection pool in this file defined, should we increase this coz as i already said before, we have more than 250 users at a time(concurrent).

                          -----------------------------------------------------------------
                          /server/default/deploy/jbossjca-service.xml
                          ------------------------------------------------------------------

                          <!-- The name that appears in thread names -->
                          WorkManager
                          <!-- The maximum amount of work in the queue -->
                          1024
                          <!-- The maximum number of active threads -->
                          100
                          <!-- How long to keep threads alive after their last work (default one minute) -->
                          60000

                          -------------------------------------------------------------------------------
                          if you need any information, plz don't hesitate to ask .

                          thanks.
                          Milan Gothe

                          • 10. Re: Jboss Server Crashed ! ! !
                            Kamil Demecki Novice

                             

                            "gothemilan" wrote:
                            Hi Friend,

                            May be this information could help us to find the solutions. we only have 100 Max connection pool in this file defined, should we increase this coz as i already said before, we have more than 250 users at a time(concurrent).


                            This attribute is for Web server threads (check localhost:8080/ and click status how many threads are busy) I think you can also check max used threads on JMX console.

                            You have exception from "org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:73)" so you probably you don't close jdbc connection. Are you using finally block to close connections ?

                            "jakiran" wrote:
                            Also, you can access the jmx-console at http://localhost:8080/jmx-console and you will find a MBean named "name=MerliaDS,service=ManagedConnectionPool" under the jboss.jca section. Click on that link which will lead you to a page which shows the various attributes of the connection pool. One of them is the InUseConnectionCount. Check out the value of this.


                            Also there is method listConnectionInUse on that JMX bean which show you which your code doesn't release connections. It is amazing JBoss feature which I used many times on production ;>

                            • 11. Re: Jboss Server Crashed ! ! !
                              Milan Gothe Newbie

                              Hi JaiKiran,

                              Did you find some solution to resolve the issue. I don't know what am i suppose to do now?

                              Did you get any hints from above mentioned lines of code or do you need further hints to pin point the issue.

                              Thanks
                              Milan Gothe

                              • 12. Re: Jboss Server Crashed ! ! !
                                Milan Gothe Newbie

                                Hi,

                                Yes, i have used the finally block to close the connection.

                                Thanks.

                                • 13. Re: Jboss Server Crashed ! ! !
                                  jaikiran pai Master

                                  Milan,

                                  Did you use the jmx-console to check the in use connection count? What value does it show?

                                  • 14. Re: Jboss Server Crashed ! ! !
                                    Milan Gothe Newbie

                                    Hi,

                                    What is this file jbossjca-service.xml file in Jboss Server?



                                    <!-- ==================================================================== -->
                                    <!-- JBossCX setup, for J2EE connector architecture support -->
                                    <!-- The RARDeployer is needed only until xslt based deployment is written.-->
                                    <!-- ==================================================================== -->

                                    mbean code="org.jboss.util.threadpool.BasicThreadPool"
                                    name="jboss.jca:service=WorkManagerThreadPool">
                                    <!-- The name that appears in thread names -->
                                    attribute name="Name">WorkManager</attribute
                                    <!-- The maximum amount of work in the queue -->
                                    attribute name="MaximumQueueSize">1024</attribute
                                    <!-- The maximum number of active threads -->
                                    attribute name="MaximumPoolSize">200</attribute
                                    <!-- How long to keep threads alive after their last work (default one minute) -->
                                    attribute name="KeepAliveTime">60000</attribute
                                    /mbean

                                    mbean code="org.jboss.resource.work.JBossWorkManager"
                                    name="jboss.jca:service=WorkManager">
                                    <depends optional-attribute-name="ThreadPoolName">jboss.jca:service=WorkManagerThreadPool
                                    <depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager


                                    mbean code="org.jboss.resource.deployment.RARDeployer"
                                    name="jboss.jca:service=RARDeployer">
                                    <depends optional-attribute-name="WorkManagerName">jboss.jca:service=WorkManager
                                    <depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager



                                    attribute name="DdSuffix">-ds.xml
                                    attribute name="EnhancedSuffixes">300:-ds.xml
                                    attribute name="XslUrl">stylesheets/ConnectionFactoryTemplate.xsl
                                    attribute name="ValidateDTDs">false
                                    /mbean>

                                    <!--
                                    | The CachedConnectionManager is used partly to relay started UserTransactions to
                                    | open connections so they may be enrolled in the new tx.
                                    -->

                                    <depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager

                                    <!--SpecCompliant false means JBoss will close connections left open when you
                                    return from a method call and generate a loud warning. SpecCompliant true
                                    means JBoss will disconnect connection handles left open on return from a
                                    method call and reconnect them with an appropriate (security, tx)
                                    connection on the next call to the same object.-->
                                    attribute name="SpecCompliant">false</attribute

                                    <!-- Enable connection close debug monitoring -->
                                    attribute name="Debug">true




                                    -------------------------------------------------------------------------------------------

                                    thanks.
                                    Milan Gothe

                                    1 2 Previous Next