AS7 admin console strange behaviour
by Vimal Kansal
Hi,
I am not sure if this is the desired behaviour or a bug (although to me
it looks like a bug). Here is what I am doing :
(1) Disabled the 'ExampleDS' by clciking the 'Disable' button. Screen
shows that datasource is disabled.
(2) I click on the 'Test' button, and I get the message 'Successfully
connected'.
I think this is not very intuitive.
Thx
Vimal
13 years, 11 months
Testsuite modules - Print out the available options/params that are required for running the tests?
by Jaikiran Pai
I haven't been closely following the testsuite refactor in these few
weeks, so I currently don't have an exact idea on what the new params
are to run the integration tests. I tried running the following from the
TRUNK/testsuite/integration:
mvn clean install
and it did not run any tests. I had to dig into the pom.xml to check
what params need to be passed to run the integration tests. Turns out I
have to use:
mvn clean install -Dbasic.integration.tests=true
Would it be possible to somehow print out all the available options and
params that need to used, when you run mvn clean install from the
testsuite modules? Something like a help?
P.S: Shouldn't the "mvn clean install" from testsuite/integration
atleast run the basic integration tests? Or does this conflict with how
Maven handles the profiles?
-Jaikiran
13 years, 11 months
AS7 : Discrepency (schema vs model)
by Vimal Kansal
Hi,
I found that datasource xsd defines an element like :
<xs:element name="*driver*" type="xs:token" minOccurs="0">
<xs:annotation>
<xs:documentation>
<![CDATA[[
An unique reference to the classloader module which
contains the JDBC driver
The accepted format is driverName#majorVersion.minorVersion
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
And the cli model defines :
[standalone@localhost:9999 data-source=java:jboss/datasources/ExampleDS]
:read-resource
{
"outcome" => "success",
"result" => {
"background-validation" => undefined,
"background-validation-millis" => undefined,
"blocking-timeout-wait-millis" => undefined,
"connection-properties" => undefined,
"connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1",
"*driver-name*" => "h2",
"enabled" => true,
"flush-strategy" => undefined,
"idle-timeout-minutes" => undefined,
"jndi-name" => "java:jboss/datasources/ExampleDS",
"jta" => true,
"max-pool-size" => 2,
"min-pool-size" => 2,
"password" => "sa",
"pool-name" => "H2DS",
"pool-prefill" => true,
"pool-use-strict-min" => undefined,
"set-tx-query-timeout" => "false",
"share-prepared-statements" => "false",
"spy" => false,
"track-statements" => "\"NOWARN\"",
"use-ccm" => true,
"use-fast-fail" => "false",
"use-java-context" => true,
"user-name" => "sa",
"validate-on-match" => "false"
}
}
While for most other elements, xsd element and the model attribute
match, this one (i.e driver vs driver-name) seems to be bit confusing.
Thx
Vimal
13 years, 11 months
How to get interface addresses using the Management CLI
by Misty Stanley-Jones
I am trying to find a way to get the addresses of the interfaces using the Management CLI. I thought this would be easy! I have tried all of these ways:
[domain@localhost:9999 /] :read-children-names(child-type=interface)
{
"outcome" => "success",
"result" => [
"management",
"public"
]
}
[domain@localhost:9999 /] :read-children-attributes(child-type=interface)
Failed to get the list of supported operation properties.
[domain@localhost:9999 /] :read-children-resources(child-type=interface)
{
"outcome" => "success",
"result" => {
"management" => {
"criteria" => undefined,
"name" => "management"
},
"public" => {
"criteria" => undefined,
"name" => "public"
}
}
}
[domain@localhost:9999 interfaces] /interface=management:read-resource
{
"outcome" => "success",
"result" => {
"criteria" => undefined,
"name" => "management"
}
}
[domain@localhost:9999 interfaces] /interface=management:read-children-resources
{
"outcome" => "failed",
"failure-description" => "child-type may not be null.",
"rolled-back" => true
}
[domain@localhost:9999 interfaces] /interface=management:read-children-resources(recursive=true)
{
"outcome" => "failed",
"failure-description" => "child-type may not be null.",
"rolled-back" => true
}
[domain@localhost:9999 interfaces] /interface=management:read-children-resources(child-type=inet-address)
{
"outcome" => "failed",
"failure-description" => "No known child type named inet-address",
"rolled-back" => true
}
--
Misty Stanley-Jones, RHCE
Content Author, ECS Brisbane
☺: misty (Freenode IRC) ✉: misty(a)redhat.com ☏: + 61 7 3514 8105 ☏: 88105
13 years, 11 months
AS7 CLI : data-source test-connection-in-pool does not seem to be doing anything
by Vimal Kansal
Hi,
I have enabled the ExampleDS, set it to min size = 2 max-size = 2 and
prefill = true which I believe will fill the pool with 2 connections to
begin with. Then when I execute the following :
data-source test-connection-in-pool
--jndi-name=java:jboss/datasources/ExampleDS
The command just returns without any message.
Thx
Vimal
13 years, 11 months
Datsource health check : How do I do?
by Vimal Kansal
Hi,
I couldn't find anything on admin console or the CLI using which can
find out things like : how many active connections are currently there
in pool, how many connections in use, idle connections, hanging
connection, if the connection is hanging to be able to kill that
connection etc. Can somebody please help or point me in right direction.
Thx
Vimal
13 years, 11 months
AS 7 CLI : Have the operation aliases been implemented yet?
by Vimal Kansal
Hi,
The "Admin doc" notes ;
Tab-completion is supported for all commands and options, i.e.
node-types and node-names, operation names and parameter names. *We are
also considering adding aliases that are less verbose for the user, and
will translate into the corresponding operation requests in the background.*
I was wondering, have we implemented the operation aliases yet?
Thx
Vimal
13 years, 11 months
Maven profile ordering puzzle
by Ondrej Zizka
Hi,
I can't get maven modules run in desired order.
I have ported test-reporting for the testsuite.
Now I am trying to put it to right place in POM.
Ideally, `mvn install site` should have reporting by default,
`-DnoReport` should skip reporting.
I've tried:
1) Having in testsuite/pom.xml, bound to the site phase.
This needs to run `mvn site` in a separate command, like `mvn install;
mvn site`, since with `mvn install site` reporting would run before the
submodules (with tests) were run.
2) Having it in testsuite/reporting/pom.xml
Because of how testsuite/pom.xml is written (multiple profiles
activating modules used to separate certain test groups),
reporting must be defined in a profile, in order to run it after other
submodules.
That blocks having it auto-activated since it's not possible to move
auto-activated profiles after property-activated.
So it's only possible to having it not running by default, and running
on-demand. (And that's what I am going to use as fallback solution.)
Any idea how should I get this working "ideally", as defined above?
Thanks,
Ondra
13 years, 11 months
