November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1136) Messages do not get redistributed to consumers following shutdown/restart sequence

by Mike Clark (JIRA)

Messages do not get redistributed to consumers following shutdown/restart sequence ---------------------------------------------------------------------------------- Key: JBMESSAGING-1136 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1136 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.GA Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database. Reporter: Mike Clark Assigned To: Tim Fox This behavior was reported in support case 18885 and can be reproduced easily: 1) Start two nodes in a JBM cluster (node1 and node2). node1 has no consumers, node2 has an MDB consuming from testDistributedQueue. Messages posted to testDistributedQueue on either node1 or node2 get consumed by the MDB on node2. 2.) Shutdown node2 3.) Queue messages on node1 4.) Shutdown node1 5.) Bring up node2 6.) Bring up node1 Messages queued during step 3 on node1 do not get consumed by node2 until another message is queued on node1. Messages queued to testDistributionQueue on node2 are consumed properly while those queued on node1 remain unconsumed. -- 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, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1323) Add caching to the Objenesis instance and move instance to the RuleBase level

by Alexander Gavrilov (JIRA)

Add caching to the Objenesis instance and move instance to the RuleBase level ----------------------------------------------------------------------------- Key: JBRULES-1323 URL: http://jira.jboss.com/jira/browse/JBRULES-1323 Project: JBoss Drools Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.0.3 Reporter: Alexander Gavrilov Priority: Critical Fix For: 4.0.4, 4.1.0 After moving to the 4.0.3 version we are taked notice of application performance degradation in comarisopn with 4.0.2. Aftert application profiling we found that most time of page loading takes our permission resolving system based on drools. For each permission request application creates new statefull session (we use statefull because facts needs a possibility to be dynamical) and after asserting some facts issued fireAllRules. Further application profiling lead us to the Objenesis calls. The creation of Objenesis's instantiator is a very slow operation and the results of instantiators creating was cached only during the working memorry life cycle (which is very short in our app). So its seems reasonlibe to turn on Objenesis cache, and move Objenesis instance to the RuleBase level to avoid memory leaks. The attached patch working for me and after applying our app working up to ten times faster. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1283) Unable to serialize rule base

by Jiri Pechanec (JIRA)

Unable to serialize rule base ----------------------------- Key: JBRULES-1283 URL: http://jira.jboss.com/jira/browse/JBRULES-1283 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Reporter: Jiri Pechanec Assigned To: Mark Proctor Priority: Minor When I am trying to serialize rulebase, I am getting the exception Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at java.util.ArrayList.writeObject(ArrayList.java:569) at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391) at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606) at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180) at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49) -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBFORUMS-230) configure JavaBuilder into .project files

by Luca Stancapiano (JIRA)

configure JavaBuilder into .project files ----------------------------------------- Key: JBFORUMS-230 URL: http://jira.jboss.com/jira/browse/JBFORUMS-230 Project: JBoss Forums Issue Type: Patch Affects Versions: 1.0.1 RC Environment: jboss forums from http://anonsvn.labs.jboss.com/branches/forums101P26 eclipse 3.2.2 Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC hi ......I think is better to configure .project files to build with eclipse as jbossportal does.....So is simpliest to build sources with eclipse. I added theese rows into .project files of forums project and authz-jaae-plugin project. Tell me if you are agree: <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.jdt.core.javanature</nature> </natures> -- 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, 8 months

2
13
0 / 0

[JBoss JIRA] Created: (JBFORUMS-254) ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster

by Lukasz Wiktor (JIRA)

ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster ---------------------------------------------------------------------------------- Key: JBFORUMS-254 URL: http://jira.jboss.com/jira/browse/JBFORUMS-254 Project: JBoss Forums Issue Type: Bug Affects Versions: 1.0.0 GA Environment: JBoss Portal 2.6.1.GA bundled with JBoss AS 4.2.1 and integrated with OpenLDAP Reporter: Lukasz Wiktor Assigned To: Ryszard Kozmik In class org.jboss.portlet.forums.ui.PortalUtil in function getPoster() userId is casted to Long. That causes ClassCastException when userId is for example type of String (in LDAP). 2007-10-04 15:35:07,700 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.portlet.forums.ui.JSFUtil java.lang.ClassCastException: java.lang.String at org.jboss.portlet.forums.ui.PortalUtil.getPoster(PortalUtil.java:467) ... It prevents from e.g. creating new topic. See my posts on the forum. I have proposed the solution. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-263) French translation

by Luc Boudreau (JIRA)

French translation ------------------ Key: JBFORUMS-263 URL: http://jira.jboss.com/jira/browse/JBFORUMS-263 Project: JBoss Forums Issue Type: Patch Components: Forum View Layer Affects Versions: 1.0.1 RC Environment: Any Reporter: Luc Boudreau Assigned To: Ryszard Kozmik Priority: Optional Here's a french translation of the forum. The web.xml file also has to be modified to tell the forum webapp that the 'fr' locale is supported. WARNING. It is useless to apply this patch unless the graphics are also translated. I've added a comment on this matter on JBFORUMS-151. It looks completely ridiculous to translate the text and not the buttons, since these don't have any link equivalents. Therefore, I would also like ton contribute images of translated buttons, but in order to do that, I'll need the original image files. Working with GIF files is a sure failure to produce even fair quality work. This translation IS NOT FINAL. I've advised your team that some strings are not present in the bundle and should be added to it before I submit a final version of this translation. You can find details on this at : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120699 -- 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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-4957) We shouild always look at the old MDB metadata for JMS MDBs

by Adrian Brock (JIRA)

We shouild always look at the old MDB metadata for JMS MDBs ----------------------------------------------------------- Key: JBAS-4957 URL: http://jira.jboss.com/jira/browse/JBAS-4957 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3 The change in jboss-head to only look at the old JMS tags in ejb-jar.xml (like message-destination-type) when there is no mesaging-type is invalid. We still need to look at the old tags (EJB1.1/2.0) even if there is a messaging-type (EJB2.1). The user should be able to choose to use the old tags or the activation-config-properties. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4959) Need to parse the activation-config-propertys in the invoker-proxy-binding for MDBs

by Adrian Brock (JIRA)

Need to parse the activation-config-propertys in the invoker-proxy-binding for MDBs ----------------------------------------------------------------------------------- Key: JBAS-4959 URL: http://jira.jboss.com/jira/browse/JBAS-4959 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3 We still need to parse the activation-config-propertys in the invoker-proxy-binding for EJB2. This is currently not working because the ActivationConfigProperty no longer implements importXML() -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1788) Workflow Approval Content must be improved

by Edgar Silva (JIRA)

Workflow Approval Content must be improved ------------------------------------------ Key: JBPORTAL-1788 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1788 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Environment: Any Reporter: Edgar Silva Assigned To: Julien Viet Priority: Critical Fix For: 2.6.3 Final In the JBoss Portal reference guide, there is a chapter covering the Workflow approval feature, but first of all it is now working according the doc, besides there's not screenshots showing this feature really working. IMHO it must be improved in the documentation, putting screeshots and everything else to help the users enable this feature in JBoss Portal. -- 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, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBFORUMS-261) Forum notification type modification not working

by Luc Boudreau (JIRA)

Forum notification type modification not working ------------------------------------------------ Key: JBFORUMS-261 URL: http://jira.jboss.com/jira/browse/JBFORUMS-261 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Affects Versions: 1.0.1 RC Environment: Firefox 2.0.0.9 Reporter: Luc Boudreau Assigned To: Ryszard Kozmik While in the MyForums page, if I click on the link to modify my subscription type to forums, once on the modification page, clicking on the "modify" link of a watched forum simply brings back the same page. -- 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, 8 months

2
8
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 November 2007