June 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8618) Web subsystem updates are not respecting resultHandler

by David Lloyd (JIRA)

Web subsystem updates are not respecting resultHandler ------------------------------------------------------ Key: JBAS-8618 URL: https://jira.jboss.org/browse/JBAS-8618 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 7.0.0.Alpha1 Reporter: David Lloyd Assignee: Remy Maucherat Fix For: 7.0.0.Alpha2 The result is generally discarded. It should be sent to the result handler when the corresponding services are successfully installed, removed, or updated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JGRP-1333) JChannel: remove src from send() methods

by Bela Ban (JIRA)

JChannel: remove src from send() methods ---------------------------------------- Key: JGRP-1333 URL: https://issues.jboss.org/browse/JGRP-1333 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 In most cases, the src argument in the send() methods is null (later filled in by the stack anyway), so let's remove it. If we want to use a src, we can use the send(Message) method -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9211) java.lang.NoClassDefFoundError: test/n (wrong name: test/N)

by miguel cheng (JIRA)

java.lang.NoClassDefFoundError: test/n (wrong name: test/N) ----------------------------------------------------------- Key: JBAS-9211 URL: https://issues.jboss.org/browse/JBAS-9211 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Modules / Class-loading Affects Versions: 6.0.0.M3 Environment: JBoss 6.0.0.M3, Windows 2003 R2 SP2. Reporter: miguel cheng Assignee: Scott Stark Priority: Critical Fix For: No Release Our application uses RSA crypto-j version 4.1. When executing a transaction we get the following error: java.lang.NoClassDefFoundError: com/rsa/cryptoj/c/di Although the class is present in the jar file (see attached screenshot). A sample .war that reproduces the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-8934) RejectedExecutionExceptions in management API

by David Lloyd (JIRA)

RejectedExecutionExceptions in management API --------------------------------------------- Key: JBAS-8934 URL: https://issues.jboss.org/browse/JBAS-8934 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: Kabir Khan Fix For: 7.0.0.Beta1 Running demos occasionally yields: Exception in thread "Read thread for localhost/127.0.0.1:9999" java.util.concurrent.RejectedExecutionException at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) at org.jboss.as.protocol.ConnectionImpl$1.run(ConnectionImpl.java:211) at java.lang.Thread.run(Thread.java:662) The created executors should most likely have a rejection policy of CallerRuns, and probably a longer queue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9101) Convert all native management communication to Remoting 3

by Brian Stansberry (JIRA)

Convert all native management communication to Remoting 3 --------------------------------------------------------- Key: JBAS-9101 URL: https://issues.jboss.org/browse/JBAS-9101 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Critical Fix For: 7.0.0.Beta3 Move the controller-client to ModelController and intra-domain comms from jboss-as-protocol to Remoting 3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Updated: (AS7-672) HostController status

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-672?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-672: --------------------------------- Assignee: (was: Brian Stansberry) Fix Version/s: 7.1.0.Beta1 (was: 7.0.0.CR1) > HostController status > --------------------- > > Key: AS7-672 > URL: https://issues.jboss.org/browse/AS7-672 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.1.0.Beta1 > > > Analogous to a server's status, but for a HostController. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9189) Interface selection for sockets bound to 0.0.0.0 is very likely to fail

by Heiko Rupp (JIRA)

Interface selection for sockets bound to 0.0.0.0 is very likely to fail ----------------------------------------------------------------------- Key: JBAS-9189 URL: https://issues.jboss.org/browse/JBAS-9189 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp Have two hosts DC and SL. When SL has its management interface bound to 0.0.0.0 (<any-ip-address> ) and it is connecting to the DC, it is sending its IP address to the DC, so that this knows how to talk to the SL. Now as the mgmt-interface is bound to 0.0.0.0, the server picks one IP address "randomly" and is very likely to pick one interface that has no route to the DC, thus making all interaction with the DC impossible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8634) ManagementRequest is not thread safe

by Brian Stansberry (JIRA)

ManagementRequest is not thread safe ------------------------------------ Key: JBAS-8634 URL: https://jira.jboss.org/browse/JBAS-8634 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Alpha2 The ManagementRequest class has a "responseBodyHandler" and a "responseEndHandler" and assumes those will not be executed concurrently, but they can be, since ConnectionImpl uses an executor to handle incoming chunks. One effect would be a null result gets passed to the ResponseFuture, as Thomas Diesler has reported in the linked forum thread. There may be other thread safety issues besides this particular one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-1295) CloseHandlers are not called when the remote connection closes

by Kabir Khan (JIRA)

CloseHandlers are not called when the remote connection closes -------------------------------------------------------------- Key: JBREM-1295 URL: https://issues.jboss.org/browse/JBREM-1295 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: David Lloyd THis is for 3.2.0 which does not appear in the version list Adding the following to org.jboss.remoting3.test.ChannelTestBase.java, the close handler does not get called. We discussed on IRC a few days ago but no matter what I do to close the channel this does not get called. Please provide a working example @Test public void testRemoteChannelClose() throws Exception { final CountDownLatch closedLatch = new CountDownLatch(1); sendChannel.addCloseHandler(new CloseHandler<Channel>() { @Override public void handleClose(Channel closed) { closedLatch.countDown(); } }); recvChannel.writeShutdown(); IoUtils.safeClose(recvChannel); System.out.println("Waiting for closed"); closedLatch.await(); System.out.println("Closed"); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1294) RemoteConnectionHandler leaks connections

by Kabir Khan (JIRA)

RemoteConnectionHandler leaks connections ----------------------------------------- Key: JBREM-1294 URL: https://issues.jboss.org/browse/JBREM-1294 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: David Lloyd 3.2.0 is not in the list of versions Nothing ever calls RemoteConnectionHandler.channels.remove -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

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 June 2011