Unified invokers in Branch_4_2
by Dimitris Andreadis
We've switched to the unified invoker (jboss-remoting 2.0.0.GA) for the
EJB containers in JBossAS Branch_4_2.
For backwards compatibility, conf/standardjboss.xml contains both the
new unified and the old rmi invoker-proxy-binding definitions, but the
default now is the unified ones.
This change and the move to the Arjuna TS is causing a lot of failures
in the testsuite, so any help is appreciated.
If you search for 'rmi-invoker' in testsuite/resources there are quite a
few references to it, so a question is whether we should switch those as
well or let them test the old rmi invokers.
While there, I've also noticed that jboss head doesn't have rmi-invoker
definitions in conf/standardjboss.xml, and
org.jboss.metadata.SessionMetadata / EntityMetaData for some reason
default to the rmi-invoker for clustered setups, so I suppose this has
been forgotten there?
public static final String DEFAULT_STATEFUL_INVOKER =
"stateful-unified-invoker";
public static final String DEFAULT_CLUSTERED_STATEFUL_INVOKER =
"clustered-stateful-rmi-invoker";
public static final String DEFAULT_STATELESS_INVOKER =
"stateless-unified-invoker";
public static final String DEFAULT_CLUSTERED_STATELESS_INVOKER =
"clustered-stateless-rmi-invoker";
public static final String DEFAULT_ENTITY_INVOKER_PROXY_BINDING =
"entity-unified-invoker";
public static final String
DEFAULT_CLUSTERED_ENTITY_INVOKER_PROXY_BINDING =
"clustered-entity-rmi-invoker";
Cheers
/Dimitris
19 years, 2 months
Re: [jboss-dev] MDB integration tests
by Tim Fox
I didn't see it before, but now I've had a quick look.
I still can't work out though if this is just a framework or it contains
actual tests.... or where those tests are.
Weston Price wrote:
> Note, Tim I specifically mentioned org.jboss.test.messagedriven. This is
> the framework I was talking about. I am not sure if you read the post or
> you just didn't see it.
>
>
>
> -----Original Message-----
> From: Adrian Brock
> Sent: Wednesday, January 17, 2007 9:44 AM
> To: JBoss.org development list
> Cc: Tim Fox; Weston Price
> Subject: Re: [jboss-dev] MDB integration tests
>
>> Scott M Stark wrote:
>>> They are spread out. Other mdb tests are:
>>>
>>> testsuite module:
>>> org.jboss.test.cts.test.MDBUnitTestCase
>>> org.jboss.test.jca.test.InflowUnitTestCase
>>>
>>> ejb3 module:
>>> org.jboss.ejb3.test.mdb
>>> org.jboss.ejb3.test.mdbtopic
>>> org.jboss.ejb3.test.mdbtransactions
>>>
>
> On Sat, 2007-01-13 at 18:48 +0000, Tim Fox wrote:
>> The coverage still seems very poor w.r.t. integration tests, unless
> I'm
>> missing something.
>>
>
> That is true of org.jboss.test.mdb
>
> I remember complaining about them 3 years ago, they are not good tests.
> I only left them in place because you can never have too many tests. :-)
>
> The real tests are in org.jboss.test.messagedriven
>
> Theses tests use a framework that creates the same tests for
> old = JMSContainerInvoker
> new = JCA Inflow
>
> They have a simple format:
>
> properties - for configuration of the activiation spec or the invoker
> proxy
>
> operation - steps in the test (including assertions)
>
> See org.jboss.test.messagedriven.support.BaseMessageDrivenTest
>
> public void runTest(Operation[] ops, Properties props) throws
>
> So you can trivially add new tests without having to create
> new MDB deployments for each test.
>
> e.g. The single mdb for JCA1.5 looks like this:
> <message-driven>
> <ejb-name>TestMDB</ejb-name>
> <activation-config>
> <activation-config-property>
>
> <activation-config-property-name>destination</activation-config-property
> -name>
>
> <activation-config-property-value>${test.messagedriven.destination}</act
> ivation-config-property-value>
> </activation-config-property>
> <activation-config-property>
>
> <activation-config-property-name>destinationType</activation-config-prop
> erty-name>
>
> <activation-config-property-value>${test.messagedriven.destinationType}<
> /activation-config-property-value>
> </activation-config-property>
> etc....
>
> But they are incomplete until this task is done:
> http://jira.jboss.com/jira/browse/JBAS-1434
>
>> From the point of view of JBM (and JBossMQ) we need to know all the
>> main use cases are tests with the JMSContainerInvoker, and also using
>> JCA1.5 inflow now this is apparently supported in production.
>>
>> Without proper coverage we can't have any confidence that JBM (or
>> JBossMQ) will work correctly with the app server.
>>
>> I've added a task to get these tests sorted before we release JBM 1.2.
>
> Is that this task?
> http://jira.jboss.com/jira/browse/JBMESSAGING-170
--
Tim Fox
JBoss Messaging Technical Lead
JBoss - a division of Red Hat
T: +44 2088006768
M: +44 7957983205
E: tim.fox(a)jboss.com tim.fox(a)redhat.com
19 years, 2 months
branch_4_2 arjuna tm commit issue
by Alexey Loubyansky
Running the testsuite of Branch_4_2 quite a few failures caused by
ConcurrentModificationException when committing a tx. Browsed Jira but
haven't found a similar issue. Has anyone else seen this?
Alexey
12:38:20,062 ERROR [STDERR] java.util.ConcurrentModificationException
12:38:20,092 ERROR [STDERR] at
java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1031)
12:38:20,092 ERROR [STDERR] at
java.util.TreeMap$KeyIterator.next(TreeMap.java:1058)
12:38:20,092 ERROR [STDERR] at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoP
haseCoordinator.java:211)
12:38:20,092 ERROR [STDERR] at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinat
or.java:88)
12:38:20,092 ERROR [STDERR] at
com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
12:38:20,092 ERROR [STDERR] at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitA
ndDisassociate(TransactionImple.java:1204)
12:38:20,112 ERROR [STDERR] at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(B
aseTransaction.java:134)
12:38:20,112 ERROR [STDERR] at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransacti
onManagerDelegate.java:87)
12:38:20,112 ERROR [STDERR] at
org.jboss.test.cmp2.ageout.test.JDBC2PmAgeOutUnitTestCase.commitTx(JDBC2PmA
geOutUnitTestCase.java:236)
19 years, 2 months
MDB integration tests
by Tim Fox
I'm trying to locate the MDB integration tests.
I have found a few in jboss-head/testsuite/src/main/org/jboss/test/mdb
which test using the old JMSContainerInvoker.
Although I am not sure whether they are worthy of being called
integration tests since test coverage is shockingly poor. Note the comment:
/**
* Some simple tests of MDB. These could be much more elaborated.
*
* In the future at least the following tests should be done some how:
* <ol>
* <li>Queue
* <li>Topic
* <li>Durable topic
* <li>Bean TX - with AUTO_ACK and DUPS_OK
* <li>CMT Required
* <li>CMT NotSupported
* <li>Selector
* <li>User and password login
* <li>Al the stuff with the context
* </ol>
I am also trying to find the equivalent tests which test using JCA1.5
message inflow, but I can't find any.
I guess they must be somewhere.
Can someone point me in the right direction?
--
Tim Fox
JBoss Messaging Technical Lead
JBoss - a division of Red Hat
T: +44 2088006768
M: +44 7957983205
E: tim.fox(a)jboss.com tim.fox(a)redhat.com
19 years, 2 months
