August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-286) Multiplexer: service views are not adjusted correctly if member dies (no graceful termination)

by Bela Ban (JIRA)

Multiplexer: service views are not adjusted correctly if member dies (no graceful termination) ---------------------------------------------------------------------------------------------- Key: JGRP-286 URL: http://jira.jboss.com/jira/browse/JGRP-286 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 To reproduce: - Start JBoss A - Start JBoss B - Look at view (service view) of A: {A,B} - Kill B (no graceful shutdown) - Look at service view of A: *still* {A,B}; should be {A} SOLUTION: handle view change, adjust service view for left members -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-284) Optimize marshalling of return values

by Bela Ban (JIRA)

Optimize marshalling of return values ------------------------------------- Key: JGRP-284 URL: http://jira.jboss.com/jira/browse/JGRP-284 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 I was doing some CPU profiling of JBoss HttpSession replication and noticed that GroupRequest.receiveResponse() took ~ 5% of the total CPU time. Thought that was a bit odd, given that all the RPC calls in JBoss Cache are to void methods. Had a look at Util.objectTo/FromByteBuffer, and if the response is null, an ObjectOutputStream gets created, and then ObjectOutputStream.writeObject(null) gets called. That method does a fair amount of stuff before ultimately writing a byte to the stream. On the other side, an ObjectInputStream is created and readObject() also jumps through quite a few hoops just to read that byte and return null. Since in HEAD you're now writing an initial byte to the stream to signal Streamable or not, perhaps having a 3rd value to signal null would make sense. Lets you skip the whole initiation of the ObjectInput/OutputStream as well as the overhead I described. Brian Stansberry -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-3573) Failure to remove a message should result in a NACK + error

by Adrian Brock (JIRA)

Failure to remove a message should result in a NACK + error ----------------------------------------------------------- Key: JBAS-3573 URL: http://jira.jboss.com/jira/browse/JBAS-3573 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.4.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-4.0.5.CR1 If an ACK fails due to a persistent store error during the remove(), e.g. database is down, the message should be NACKed and an error reported. Currently, you have to recover the queue (e.g. redeploy the queue) otherwise the message is stuck in limbo. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3510) Backport fixes from ServiceController rewrite to JBoss4

by Adrian Brock (JIRA)

Backport fixes from ServiceController rewrite to JBoss4 ------------------------------------------------------- Key: JBAS-3510 URL: http://jira.jboss.com/jira/browse/JBAS-3510 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-4.0.4.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-4.0.5.CR1 Backport fixes from JBAS-1841 to JBoss4 -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=comments#action_123... ] Ales Justin commented on JBMICROCONT-35: ---------------------------------------- public class MyClass { private List<String> list; public List<String> getList(); } <property name="list"><list><value>...</value><list></property> i.e. this will do getList() and if it is not null, it will add to the list rather than overwriting it. > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0 final > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=all ] Ales Justin reassigned JBMICROCONT-35: -------------------------------------- Assignee: Ales Justin > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0 final > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3466) JMS PersistenceManager: org.jboss.mq.SpyJMSException: Could not remove message when using MySQL DB

by Luc Texier (JIRA)

JMS PersistenceManager: org.jboss.mq.SpyJMSException: Could not remove message when using MySQL DB --------------------------------------------------------------------------------------------------- Key: JBAS-3466 URL: http://jira.jboss.com/jira/browse/JBAS-3466 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-3.2.8.SP1, JBossAS-4.0.3 SP1 Environment: MySQL DB with InnoDB engine Reporter: Luc Texier Assigned To: Adrian Brock Priority: Minor Fix For: JBossAS-4.0.5.CR1 Configuring the JMS persistence manager to use MySQL DB, under load, we get Caused by: org.jboss.mq.SpyTransactionRolledBackException: Transaction was rolled back.; - nested throwable: (org.jboss.mq.SpyJMSException: Could not remove message: 20 msg=12 soft STORED PERSISTENT queue=QUEUE.KVSMSLogQueue priority=4 lateClone=false hashCode=19088493; - nested throwable: (java.sql.SQLException: Deadlock found when trying to get lock; try restarting transaction)) at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:490) at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186) at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:182) at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438) at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186) at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:166) at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:361) at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377) -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBPM-587) GPD crashes if xmlbuddy plugin is installed

by Carmine Frasci (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-587?page=comments#action_12341982 ] Carmine Frasci commented on JBPM-587: ------------------------------------- This problem is also there if XMLBuddy is not installed! My configuration: gpd-3.0.11 with jbpm-3.0.4 on eclipse-3.1.1 other plugins on my installation: GEF 3.1.1 JBoss IDE 1.5.0 (ALL) > GPD crashes if xmlbuddy plugin is installed > ------------------------------------------- > > Key: JBPM-587 > URL: http://jira.jboss.com/jira/browse/JBPM-587 > Project: JBoss jBPM > Issue Type: Bug > Components: Graphical Process Designer > Affects Versions: jBPM GPD 3.0.8 > Environment: Gentoo Linux / Eclipse 3.1.2 > Reporter: Matthias Germann > Assigned To: Tom Baeyens > > If the Graphical Process Designer plugin and the XML Buddy Plugin are installed in the same eclipse installation, the GPD crases when opening a process definition file. The problem can be reproduced by unzipping the XML Buddy Free Edition ZIP File into the plugins directory of a eclipse installation with GPD installed. > The GPD reports the following error when opening a jBPM process definition File: > Unable to create this part due to an internal error. Reason for the failure: An unexpected exception was thrown. > Detail: > java.lang.NullPointerException > at org.jbpm.ui.editor.DesignerContentProvider.addProcessDiagramDimension(Unknown Source) > at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source) > at org.jbpm.ui.editor.DesignerGraphicalEditorPage.initInput(Unknown Source) > at org.jbpm.ui.editor.DesignerGraphicalEditorPage.init(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:152) > at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source) > at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source) > at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:241) > at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:609) > at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:384) > at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552) > at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:223) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2362) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2295) > at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2287) > at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2273) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2268) > at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:279) > at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:271) > at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:178) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1021) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2867) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2572) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) > at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) > at org.eclipse.core.launcher.Main.basicRun(Main.java:278) > at org.eclipse.core.launcher.Main.run(Main.java:973) > at org.eclipse.core.launcher.Main.main(Main.java:948) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3565) Resolve OOME issue with HttpSession replication

by Brian Stansberry (JIRA)

Resolve OOME issue with HttpSession replication ----------------------------------------------- Key: JBAS-3565 URL: http://jira.jboss.com/jira/browse/JBAS-3565 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: JBossAS-4.0.5.CR1 I'm seeing OOMEs when running JBento benchmarks of Branch_4_0. JBC is 1.4.0.SP1, JGroups is 2.2.9.2. REPL_SYNC, UDP stack. Same config, same JBC and JG versions with 4.0.4.GA have no issues, so it looks like something in the session replication layer. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-282) The failure detection protocols (FD, FD_SOCK) should not accept SUSPECT messages from non-members

by Bela Ban (JIRA)

The failure detection protocols (FD, FD_SOCK) should not accept SUSPECT messages from non-members ------------------------------------------------------------------------------------------------- Key: JGRP-282 URL: http://jira.jboss.com/jira/browse/JGRP-282 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1, 2.3, 2.2.9 SP3 (2.2.9.3), 2.2.9.2, 2.2.9.1, 2.2.9, 2.2.8 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 This could happen if we have A and B (with shun=false), disconnect the network cable, so A and B form singleton groups, and reconnect the network again. A and B will both have queued-up SUSPECT messages that should be discarded -- 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, 11 months

1
1
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 August 2006