April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-672) Nexus index of "Public JBoss Repository Group" and "Public Repository Group" is out of date

by Bruno Hernandes (JIRA)

Nexus index of "Public JBoss Repository Group" and "Public Repository Group" is out of date ------------------------------------------------------------------------------------------- Key: JBBUILD-672 URL: https://issues.jboss.org/browse/JBBUILD-672 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Affects Versions: Repository Support 2010, Maven Repository Nexus Rollout Reporter: Bruno Hernandes The latest update of Nexus index for "Public JBoss Repository Group" and "Public Repository Group" was on October, 8th, 2010. See: * [https://repository.jboss.org/nexus/content/groups/public/.index/nexus-mav...] * [https://repository.jboss.org/nexus/content/groups/public-jboss/.index/nex...] So newer artifacts like {{infinispan-core-4.2.1.CR3.jar}} cant be found by any index search oriented engine, like the Dependency Selection feature of m2eclipse plugin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7922) MDB transaction still commits when EJB container is not started, resulting in undelivered messages being ACK'd

by Robert West (JIRA)

MDB transaction still commits when EJB container is not started, resulting in undelivered messages being ACK'd -------------------------------------------------------------------------------------------------------------- Key: JBAS-7922 URL: https://jira.jboss.org/jira/browse/JBAS-7922 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: Version info: JBoss 5.1.0 GA (we use a local build, and have updated JBoss Cache to 3.2.1.GA, JBossTS to 4.6.1.GA_CP03 and JGroups to 2.6.13.GA to pick up bug fixes for issues we have encountered in production) ActiveMQ 5.3.0 GA HornetQ 2.0.0 GA Java 1.6.0_17 Mac OS 10.6.2 Reporter: Robert West Assignee: Carlo de Wolf Priority: Critical Testing scenario: Deployed JBoss 5.1.0.GA (with tweaks to the pom during build, see Environment) with a JCA adapter for an external JMS broker, used both ActiveMQ 5.3.0 and HornetQ 2.0.0, both clustered and standalone. Also tried an embedded HornetQ broker with the same results. Deployed an ear that has a simple MDB requiring container managed transactions listening to a queue with max sessions set to 2 and a simple jsp to publish an arbitrary number of text messages to that queue. The MDB simply prints the text information provided by the message, but also has a hard-coded 1 second pause for every even numbered message. When I shut down JBoss while messages are still being consumed, the BlockContainerShutdownInterceptor starts throwing DispatcherConnectExceptions, as the EJB container has been stopped or is in the process of being stopped. However, it doesn't mark the transaction for rollback itself, and MessageInflowLocalProxy.delivery() only marks the transaction for rollback if the invocation chain throws an Error or RuntimeException. Thus, in this case, JBoss failed to deliver the message to the MDB, but committed the transaction. According to the spec, for an MDB with a container managed transaction, the message should be ACK'd to the broker if the transaction successfully commits, and both the ActiveMQ and HornetQ JCA implementations dutifully do this, resulting in all messages that were attempted to be delivered after the EJB container shutdown being lost. When the BlockContainerShutdownInterceptor detects that the EJB container has been shutdown, it needs to take an action that will ensure the transaction is marked for rollback. After parsing through the code involved in the interceptor chain, I can see a few potential solutions: * Have BlockContainerShutdownInterceptor.invoke() call TxUtil.getTransactionManager().setRollbackOnly() before it would throw a DispatcherConnectException. Probably need to consume any exception thrown from setRollbackOnly() and log it first I suppose, although it's always a bit odd when you get an exception thrown when you intend to throw an exception anyway for a different reason. * Have BlockContainerShutdownInterceptor.invoke() put some state on the Invocation to indicate that delivery is being blocked. MessagingContainer.localInvoke() could then take some action based on this state to ensure the transaction is rolled back, either rolling it back itself or notifying its caller that the transaction should be rolled back. A bit odd here if BlockContainerShutdownInterceptor.invoke() continues to throw an exception, as there would be data about the exception being passed back outside the exception though. * Have MessageInflowLocalProxy handle DispatcherConnectExceptions. It might be better to introduce an additional class, say InvocationInterruptedException that DispatcherConnectException could extend, to allow for the possibility that invocations may be interrupted for other reasons, allowing MessageInflowLocalProxy to not care as much about the particular reason invocation was halted, but still be able to roll back the transaction whenever it is. I slightly favor the third approach based on what I've seen of that portion of the code so far, so I will probably work to put together a patch file along those lines. This is the first time I've delved deeply into the JBoss source code though. If I can find some examples of test cases in this part of the code base, I'll attempt to put together a verifying test case as well. I marked the priority as Critical, based on the guidelines, as this is resulting in data loss and as far as I best understand the spec is a violation of the spec. -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-9233) injection of persistence context into Hibernate session is not working

by Scott Marlow (JIRA)

injection of persistence context into Hibernate session is not working ---------------------------------------------------------------------- Key: JBAS-9233 URL: https://issues.jboss.org/browse/JBAS-9233 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Scott Marlow Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-9200) JPA service names should begin with a description of the service

by Scott Marlow (JIRA)

JPA service names should begin with a description of the service ---------------------------------------------------------------- Key: JBAS-9200 URL: https://issues.jboss.org/browse/JBAS-9200 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Priority: Minor Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWEB-107) Cross Domain JSESSIONID Cookie

by Mike Millson (JIRA)

Cross Domain JSESSIONID Cookie ------------------------------ Key: JBWEB-107 URL: http://jira.jboss.com/jira/browse/JBWEB-107 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Mike Millson Assigned To: Mladen Turk Currently the JSESSIONID cookie domain is set to the domain name of the Host that emits the cookie (e.g. www.domain.com). This is an issue with customers using Aliases (e.g. secure.domain.com, zzz.domain.com, etc.), as the session is lost when switching between the main domain and any aliases. In these cases, it would be useful to be able to specify the domain to be "domain.com" so the same JSESSIONID cookie is used across the aliases and converges to the same session. -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-9235) @ConcurrencyManagement type BEAN on a singleton EJB leads to deployment exception

by jaikiran pai (JIRA)

@ConcurrencyManagement type BEAN on a singleton EJB leads to deployment exception --------------------------------------------------------------------------------- Key: JBAS-9235 URL: https://issues.jboss.org/browse/JBAS-9235 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 7.0.0.Beta2 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.0.Beta3 A singleton EJB with BEAN concurrency management leads to: {code} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected concurrency management type: BEAN on bean SingletonBean at org.jboss.as.ejb3.deployment.processors.ConcurrencyManagementAnnotationProcessor.processAnnotations(ConcurrencyManagementAnnotationProcessor.java:87) at org.jboss.as.ejb3.deployment.processors.ConcurrencyManagementAnnotationProcessor.processAnnotations(ConcurrencyManagementAnnotationProcessor.java:46) at org.jboss.as.ejb3.deployment.processors.AbstractAnnotationEJBProcessor.processComponentConfig(AbstractAnnotationEJBProcessor.java:54) at org.jboss.as.ee.component.AbstractComponentConfigProcessor.deploy(AbstractComponentConfigProcessor.java:53) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more {code} The ConcurrencyManagementAnnotationProcessor is missing a "break" statement in the switch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2242) Allow embedded usage in failsafe and surefire plugin

by Carlo de Wolf (JIRA)

Allow embedded usage in failsafe and surefire plugin ---------------------------------------------------- Key: EJBTHREE-2242 URL: https://issues.jboss.org/browse/EJBTHREE-2242 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Because AS 6 doesn't shutdown cleanly a test must always be forked off. This has the implication that java.class.path does not reflect the true class path, instead surefire.test.class.path must be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2083) Create "embedded" component for EJB 3.1 EJBContainer implementation

by Andrew Lee Rubinger (JIRA)

Create "embedded" component for EJB 3.1 EJBContainer implementation ------------------------------------------------------------------- Key: EJBTHREE-2083 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2083 Project: EJB 3.0 Issue Type: Feature Request Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Start porting in local development towards the EJB 3.1 Embedded container support. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1999) Create "embedded" component

by Andrew Lee Rubinger (JIRA)

Create "embedded" component --------------------------- Key: EJBTHREE-1999 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1999 Project: EJB 3.0 Issue Type: Task Components: embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Create a component w/ SPI/API, build, and impl modules to house the E-EJB3 configuration -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8963) Inject Persistence Context into Hibernate session

by Scott Marlow (JIRA)

Inject Persistence Context into Hibernate session ------------------------------------------------- Key: JBAS-8963 URL: https://issues.jboss.org/browse/JBAS-8963 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott Marlow This will probably use unwrap and should be independent of Hibernate, so that other PersistenceProvider classes can also be handled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011