[JBoss JIRA] Updated: (JBPM-1445) The jBPM 'websale' sample application fails
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1445?page=com.atlassian.jira.plug... ]
Alejandro Guizar updated JBPM-1445:
-----------------------------------
Assignee: (was: Alejandro Guizar)
Unassigning issues on which I won't work in the near term.
> The jBPM 'websale' sample application fails
> --------------------------------------------
>
> Key: JBPM-1445
> URL: https://jira.jboss.org/jira/browse/JBPM-1445
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Engine
> Environment: JBoss Developer Studio
> Build id: 1.0.0.GA
> SOA-P GA
> /opt/GA/soa-4.2.0.GA.zip
> /opt/GA/standalone-soa-4.2.0.GA.zip
> RHEL5
> Linux ldimaggi.csb 2.6.18-53.1.13.el5 #1 SMP Mon Feb 11 13:27:52 EST 2008 i686 i686 i386 GNU/Linux
> Sun Java 1.5
> java version "1.5.0_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode)
> RDBMS
> H2, version: 1.0.66 (2008-01-18)
> CPU
> cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 13
> model name : Intel(R) Pentium(R) M processor 1.70GHz
> stepping : 6
> cpu MHz : 1700.000
> cache size : 2048 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2
> bogomips : 3398.35
> Reporter: Len DiMaggio
> Fix For: SOA 4.2 CP03, SOA 4.3
>
> Attachments: Screenshot-1.png, server.log, server.log, server.log.gz
>
>
> The jBPM 'websale' sample application fails - when an order is approved (OK is selected). This exception is displayed back to the user:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> Closing the database context failed: An exception of type org.jbpm.JbpmException was thrown, with the message: problem closing services {persistence=org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifies user managed transactions}
> The server.log is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Resolved: (JBPM-1619) Wrong JNDI lookup to java:comp/env space in non-EJB enterprise components
by Alejandro Guizar (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1619?page=com.atlassian.jira.plug... ]
Alejandro Guizar resolved JBPM-1619.
------------------------------------
Resolution: Won't Fix
Martin, please reopen if you encounter problems with the EAP.
> Wrong JNDI lookup to java:comp/env space in non-EJB enterprise components
> -------------------------------------------------------------------------
>
> Key: JBPM-1619
> URL: https://jira.jboss.org/jira/browse/JBPM-1619
> Project: JBoss jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Engine
> Affects Versions: jBPM 3.2.3
> Reporter: Martin Putz
> Assignee: Alejandro Guizar
> Attachments: JBPM-1619.patch
>
>
> The following components of the enterprise archive attempt to make a lookup from their local JNDI environment at java:comp/env:
> - org.jbpm.msg.jms.JmsMessageServiceFactoryImpl
> - org.jbpm.scheduler.ejbtimer.EjbSchedulerServiceFactory
> - org.jbpm.scheduler.ejbtimer.EntitySchedulerServiceFactory
> As these components are no EJB's, they have no local JNDI environment. The lookup should use the In-VM space by default (eg. java:/JmsXA), and it should be possible to override the lookup locations through jbpm.cfg.xml (see JBPM-960).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Created: (JBPM-1712) ERROR Error in named query: GraphSession.findTokensForProcessInNode: Invalid path: 'node.name'
by Martin Putz (JIRA)
ERROR Error in named query: GraphSession.findTokensForProcessInNode: Invalid path: 'node.name'
----------------------------------------------------------------------------------------------
Key: JBPM-1712
URL: https://jira.jboss.org/jira/browse/JBPM-1712
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.3, SOA 4.2 CP02
Reporter: Martin Putz
org/jbpm/db/hibernate.queries.hbm.xml:
<query name="GraphSession.findTokensForProcessInNode">
<![CDATA[
select token
from org.jbpm.graph.exe.Token token
where token.processInstance.processDefinition.name = :processDefinitionName
and node.name = :nodeName
]]>
</query>
throws org.hibernate.hql.ast.QuerySyntaxException: Invalid path: 'node.name' b/c 'node' isn't defined.
Looking at org.jbpm.command.BatchSignalCommand (the only class using this named query), I guess it should rather be
and token.node.name = :nodeName
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months