August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3716) Upgrade JAXB to 2.2.5.jboss-2 for bug fixes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3716?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3716: ----------------------------------------------- Navin Surtani <nsurtani(a)redhat.com> changed the Status of [bug 1127326|https://bugzilla.redhat.com/show_bug.cgi?id=1127326] from NEW to ASSIGNED > Upgrade JAXB to 2.2.5.jboss-2 for bug fixes > ------------------------------------------- > > Key: WFLY-3716 > URL: https://issues.jboss.org/browse/WFLY-3716 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Paul Gier > Assignee: Paul Gier > > Upgrade jaxb to 2.2.5.jboss-2 to include some bug fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-575) Missing maps accessors in IdentityPlaceholderResolverStrategy

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-575?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-575. -------------------------------- Fix Version/s: 6.2.0.Beta2 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/df0e7c6b1 > Missing maps accessors in IdentityPlaceholderResolverStrategy > -------------------------------------------------------------- > > Key: DROOLS-575 > URL: https://issues.jboss.org/browse/DROOLS-575 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.Beta2 > > > IdentityPlaceholderResolverStrategy misses the accessors to at least one of the 2 maps it uses. In fact when you want to unmarshall a KieSession you need to initialize that strategy with the maps produced during the marshalling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-575) Missing maps accessors in IdentityPlaceholderResolverStrategy

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-575: ---------------------------------- Summary: Missing maps accessors in IdentityPlaceholderResolverStrategy Key: DROOLS-575 URL: https://issues.jboss.org/browse/DROOLS-575 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco IdentityPlaceholderResolverStrategy misses the accessors to at least one of the 2 maps it uses. In fact when you want to unmarshall a KieSession you need to initialize that strategy with the maps produced during the marshalling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1208) Eclipse plugin update for IronJacamar 1.2

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1208?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1208: --------------------------- Description: Differences between resource_adapters_1_1.xsd and resource_adapters_1_2.xsd are: * Boolean 'connectable' attribute added: "Defines if external components can obtain a connection through the IronJacamar SPI if supported by the resource adapter" * Boolean 'tracking' attribute added: "Defines if IronJacamar should track connection handles across transaction boundaries" * Boolean 'validate-on-match' element added: "indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set." > Eclipse plugin update for IronJacamar 1.2 > ----------------------------------------- > > Key: JBJCA-1208 > URL: https://issues.jboss.org/browse/JBJCA-1208 > Project: IronJacamar > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Eclipse > Reporter: Lin Gao > Assignee: Lin Gao > > Differences between resource_adapters_1_1.xsd and resource_adapters_1_2.xsd are: > * Boolean 'connectable' attribute added: "Defines if external components can obtain a connection through the IronJacamar SPI if supported by the resource adapter" > * Boolean 'tracking' attribute added: "Defines if IronJacamar should track connection handles across transaction boundaries" > * Boolean 'validate-on-match' element added: "indicates whether or not connection level validation should be done when a connection factory attempts to match a managed connection for a given set." -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3619) XA END / un-enlist for database connection called to early

by Rob Heine (JIRA)

[ https://issues.jboss.org/browse/WFLY-3619?page=com.atlassian.jira.plugin.... ] Rob Heine commented on WFLY-3619: --------------------------------- [~scottmarlow] Let me know, if you need any further information. > XA END / un-enlist for database connection called to early > ---------------------------------------------------------- > > Key: WFLY-3619 > URL: https://issues.jboss.org/browse/WFLY-3619 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, JCA, JPA / Hibernate, Transactions > Affects Versions: 8.0.0.Final > Environment: Windows 7 64-bit > JDK 1.8.0_05-b13 64-Bit > MS SQL Server 2012 database > Latest MS JDBC driver > XA datasource > Reporter: Andreas Liebscher > Assignee: Scott Marlow > Priority: Blocker > Attachments: server-9.0.0.Alpha1-SNAPHOT-trace.log, server-9.0.0.Alpha1-SNAPHOT.log, server.jca.log, server_MSSQL_Trace.log > > > While trying to port an EE application from JBoss5 to WF8 the following problem occurred: > EJBs (@Required) using JPA to do some data changes. > Some changes get already written to the database, others reside in the session cache. > After the top EJB call returns, a Hibernate Session flush is triggered in beforeCompletion. > Then more changes are flushed to the database, but I run in a reproduceable database locking problem. > After some time an update of a row fails with lock wait timeout. This row has been inserted prior during the EJB call. > There should be exactly one xa transaction active processing all data changes. > But the database shows two active session, one is an xa transaction with sessionId -2 (orphaned), the other session is a local transaction. > After analyzing all database communication with the help of the JDBC driver logging I found the following behaviour: > - a connection is enlisted and xa start called > - the same connection is used for several select / insert / update statements > - after return of the top EJB call on the same connection xa end and connection un-enlist is called > - the same connection is used for session flush (beforeCompletion) but with local transaction because the connection is no longer associated with the xa transaction, so locks can be expected. > Shouldn't xa end be called AFTER beforeCompletion / session flush!?! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3619) XA END / un-enlist for database connection called to early

by Rob Heine (JIRA)

[ https://issues.jboss.org/browse/WFLY-3619?page=com.atlassian.jira.plugin.... ] Rob Heine updated WFLY-3619: ---------------------------- Attachment: server-9.0.0.Alpha1-SNAPHOT-trace.log Segment from server.log (taken from WildFly-9.0.0.Alpha1) with loglevel trace for: org.jboss.jca, org.jboss.jpa, org.hibernate, com.arjuna > XA END / un-enlist for database connection called to early > ---------------------------------------------------------- > > Key: WFLY-3619 > URL: https://issues.jboss.org/browse/WFLY-3619 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, JCA, JPA / Hibernate, Transactions > Affects Versions: 8.0.0.Final > Environment: Windows 7 64-bit > JDK 1.8.0_05-b13 64-Bit > MS SQL Server 2012 database > Latest MS JDBC driver > XA datasource > Reporter: Andreas Liebscher > Assignee: Scott Marlow > Priority: Blocker > Attachments: server-9.0.0.Alpha1-SNAPHOT-trace.log, server-9.0.0.Alpha1-SNAPHOT.log, server.jca.log, server_MSSQL_Trace.log > > > While trying to port an EE application from JBoss5 to WF8 the following problem occurred: > EJBs (@Required) using JPA to do some data changes. > Some changes get already written to the database, others reside in the session cache. > After the top EJB call returns, a Hibernate Session flush is triggered in beforeCompletion. > Then more changes are flushed to the database, but I run in a reproduceable database locking problem. > After some time an update of a row fails with lock wait timeout. This row has been inserted prior during the EJB call. > There should be exactly one xa transaction active processing all data changes. > But the database shows two active session, one is an xa transaction with sessionId -2 (orphaned), the other session is a local transaction. > After analyzing all database communication with the help of the JDBC driver logging I found the following behaviour: > - a connection is enlisted and xa start called > - the same connection is used for several select / insert / update statements > - after return of the top EJB call on the same connection xa end and connection un-enlist is called > - the same connection is used for session flush (beforeCompletion) but with local transaction because the connection is no longer associated with the xa transaction, so locks can be expected. > Shouldn't xa end be called AFTER beforeCompletion / session flush!?! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1208) Eclipse plugin update for IronJacamar 1.2

by Lin Gao (JIRA)

Lin Gao created JBJCA-1208: ------------------------------ Summary: Eclipse plugin update for IronJacamar 1.2 Key: JBJCA-1208 URL: https://issues.jboss.org/browse/JBJCA-1208 Project: IronJacamar Issue Type: Task Security Level: Public (Everyone can see) Components: Eclipse Reporter: Lin Gao Assignee: Lin Gao -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3619) XA END / un-enlist for database connection called to early

by Rob Heine (JIRA)

[ https://issues.jboss.org/browse/WFLY-3619?page=com.atlassian.jira.plugin.... ] Rob Heine updated WFLY-3619: ---------------------------- Attachment: server-9.0.0.Alpha1-SNAPHOT.log Error thrown in WildFly-9.0.0.Alpha1-SNAPSHOT > XA END / un-enlist for database connection called to early > ---------------------------------------------------------- > > Key: WFLY-3619 > URL: https://issues.jboss.org/browse/WFLY-3619 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, JCA, JPA / Hibernate, Transactions > Affects Versions: 8.0.0.Final > Environment: Windows 7 64-bit > JDK 1.8.0_05-b13 64-Bit > MS SQL Server 2012 database > Latest MS JDBC driver > XA datasource > Reporter: Andreas Liebscher > Assignee: Scott Marlow > Priority: Blocker > Attachments: server-9.0.0.Alpha1-SNAPHOT.log, server.jca.log, server_MSSQL_Trace.log > > > While trying to port an EE application from JBoss5 to WF8 the following problem occurred: > EJBs (@Required) using JPA to do some data changes. > Some changes get already written to the database, others reside in the session cache. > After the top EJB call returns, a Hibernate Session flush is triggered in beforeCompletion. > Then more changes are flushed to the database, but I run in a reproduceable database locking problem. > After some time an update of a row fails with lock wait timeout. This row has been inserted prior during the EJB call. > There should be exactly one xa transaction active processing all data changes. > But the database shows two active session, one is an xa transaction with sessionId -2 (orphaned), the other session is a local transaction. > After analyzing all database communication with the help of the JDBC driver logging I found the following behaviour: > - a connection is enlisted and xa start called > - the same connection is used for several select / insert / update statements > - after return of the top EJB call on the same connection xa end and connection un-enlist is called > - the same connection is used for session flush (beforeCompletion) but with local transaction because the connection is no longer associated with the xa transaction, so locks can be expected. > Shouldn't xa end be called AFTER beforeCompletion / session flush!?! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2752) Using an injected UriInfo object by the JAX-RS runtime environment does not work

by Christian Nedregård (JIRA)

[ https://issues.jboss.org/browse/WFLY-2752?page=com.atlassian.jira.plugin.... ] Christian Nedregård commented on WFLY-2752: ------------------------------------------- We had the same problem in 8.1.0. For us this proved to be related to the fact that Wildfly will treat all JAX-RS beans as CDI beans by default: WFLY-2859. [CdiPropertyInjector|http://grepcode.com/file/repository.jboss.org/nexus/c...] will only perform @Context field and method injection on "non-CDI beans" and since all JAX-RS beans are treated as CDI beans by default this means no such injection is performed. Fix was to add require-bean-descriptor="true" to server config as described in the first comment of WFLY-2859. > Using an injected UriInfo object by the JAX-RS runtime environment does not work > -------------------------------------------------------------------------------- > > Key: WFLY-2752 > URL: https://issues.jboss.org/browse/WFLY-2752 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Affects Versions: 8.0.0.CR1 > Environment: Linux Fedora > Reporter: Stan Zelivinski > Assignee: Bill Burke > > The code that works perfectly in WildFly.8.0.0.Beta: > package jdsu.vts.tcpcontroller.webservices.rest.resources; > import java.net.URI; > import javax.ws.rs.DELETE; > import javax.ws.rs.GET; > import javax.ws.rs.PUT; > import javax.ws.rs.Path; > import javax.ws.rs.PathParam; > import javax.ws.rs.Produces; > import javax.ws.rs.Consumes; > import javax.ws.rs.core.Context; > import javax.ws.rs.core.Response; > import javax.ws.rs.core.UriInfo; > import jdsu.vts.tcpcontroller.webservices.rest.application.V1_TCPController; > import jdsu.vts.shared.transferobjects.V1_TCPSetups; > @Path("/v1") > public class V1_TCPControllerResource { > @Context UriInfo uriInfo; > > @GET > @Produces("application/json") > /** > * > * @return > */ > public Response getControllers() { > > //String json = String.valueOf(m_testsMap.size()); > return Response.ok(V1_TCPController.getCollection()).build(); > } > > @PUT > @Path("{id}") > @Produces("application/json") > public Response addController(@PathParam("id") String id){ > > V1_TCPController controller = V1_TCPController.find(id); > if(controller != null) { > return Response.status(Response.Status.CONFLICT).build(); > } > > controller = new V1_TCPController(id); > > URI uri = uriInfo.getAbsolutePathBuilder().path(id).build(); > > return Response.created(uri).build(); > } > } > does not work in WildFly.8.0.0.CR1. uriInfo is null in the call. > Please help. > Stan -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3716) Upgrade JAXB to 2.2.5.jboss-2 for bug fixes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3716?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3716: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1127327|https://bugzilla.redhat.com/show_bug.cgi?id=1127327] from NEW to POST > Upgrade JAXB to 2.2.5.jboss-2 for bug fixes > ------------------------------------------- > > Key: WFLY-3716 > URL: https://issues.jboss.org/browse/WFLY-3716 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Paul Gier > Assignee: Paul Gier > > Upgrade jaxb to 2.2.5.jboss-2 to include some bug fixes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
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 August 2014