[JBoss JIRA] Created: (JBAS-4083) Ejb timers fire before the ear completely deploys
by Vadim Kopichenko (JIRA)
Ejb timers fire before the ear completely deploys
-------------------------------------------------
Key: JBAS-4083
URL: http://jira.jboss.com/jira/browse/JBAS-4083
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2, Scheduling/Timers
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Environment: WinNT, Sun JDK 1.5
Reporter: Vadim Kopichenko
Assigned To: Scott M Stark
Consider the following usecase.
The is an ear containing several ejb modules.
One of them has a ejb2.1 timed cmp entity bean.
If the timer associated with the bean fires during application deployment unexpected errors happen, cause other beans could be not already deployed.
This breaks application logic.
The problem happens both while server starts/stops and while hot ear's redeployment.
It would be much better if timers began to fire after the application had completely deployed.
I've also experienced a similar problem with undeployment.
Timer code was executed about a half of second after the undeployment had begun. Several ejb modules had been already undeployed by that moment.
I guess that timer actually fired exactly before the undeployment had begun but the ejbTimeout executed later due to threads syncronization issue.
Please, try also to investigate if this can be avoided.
PS
Some kind of patch or workaround for 4.0.5 (or even a hint about how this can be fixed) would be greatly appreciated.
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBRULES-1732) Put the permission list into the session.
by chuan wu (JIRA)
Put the permission list into the session.
------------------------------------------
Key: JBRULES-1732
URL: https://jira.jboss.org/jira/browse/JBRULES-1732
Project: JBoss Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: chuan wu
Assignee: Mark Proctor
Need to work out where to store the List<RoleBasePermission>'s - in
the session or whatever. In any case, it should be ONE list for all
permissions, not a separate one for categories and packages.
- one possibility is to create a Seam component that encapsulates
this list - you can then declaritively set its lifecycle to session,
and then it can be got from the Seam context from anywhere without
having to worry if it is in the session, or if it is cached etc - it
just gets that component which returns a list of perms.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBMETA-94) @Resource injection for SessionContext is expecting a mapped-name
by Andrew Lee Rubinger (JIRA)
@Resource injection for SessionContext is expecting a mapped-name
-----------------------------------------------------------------
Key: JBMETA-94
URL: https://jira.jboss.org/jira/browse/JBMETA-94
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta35
Reporter: Andrew Lee Rubinger
Assignee: Alexey Loubyansky
Priority: Blocker
Source is:
@Resource
public void setSessionContext(SessionContext sc) {
sctx = sc;
}
jboss-metadata populates ResourceEnvironmentReferenceMetaData properly, given that there's no mapped-name.
However, EJB3 Module in AS has error:
java.lang.RuntimeException: mapped-name is required for sessionContext of deployment someEjbTest
at org.jboss.ejb3.client.ClientResourceHandler.loadXmlResourceEnvRefs(ClientResourceHandler.java:181)
at org.jboss.ejb3.client.ClientResourceHandler.loadXml(ClientResourceHandler.java:212)
at org.jboss.ejb3.client.ClientContainer.processMetadata(ClientContainer.java:341)
at org.jboss.ejb3.client.ClientContainer.<init>(ClientContainer.java:123)
at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:83)
at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:184)
at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:177)
This is a regression; was some code removed which populates mapped-name, given that the injection target is javax.ejb.SessionContext?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (EJBTHREE-1455) EJB References are getting mapped to Business Default Interface, not Interface-Specific
by Andrew Lee Rubinger (JIRA)
EJB References are getting mapped to Business Default Interface, not Interface-Specific
---------------------------------------------------------------------------------------
Key: EJBTHREE-1455
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1455
Project: EJB 3.0
Issue Type: Bug
Components: core
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
>From EJBRemoteHandler:
protected void ejbRefXml(AbstractEJBReferenceMetaData ref, String interfaceName, InjectionContainer container, String errorType)
{
String encName = "env/" + ref.getEjbRefName();
InjectionUtil.injectionTarget(encName, ref, container, container.getEncInjections());
if (container.getEncInjectors().containsKey(encName))
return;
String mappedName = ref.getMappedName();
if (mappedName != null && mappedName.equals(""))
mappedName = null;
if(mappedName == null && ref.getResolvedJndiName() != null)
mappedName = ref.getResolvedJndiName();
.....
}
mappedName becomes "stateless_sessioncontext_descriptor/SessionContextBean/local", when in JNDI this does not have the requisite interface-specific information associated with it:
+- stateful_sessioncontext_descriptor (class: org.jnp.interfaces.NamingContext)
| +- AcceptBean (class: org.jnp.interfaces.NamingContext)
| | +- remote-com.sun.ts.tests.ejb30.common.sessioncontext.AcceptIF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.AcceptIF)
| | +- local (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.AcceptLocalIF)
| | +- local-com.sun.ts.tests.ejb30.common.sessioncontext.AcceptLocalIF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.AcceptLocalIF)
| +- SessionContextBean (class: org.jnp.interfaces.NamingContext)
| | +- local (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal2IF, com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal1IF)
| | +- remote-com.sun.ts.tests.ejb30.common.sessioncontext.Three2IF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.Three2IF)
| | +- local-com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal2IF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal2IF)
| | +- localHome (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.TwoLocalHome)
| | +- remote-com.sun.ts.tests.ejb30.common.sessioncontext.Three1IF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.Three1IF)
| | +- local-com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal1IF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.ThreeLocal1IF)
| +- TestBean (class: org.jnp.interfaces.NamingContext)
| | +- remote-com.sun.ts.tests.ejb30.common.sessioncontext.TestIF (class: Proxy for: com.sun.ts.tests.ejb30.common.sessioncontext.TestIF)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months