You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Jeffery Painter <je...@jivecast.com> on 2018/10/03 14:07:22 UTC
fulcrum updates and problems
Hi guys,
Working to insure fulcrum is building OK in jdk 8... all components seem
OK except I am getting two test failures in fulcrum/cache related to the
JCSCacheTest. This is outside my realm of expertise, but I am happy to
dig deeper if you have any pointers. All other fulcrum components seem
relatively happy.
I tried to update fulcrum/security/torque to see what the state of it
looks like when using torque-4.1-SNAPSHOT, and I am getting a series of
test failures where it tells me that the jdbc connection is closed on
each test for the HsqlDb object. I tried to dig into that one also, but
had no luck figuring out where things went wrong.
I figured my time was better spent making sure everything is working
properly in jdk-8 first before attempting to get it working in java
9,10,11, etc.
--
Jeff
Tests run: 10, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 142.003
sec <<< FAILURE! - in org.apache.fulcrum.cache.JCSCacheTest
test2ObjectAddGetCachedObject(org.apache.fulcrum.cache.JCSCacheTest)
Time elapsed: 0.019 sec <<< ERROR!
org.apache.fulcrum.cache.ObjectExpiredException
at
org.apache.fulcrum.cache.impl.JCSCacheService.getObject(JCSCacheService.java:189)
at
org.apache.fulcrum.cache.CacheTest.test2ObjectAddGetCachedObject(CacheTest.java:153)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:99)
at
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:136)
at
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:109)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
testObjectCount(org.apache.fulcrum.cache.JCSCacheTest) Time elapsed:
18.345 sec <<< FAILURE!
junit.framework.AssertionFailedError: After three refreshes expected:<0>
but was:<1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:201)
at
org.apache.fulcrum.cache.CacheTest.testObjectCount(CacheTest.java:299)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:99)
at
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:136)
at
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:109)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Results :
Failed tests:
org.apache.fulcrum.cache.JCSCacheTest#testObjectCount
AssertionFailedError Aft...
Tests in error:
org.apache.fulcrum.cache.EHCacheTest#test2ObjectAddGetCachedObject
ObjectExpiredException
org.apache.fulcrum.cache.JCSCacheTest#test2ObjectAddGetCachedObject
ObjectExpiredException
Tests run: 30, Failures: 1, Errors: 2, Skipped: 0
Re: fulcrum updates and problems
Posted by Jeffery Painter <je...@jivecast.com>.
Sounds good... I have been updating references to fulcrum and turbine
with torque-4.1 - everything compiles ok, but there are a lot of test
failures in fulcrum-security-torque I am trying to figure out. I think
the issue has more to do with talking to HsqlDb than the torque classes
themselves. I will let you know if I am able to make it work today.
Also, I think I recall that Georg was moving the maven archetypes out to
git so that is probably why I am not able to update the svn there. I
need to go back and re-read his emails on that :-)
--
Jeff
On 10/05/2018 12:02 PM, Thomas Vandahl wrote:
> Hi Jeff,
>
> On 10/4/18 9:13 PM, Jeffery Painter wrote:
>> Finally, I am not sure how much work is involved to update to torque-4.1
>> (or when it will be released), but so far all is still working fine with
>> torque-4.0
> I was planning to add some kind of streaming support and then leave it
> at that. I'm literally practicing my Java8 skills there...
>
>> I was fortunate to have a couple days of downtime, so I dug back in. I
>> was inspired again after attending ApacheCon NA last week. Even though
>> my talk was not accepted, I did a lighting talk "Apache Turbine Isn't
>> Dead" - I got some great comments after, but I did hear from a number of
>> people that they thought it was dead :-/
>>
>> If you want to watch my talk, it is posted here:
>> https://www.youtube.com/watch?v=FTROCvmhXko
> Just watched it. Great stuff. Thanks so much, buddy. I really appreciate it.
>
> Bye, Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
Re: fulcrum updates and problems
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Jeff,
On 10/4/18 9:13 PM, Jeffery Painter wrote:
> Finally, I am not sure how much work is involved to update to torque-4.1
> (or when it will be released), but so far all is still working fine with
> torque-4.0
I was planning to add some kind of streaming support and then leave it
at that. I'm literally practicing my Java8 skills there...
> I was fortunate to have a couple days of downtime, so I dug back in. I
> was inspired again after attending ApacheCon NA last week. Even though
> my talk was not accepted, I did a lighting talk "Apache Turbine Isn't
> Dead" - I got some great comments after, but I did hear from a number of
> people that they thought it was dead :-/
>
> If you want to watch my talk, it is posted here:
> https://www.youtube.com/watch?v=FTROCvmhXko
Just watched it. Great stuff. Thanks so much, buddy. I really appreciate it.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: fulcrum updates and problems
Posted by Jeffery Painter <je...@jivecast.com>.
My pleasure .... and I agree with marking the components. I was working
hard to track down what matters, but then ultimately it was easier to
just start updating everything :-)
And I haven't used the XMLRPC service since around 2003 when I had to
talk to an old piece of software to deliver shipping labels. ha! I have
no use for it now though.
Happy to report I just migrated a fairly large app to the turbine-5.0
code base with pretty minimal effort. The main things to watch out for
was to make sure all configuration was updated to commons-configuration2
and the changes to Part/FileItem I sent to the user list. Other than
that, it seems to be working like a charm!
I also just pushed another set of changes to github to update the mysql
database driver to latest (8.0.12). The only real issue I ran into
there was the additional parameter required for setting the
serverTimezone - I made this a configuration on the archetype when
setting up a new project (and set UTC as default).
Finally, I am not sure how much work is involved to update to torque-4.1
(or when it will be released), but so far all is still working fine with
torque-4.0
I was fortunate to have a couple days of downtime, so I dug back in. I
was inspired again after attending ApacheCon NA last week. Even though
my talk was not accepted, I did a lighting talk "Apache Turbine Isn't
Dead" - I got some great comments after, but I did hear from a number of
people that they thought it was dead :-/
If you want to watch my talk, it is posted here:
https://www.youtube.com/watch?v=FTROCvmhXko
My part starts around 16:55
--
Jeff
On 10/04/2018 02:36 PM, Thomas Vandahl wrote:
> On 03.10.18 16:07, Jeffery Painter wrote:
>> I figured my time was better spent making sure everything is working
>> properly in jdk-8 first before attempting to get it working in java
>> 9,10,11, etc.
> Great stuff, Jeff. Thanks for taking the time.
>
> I guess we should define what the status of all the Fulcrum modules is
> going to be. Some of them are plain dead (know someone who uses
> XMLRPC?), others purposes are at least questionable (configuration,
> cache). In Commons, components are put into the categories "proper",
> "sandbox" and "dormant". I propose to establish something similar here.
>
> Bye, Thomas
>
Re: fulcrum updates and problems
Posted by Thomas Vandahl <tv...@apache.org>.
On 03.10.18 16:07, Jeffery Painter wrote:
> I figured my time was better spent making sure everything is working
> properly in jdk-8 first before attempting to get it working in java
> 9,10,11, etc.
Great stuff, Jeff. Thanks for taking the time.
I guess we should define what the status of all the Fulcrum modules is
going to be. Some of them are plain dead (know someone who uses
XMLRPC?), others purposes are at least questionable (configuration,
cache). In Commons, components are put into the categories "proper",
"sandbox" and "dormant". I propose to establish something similar here.
Bye, Thomas