February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1663) An extended persistence context should not be propagated if there is no JTA transaction

by Scott Marlow (JIRA)

An extended persistence context should not be propagated if there is no JTA transaction --------------------------------------------------------------------------------------- Key: AS7-1663 URL: https://issues.jboss.org/browse/AS7-1663 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Affects Versions: 7.0.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.2.Final JPA 2.0 specification section 7.6.3.1 Requirements for Persistence Context Propagation: " Persistence contexts are propagated by the container across component invocations as follows. If a component is called and there is no JTA transaction or the JTA transaction is not propagated, the persistence context is not propagated. " For the case of a SFSB (with an extended persistence context XPC) method that is not in a JTA transaction, invoking a SLSB (with a transactional entity manager PC) method that requires a transaction. The SLSB method should not use the extended persistence context but should instead start a new persistence context instead for the duration of the SLSB transaction (will end at the method end). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] (AS7-3658) NPE when starting a hornetQ backup server

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-3658: ---------------------------------------- Summary: NPE when starting a hornetQ backup server Key: AS7-3658 URL: https://issues.jboss.org/browse/AS7-3658 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Emanuel Muckenhuber Assignee: Andy Taylor Fix For: 7.1.1.Final When configuring a <hornetq-server /> with <backup>true</backup> - the service fails to start: {code} 17:45:00,446 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.messaging.backup-server.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging.backup-server.jms.manager: java.lang.NullPointerException at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:80) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: java.lang.NullPointerException at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:74) ... 5 more {code} This affects e.g. docs/examples/configs/standalone-hornetq-colocated.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
7
0 / 0

[JBoss JIRA] (JBRULES-3315) Remove drools-grip from spring

by Mark Proctor (Created) (JIRA)

Remove drools-grip from spring ------------------------------ Key: JBRULES-3315 URL: https://issues.jboss.org/browse/JBRULES-3315 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor As the grid work is only partially working and causes complexity in the release process for drools-spring, we have decided to remove drools-grip from spring for now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
22
0 / 0

[JBoss JIRA] (JBRULES-3375) Adding ProcessEventListener throws NPE

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3375: ------------------------------------ Summary: Adding ProcessEventListener throws NPE Key: JBRULES-3375 URL: https://issues.jboss.org/browse/JBRULES-3375 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Description of problem: When you try to add a ProcessEventListener to StatefulKnowledgeSession and you are missing jBPM libraries on classpath, you get a NullPointerException. Version-Release number of selected component (if applicable): BRMS-5.3.0.dev5 Drools-5.3.0.Final How reproducible: Using attached reproducer. Steps to Reproduce: 1. Make sure you don't have any jBPM libs on classpath 2. Create stateful session 3. Add ProcesEventListener (e.g. DebugProcessEventListener) Actual results: java.lang.NullPointerException at org.drools.impl.StatefulKnowledgeSessionImpl.addEventListener(StatefulKnowledgeSessionImpl.java:199) at org.sample.TryProcessListener.main(TryProcessListener.java:20) Expected results: Either meaningful exception (like NojBPMException) or correct addition of listener Additional info: It only affects StatefulKnowledgeSession, the StatefulKnowledgeSession runs just fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (AS7-1815) Provide management use cases and operations for the remoting subsystem

by Heiko Braun (JIRA)

Provide management use cases and operations for the remoting subsystem ---------------------------------------------------------------------- Key: AS7-1815 URL: https://issues.jboss.org/browse/AS7-1815 Project: Application Server 7 Issue Type: Feature Request Components: Remoting Reporter: Heiko Braun Assignee: David Lloyd Fix For: 7.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
9
0 / 0

[JBoss JIRA] (AS7-3488) Make default-cache attribute of cache-container "eventually required" rather than required.

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-3488: ---------------------------------------- Summary: Make default-cache attribute of cache-container "eventually required" rather than required. Key: AS7-3488 URL: https://issues.jboss.org/browse/AS7-3488 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Fix For: 7.1.0.Final Can we remove the restriction that default-cache must be set when you create the cache-container? That way, I can just make it so the UI forces them to set that value before calling the start operation. So under that covers, the console does this: {noformat}  /subsystem=infinispan/cache-container=X:add  /subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)  /subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=stack, value=udp) /subsystem=infinispan/cache-container=X/transport=TRANSPORT:write-attribute(name=lock-timeout, value=100)   /subsystem=infinispan/cache-container=X:write-attribute(name=default-cache, value=Y) /subsystem=infinispan/cache-container=X:start(mode=on-demand) {noformat} Any thoughts on this? The answer has great implications on the UI design. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
27
0 / 0

[JBoss JIRA] Created: (JBAS-9026) Create JBoss AS Javadoc aggregate project

by David Lloyd (JIRA)

Create JBoss AS Javadoc aggregate project ----------------------------------------- Key: JBAS-9026 URL: https://issues.jboss.org/browse/JBAS-9026 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: John Casey 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

13 years, 11 months

12
84
0 / 0

[JBoss JIRA] (AS7-2897) Intermittent failures in IIOP tests

by Brian Stansberry (Created) (JIRA)

Intermittent failures in IIOP tests ----------------------------------- Key: AS7-2897 URL: https://issues.jboss.org/browse/AS7-2897 Project: Application Server 7 Issue Type: Bug Components: IIOP Reporter: Brian Stansberry Assignee: Stefan Guilhen Fix For: 7.1.0.CR1 See, for example, 8 of the 10 failures in https://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-7.0.x-git... The same 8 failures occasionally pop up on my local test runs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (AS7-1897) update jasper-jdt

by Jean-Frederic Clere (JIRA)

update jasper-jdt ----------------- Key: AS7-1897 URL: https://issues.jboss.org/browse/AS7-1897 Project: Application Server 7 Issue Type: Bug Components: Web Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere Fix For: 7.1.0.Beta1 the version is still 7.0.0.Beta8 should be the same as org.jboss.web -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
12
0 / 0

[JBoss JIRA] (JBRULES-3328) Add an API to allow access to the constraint occurrences of a solution

by David Glassborow (Created) (JIRA)

Add an API to allow access to the constraint occurrences of a solution ---------------------------------------------------------------------- Key: JBRULES-3328 URL: https://issues.jboss.org/browse/JBRULES-3328 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: FUTURE Reporter: David Glassborow Assignee: Mark Proctor For a given solution, I'd like to show what constraint occurrences are in the working memory, and ideally which occurrences for each planning entity. This allows end users to understand the schedule, in my experience otherwise they stop trusting the system. Currently the demo harness uses an internal API to get this information, and I think it maybe getting the wrong WM, the values looked out of step with the solver last time I looked -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
4
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 February 2012