[JBoss JIRA] Created: (JBAS-9012) Eliminate the threads subsystem
by David Lloyd (JIRA)
Eliminate the threads subsystem
-------------------------------
Key: JBAS-9012
URL: https://issues.jboss.org/browse/JBAS-9012
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: 7.0.0.CR1
The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models.
Subtasks for affected subsystems.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-9355) EJBs contained in an EAR are not accessible to WARs in the same EAR
by Fred Bricon (JIRA)
EJBs contained in an EAR are not accessible to WARs in the same EAR
-------------------------------------------------------------------
Key: JBAS-9355
URL: https://issues.jboss.org/browse/JBAS-9355
Project: JBoss Application Server
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: EE, EJB
Affects Versions: 7.0.0.Beta2
Environment: Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Default locale: fr_FR, platform encoding: UTF-8
OS name: "linux", version: "2.6.35.12-88.fc14.x86_64", arch: "amd64", family: "unix"
Reporter: Fred Bricon
Attachments: demo-ear.ear
In order to test m2eclipse-wtp, I usually use the multi-javaee5-archetype (mvn archetype:generate -DarchetypeCatalog=http://open-archetypes.googlecode.com/svn/snapshots-repository/archetype-catalog.xml) to create an EAR containing an EJB jar and a WAR referencing said EJB.
The generated EAR deploys and runs on JBoss AS 5, 6, Glassfish 3.x but fails on deploying in JBoss AS 7 :
{noformat} Caused by: java.lang.ClassNotFoundException: foo.bar.demo.ejb.HelloService from [Module "deployment.demo-ear.ear.demo-web-0.0.1-SNAPSHOT.war:main" from Service Module Loader]{noformat}
It seems AS 7 strictly enforces the EE spec :
{quote}
(15:26:40) dmlloyd: EE.8.3.2
(15:27:01) dmlloyd: portable applications must not depend on having or not having access to these classes or resources: The content of any EJB jar files included in the same ear file.
{quote}
I guess it would be practical if EJBs inside an EAR were still available to WARs from the same EAR, from a migration point of view first, and it would also allow projects to be deployed using m2eclipse-wtp/jboss tools out of the box :-D
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-8780) "No original methods found" error when deploying EJBs that extend base classes
by Richard Kennard (JIRA)
"No original methods found" error when deploying EJBs that extend base classes
------------------------------------------------------------------------------
Key: JBAS-8780
URL: https://issues.jboss.org/browse/JBAS-8780
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.Final
Reporter: Richard Kennard
Assignee: Ales Justin
Priority: Critical
An error, new to JBoss 6 (works okay in JBoss 5.1.0)...
"java.lang.IllegalStateException: No original methods found"
...halts deployment when you try to deploy an EJB that subclasses a base class with public methods.
For example, if you have a base class 'PersistentEntityBean' that has a bunch of methods related to loading/saving/deleting, and then you extend that base class with 'EmployerBean' simply to override loading/saving (but without adding any extra methods), it will fail to deploy.
A workaround (from the forum) appears to be to override *every* subclassed method and just call 'super'. However this error even occurs for public final methods, which clearly cannot be overridden.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (AS7-910) Error with signed jars during deployment
by Joshua Wulf (JIRA)
Error with signed jars during deployment
----------------------------------------
Key: AS7-910
URL: https://issues.jboss.org/browse/AS7-910
Project: Application Server 7
Issue Type: Bug
Reporter: Joshua Wulf
Assignee: Stuart Douglas
13:40:20,345 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."TopicIndex.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TopicIndex.war".INSTALL: Failed to process phase INSTALL of deployment "TopicIndex.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.jboss.classfilewriter.ClassFile.define(ClassFile.java:284)
at org.jboss.classfilewriter.ClassFile.define(ClassFile.java:255)
at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:154)
at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:118)
at org.jboss.as.ee.component.ViewConfiguration.addViewInterceptorToFront(ViewConfiguration.java:194)
at org.jboss.as.ejb3.component.stateful.StatefulComponentDescription$2.configure(StatefulComponentDescription.java:106)
at org.jboss.as.ee.component.ComponentDescription$DefaultFirstConfigurator.configure(ComponentDescription.java:661)
at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 4 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22]
at org.jboss.classfilewriter.ClassFile.define(ClassFile.java:279)
... 12 more
Caused by: java.lang.SecurityException: class "org.jboss.seam.transaction.LocalEjbSynchronizations$$$view1"'s signer information does not match signer information of other classes in the same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:787) [:1.6.0_22]
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:502) [:1.6.0_22]
at java.lang.ClassLoader.defineClass(ClassLoader.java:628) [:1.6.0_22]
at java.lang.ClassLoader.defineClass(ClassLoader.java:480) [:1.6.0_22]
... 17 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (AS7-896) @Resource of type enum fail with "Can't handle @Resource for ENC name"
by jaikiran pai (JIRA)
@Resource of type enum fail with "Can't handle @Resource for ENC name"
----------------------------------------------------------------------
Key: AS7-896
URL: https://issues.jboss.org/browse/AS7-896
Project: Application Server 7
Issue Type: Bug
Components: EE
Reporter: jaikiran pai
Assignee: jaikiran pai
A @Resource on a enum type field leads to:
{code}
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Can't handle @Resource for ENC name: timeUnit since it's missing a lookup value and isn't of any known type
at org.jboss.as.ee.component.ResourceInjectionAnnotationParsingProcessor.process(ResourceInjectionAnnotationParsingProcessor.java:216)
at org.jboss.as.ee.component.ResourceInjectionAnnotationParsingProcessor.processMethodResource(ResourceInjectionAnnotationParsingProcessor.java:173)
at org.jboss.as.ee.component.ResourceInjectionAnnotationParsingProcessor.deploy(ResourceInjectionAnnotationParsingProcessor.java:124)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT]
... 4 more
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month