March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-703) allow for total configuration of socket via socket invoker

by Tom Elrod (JIRA)

allow for total configuration of socket via socket invoker ---------------------------------------------------------- Key: JBREM-703 URL: http://jira.jboss.com/jira/browse/JBREM-703 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha7 Reporter: Tom Elrod Assigned To: Tom Elrod Priority: Minor Fix For: 2.2.0.Beta2 (Bluto) Currently remoting does not expose all the configuration properties for a socket for the socket invokers. Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize) -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-128) ClassInfo should be serialzable

by Adrian Brock (JIRA)

ClassInfo should be serialzable ------------------------------- Key: JBMICROCONT-128 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-128 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The ClassInfo objects should be serializable, this is currently not the case because they hold references back to their factory to support lazy initialization. -- 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, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-3996) Web Console AppletBrowser hangs browser because of missing Logger

by teej TJ (JIRA)

Web Console AppletBrowser hangs browser because of missing Logger ----------------------------------------------------------------- Key: JBAS-3996 URL: http://jira.jboss.com/jira/browse/JBAS-3996 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-5.0.0.Beta1 Environment: Ubuntu Edgy Eft 6.10 Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux Firefox 2.0.0.1 Sun Java 1.5.0_08 Reporter: teej TJ Assigned To: Darran Lofthouse Firefox hangs and has to be killed when the JBoss Web Console link is followed on the JBoss Management service (http://localhost:8080/). The hang is caused by a NoClassDefFoundError exception whilst attempting to load AppletBrowser in applet.jar. This appears to be another instance of the use of Logger where it has been removed (as in the shutdown.sh script bugs JBAS-3560). org.jboss.console.remote.Util: private static org.jboss.logging.Logger log = org.jboss.logging.Logger.getLogger(Util.class); --- Java Console Report --- basic: Loading applet ... basic: Initializing applet ... basic: Starting applet ... network: Connecting http://10.254.251.2:8080/web-console/applet.jar with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/applet.jar with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" basic: Loading http://10.254.251.2:8080/web-console/applet.jar from cache basic: No certificate info, this is unsigned JAR file. http://10.254.251.2:8080/web-console/Invoker network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) basic: Exception: java.lang.NoClassDefFoundError: org/jboss/logging/Logger java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) -- 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, 2 months

6
5
0 / 0

[JBoss JIRA] Created: (JBAS-3857) shutdown.sh does not work

by Ovidiu Feodorov (JIRA)

shutdown.sh does not work ------------------------- Key: JBAS-3857 URL: http://jira.jboss.com/jira/browse/JBAS-3857 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Ovidiu Feodorov $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/system/server/ServerImplMBean at org.jboss.Shutdown.main(Shutdown.java:116) -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-682) Test real-life problem/constraints with large data sets

by Geoffrey De Smet (JIRA)

Test real-life problem/constraints with large data sets ------------------------------------------------------- Key: JBRULES-682 URL: http://jira.jboss.com/jira/browse/JBRULES-682 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Exam Timetabling http://www.cs.nott.ac.uk/~rxq/data.htm Nurse rostering: http://www.cs.nott.ac.uk/~tec/NRP/ -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-679) Move code into JBoss svn + refactor rename packages

by Geoffrey De Smet (JIRA)

Move code into JBoss svn + refactor rename packages --------------------------------------------------- Key: JBRULES-679 URL: http://jira.jboss.com/jira/browse/JBRULES-679 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Rename package net.sf.taseree to org.drools.solver -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-480) Change contract of Receiver

by Tim Fox (JIRA)

Change contract of Receiver --------------------------- Key: JBMESSAGING-480 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-480 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- 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, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-876) Allow onMessage to be executed on the remoting thread

by Tim Fox (JIRA)

Allow onMessage to be executed on the remoting thread ----------------------------------------------------- Key: JBMESSAGING-876 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-876 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As an optimisation we should allow message listeners to be executed straight through using the same thread that delivers the message to the message callback handler. This would avoid an extra context switch.. Currently the thread used is from an executor per session - so as to be strictly JMS compliant. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-875) Non durable subscription optimisation

by Tim Fox (JIRA)

Non durable subscription optimisation ------------------------------------- Key: JBMESSAGING-875 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs. Basically I think we can acknowledge them before they are sent from server to client. This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks. On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver. This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time. -- 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, 2 months

2
6
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 March 2007