Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-315

CLI pretends that it's possible to change JDBC job repository JNDI name even for in-memory repository type

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • 7.0.0.DR2
    • Batch
    • None

      [standalone@localhost:9990 /] /subsystem=batch:read-attribute(name=job-repository-type)
      {
          "outcome" => "success",
          "result" => "in-memory"
      }
      [standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:write-attribute(name=jndi-name,value=java:jboss/datasources/ExampleDS)
      {
          "outcome" => "success",
          "response-headers" => {
              "operation-requires-reload" => true,
              "process-state" => "reload-required"
          }
      }
      [standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:read-attribute(name=jndi-name)
      {
          "outcome" => "success",
          "result" => "java:jboss/datasources/ExampleDS",
          "response-headers" => {"process-state" => "reload-required"}
      }
      [standalone@localhost:9990 /] :reload
      {
          "outcome" => "success",
          "result" => undefined
      }
      [standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:read-attribute(name=jndi-name)
      {
          "outcome" => "success",
          "result" => undefined
      }
      

            jperkins-rhn James Perkins
            pjelinek@redhat.com Pavel Jelinek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: