[JBoss JIRA] (AS7-6441) Transaction automatically started for MDB even though it uses BMT
by Justin Bertram (JIRA)
[ https://issues.jboss.org/browse/AS7-6441?page=com.atlassian.jira.plugin.s... ]
Justin Bertram updated AS7-6441:
--------------------------------
Description:
When an MDB uses BMT a transaction is still begun when onMessage() is invoked. This is because org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent#isDeliveryTransacted doesn't check whether or not the MDB is using BMT.
You can workaround this issue by using CMT with NOT_SUPPORTED.
was:When an MDB uses BMT a transaction is still begun when onMessage() is invoked. This is because org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent#isDeliveryTransacted doesn't check whether or not the MDB is using BMT.
> Transaction automatically started for MDB even though it uses BMT
> -----------------------------------------------------------------
>
> Key: AS7-6441
> URL: https://issues.jboss.org/browse/AS7-6441
> Project: Application Server 7
> Issue Type: Feature Request
> Components: EJB
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Justin Bertram
> Assignee: jaikiran pai
>
> When an MDB uses BMT a transaction is still begun when onMessage() is invoked. This is because org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent#isDeliveryTransacted doesn't check whether or not the MDB is using BMT.
> You can workaround this issue by using CMT with NOT_SUPPORTED.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6441) Transaction automatically started for MDB even though it uses BMT
by Justin Bertram (JIRA)
Justin Bertram created AS7-6441:
-----------------------------------
Summary: Transaction automatically started for MDB even though it uses BMT
Key: AS7-6441
URL: https://issues.jboss.org/browse/AS7-6441
Project: Application Server 7
Issue Type: Feature Request
Components: EJB
Affects Versions: 7.1.3.Final (EAP)
Reporter: Justin Bertram
Assignee: jaikiran pai
When an MDB uses BMT a transaction is still begun when onMessage() is invoked. This is because org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent#isDeliveryTransacted doesn't check whether or not the MDB is using BMT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6216) Some javax.* bundles show version 0.0.0 in AS7
by Paul Gier (JIRA)
[ https://issues.jboss.org/browse/AS7-6216?page=com.atlassian.jira.plugin.s... ]
Paul Gier updated AS7-6216:
---------------------------
Assignee: Cheng Fang (was: Paul Gier)
> Some javax.* bundles show version 0.0.0 in AS7
> ----------------------------------------------
>
> Key: AS7-6216
> URL: https://issues.jboss.org/browse/AS7-6216
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Reporter: Thomas Diesler
> Assignee: Cheng Fang
> Fix For: 7.2.0.CR1
>
>
> Some javax bundles that we configure by default do not show valid bundle version info
> javax.jws.api:0.0.0
> javax.ws.rs.api:0.0.0
> The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this
> {code}
> Bundle-SymbolicName: hibernate-jpa-2.0-api
> Bundle-Version: 1.0.1.Final
> Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0"
> {code}
> This should be replaced by metadata coming from the artefacts manifest.
> Generally, all javax api artefacts should have valid OSGi metadata
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-430) DomainController discovery system
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/AS7-430?page=com.atlassian.jira.plugin.sy... ]
Farah Juma commented on AS7-430:
--------------------------------
Created a new pull request: https://github.com/jbossas/jboss-as/pull/3982
Static discovery options are now configured using the <static-discovery> element and S3 discovery options are configured using the generic <discovery-option> element:
{code:xml}
<discovery-options>
<static-discovery name="option-one" host="172.16.81.100" port="9999"/>
<discovery-option name="option-two" code="org.jboss.as.host.controller.discovery.S3Discovery">
<property name="access-key" value="s3_access_key"/>
<property name="secret-access-key" value="s3_secret_access_key"/>
<property name="location" value="s3_bucket_name"/>
</discovery-option>
</discovery-options>
{code}
> DomainController discovery system
> ---------------------------------
>
> Key: AS7-430
> URL: https://issues.jboss.org/browse/AS7-430
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Farah Juma
> Fix For: 7.3.0.Alpha1
>
>
> Mechanism(s) by which a Host Controller finds a Domain Controller so it can begin the process of integrating into the domain.
> Task includes the host.xml schema elements to configure this, the domain object model classes behind those elements, and the actual implementation of discovery from both the ServerManager and DomainController sides.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] (AS7-6440) EmbeddedDeployableContainer should support multiple module paths
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-6440:
-------------------------------------
Summary: EmbeddedDeployableContainer should support multiple module paths
Key: AS7-6440
URL: https://issues.jboss.org/browse/AS7-6440
Project: Application Server 7
Issue Type: Bug
Reporter: Galder Zamarreño
AS7 Arquillian EmbeddedDeployableContainer is making the wrong assumptions about the module path. The module path can be made out of several paths separated with a ':'. The following module path fails to start with Embedded container:
{code}/var/folders/vk/g4jts68n6nd37lgvynmtrwxh0000gn/T/test-module:./build/target/jboss-as/modules:./build/target/jboss-as/thirdparty-modules{code}
It fails with:
{code}java.lang.IllegalStateException: Invalid modules directory: /var/folders/vk/g4jts68n6nd37lgvynmtrwxh0000gn/T/test-module:./build/target/jboss-as/modules:./build/target/jboss-as/thirdparty-modules
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setupModuleLoader(EmbeddedDeployableContainer.java:89)
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setup(EmbeddedDeployableContainer.java:65)
at org.jboss.as.arquillian.container.embedded.EmbeddedDeployableContainer.setup(EmbeddedDeployableContainer.java:40)
at org.jboss.arquillian.container.impl.ContainerImpl.setup(ContainerImpl.java:180){code}
The same path works without problems with the Managed Container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months