February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-16) Add support for Thread Priority to the BasicThreadPool

by Adrian Brock (JIRA)

Add support for Thread Priority to the BasicThreadPool ------------------------------------------------------ Key: JBCOMMON-16 URL: http://jira.jboss.com/jira/browse/JBCOMMON-16 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Adrian Brock The ThreadPool should have configuration for the default thread priority. i.e. introduce a "priority" attribute into BasicThreadPool[MBean] and update the internal ThreadPoolFactory code to use it. There is also a Task.getPriority() that is currently unused. This should allow dynamic changing of the thread priority based upon individual task requests. Additional constraints may also be useful, e.g. having a min/max priority on the BasicThreadPool that constrains what tasks can ask for, and possibly a seperate option to always ignore what the tasks request. -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-825) Usability improvements in Admin UI

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-825?page=all ] Julien Viet updated JBPORTAL-825: --------------------------------- Fix Version/s: 2.6.CR1 (was: 2.6.Beta1) > Usability improvements in Admin UI > ---------------------------------- > > Key: JBPORTAL-825 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-825 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.6.Alpha1 > Reporter: Roy Russo > Assigned To: Roy Russo > Fix For: 2.6.CR1 > > > Address usability issues with interface redesign, tooltips, and help mode in management portlet. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1224) Isolate admin package

by Roy Russo (JIRA)

Isolate admin package --------------------- Key: JBPORTAL-1224 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1224 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Beta1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Beta1 use core-* naming scheme and isolate package dependencies - lib/build/config -- 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 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1277) Mistake in portal-object_2_6.dtd

by Ian White (JIRA)

Mistake in portal-object_2_6.dtd -------------------------------- Key: JBPORTAL-1277 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1277 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha2 Environment: As 4.0.5.GA Reporter: Ian White Assigned To: Julien Viet In the portal-object dtd, the following line <!ELEMENT security-constraint (policy-permission)> should be <!ELEMENT security-constraint (policy-permission*)> i.e. should allow multiple permissions to be set -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-417) ConnectionTable.run / ClassCastException with IBM Java 1.5

by Yves Martin (JIRA)

ConnectionTable.run / ClassCastException with IBM Java 1.5 ---------------------------------------------------------- Key: JGRP-417 URL: http://jira.jboss.com/jira/browse/JGRP-417 Project: JGroups Issue Type: Bug Affects Versions: 2.2.9 SP4 Environment: $ java -version java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20061107 (iFix 111765: SR3 + 111700) ) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20061001 (JIT enabled) J9VM - 20060915_08260_lHdSMR JIT - 20060908_1811_r8 GC - 20060906_AA) JCL - 20061107 Reporter: Yves Martin Assigned To: Bela Ban Priority: Critical When migrating a project to IBM Java 1.5, I get the following warning from ConnectionTable: ConnectionTable.run(): exception is java.lang.ClassCastException: IpAddress.compareTo(): comparison between different classes And communication times out. The same code works perfectly well with Sun Java 1.5.0_07 The drop stack trace show it comes from Hashtable.contains. After comparison between Sun src.zip and IBM src.jar for Hashtable, . Sun does entry.equals(value) . IBM does value.equals(entry) As a result, JGroups happens to do a IpAddress.equals(Connection) with IBM JVM and fails. Whereas Connection.equals(IpAddress) is properly handled in case of Sun JVM. Patch is trivial but the bug analysis was difficult !! Here is a valid IpAddress.equals method. public boolean equals(Object obj) { if (obj == null || !(obj instanceof IpAddress)) return false; return compareTo(obj) == 0 ? true : false; } Thank you in advance to include this patch in JGroups 2.2.9 so that JBoss 4.0.x may work one day with IBM Java 1.5 -- 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 months

4
9
0 / 0

[JBoss JIRA] Reopened: (JBAS-1820) JCA 1.5 compliance bug

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1820?page=all ] Adrian Brock reopened JBAS-1820: -------------------------------- Re-opened since this is still unresolved. Specifying the <resource-adapter-name/> should be enough. The <depends> should be automatically added from that. > JCA 1.5 compliance bug > ---------------------- > > Key: JBAS-1820 > URL: http://jira.jboss.com/jira/browse/JBAS-1820 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.2 Final > Environment: Windows 2000 > Reporter: guillaume holler > Assigned To: Weston Price > Priority: Minor > Attachments: jcasample.zip > > > This is a deployment bug that affects inflow messages. > JCA 1.5 specification states states that "Before a rsource adapter is undeployed, the application server must deactivate all active enpoints consuming messages from that specific resource adapter". This doesn't seem to be the case: > 1 - start the server with a RAR and an MDB endpoint setup (the test connector accept messages from network and the mdb merely print them on the console after wainting 10s to easealy test enpoint concurrency issues). > OK: I see the start() and endpointActivation(...) callback called > 2 - run the client test several times (in a way that enables concurrent message consumption): OK (client OK, console prints all messages) > 3 - undeploy RAR: I can see the stop callback, but no MDB undeploy or endpointDeactivation(...) callback on resource adapter. > 4 - deploy RAR again: deployment OK, I can see the start() callback but no endpointActivation(...) callback called > 5 - run the client test again: client OK, demonstrating the network endpoint is working, but no message printed on the console (no endpoint consumption). > 6 - undeploy/deploy MDB: everything works again as in 2 (plus, messages pending from step 5 are obviously consumed) > I think we should have, according to spec, an undeployment of MDBs that depend on the RAR service when the service is undeployed, and a furter restart should trigger a new endpointActivation callback. -- 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 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=all ] Ovidiu Feodorov closed JBMESSAGING-371. --------------------------------------- Resolution: Done Test passes using bisocket. That's good enough. > MessageListener times out on inactivity, after receiving at least one message > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-371 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Affects Versions: 1.0.1.CR1, 1.2.0.Beta2 > Reporter: Ovidiu Feodorov > Assigned To: Ron Sigal > Priority: Blocker > Fix For: 1.2.0.CR1 > > > 15:15:31,530 ERROR [ServerThread] socket timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) > at java.io.BufferedInputStream.read(BufferedInputStream.java:201) > at java.io.FilterInputStream.read(FilterInputStream.java:66) > at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) > at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-822) Outstanding remoting issues.

by Ovidiu Feodorov (JIRA)

Outstanding remoting issues. ---------------------------- Key: JBMESSAGING-822 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-822 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.CR1 Make sure these make it into Alpha8 http://jira.jboss.org/jira/browse/JBREM-690 http://jira.jboss.org/jira/browse/JBREM-693 -- 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 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-690) Once the socket of a callback server timeouts, it starts to silently discard traffic

by Ovidiu Feodorov (JIRA)

Once the socket of a callback server timeouts, it starts to silently discard traffic ------------------------------------------------------------------------------------ Key: JBREM-690 URL: http://jira.jboss.com/jira/browse/JBREM-690 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.2.0.Alpha6 Reporter: Ovidiu Feodorov Assigned To: Tom Elrod Priority: Blocker Fix For: 2.2.0.Alpha7 Please write the following test (and I actually mean it, please do, and keep it your test suite): Create a "socket" transport client and register a listener to it, so the push callback server is initialized. Send a callback to the client, to make sure a socket is created and traffic is sent over it. Wait enough for the callback socket to timeout (a little bit longer than ServerInvoker.DEFAULT_TIMEOUT_PERIOD). Send a new callback to the client. The callback will be silently discarded, never to be heard of again. For the Messaging version of this bug, please see http://jira.jboss.org/jira/browse/JBMESSAGING-371 and the associated RemotingTest.test testMessageListenerTimeout() -- 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 months

4
8
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Ovidiu Feodorov updated JBMESSAGING-412: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.2.0.CR1) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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 months

1
0
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 February 2007