July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-570) Do we need acceptReliableMessages flag on the channel?

by Tim Fox (JIRA)

Do we need acceptReliableMessages flag on the channel? ------------------------------------------------------ Key: JBMESSAGING-570 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-570 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Alpha1 Reporter: Tim Fox Priority: Minor Fix For: 1.2.0.Beta1 Is there a real use case for ever setting this to false? I can't think of one in a typical messaging application. If not, we should consider removing this flag. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-894) Combine postoffice and clustered post office

by Tim Fox (JIRA)

Combine postoffice and clustered post office -------------------------------------------- Key: JBMESSAGING-894 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-894 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 We should combine clustered and non clustered post office into one single post office that handles both clusterd and non clustered bindings. This means we can have a single persistence manager config too, and remove all that nasty condition code like If (queue.isClustered()) { postOffice.unbind(); } else { postOffice.clusteredUnbind() } etc which is currently ugly and prone to error -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-883) Bug in failover with multiple consumers on same queue

by Tim Fox (JIRA)

Bug in failover with multiple consumers on same queue ----------------------------------------------------- Key: JBMESSAGING-883 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-883 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.CR1 Reporter: Tim Fox Assigned To: Tim Fox Priority: Blocker Fix For: 1.2.0.GA If you have two connections with a consumer each on the same queue, and one of the consumers has consumed a message transactionally but not committed it. Then when failover occurs, if the second connection fails over first then it might "grab" the message before session::recoverDeliveries kicks in for the other connection. This means the message can get delivered more than once. -- 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
21
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-909) Add tests that test failure on ACK

by Tim Fox (JIRA)

Add tests that test failure on ACK ---------------------------------- Key: JBMESSAGING-909 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-909 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Need to add tests that test failover occuring because an ack failed. This needs to be done for all ack modes. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1497) Upgrade Jackrabbit to 1.1.1 in 2.4 Branch

by Thomas Heute (JIRA)

Upgrade Jackrabbit to 1.1.1 in 2.4 Branch ----------------------------------------- Key: JBPORTAL-1497 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1497 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Julien Viet Assigned To: Sohil Shah Fix For: 2.6 Final -- 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
2
0 / 0

[JBoss JIRA] Created: (JBRULES-593) Rule names must be globally unique, even if they come from different packages

by Jeff Lansing (JIRA)

Rule names must be globally unique, even if they come from different packages ----------------------------------------------------------------------------- Key: JBRULES-593 URL: http://jira.jboss.com/jira/browse/JBRULES-593 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.5 Environment: NA Reporter: Jeff Lansing Assigned To: Mark Proctor When 2 DRL rule files with different package names (the name following the 'package' keyword) each have a rule with the same name (the name being the quoted string that follows the 'rule' keyword), then the following exception occurs: org.drools.rule.InvalidRulePackage: Rule Compilation error The type Rule_Incident__Vehicle_0 is already defined at org.drools.rule.Package.checkValidity(Unknown Source) at org.drools.common.AbstractRuleBase.addPackage(Unknown Source) at driver.RulesTest.readRule(RulesTest.java:256) This occurs when using a single org.drools.rule.Package object, as in: private void test(Reader source1, Reader source2) throws Exception { PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl( source1 ); builder.addPackageFromDrl( source2 ); Package pkg = builder.getPackage(); RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage( pkg ); } If, on the other hand two org.drools.rule.Package objects are used, as in: private void test2(Reader source1, Reader source2) throws Exception { PackageBuilder builder1 = new PackageBuilder(); PackageBuilder builder2 = new PackageBuilder(); builder1.addPackageFromDrl( source1 ); builder2.addPackageFromDrl( source2 ); Package pkg1 = builder1.getPackage(); Package pkg2 = builder2.getPackage(); RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage( pkg1 ); ruleBase.addPackage( pkg2 ); } then one of the identically named rules is simply ignored. In either case, rule names must be globally unique. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBAOP-438) NPE getting PER_INSTANCE and PER_JOINPOINT aspects for InstanceProxyContainer

by Kabir Khan (JIRA)

NPE getting PER_INSTANCE and PER_JOINPOINT aspects for InstanceProxyContainer ------------------------------------------------------------------------------ Key: JBAOP-438 URL: http://jira.jboss.com/jira/browse/JBAOP-438 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.beta This happens when the InstanceProxyContainer's domain has interface introductions including the aspect, i.e. the aspect exists only in the InstanceProxyContainer and not in the ClassProxyContainer at org.jboss.aop.InstanceAdvisorDelegate.getPerInstanceAspect(InstanceAdvisorDelegate.java:1 68) at org.jboss.aop.proxy.container.InstanceProxyContainer.getPerInstanceAspect(InstanceProxyCo ntainer.java:85) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at AOPContainerProxy$0.beforeDelivery(AOPContainerProxy$0.java) at org.jboss.test.jca.inflow.test.InflowUnitTestCase.testInflow(InflowUnitTestCase.java:59) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) -- 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
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1571) Doco example is invalid XML

by Andrew Oliver (JIRA)

Doco example is invalid XML --------------------------- Key: JBPORTAL-1571 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1571 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.6 Final Reporter: Andrew Oliver Assigned To: Julien Viet 15.2.2 the config example: <login-module code = "org.jboss.portal.identity.auth.DBIdentityLoginModule" flag="sufficient"> <module-option name="dsJndiName">java:/PortalDS</module-option> <module-option name="principalsQuery"> SELECT jbp_password FROM jbp_users WHERE jbp_uname=? </module-option <module-option name="rolesQuery"> SELECT jbp_roles.jbp_name, 'Roles' FROM jbp_role_membership INNER JOIN jbp_roles ON jbp_role_membership.jbp_rid = jbp_roles.jbp_rid INNER JOIN jbp_users ON jbp_role_membership.jbp_uid = jbp_users.jbp_uid WHERE jbp_users.jbp_uname=? </module-option> <module-option name="hashAlgorithm">MD5</module-option> <module-option name="hashEncoding">HEX</module-option> <module-option name="additionalRole">Authenticated</module-option> </login-module> principals quey module option is missing ">" -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-193) VFS real deployer with optional input

by Carlo de Wolf (JIRA)

VFS real deployer with optional input ------------------------------------- Key: JBMICROCONT-193 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-193 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Carlo de Wolf There should be an abstract more complicated VFS real deployer where the input is optional instead of mandatory. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1528) Admin apps checkboxes are surrounded by blue in IE7

by Julien Viet (JIRA)

Admin apps checkboxes are surrounded by blue in IE7 --------------------------------------------------- Key: JBPORTAL-1528 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1528 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6 Final Reporter: Julien Viet Fix For: 2.6.1 Final, 2.8 Final Attachments: screenshot.jpeg -- 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

2
2
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