[ 
https://issues.apache.org/jira/browse/GEODE-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108670#comment-17108670
 ] 

ASF GitHub Bot commented on GEODE-8096:
---------------------------------------

nabarunnag merged pull request #5119:
URL: https://github.com/apache/geode/pull/5119


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> redeployingParentClassDoesNotCauseSubclassIncompatibilities encounters 
> ClassNotFoundException exception
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-8096
>                 URL: https://issues.apache.org/jira/browse/GEODE-8096
>             Project: Geode
>          Issue Type: Bug
>          Components: serialization
>            Reporter: Bill Burcham
>            Assignee: Nabarun Nag
>            Priority: Major
>              Labels: caching-applications
>
> JUnit test failed in this CI run: 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/134#A
> {code}
> org.apache.geode.internal.ClassPathLoaderJUnitTest > 
> redeployingParentClassDoesNotCauseSubclassIncompatibilities FAILED
>     java.lang.ClassNotFoundException: jddunit.function.classB
>         at 
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:186)
>         at 
> org.apache.geode.internal.ClassPathLoader$1.loadClass(ClassPathLoader.java:366)
>         at 
> org.apache.geode.internal.ClassPathLoaderJUnitTest.redeployingParentClassDoesNotCauseSubclassIncompatibilities(ClassPathLoaderJUnitTest.java:242)
> {code}
> I ran it 100 times in IntelliJ with no failures. On the theory that maybe we 
> ran out of disk I visually traced through the paths dealing w/ (jar) files 
> and didn't see anywhere where the product might have been swallowing 
> exceptions. So I don't know what went wrong.
> Marked component as serialization because this is testing loading a Jar file 
> that redefines a class which was the base class (of a derived class) loaded 
> previously from a different jar file. Seems like the point of all that is 
> mainly to support users updating their jar files without restarting their 
> JVMs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to