June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-956) StatefulTreeCache does not replicate removed parent if it has live nested children

by Brian Stansberry (JIRA)

StatefulTreeCache does not replicate removed parent if it has live nested children ---------------------------------------------------------------------------------- Key: EJBTHREE-956 URL: http://jira.jboss.com/jira/browse/EJBTHREE-956 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 CR2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 GA When StatefulTreeCache gets a callback from StatefulRemoveInterceptor telling it an @Remove method has been invoked, it only removes the bean context from the clustered cache if the bean doesn't have any live nested children. Problem is, it also doesn't replicate the bean context. Effect of this is that the other nodes in the cluster are made aware that the parent bean has been removed. This problem occurs because the StatefulRemoveInterceptor handles the @Remove after the call has already passed through the StatefulReplicationInterceptor. Solution is to have StatefulTreeCache.remove() replicate the context via a TreeCache.put() if the presence of live nested beans prevents it removing the context via a TreeCache.remove(). -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1479) PDF for ReferenceGuide is not created by build script

by Boleslaw Dawidowicz (JIRA)

PDF for ReferenceGuide is not created by build script ----------------------------------------------------- Key: JBPORTAL-1479 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1479 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR2 Reporter: Boleslaw Dawidowicz Assigned To: Prabhat Jha Fix For: 2.6 Final The pdf for the Reference Guide is not generated at the moment. http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-latest-doc/refer... I think it was disabled in the main target but when I do: [referenceGuide]$ ant lang.docpdf -Dlang=en I get [java] [ERROR] file:/home/bdaw/Workshop/JBoss/portal/docs/trunk/referenceGuide/build/en/pdf/docbook_fop.tmp:4323:147 A table row must be child of fo:table-body, fo:table-header or fo:table-footer, not fo:table [java] Java Result: 2 HTML is generated correctly so it doesn't seem to be wrong nested tags problem. -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Closed: (JBBUILD-297) Externalise the JBossRetro weaving implementation

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-297?page=all ] Paul Gier closed JBBUILD-297. ----------------------------- Resolution: Done The weaving behaviour can now be specified through setting a custom weaver class. The class renames and class editing within a weaver can also be customized through the weaver's methods. > Externalise the JBossRetro weaving implementation > ------------------------------------------------- > > Key: JBBUILD-297 > URL: http://jira.jboss.com/jira/browse/JBBUILD-297 > Project: JBoss Build System > Issue Type: Task > Components: Targets and Tasks, JBossRetro > Reporter: Adrian Brock > Assigned To: Paul Gier > Fix For: JBossRetro-1.1.0.GA > > > The JBossRetro task should externalise the weaving > such that you can configure the mappings, etc. in the ant xml or some other property file. > See the FIXMEs in the Weaver class. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-330) Add support for java.lang.reflect.AnnotatedElement

by Thomas Diesler (JIRA)

Add support for java.lang.reflect.AnnotatedElement -------------------------------------------------- Key: JBBUILD-330 URL: http://jira.jboss.com/jira/browse/JBBUILD-330 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro Reporter: Thomas Diesler Please add support for this: Field someField; Method someMethod; processAnnotatedElement(someField); processAnnotatedElement(someMethod); processAnnotatedElement(AnnotatedElement el) { SomeAnnotation an = el.getAnnotation(SomeAnnotation.class); ... } -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-783) NoViableAltException when parsing eval rules

by John Howard (JIRA)

NoViableAltException when parsing eval rules -------------------------------------------- Key: JBRULES-783 URL: http://jira.jboss.com/jira/browse/JBRULES-783 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.1-m1 Environment: VISTA 64bit Reporter: John Howard Assigned To: Mark Proctor Priority: Minor The following rules causes a NoViableAltException. Although the exception is thrown the rule does appear to fire correctly package com.sample rule "Test Parse" when eval( 3==3 ) then System.out.println("OK"); end NoViableAltException(-1!=[685:3: ( ( (LT|GT|LE|GE) shiftExpression )* | 'instanceof' typeSpec )]) in JavaParserParser If the eval line is replaced by eval( 3>=3 ) then no exception is thrown -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-748) Putting double quotes around a template name causes NPE

by Michael Neale (JIRA)

Putting double quotes around a template name causes NPE ------------------------------------------------------- Key: JBRULES-748 URL: http://jira.jboss.com/jira/browse/JBRULES-748 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Edson Tirelli Priority: Minor Fix For: 3.1-m2 template "Foo" String bar String baz end That will cause an NPE (quotes are not needed) - grammar could be made to have optional quotes. -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-781) semi colon after 'end' breaks parsing

by Mark Proctor (JIRA)

semi colon after 'end' breaks parsing ------------------------------------- Key: JBRULES-781 URL: http://jira.jboss.com/jira/browse/JBRULES-781 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.1-m1 Reporter: Mark Proctor Assigned To: Edson Tirelli Fix For: 3.1-m2 If you have a rule with a ; semicolon after the 'end' then it doesn't report an error, but nor does it parse the rest of the file. It should either error or accept the ; -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-585) WebServices is having trouble using Messaging

by Ovidiu Feodorov (JIRA)

WebServices is having trouble using Messaging --------------------------------------------- Key: JBMESSAGING-585 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-585 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.Alpha2 Thomas Diesler's report (1): ------------------------------------------------------------------------------------------------------------------------------------------------------------- Hi Folks, on jbossas/trunk this jboss-service.xml does not deploy <server> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> </server> 2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar 2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue 2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on 2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar >From the error output I cannot figure out what is missing. 2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED Hi Folks, on jbossas/trunk this jboss-service.xml does not deploy <server> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> </server> 2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar 2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue 2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on 2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar >From the error output I cannot figure out what is missing. 2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ------------------------------------------------------------------------------------------------------------------------------------------------------------- Thomas Diesler's report (2): ------------------------------------------------------------------------------------------------------------------------------------------------------------- Please follow How can I build and install the latest? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstallJBoss50x Instead of Step 8, do 8. Run the jbossws testsuite cd jbossws/src/test ant main ant -Dtest=org.jboss.test.ws.samples.jmstransport.JMSTransportTestCase one-test You can also run ant tests-samples -- 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, 1 month

6
11
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-322) Deploying an MDB for a destination that doesn't exist fails.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-322?page=all ] Tim Fox closed JBMESSAGING-322. ------------------------------- Resolution: Won't Fix Assignee: Tim Fox This is a non issue. The JMSContainerInvoker only attempts to create a JBossMQ destination if the attribute "createJBossMQDestination" is true. The JBM installation guide clearly states to set this to false. What's more even if this was an issue, it should be an issue for the AS project not JBM. > Deploying an MDB for a destination that doesn't exist fails. > ------------------------------------------------------------ > > Key: JBMESSAGING-322 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-322 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.4.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the destination an MDB is configured with doesn't exist, the MDB Container's JMSContainerInvoker tries to create the destination and fails because uses a non-portable interface that only works with JBossMQ. > Line 1201, org.jboss.ejb.plugins.jms.JMSContainerInvoker.createDestination() > // invoke the server to create the destination > server.invoke(new ObjectName("jboss.mq:service=DestinationManager"), ..... > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-810) Uncomment thirdparty remoting causality tests

by Ovidiu Feodorov (JIRA)

Uncomment thirdparty remoting causality tests --------------------------------------------- Key: JBMESSAGING-810 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-810 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.2.CR1 I've commented out causality thridparty remoting tests to get a clean Beta2 test run, but they need to be uncommented and underlying behavior fixed. -- 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, 1 month

3
5
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 June 2007