April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-808) DefaultExpander not failing when it should (partial expansion)

by Michael Neale (JIRA)

DefaultExpander not failing when it should (partial expansion) -------------------------------------------------------------- Key: JBRULES-808 URL: http://jira.jboss.com/jira/browse/JBRULES-808 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Michael Neale Assigned To: Edson Tirelli In DefaultExpanderTest I have added a method: FIXME_testExpanderFailure() This shows a drl which should fail. eg if "foo" expands to "Foo()", then "foos" should NOT expand to "Foo()s" - it should be an error I believe (correct me if wrong). -- 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

19 years, 3 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBCACHE-97) ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer waiting to upgrade lock

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-97?page=all ] Jason T. Greene updated JBCACHE-97: ----------------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR1) > ReadWriteLockWithUpgrade: UpgradeException with more than 1 reader/writer waiting to upgrade lock > ------------------------------------------------------------------------------------------------- > > Key: JBCACHE-97 > URL: http://jira.jboss.com/jira/browse/JBCACHE-97 > Project: JBoss Cache > Issue Type: Bug > Components: Clustering > Reporter: Bela Ban > Assigned To: Jason T. Greene > Fix For: 2.0.0.GA > > > TxDeadlockUnitTestCase has 2 methods that show the following stack traces: > testMoreThanOneUpgrader: > Upgrader#0: get(/a/b/c) > Upgrader#1: get(/a/b/c) > main: locks: > /a (read owners=[<null>:2, <null>:1]) > /b (read owners=[<null>:2, <null>:1]) > /c (read owners=[<null>:2, <null>:1]) > Upgrader#0: put(/a/b/c) > Upgrader#1: put(/a/b/c) > Upgrader#1: org.jboss.cache.lock.LockingException: acquireWriteLock(): lock upgrade failed for /a/b/c (caller=<null>:2); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock) > Upgrader#0: org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [<null>:2] > Write lock owner: null > (caller=<null>:1) > org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [<null>:2] > Write lock owner: null > (caller=<null>:1) > at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:155) > at org.jboss.cache.Node.acquireWriteLock(Node.java:448) > at org.jboss.cache.Node.acquire(Node.java:417) > at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:199) > at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:144) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at org.jboss.cache.interceptors.CreateIfNotExistsInterceptor.invoke(CreateIfNotExistsInterceptor.java:145) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) > at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:2998) > at org.jboss.cache.TreeCache.put(TreeCache.java:1657) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$MyUpgrader._run(TxDeadlockUnitTestCase.java:346) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) > and > testConcurrentUpgrade(): > MyThread#1: get(/a/b/c) > MyThread#2: get(/a/b/c) > MyThread#2: done, locks: > /a (read owners=[<null>:2]) > /b (read owners=[<null>:2]) > /c (read owners=[<null>:2]) > MyThread#1: done, locks: > /a (read owners=[<null>:2, <null>:1]) > /b (read owners=[<null>:2, <null>:1]) > /c (read owners=[<null>:2, <null>:1]) > MyThread#2: put(/a/b/c) > MyThread#1: put(/a/b/c) > MyThread#1: org.jboss.cache.lock.LockingException: acquireWriteLock(): lock upgrade failed for /a/b/c (caller=<null>:1); - nested throwable: (org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock) > MyThread#2: org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [<null>:1] > Write lock owner: null > (caller=<null>:2) > org.jboss.cache.lock.TimeoutException: upgrade lock for /a/b/c could not be acquired after 3000 ms. Lock map ownership Read lock owners: [<null>:1] > Write lock owner: null > (caller=<null>:2) > at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:155) > at org.jboss.cache.Node.acquireWriteLock(Node.java:448) > at org.jboss.cache.Node.acquire(Node.java:417) > at org.jboss.cache.interceptors.LockInterceptor.lock(LockInterceptor.java:199) > at org.jboss.cache.interceptors.LockInterceptor.invoke(LockInterceptor.java:144) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at org.jboss.cache.interceptors.CreateIfNotExistsInterceptor.invoke(CreateIfNotExistsInterceptor.java:145) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:40) > at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:35) > at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:2998) > at org.jboss.cache.TreeCache.put(TreeCache.java:1657) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$MyThread._run(TxDeadlockUnitTestCase.java:317) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) > at org.jboss.test.cache.test.local.TxDeadlockUnitTestCase$GenericThread.run(TxDeadlockUnitTestCase.java:213) -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1019) Revisit JGroups stack in config files shipped with JBoss Cache to make them JGroups 2.5-friendly

by Manik Surtani (JIRA)

Revisit JGroups stack in config files shipped with JBoss Cache to make them JGroups 2.5-friendly ------------------------------------------------------------------------------------------------ Key: JBCACHE-1019 URL: http://jira.jboss.com/jira/browse/JBCACHE-1019 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR1 -- 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

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4347) Patch xalan 2.7.0 so that javax.xml.transform.TransformerFactory.newTransformer() does not return null

by Dimitris Andreadis (JIRA)

Patch xalan 2.7.0 so that javax.xml.transform.TransformerFactory.newTransformer() does not return null ------------------------------------------------------------------------------------------------------- Key: JBAS-4347 URL: http://jira.jboss.com/jira/browse/JBAS-4347 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: XML services Reporter: Dimitris Andreadis Assigned To: Fernando Nasser Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3 See JBCTS-370 -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1032) Remove dependency on JBoss Serialization

by Manik Surtani (JIRA)

Remove dependency on JBoss Serialization ---------------------------------------- Key: JBCACHE-1032 URL: http://jira.jboss.com/jira/browse/JBCACHE-1032 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR1, 2.0.0.GA Decided to drop jboss-serialization since updated Java5 JDKs contain the same benefits that JBoss Serialization brings. Dropping the jar means 1 less dependency jar to ship with. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1351) Portlets "forget" that they are in EDIT mode

by Adam Warski (JIRA)

Portlets "forget" that they are in EDIT mode -------------------------------------------- Key: JBPORTAL-1351 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1351 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR1 Reporter: Adam Warski Assigned To: Julien Viet Priority: Critical Fix For: 2.6.CR2 Attachments: edit-test.war.tar.gz Portlets forget that they are in "edit" mode and go back to "view" on an action request. The attached portlet demonstrates it. Steps to reproduce: 1. open the page, in the portlet click the render url (<portlet:renderURL portletMode="edit" />) 2. the edit-mode jsp appears, with an action url (<portlet:actionURL />) 3. click the action URL, the portlet goes back to "view" mode. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (BPEL-131) web service consumption

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-131?page=all ] Alejandro Guizar updated BPEL-131: ---------------------------------- Summary: web service consumption (was: bpel web service consumption) > web service consumption > ----------------------- > > Key: BPEL-131 > URL: http://jira.jboss.com/jira/browse/BPEL-131 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Environment: saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-168) soap header processing

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-168?page=all ] Alejandro Guizar updated BPEL-168: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1 GA) > soap header processing > ---------------------- > > Key: BPEL-168 > URL: http://jira.jboss.com/jira/browse/BPEL-168 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > > Extract the WSDL message parts carried in SOAP headers and add them to incoming requests. > Ensure this mechanism makes WS-Addressing headers available to the process. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (BPEL-144) publish document/literal endpoints

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-144?page=all ] Alejandro Guizar resolved BPEL-144. ----------------------------------- Resolution: Done SoapHandler no longer assumes the endpoint is RPC-oriented. Instead, it retrieves the port description through the ws stack integration subsystem and formats/parses SOAP messages according to the binding information. Updating the service generation tool to cover document-oriented endpoints will be tracked as a separate issue. > publish document/literal endpoints > ---------------------------------- > > Key: BPEL-144 > URL: http://jira.jboss.com/jira/browse/BPEL-144 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: jaxrpc, saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 GA > > > jBPM BPEL currently generates service WSDL documents and processes SOAP request/response messages only for RPC/literal web services. Enhancing the service generation tool and the JAX-RPC handler to cover the document style is crucial for interoperability, particulary with .NET. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-143) web service production

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-143?page=all ] Alejandro Guizar updated BPEL-143: ---------------------------------- Summary: web service production (was: bpel web service production) > web service production > ---------------------- > > Key: BPEL-143 > URL: http://jira.jboss.com/jira/browse/BPEL-143 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 1 > Environment: ws4ee, w3c dom, saaj, jms > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > -- 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

19 years, 3 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 April 2007