[JBoss JIRA] Created: (JBMETA-41) EJBTHREE-1127 processing
by Scott M Stark (JIRA)
EJBTHREE-1127 processing
------------------------
Key: JBMETA-41
URL: http://jira.jboss.com/jira/browse/JBMETA-41
Project: JBoss Metadata
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta15
Reporter: Scott M Stark
Assigned To: Alexey Loubyansky
Fix For: 1.0.0.CR1
Another annotation processing example is:
@RemoteHome
public interface RemoteHome extends EJBHome
{
public RemoteInterface1 create();
public RemoteInterface2 create2();
}
The above example defines 2 EJB2.x Remote interfaces, even though they're not explicitly marked as such anywhere.
That's EJBTHREE-1127, defined by, "EJB3 Core Specification 3.6.2.1":
The return type of a create method on the remote home interface is the session bean's remote interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Created: (JBAS-5593) EJB2 ProxyFactoryHA has unbalanced lifecycle
by Brian Stansberry (JIRA)
EJB2 ProxyFactoryHA has unbalanced lifecycle
--------------------------------------------
Key: JBAS-5593
URL: http://jira.jboss.com/jira/browse/JBAS-5593
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, EJB2
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Sets stuff up in setupInvokers(), which is called as part of start(). Tears it down in destroy(). Effect is a start()/stop()/start() fails:
2008-06-05 14:19:20,752 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(5)-127.0.0.1) Error installing to Start: name=jboss.j2ee:jndiName=nextgen_StatefulSession,service=EJB state=Create mode=Manual requiredState=Installed
java.lang.IllegalStateException: Trying to register target using an existing hashCode.
at org.jboss.invocation.unified.server.UnifiedInvokerHA.registerBean(UnifiedInvokerHA.java:75)
at org.jboss.proxy.ejb.ProxyFactoryHA.setupInvokers(ProxyFactoryHA.java:119)
at org.jboss.proxy.ejb.ProxyFactory.start(ProxyFactory.java:238)
at org.jboss.proxy.ejb.ProxyFactoryHA.start(ProxyFactoryHA.java:101)
at org.jboss.ejb.SessionContainer.startInvokers(SessionContainer.java:440)
at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:398)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
The destroy() work needs to be moved to stop().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Created: (EJBTHREE-1018) ClassCastException on concurrent EJB3 method invocation from different beans
by Michael Pfeiffer (JIRA)
ClassCastException on concurrent EJB3 method invocation from different beans
----------------------------------------------------------------------------
Key: EJBTHREE-1018
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1018
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA
Environment: Java: JDK 1.5.0_11
Eclipse: SDK 3.2.2
Reporter: Michael Pfeiffer
Two different EJB3 stateless session beans A and B packaged into separate EAR files deployed on the same JBoss instance
invoke a method of another stateless session bean C on another JBoss instance that returns an object of a user
defined class Value.
There seems to be a multi-threading issue.
Sometimes when both beans concurrently call the method of C an ClassCastException Value is thrown within the remote
interface proxy before the result object is returned to the calling bean.
The class Value and the remote interface for C are packaged into a JAR file within each EAR file inside a "lib" folder.
If this JAR file is deployed instead and not packaged into the EAR files of bean A and B everything works fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month