July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1460) WildFly server fails to start with transactions configured to be run with JDBCObject store

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1460?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1460: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 971358|https://bugzilla.redhat.com/show_bug.cgi?id=971358] > WildFly server fails to start with transactions configured to be run with JDBCObject store > ------------------------------------------------------------------------------------------ > > Key: WFLY-1460 > URL: https://issues.jboss.org/browse/WFLY-1460 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.0.0.Alpha1 > Reporter: Ondřej Chaloupka > Assignee: Stefano Maestri > > In case that you configure transactions subsystem for running with JDBCObject store the app server fails to start because of (it seems so) a circular dependency. > You can expect the exception like: > {code} > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 52) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "transactions")]): org.jboss.msc.service.CircularDependencyException: Container jboss-as has a circular dependency: [service jboss.txn.ArjunaObjectStoreEnvironment, service jboss.txn.ArjunaRecoveryManager, service jboss.connector.transactionintegration, service jboss.cached-connection-manager, service jboss.data-source.java:jboss/datasources/JDBCObjectDS] > {code} > My assumption came from the configuration similar to this: > {code} > <datasource jta="false" jndi-name="java:jboss/datasources/JDBCObjectDS" pool-name="JDBCObjectDS" enabled="true" use-ccm="false"> > <connection-url>jdbc:postgresql://postgresserver.com:5432/user1</connection-url> > <driver-class>org.postgresql.Driver</driver-class> > <driver>postgresql-9.2-1002.jdbc4.jar</driver> > <security> > <user-name>user1</user-name> > <password>user1</password> > </security> > </datasource> > {code} > and the transaction config looks like this > {code} > <jdbc-store datasource-jndi-name="java:jboss/datasources/JDBCObjectDS" /> > {code} -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1779) Build switch for choosing the Analytics provider doesn't work

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1779?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-1779: ------------------------------ Summary: Build switch for choosing the Analytics provider doesn't work (was: Build switch for chosing the Analtytics provider doesn't work) > Build switch for choosing the Analytics provider doesn't work > ------------------------------------------------------------- > > Key: WFLY-1779 > URL: https://issues.jboss.org/browse/WFLY-1779 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Priority: Critical > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-592) Pluggable policy for picking coordinator

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.s... ] Bela Ban commented on JGRP-592: ------------------------------- Actually, I take the above statement back :-) We can leave the basic tenet in place: the first element of the membership is always the coordinator ! We only make the way the *membership is computed* pluggable. This needs to be done in 2 places: * When the coordinator determines the new membership * When the coordinator is suspected and the next-in-line participant needs to determine whether it will become the new coordinator We also need to make the computation of the new MergeView in Merger.MergeTask.run() pluggable > Pluggable policy for picking coordinator > ---------------------------------------- > > Key: JGRP-592 > URL: https://issues.jboss.org/browse/JGRP-592 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4 > > > Make policy to pick coordinator pluggable. Pick new coordinator after existing coordinator crashes by calling this policy. > Default policy is to pick the next in line. > Other policies could pick the next in line from a set of pinned coordinator, so certain members can never become coordinators. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1780) Port EL performance fixes to EL 3.0 impl

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-1780: ------------------------------------ Summary: Port EL performance fixes to EL 3.0 impl Key: WFLY-1780 URL: https://issues.jboss.org/browse/WFLY-1780 Project: WildFly Issue Type: Task Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1779) Build switch for chosing the Analtytics provider doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1779?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1779: ----------------------------------------------- Heiko Braun <hbraun(a)redhat.com> made a comment on [bug 989549|https://bugzilla.redhat.com/show_bug.cgi?id=989549] A bug in the build environment enabled thos feature, although it should be turned off in the product builds. We fix it in the next version, however in the meantime, Google Analytics can be turned in the console settings: "Settings>Analytics Enabled" > Build switch for chosing the Analtytics provider doesn't work > ------------------------------------------------------------- > > Key: WFLY-1779 > URL: https://issues.jboss.org/browse/WFLY-1779 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Priority: Critical > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1779) Build switch for chosing the Analtytics provider doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1779?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1779: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989549 > Build switch for chosing the Analtytics provider doesn't work > ------------------------------------------------------------- > > Key: WFLY-1779 > URL: https://issues.jboss.org/browse/WFLY-1779 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Priority: Critical > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1779) Build switch for chosing the Analtytics provider doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1779?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1779: ----------------------------------------------- Heiko Braun <hbraun(a)redhat.com> made a comment on [bug 989549|https://bugzilla.redhat.com/show_bug.cgi?id=989549] Confirmed. > Build switch for chosing the Analtytics provider doesn't work > ------------------------------------------------------------- > > Key: WFLY-1779 > URL: https://issues.jboss.org/browse/WFLY-1779 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Priority: Critical > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1779) Build switch for chosing the Analtytics provider doesn't work

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1779: --------------------------------- Summary: Build switch for chosing the Analtytics provider doesn't work Key: WFLY-1779 URL: https://issues.jboss.org/browse/WFLY-1779 Project: WildFly Issue Type: Bug Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Priority: Critical -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1496) @Transactional doesn't work

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1496?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-1496: ------------------------------------------ Paul, I replaced all JARs of IronJacamar with those of version 1.1.0.CR2, but get the following errors in server.log. I'd recommend to upgrade IronJacamar in the near future, and I'll test it with my web app asap. {code} WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER {code} > @Transactional doesn't work > --------------------------- > > Key: WFLY-1496 > URL: https://issues.jboss.org/browse/WFLY-1496 > Project: WildFly > Issue Type: Bug > Components: JCA, Transactions > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Stefano Maestri > Attachments: testcase-WFLY-1496.zip > > > I just tried the WildFly Alpha 2 snapshot containing Narayana 5.0.0.M3 and get the error message below. The classes causing the error are: > @Path("/bestellungen") > @Produces({ APPLICATION_JSON, APPLICATION_XML }) > //@RequestScoped is default for JAX-RS > @Transactional > public class BestellungResource { > @Inject > private BestellungService bs; > ... > } > @Transactional(TxType.MANDATORY) > public class BestellungServiceImpl implements Serializable { > private static final long serialVersionUID = ...L; > > @PersistenceContext > private transient EntityManager em; > // method invoking JPA / Hibernate > } > The fragment of server.log: > 15:11:43,254 DEBUG [org.hibernate.SQL] > /* named HQL query Bestellung.findKundeById */ select > distinct abstractku1_.id as id2_8_, > abstractku1_.aktualisiert as aktualis3_8_, > abstractku1_.bemerkungen as bemerkun4_8_, > abstractku1_.email as email5_8_, > abstractku1_.erzeugt as erzeugt6_8_, > abstractku1_.file_fk as file18_8_, > abstractku1_.kategorie as kategori7_8_, > abstractku1_.nachname as nachname8_8_, > abstractku1_.newsletter as newslett9_8_, > abstractku1_.password as passwor10_8_, > abstractku1_.rabatt as rabatt11_8_, > abstractku1_.seit as seit12_8_, > abstractku1_.umsatz as umsatz13_8_, > abstractku1_.version as version14_8_, > abstractku1_.vorname as vorname15_8_, > abstractku1_.familienstand_fk as familie16_8_, > abstractku1_.geschlecht_fk as geschle17_8_, > abstractku1_.art as art1_8_ > from > Bestellung bestellung0_ > inner join > kunde abstractku1_ > on bestellung0_.kunde_fk=abstractku1_.id > where > bestellung0_.id=? > 15:11:43,254 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null > 15:11:43,254 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] UserTransaction is not available within the scope of a bean or method annotated with @Transactional and a Transactional.TxType other than NOT_SUPPORTED or NEVER -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1778) Web Console: Deal with isolated read-only attibutes

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1778: --------------------------------- Summary: Web Console: Deal with isolated read-only attibutes Key: WFLY-1778 URL: https://issues.jboss.org/browse/WFLY-1778 Project: WildFly Issue Type: Feature Request Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun In some cases single attributes may be read-only. We need to treat them similar to sensitive attributes, just that the values will not be blanked. -- 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

12 years, 11 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 July 2013