[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
[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
[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
[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}
<!-- user creates a new cache container without specifying default-cache. -->
/subsystem=infinispan/cache-container=X:add
<!-- for top-level cache container attributes, user sets them via write-attribute -->
/subsystem=infinispan/cache-container=X:write-attribute(name=jndi-name,value=W)
<!-- for nested nested cache-container attributes, user access them as an addressable resource and sets them via write-attribute -->
/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)
<!-- When user is ready to start the cache-container, prompt for default-cache if not set. -->
<!-- Then do these two as a batch -->
/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
[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