Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-6620 JON/Open Console Issues
  3. JBAS-6777

'interleaving' prop on connection factories and datasources is always null, even when underlying ds.xml file contains the interleaving element

    Details

    • Similar Issues:
      Show 10 results 

      Description

      My ds.xml file:

      <connection-factories>
      <tx-connection-factory>
      <jndi-name>MyXATxCF</jndi-name>
      <rar-name>jms-ra.rar</rar-name>
      <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
      ...
      <interleaving/>
      </tx-connection-factory>
      </connection-factories>

      But the interleaving ManagedProperty on this CF is still null, rather than true:

      name=interleaving, viewUse=NONE, readOnly=false, mandatory=false, removed=false, type=SimpleMetaType:java.lang.Boolean, value= <<<null>>>

        Issue Links

          Activity

          Hide
          Ian Springer
          added a comment -

          Using EAP branch r90482, the 'interleaving' prop still gets reset to false by the Profile Service after I set it to true via a component update. I tried with both an XA Datasource and a Tx Connection Factory with XA enabled. Did you forget to check the fix into the EAP branch?

          Show
          Ian Springer
          added a comment - Using EAP branch r90482, the 'interleaving' prop still gets reset to false by the Profile Service after I set it to true via a component update. I tried with both an XA Datasource and a Tx Connection Factory with XA enabled. Did you forget to check the fix into the EAP branch?
          Hide
          Scott Stark
          added a comment -

          Yes, its in the https://svn.jboss.org/repos/jbossas/branches/JBPAPP_5_0 and the test is validating that the interleaving property is true on the underlying component:

          // Query the interleaving
          ManagementView mgtView = getManagementView();
          ComponentType type = KnownComponentTypes.DataSourceTypes.XA.getType();
          ManagedComponent txcf = mgtView.getComponent(jndiName, type);
          assertNotNull(txcf);
          ManagedProperty interleaving = txcf.getProperty("interleaving");
          assertNotNull("interleaving", interleaving);
          MetaValue interleavingMV = interleaving.getValue();
          assertNotNull("interleaving.value", interleavingMV);
          assertEquals("interleaving.value is true", SimpleValueSupport.wrap(Boolean.TRUE), interleavingMV);

          Can you attach the ds.xml file that is showing the false value.

          Show
          Scott Stark
          added a comment - Yes, its in the https://svn.jboss.org/repos/jbossas/branches/JBPAPP_5_0 and the test is validating that the interleaving property is true on the underlying component: // Query the interleaving ManagementView mgtView = getManagementView(); ComponentType type = KnownComponentTypes.DataSourceTypes.XA.getType(); ManagedComponent txcf = mgtView.getComponent(jndiName, type); assertNotNull(txcf); ManagedProperty interleaving = txcf.getProperty("interleaving"); assertNotNull("interleaving", interleaving); MetaValue interleavingMV = interleaving.getValue(); assertNotNull("interleaving.value", interleavingMV); assertEquals("interleaving.value is true", SimpleValueSupport.wrap(Boolean.TRUE), interleavingMV); Can you attach the ds.xml file that is showing the false value.
          Hide
          Ian Springer
          added a comment -

          For an existing ds.xml that contains the <interleaving/> tag, the interleaving managed prop is true; so that part of it appears to be fixed. The issue that still exists is that when I call updatecomponent() on the management view and then load() on the management view, the managed prop's value has been reset to false. Similarly, when I have an existing datasource or conn factory with interleaving set to false, when I try to change it to true via the PS and then reload the view, its value is still false.

          Show
          Ian Springer
          added a comment - For an existing ds.xml that contains the <interleaving/> tag, the interleaving managed prop is true; so that part of it appears to be fixed. The issue that still exists is that when I call updatecomponent() on the management view and then load() on the management view, the managed prop's value has been reset to false. Similarly, when I have an existing datasource or conn factory with interleaving set to false, when I try to change it to true via the PS and then reload the view, its value is still false.
          Hide
          Scott Stark
          added a comment -

          Ok, I'll create a test that attempts to change the value from false to true.

          Show
          Scott Stark
          added a comment - Ok, I'll create a test that attempts to change the value from false to true.
          Hide
          Scott Stark
          added a comment -

          To be able to update the interleaving value requires a deployment restart. I have updated the activationPolicy to be DEPLOYMENT_RESTART.

          Show
          Scott Stark
          added a comment - To be able to update the interleaving value requires a deployment restart. I have updated the activationPolicy to be DEPLOYMENT_RESTART.

            People

            • Assignee:
              Scott Stark
              Reporter:
              Ian Springer
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: