Is MBean "ManagedConnectionPool" still available in AS7?
by Bill Hong (Gong)
Hi,
We need to migrate a program that rests connection pool from AS6 to AS7. The following codes do not work in AS7 any more:
...
MBeanServer connector = (MBeanServer) javax.management.MBeanServerFactory.findMBeanServer(null).iterator().next();
ObjectName objectName = new ObjectName("jboss.jca:service=ManagedConnectionPool,name=" + dbPoolId);
connector.invoke(objectName, "flush", null, null);
...
I have a couple of questions:
1) It seems IronJacamar replaced previous JCA container in AS7. Is there specific document explain how to configure/debug it in AS7 environment? Is it deployed as a core module in AS7?
2) What is the equivalent way to reset connection pool in AS7 if "jboss.jca. ManagedConnectionPool" is not available now?
Thank you!
Regards,
Bill
________________________________
CONFIDENTIALITY NOTICE
This e-mail message from Delphi Technology, Inc. is intended only for the individual or entity to which it is addressed. This e-mail may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you received this e-mail by accident, please notify the sender immediately and destroy this e-mail and all copies of it.
14 years, 12 months
deprecate/remove or change ServerEnvironment.getModulesDir() which returns a single File representing the AS7 Modules directory path....
by Scott Marlow
I tried changing the testsuite/pom.xml to allow a hibernate3 test to
supply its own jars in the hibernate3 module (otherwise would be an
empty module), by adding a "testsuite" modules entry to the
module.path.
It looks like OSGi gets confused by multiple entries in
the module path.
module.path =
/home/smarlow/work/as7/testsuite/compat/target/jbossas:/home/smarlow/work/as7/testsuite/compat/../../build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/modules
server.log http://pastie.org/2278519 that shows what looks like an
OSGI error.
Earlier today on IRC, we discussed whether the modules directory should
be returned from ServerEnvironment. The concern being that the boot
module loader might not be filesystem accessible (returning as a File
instance could be wrong). The other concern is that the module path can
contain multiple paths (separated by native OS file separator).
The suggestion on IRC was for OSGi to use the server home directory
instead (ServerEnvironment.getHomeDir()).
How can/should we solve this? Change the AS7 OSGi integration code to
stop using ServerEnvironment.getModulesDir()? Can we remove the
ServerEnvironment.getModulesDir() or should we deprecate it? If we
deprecate it, perhaps it should return File[] to represent the possible
multiple module directories. Does anyone know of any external caller
into ServerEnvironment.getModulesDir()?
Scott
15 years
Re: [jboss-as7-dev] Arquillian TS: Clustering tests on multiple AS7 instances proposal
by Kabir Khan
RespawnTestCase in testsuite/domain sort of does this but having it centralized somewhere would be better
Sent from my Android phone using TouchDown (www.nitrodesk.com)
-----Original Message-----
From: Rostislav Svoboda [rsvoboda(a)redhat.com]
Received: Wednesday, 10 Aug 2011, 13:52
To: Karel Piwko [kpiwko(a)redhat.com]
CC: jboss-as7-dev(a)lists.jboss.org
Subject: Re: [jboss-as7-dev] Arquillian TS: Clustering tests on multiple AS7 instances proposal
Hi.
I would like to see default implementation of kill methods for Linux, Solaris and Windows directly in Arquillian shipped with ARQ-336 release.
Currently I know only about implementation [1] suitable only for Linux + you must register it using META-INF/services [2].
Rosta
[1] https://github.com/mgencur/edg-tests/blob/master/failover/src/main/java/o...
[2] https://github.com/mgencur/edg-tests/blob/master/failover/src/main/resour...
----- Original Message -----
> This is my very next step. However, I'm waiting for ARQ-336 impl [1]
> to
> be pushed upstream.
>
> Karel
>
>
> [1] https://issues.jboss.org/browse/ARQ-336
>
> On Wed, 2011-08-10 at 15:35 +0300, Vladimir Ralev wrote:
> > Very useful.
> >
> >
> > Shouldn't there be some kind of API to kill and restart nodes or is
> > this outside the scope of the current project? For tests like:
> > 1. Send request1 to node1
> > 2. Kill node1
> > 3. Send request to node 2
> > 4. Bring node1 back online
> > 6. Send request to node3
> >
> > On Wed, Aug 10, 2011 at 3:24 PM, Karel Piwko <kpiwko(a)redhat.com>
> > wrote:
> > Hi All,
> >
> > I have following proposal to make multiple AS7 instance
> > testing
> > available [1]:
> >
> > 1/ Create testsuite/clustering aggregation pom
> > 2/ Move current clustering TS to single-node submodule
> > 3/ Create multiple-nodes submodule, which does not inherit
> > org.jboss.as:jboss-as-testsuite but have its own environment
> > preparation
> > 4/ Use Arquillian Managed Container for standalone as this
> > is
> > only
> > available container we have now for given purpose
> >
> > I have implemented prototype at [2].
> >
> > Please let me know what do you think of that approach.
> >
> > Thanks,
> >
> > Karel
> >
> > [1] https://issues.jboss.org/browse/AS7-1418
> > [2] https://github.com/kpiwko/jboss-as/tree/AS7-1418
> >
> >
> >
> > _______________________________________________
> > jboss-as7-dev mailing list
> > jboss-as7-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >
> >
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
15 years
Disabled Tests in arquillian/container-managed
by Andrew Lee Rubinger
Hi guys:
The tests under arquillian/container-managed are not running as part of
the build. This is on purpose? I could speculate that they were turned
off in order to save some time, and that the assumption was that the
testsuite module will take care of any errors.
Problem is that there's coverage in those tests not addressed by the
"testsuite" module. So either we need to unify the tests into one
location, or re-activate them in their current place.
Thoughts?
S,
ALR
15 years
JSF 2.1 on AS7
by ssilvert＠redhat.com
If you want to try JSF 2.1 on AS7, read on.
I've created a branch that replaces JSF 2.0 with JSF 2.1:
https://github.com/ssilvert/jboss-as/commits/JSF_20_to_JSF_21
I thought this might be useful for those wanting to try their
apps/components on 2.1 right away. Everything should be working
properly including bean validation, annotations, JSP/JSTL, etc.
Please let me know if you find anything strange.
It does not yet contain Jason's JAXP fix:
http://java.net/jira/browse/JAVASERVERFACES-2156
I don't yet know when we will have pluggable JSF impls like in AS6,
but I'm looking into it. At the very least AS7.1 will have JSF 1.2
and JSF 2.1 (or 2.2). Both impls are Mojarra and not MyFaces.
Enjoy,
Stan
15 years
Subsystem testing harness
by Kabir Khan
There is now a testing harness for testing subsystem parsing, that the operations work, that the model gets updated and services get installed in the service container as expected.
If your subsystem is not totally self contained, the harness provided makes it easy to
* Install services your subsystem depends on manually
* Add socket bindings, paths and system properties used by your subsystem
* Add parsers and other subsystem extensions required by your subsystem
It lives in https://github.com/jbossas/jboss-as/tree/master/subsystem-test and contains some examples/tests of the harness itself in https://github.com/jbossas/jboss-as/tree/master/subsystem-test/src/test.
To see it used in the wild, take a look at https://github.com/jbossas/jboss-as/blob/master/jmx/src/test/java/org/jbo.... As you can see here it
* checks that the model exists:
https://github.com/jbossas/jboss-as/blob/master/jmx/src/test/java/org/jbo...
* actually bootstraps the controller and uses the services installed by the JMX service (the jmx connector in this case):
https://github.com/jbossas/jboss-as/blob/master/jmx/src/test/java/org/jbo...
The JMX subsystem is trivial, but when writing this test I found a few minor bugs. So if you are a subsystem maintainer, I'd highly recommend using this to test your subsystem properly in isolation.
This is based on the stuff that was in the subsystem maven artifact, which now in turn will be based on jboss-as-subsystem-test instead. So, if you find some problems with it try to add to the API rather than changing it, or check with me.
15 years
Is Arquillian remote support present in AS7?
by Jaikiran Pai
A recent change to arquillian configuration in AS7 shows me a error like
this:
"The server is already running! Managed containers does not support
connecting to running server instances due to the possible harmfull
effect of connecting to the wrong server. Please stop server before
running or change to another type of container."
Admittedly, I used to abuse the Arquillian "managed" container to run
specific individual tests in the integration testsuite, by starting the
server myself and then running the tests. This doesn't seem to be
possible anymore. Is there a way I can switch back to the previous
behaviour (arquillian "remote" type) somehow in AS7? I don't want
Arquillian to start the server for me (for some specific reasons).
P.S: Adding Aslak to cc, since I'm not sure he's on AS7 dev list.
-Jaikiran
15 years
Externalize the number of ServiceContainer.ContainerExecutor thread pool max threads
by Scott Stark
I created this feature request:
https://issues.jboss.org/browse/AS7-1448
to incorporate a change that I made for the AS7 used by the openshift
express cartridge. I need control over how many threads the server
creates to ensure that the imposed process limit is not exceeded. One
place that has no externalized control is the bootstrap of the
ServiceContainer.ContainerExecutor thread pool max threads. Can we add a
new org.jboss.as.server.ServerEnvironment property along the lines of
the org.jboss.server.bootstrap.maxThreads shown in the issue?
Assign the issue to me if there is a change along the patch shown in the
issue, otherwise, propose an alternative.
15 years
