Go to 26 or whatever the latest on the 2.4 branch is. There is nothing
special about 23.
----- Original Message -----
From: Julian Gosnell
To: [EMAIL PROTECTED]
Sent: Wednesday, August 08, 2001 7:16 AM
Subject: [JBoss-dev] 2.4.0.23 or 26 ??? was -
jbosstest/2.4.0/flushAuthenticationCache problem....
I just tried this on a freshly updated 2.4 jboss
branch (now reporting itself as Rel_2_4_0_26 and it
seems quite happy.
So I guess this is just a change between 2.4.0.23 and
26 and that jboss and jbosstest are in synch.
Should I stick with 23 for my forthcoming release - or
go for a 26 ?
Anyone feel strongly ?
Is there any particular reason why 2.4.0.23 was chosen
as a release point and that I should stick with this
and not go to 2.4.0.26 ?
Thanks,
Jules
--- Julian Gosnell <[EMAIL PROTECTED]> wrote: >
on running the web integration tests in jbosstest
> against 2.4.0.23_BETA and the 2.4 branch from CVS
> integrated with the latest Jetty I am getting a
> nasty
> :
>
> run-testcase:
> [junit] Running
> org.jboss.test.web.test.TestWebIntegration
> [junit] Found warDeployer named: :service=Jetty
> [junit] Deploying: jbosstest-web.ear...Done
> [junit] javax.management.ReflectionException:
> The
> operation with name flushAuthenticationCache could
> not
> be found
> [junit] at
>
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC
all.java:245)
> [junit] No war deployer found, skipping tests
> [junit] Tests run: 8, Failures: 0, Errors: 0,
> Time
> elapsed: 6.099 sec
> [junit] at
>
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
> [junit] at
>
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
> [junit] at
>
org.jboss.jmx.server.RMIConnectorImpl_Stub.invoke(Unknown
> Source)
> [junit] at
>
org.jboss.test.web.test.TestWebIntegration.setUp(TestWebIntegration.java:83)
> [junit] at
> junit.framework.TestCase.runBare(TestCase.java:127)
> [junit] at
>
junit.framework.TestResult$1.protect(TestResult.java:100)
> [junit] at
>
junit.framework.TestResult.runProtected(TestResult.java:117)
> [junit] at
> junit.framework.TestResult.run(TestResult.java:103)
> [junit] at
> junit.framework.TestCase.run(TestCase.java:120)
> [junit] at
> junit.framework.TestSuite.run(TestSuite.java:144)
> [junit] at
> junit.framework.TestSuite.run(TestSuite.java:144)
> [junit] at
>
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRu
nner.java:209)
> [junit] at
>
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestR
unner.java:342)
>
>
> I think this has happened in jbosstest underneath
> me.
> Perhaps this is a HEAD-ism that hasn't been
> completely
> patched into 2.4. I have run it with an older
> JBoss/Jetty with the same result....
>
> I'm preparing for a new JBoss/Jetty release and
> would
> be grateful if someone could confirm that this is
> not
> my problem......
>
>
>
> Cheers Guys,
>
>
> Jules
>
>
>
____________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.co.uk address at
> http://mail.yahoo.co.uk
> or your free @yahoo.ie address at
> http://mail.yahoo.ie
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
>
http://lists.sourceforge.net/lists/listinfo/jboss-development
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
