[jboss-dev] new scanning in AS trunk

Kabir Khan kabir.khan at jboss.com
Tue Jun 8 09:08:57 EDT 2010 

I have upgraded to jboss-aop 2.2.1.Alpha3 and jboss-classpool 1.0.0.Alpha6 along with updates to bootstrap/aop.xml + the classpath in Main.java.

https://jira.jboss.org/browse/JBAS-8081
https://jira.jboss.org/browse/JBAS-8082
https://jira.jboss.org/browse/JBAS-8083

This should fix the following from https://jira.jboss.org/secure/attachment/12334744/jbas8060-test-regressions.txt
======================================================================
Test: org.jboss.test.aop.test.ScopedAnnotatedTestCase(aop-scoped)

2010-06-02 21:19:10,325 DEBUG [org.jboss.aop.asintegration.jboss5.AOPDeploymentAopMetaDataDeployer] (RMI TCP Connection(2)-127.0.0.1) Finished deploying AbstractVFSDeploymentContext at 7879273{vfs:///work/TRUNK/trunk/testsuite/output/lib/aop-scoped-annotated.sar/aop-scoped-annotated.aop/}
2010-06-02 21:19:11,786 DEBUG [org.jboss.scanning.deployers.ScanningDeployer] (RMI TCP Connection(2)-127.0.0.1) Error during deploy: vfs:///work/TRUNK/trunk/testsuite/output/lib/aop-scoped-annotated.sar/aop-scoped-annotated.aop/: java.lang.Error: Error visiting "/work/TRUNK/trunk/testsuite/output/lib/aop-scoped-annotated.sar/aop-scoped-annotated.aop/org/jboss/test/aop/jdk15annotated/NoInterfacesPOJO2.class"
        at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:268) [jboss-classloading-vfs.jar:2.2.0.Alpha5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5]
        at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:102) [jboss-classloading-vfs.jar:2.2.0.Alpha5]
        at org.jboss.deployers.vfs.plugins.classloader.VFSDeploymentClassLoaderPolicyModule.visit(VFSDeploymentClassLoaderPolicyModule.java:181) [:2.2.0.Alpha5]
        at org.jboss.scanning.plugins.DeploymentUnitScanner.scan(DeploymentUnitScanner.java:111) [:1.0.0.Alpha2]
        at org.jboss.scanning.spi.helpers.UrlScanner.scan(UrlScanner.java:96) [:1.0.0.Alpha2]
        at org.jboss.scanning.deployers.ScanningDeployer.deploy(ScanningDeployer.java:90) [:1.0.0.Alpha2]
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha5]
        at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha5]
<snip>
Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException: Null type
        at org.jboss.scanning.plugins.visitor.IgnoreSetErrorHandler.handleError(IgnoreSetErrorHandler.java:57) [:1.0.0.Alpha2]
        at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:91) [:1.0.0.Alpha2]
        at org.jboss.scanning.annotations.plugins.AnnotationsScanningPlugin.visit(AnnotationsScanningPlugin.java:89) [:1.0.0.Alpha2]
        at org.jboss.scanning.spi.helpers.ScanningPluginWrapper.visit(ScanningPluginWrapper.java:112) [:1.0.0.Alpha2]
        at org.jboss.classloading.plugins.visitor.FederatedResourceVisitor.visit(FederatedResourceVisitor.java:101) [jboss-classloading.jar:2.2.0.Alpha5]
        at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:264) [jboss-classloading-vfs.jar:2.2.0.Alpha5]

On 8 Jun 2010, at 10:29, Ales Justin wrote:

> Yeah, my mistake. :-(
> I was too eager to exclude those dirs, that I then forgot about TODO that I put into the xml file.
>                <!-- dirs TODO - fix exact names -->
> 
> I'll see how easy it is to add custom jboss-scanning.xml to those dirs' deployments.
> 
> On Jun 8, 2010, at 8:11 AM, Alessio Soldano wrote:
> 
>> Thanks Brian,
>> this would also solve the issue I mentioned in a comment on JBAS-8060.
>> Cheers
>> Alessio
>> 
>> Brian Stansberry wrote:
>>> Found it; should be easy to fix. Deployments whose names include the 
>>> string "cluster" aren't being scanned.
>>> 
>>> https://jira.jboss.org/browse/JBAS-8076
>>> 
>>> This problem may be the cause of some other failures as well, as 
>>> deployments including the string "hornetq" or "security" in their names 
>>> will have the problem.
>>> 
>>> On 06/07/2010 01:49 PM, Brian Stansberry wrote:
>>> 
>>>> I'll poke into this some more this afternoon and will file a JIRA. I
>>>> suspect it will be easy enough to isolate; there's ZERO logging from any
>>>> EJB3 deployer, so something pretty early in the process must be going wrong.
>>>> 
>>>> On 06/07/2010 12:38 PM, Jaikiran Pai wrote:
>>>> 
>>>>> Is there a JIRA around this one? We are seeing similar clustering
>>>>> deployment failures in our EJB3 build environment. I haven't yet looked
>>>>> into the details to see what exactly causes the issue.
>>>>> 
>>>>> -Jaikiran
>>>>> Brian Stansberry wrote:
>>>>> 
>>>>>> Still fails.
>>>>>> 
>>>>>> I don't think the problem is on the JPA side -- or at least that's not
>>>>>> the obvious surface problem. The persistence unit deployment seems to
>>>>>> go ok.
>>>>>> 
>>>>>> The obvious surface problem is that during the deployment there is no
>>>>>> logging by any EJB3 related deployers. The session beans the test
>>>>>> invokes on are not getting deployed.
>>>>>> 
>>>>>> On 06/03/2010 03:17 PM, Ales Justin wrote:
>>>>>> 
>>>>>>> The JPA has known issues:
>>>>>>> 
>>>>>>> 
>>>>>>>> https://jira.jboss.org/browse/JBJPA-29
>>>>>>>> https://jira.jboss.org/browse/JBAS-8064
>>>>>>>> 
>>>>>>> ALR already fixed this with new jpa.vfs3 release.
>>>>>>> And Shelly just confirmed this now works as expected.
>>>>>>> 
>>>>>>> The new jsp.vfs3 lib is already commited into c-m/pom.xml.
>>>>>>> Can you try it and let us know if this also works for you?
>>>>>>> 
>>>>>>> 
>>>>>>> On Jun 3, 2010, at 10:07 PM, Brian Stansberry wrote:
>>>>>>> 
>>>>>>> 
>>>>>>>> The tests artifacts are jars that all have this structure:
>>>>>>>> 
>>>>>>>> META-INF/
>>>>>>>> ++ MANIFEST.MF (w/ nothing interesting
>>>>>>>> ++ persistence.xml
>>>>>>>> org/blah/...
>>>>>>>> 
>>>>>>>> where some of the classes are entities and some are annotated EJB3
>>>>>>>> session beans. No ejb-jar.xml or jboss.xml.
>>>>>>>> 
>>>>>>>> The testsuite/output/lib/clusteredentity-test.jar is a good example.
>>>>>>>> 
>>>>>>>> In some but not all tests the jar is packaged in an ear along with a
>>>>>>>> datasource.
>>>>>>>> 
>>>>>>>> There's no EJB3 deployer logging, so perhaps the scanning isn't picking
>>>>>>>> up the EJB annotations?
>>>>>>>> 
>>>>>>>> On 06/03/2010 03:01 PM, Brian Stansberry wrote:
>>>>>>>> 
>>>>>>>>> Following this commit (r105574), the tests in the
>>>>>>>>> o.j.t.clustered.clusteredentity package started failing.[1] I
>>>>>>>>> brought an
>>>>>>>>> AS checkout up to the commit before that (r105506) and they pass, but
>>>>>>>>> with the r105574 commit they start failing.
>>>>>>>>> 
>>>>>>>>> The tests deploy ejb3 jars with persistence units included. The tests
>>>>>>>>> are failing because the EJBs are not bound in JNDI. Looking at the
>>>>>>>>> logs
>>>>>>>>> there are no obvious failures during the artifact deployments. But
>>>>>>>>> there's no logging from any EJB3 deployers, just from Hibernate.
>>>>>>>>> 
>>>>>>>>> [1]
>>>>>>>>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSuite-sun16/739/testReport/org.jboss.test.cluster.defaultcfg.clusteredentity.test/
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On 06/02/2010 08:26 AM, Ales Justin wrote:
>>>>>>>>> 
>>>>>>>>>> I've just updated the AS trunk with new Scanning lib.
>>>>>>>>>> It also includes some other MC changes: Reflect, MDR, Kernel, CL,
>>>>>>>>>> Deployers.
>>>>>>>>>> 
>>>>>>>>>> Apart from AnnotationRepository (which was already there with the
>>>>>>>>>> old code),
>>>>>>>>>> I've also hacked around Hibernate's Scanner a bit, so it uses new
>>>>>>>>>> scanning lib's ScannerImpl.
>>>>>>>>>> (the hack is mostly in place due to some impl issues in Hibernate
>>>>>>>>>> itself, Emmanuel is working on it)
>>>>>>>>>> 
>>>>>>>>>> JSF can now use new JBossAnnotationProvider -- let me know how that
>>>>>>>>>> goes Stan.
>>>>>>>>>> And web can use ResourcesIndex from DeploymentUnit -- Remy.
>>>>>>>>>> 
>>>>>>>>>> WeldScanningPlugin is currently commented out.
>>>>>>>>>> We need to disable one of the deployers in plugin's favor.
>>>>>>>>>> Pete, let me know when the new Weld release is coming in,
>>>>>>>>>> and I'll enable the plugin + run a few tests.
>>>>>>>>>> 
>>>>>>>>>> All in all, if you spot any issues / regressions wrt this change,
>>>>>>>>>> let me know, and I'll try to fix the stuff asap.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jboss-development mailing list
>>>>>>>>>> jboss-development at lists.jboss.org
>>>>>>>>>> <mailto:jboss-development at lists.jboss.org>
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>>>>> 
>>>>>>>> --
>>>>>>>> Brian Stansberry
>>>>>>>> Lead, AS Clustering
>>>>>>>> JBoss by Red Hat
>>>>>>>> _______________________________________________
>>>>>>>> jboss-development mailing list
>>>>>>>> jboss-development at lists.jboss.org
>>>>>>>> <mailto:jboss-development at lists.jboss.org>
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>>> 
>>>>>> 
>>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> Alessio Soldano
>> Web Service Lead, JBoss
>> 
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development

More information about the jboss-development mailing list