[JBoss JIRA] Created: (JBAS-8398) Injection metadata validation on deploy-time is too aggressive
by Toshiya Kobayashi (JIRA)
Injection metadata validation on deploy-time is too aggressive
--------------------------------------------------------------
Key: JBAS-8398
URL: https://jira.jboss.org/browse/JBAS-8398
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers, Web (Tomcat) service
Affects Versions: 6.0.0.M4, JBossAS-5.1.0.GA
Reporter: Toshiya Kobayashi
Assignee: Ales Justin
If your war file includes Pojo whose field is annotated with @Resource, deployer throws Exception below:
2010-09-09 00:51:45,460 ERROR [org.apache.catalina.core.StandardContext] (main) Context [/simple1] startup failed due to previous errors
java.lang.RuntimeException: mapped-name is required for com.example.ResourceBean/obj of deployment simple1.war
at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXmlResourceEnvRefs(WebResourceHandler.java:287)
at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXml(WebResourceHandler.java:325)
at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:550)
at org.jboss.web.tomcat.service.WebCtxLoader.start(WebCtxLoader.java:158)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4272)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
Scanning is ok, but validation is too aggressive.
In JBoss AS 4, such @Resource usage is allowed and it can be utilized by Spring etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JGRP-1232) GossipRouter.stop() call to GossipRouter.clear() is ignored due to GossipRouter.running
by Scott Marlow (JIRA)
GossipRouter.stop() call to GossipRouter.clear() is ignored due to GossipRouter.running
---------------------------------------------------------------------------------------
Key: JGRP-1232
URL: https://jira.jboss.org/browse/JGRP-1232
Project: JGroups
Issue Type: Bug
Affects Versions: 2.10
Reporter: Scott Marlow
Assignee: Scott Marlow
Came across this while working on Infinispan integration into AS 6. One of the AS test cases (integration branch view http://anonsvn.jboss.org/repos/jbossas/branches/infinispan-int/testsuite/...) is starting a gossip router for testing (with two members). After testing a few things, we stop the gossip router. We then test to see if the group membership (via AS cluster partition abstraction) has been updated). It is expected that each AS node will see one member in their view but they still see two (which triggers a failure).
Anyway, while looking into the above, I noticed that GossipRouter.stop invokes GossipRouter.clear but only after setting GossipRouter.running = false. GossipRouter.clear will not close the client connections as a result. Perhaps we should have GossipRouter.stop + GossipRouter.clear both call an internal clear that is unguarded (e.g. let the public methods guard against GossipRouter.running being false).
As a short term workaround for the above unit test failure, I changed DRMTestCase to call GossipRouter.clear() before GossipRouter.stop().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months