1 2 3 Previous Next 31 Replies Latest reply on Aug 21, 2012 11:30 AM by avneesh Go to original post
      • 15. Re: Deployment of "war" was rolled back with failure message Operation cancel led
        sfcoy

        And the database connectivity?

         

        If that is all fine then please post a thread dump. You can use jvisualvm to create this for you.

        • 16. Re: Deployment of "war" was rolled back with failure message Operation cancel led
          avneesh

          And the database connectivity?

           

          Yes, I checked database connectivity . It is directly accessible.

           


          If that is all fine then please post a thread dump. You can use jvisualvm to create this for you.

          How can I post this thread dump could You plz explain it to me.

          • 17. Re: Deployment of "war" was rolled back with failure message Operation cancel led
            sfcoy

            You need to click "Use advanced editor" in the top right of the reply panel. That exposes a button that allows you to add attachments.

            • 18. Re: Deployment of "war" was rolled back with failure message Operation cancel led
              avneesh

              But what I have to upload there?

              • 19. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                sfcoy
                1. Run jvisualvm (on the problem machine).
                2. Connect to your hung jboss instance.
                3. Click on the "Threads" tab
                4. Click the "Thread Dump" button. A thread dump will appear below the application in the left hand panel
                5. Right click the thread dump and "Save As..."
                • 20. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                  avneesh

                  here is my thread dump.

                  • 21. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                    sfcoy

                    How long had your app been running when you did this?

                     

                    There is a thread "MSC service thread 1-4" waiting on data from your database while attempting to logon to it.

                     

                    If you do a couple more thread dumps, say, 30 seconds apart and we still see the same thread stuck in the same place then that would indicate some kind of connectivity issue with SQLServer. (Exceeded the number of licenced connections perhaps?)

                     

                    As a side issue I see that you have not configured a JNDI based datasource in your Spring configuration. It's using Apache Commons DBCP instead. It's worthwhile fixing this because data sources configured in the server are much easier for an administrator to manage and tune.

                    • 22. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                      avneesh

                      Here is my spring configuration code:;

                       

                      <tx:annotation-driven transaction-manager="txManager" />
                      
                          <bean id="txManager"
                              class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
                              <property name="dataSource" ref="dataSource" />
                          </bean>
                      
                      
                          <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
                              <property name="driverClassName" value="com.microsoft.sqlserver.jdbc.SQLServerDriver" />
                              <property name="url"
                                  value="jdbc:sqlserver://IITC-****-DB***:1433;databaseName=RI" />
                              <property name="username" value="***" />
                              <property name="password" value="****" />
                          </bean>
                      
                          <bean id="sessionFactory"
                              class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"
                              p:dataSource-ref="dataSource" p:configLocation="classpath:hibernate.cfg.xml">
                              <property name="hibernateProperties">
                                  <props>
                                      <prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop>
                                      <prop key="hibernate.show_sql">true</prop>
                                  </props>
                              </property>
                      
                          </bean>
                      

                       

                      and in standalone config file ::

                       

                      <subsystem xmlns="urn:jboss:domain:datasources:1.0">
                                  <datasources>
                                      <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="H2DS" enabled="true" jta="true" use-java-context="true" use-ccm="true">
                                          <connection-url>
                                              jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
                                          </connection-url>
                                          <driver>
                                              h2
                                          </driver>
                                          <pool>
                                              <prefill>
                                                  false
                                              </prefill>
                                              <use-strict-min>
                                                  false
                                              </use-strict-min>
                                              <flush-strategy>
                                                  FailingConnectionOnly
                                              </flush-strategy>
                                          </pool>
                                          <security>
                                              <user-name>
                                                  ***
                                              </user-name>
                                              <password>
                                                  ****
                                              </password>
                                          </security>
                                          <validation>
                                              <validate-on-match>
                                                  false
                                              </validate-on-match>
                                              <background-validation>
                                                  false
                                              </background-validation>
                                              <useFastFail>
                                                  false
                                              </useFastFail>
                                          </validation>
                                      </datasource>
                                      <drivers>
                                          <driver name="h2" module="com.h2database.h2">
                                              <xa-datasource-class>
                                                  org.h2.jdbcx.JdbcDataSource
                                              </xa-datasource-class>
                                          </driver>
                                      </drivers>
                                  </datasources>
                              </subsystem>
                      
                      • 23. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                        sfcoy

                        Let's fix the other problem first...

                        • 24. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                          avneesh

                          okey. Tell me what should I do now?

                          • 25. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                            sfcoy
                            If you do a couple more thread dumps, say, 30 seconds apart and we still see the same thread stuck in the same place then that would indicate some kind of connectivity issue with SQLServer. (Exceeded the number of licenced connections perhaps?)
                            • 26. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                              avneesh

                              Here is another thread dump...

                              • 27. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                                sfcoy

                                It still seems to be hung in the same place.

                                 

                                Is there any chance you've exceeded the number of licenced SQLServer connections?

                                 

                                Does SQLServer Studio work OK on the problem machine?

                                • 28. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                                  avneesh

                                  Yes SQLServer Studio is working in very fine way. There is no problem in running of SQLServer Studio.

                                  • 29. Re: Deployment of "war" was rolled back with failure message Operation cancel led
                                    sfcoy

                                    Can you please answer all the questions?

                                     

                                    Also, do you have logging configured in your application somehow? It would be useful to see the debug output from both Spring Framework and Hibernate.