July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-995) CLONE -concurrent job acquirement fails

by Edward Staub (JIRA)

CLONE -concurrent job acquirement fails --------------------------------------- Key: JBPM-995 URL: http://jira.jboss.com/jira/browse/JBPM-995 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Edward Staub Assigned To: Tom Baeyens when more than 1 job executor thread is configured and concurrent async nodes are to be executed, it results in hibernate exceptions. reason: job acquirement is not synchronized well, resulting in multiple threads trying to work on the same job. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1148) SEAM / JSF / Portlet: Compatibility problem

by JP Barbe (JIRA)

SEAM / JSF / Portlet: Compatibility problem ------------------------------------------- Key: JBPORTAL-1148 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1148 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.CR1 Environment: Windows XP MyFaces 1.1.5 SEAM 1.0.1 Reporter: JP Barbe Assigned To: Julien Viet When I use a seam tag into a jsf page, I have the following exception (You can see config files after the exception): 2006-11-30 17:20:57,934 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seam-desk]] No active conversation context java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.Process.instance(Process.java:32) at org.jboss.seam.core.TaskInstance.instance(TaskInstance.java:51) at org.jboss.seam.contexts.BusinessProcessContext.getTaskInstance(BusinessProcessContext.java:213) at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:51) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:155) at org.jboss.seam.Component.getInstance(Component.java:1245) at org.jboss.seam.Component.getInstance(Component.java:1230) at org.jboss.seam.contexts.Lifecycle.resumeConversation(Lifecycle.java:328) at org.jboss.seam.jsf.AbstractSeamPhaseListener.restoreAnyConversationContext(AbstractSeamPhaseListener.java:42) at org.jboss.seam.jsf.SeamPortletPhaseListener.beforePhase(SeamPortletPhaseListener.java:51) at org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener.beforePhase(SeamExtendedManagedPersistencePortletPhaseListener.java:37) at org.apache.myfaces.lifecycle.LifecycleImpl.informPhaseListenersBefore(LifecycleImpl.java:520) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:342) at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:396) at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) at com.eads.desk.core.portlet.DeskAccessPortlet.doView(DeskAccessPortlet.java:30) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) #### Here is the faces-config.xml file: <faces-config> <lifecycle> <phase-listener> org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener </phase-listener> </lifecycle> <navigation-rule> <from-view-id>/view/deskAccess.jsp</from-view-id> <navigation-case> <from-outcome>trManager</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> <redirect /> </navigation-case> </navigation-rule> <navigation-rule> <navigation-case> <from-action>#{pooledTask.assignToCurrentActor}</from-action> <from-outcome>taskAssignedToActor</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> </navigation-case> </navigation-rule> </faces-config> #### web.xml: <?xml version="1.0" encoding="UTF-8"?> <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">  <listener> <listener-class>org.jboss.seam.servlet.SeamListener</listener-class> </listener> </web-app> ### I have seen an issue (Key: JBSEAM-347) but I don't anderstand the solution proposed or if a solution exists ! (http://jira.jboss.org/jira/browse/JBSEAM-347) Thanks. JP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1498) Add Support for Internet Explorer's Conditional Comments

by Andy Pemberton (JIRA)

Add Support for Internet Explorer's Conditional Comments -------------------------------------------------------- Key: JBPORTAL-1498 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1498 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.CR1 Environment: All Reporter: Andy Pemberton Assigned To: Julien Viet Currently, JBoss Portal's theme and layout architecture relies on XML deployment descriptors for several objects. For example, the portal-theme.xml is used to create themes (javascript and css) that will be applied to layouts. The request I have is this: given the XML deployment descriptors, add in support for Internet Explorer's Conditional Comment system. Conditional Comments have been a feature of IE since IE5. Basically, Conditional Comments are specially formatted HTML comments that allow web developers to target specific markup to Internet Explorer. Typically, Conditional Comments are used to import specific Cascading Style Sheets (CSS) to HTML pages to handle IE-specific CSS defects. Currently, the lack of support for Conditional Comments is caused by the fact that Conditional Comments rely on XHTML-based comments, which are thus filtered out at the portal-theme.xml level. I considered adding this request as a defect, but decided against it as not reading in comments in an XML deployment descriptor is quite logical, and of course - IE's conditional comment system (though useful) is counter-intuitive. Reference: - http://msdn2.microsoft.com/en-us/library/ms537512.aspx -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1031) using Not only allows me to use 4 equality checks for fact

by Eric Miles (JIRA)

using Not only allows me to use 4 equality checks for fact ---------------------------------------------------------- Key: JBRULES-1031 URL: http://jira.jboss.com/jira/browse/JBRULES-1031 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: Fedora 7, JDK 1.5.0_12 Reporter: Eric Miles Assigned To: Mark Proctor Attachments: drools-not-fact-test.tar.gz I have a single rule in my test bed as such: rule "5th Item Not Test" when $first : FirstClass($i1 : item1, $i2 : item2, $i3 : item3, $i4 : item4, $i5 : item5) not SecondClass(item1 == $i1, item2 == $i2, item3 == $i3, item4 == $i4, item5 == $i5) then System.out.println("NOT test matched"); end In the not SecondClass() section of the test, the last equality checks always fail, no matter what it is. I can switch the order around of the checks, no matter what the last one is, it causes THEN clause to not fire, even when I am absolutely positive there is not a match. (I can remove the not and the equality works fine). Is there a limit on the number of equality tests I can do with a not? It seems as though it is 4. I have attached a test case that can reproduce this (it is different from my project's code, but I have been able to reproduce this in multiple projects). It is a maven Eclipse project and includes a junit with some minor instructions. I have created a rule that will fire as the opposite of the rule I'm trying to test and it prints out the values to the console. You can see in the console that the values are not equal, although the rule fired that they were. If these instructions do not make sense, please email me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (GPD-81) Add support for reconnecting transitions

by Ronald van Kuijk (JIRA)

Add support for reconnecting transitions ---------------------------------------- Key: GPD-81 URL: http://jira.jboss.com/jira/browse/GPD-81 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.alpha4 Environment: Clean eclipse 3.2.2 and gpd 3.1alpha4 Reporter: Ronald van Kuijk Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 Not being able to reconnect transitions graphically from e.g. node a to node b is still a big omission for the gpd to be used by 'grey suites' as well as 'jeans and t-shirts', at least within our company. I thought there was a long standing issue for this, but I cannot find it. If someone could point me to a place to start looking into this, I'd be happy to try to implement this (but it will be the only gpd thing I do ;-) ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (GPD-77) Need a way to initialize palette objects in GD 3.1

by John Ruud (JIRA)

Need a way to initialize palette objects in GD 3.1 -------------------------------------------------- Key: GPD-77 URL: http://jira.jboss.com/jira/browse/GPD-77 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: John Ruud Assigned To: Koen Aers For example, whenever an 'EndState' node is added to the diagram, I need for it to be initialized with a particular event, action, and some action properties. I have made some minor changes to the GD code in order to support this, as described in the following post: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=108175 It would be very helpful if these changes, or similar functionality, can be included in 3.1, as I wouldn't need to keep maintaining my own custom version of the GD feature. I'd be happy to post a patch, if that helps (while my changes are very simple, as described in the post) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

2
16
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-858) org.jboss.test.messaging.jms.bridge.ReconnectTest times out

by Ovidiu Feodorov (JIRA)

org.jboss.test.messaging.jms.bridge.ReconnectTest times out ----------------------------------------------------------- Key: JBMESSAGING-858 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-858 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Tim Fox Fix For: 1.2.0.GA Temporarily commented out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot

by Ovidiu Feodorov (JIRA)

Starting two node clusters simultaneously may end in failed messaging server node boot -------------------------------------------------------------------------------------- Key: JBMESSAGING-693 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in RequestHandler java.lang.IllegalStateException: Don't know about node id: 1 at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597) at org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55) at org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526) at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623) at org.jgroups.blocks.RequestCorrelator.access -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

6
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-750) Remove manually spawning of servers from runtest and build.xml

by Tim Fox (JIRA)

Remove manually spawning of servers from runtest and build.xml -------------------------------------------------------------- Key: JBMESSAGING-750 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-750 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Both runtest and tests/build.xml still use startrmiserver to start (and stop) remote servers prior (and after) to test run. The test framework now has the ability to start servers programmatically so this should be unnecessary. Removing it wil aid clarity of test scripts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-697) Convert crash tests to use new server management framework

by Tim Fox (JIRA)

Convert crash tests to use new server management framework ---------------------------------------------------------- Key: JBMESSAGING-697 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-697 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Now the testing framework supports the ability to kill and restart servers we should transfer the crash tests across to this new way of doing things -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 11 months

3
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 July 2007