May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-20) Map the jboss TRACE level logging to log4j TRACE

by Dimitris Andreadis (JIRA)

Map the jboss TRACE level logging to log4j TRACE ------------------------------------------------ Key: JBCOMMON-20 URL: http://jira.jboss.com/jira/browse/JBCOMMON-20 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-old, logging-log4j Affects Versions: 1.0.4.GA, 2.0.1.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA, 2.0.4.GA See JBAS-4163 -- 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
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-22) Revert JBCOMMON-20 for JBossCommon 1.0.x

by Dimitris Andreadis (JIRA)

Revert JBCOMMON-20 for JBossCommon 1.0.x ---------------------------------------- Key: JBCOMMON-22 URL: http://jira.jboss.com/jira/browse/JBCOMMON-22 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Components: common-old Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: 1.0.5.GA JBCOMMON-20 needs to be reverted so that jboss common 1.0.5 can still be a drop-in-replacement that doesn't require a log4j upgrade. -- 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: (JBAS-4237) mail-ra should support encrypted connections

by Pete Muir (JIRA)

mail-ra should support encrypted connections -------------------------------------------- Key: JBAS-4237 URL: http://jira.jboss.com/jira/browse/JBAS-4237 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.0.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Javamail supports pop3s, imaps and imap/tls -- 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
2
0 / 0

[JBoss JIRA] Created: (JBREM-748) BisocketClientInvoker should guard agains scheduling on an expired Timer

by Ron Sigal (JIRA)

BisocketClientInvoker should guard agains scheduling on an expired Timer ------------------------------------------------------------------------ Key: JBREM-748 URL: http://jira.jboss.com/jira/browse/JBREM-748 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) In two places, org.jboss.remoting.transport.bisocket.BisocketClientInvoker schedules a PingTimerTask on the Timer referenced by the static variable timer. The problem is that if the Timer has been around for a while and all of its tasks have completed, it could have entered a state in which in can no longer schedule new tasks. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBREM-653) allow user to set content-type for http responses

by Tom Elrod (JIRA)

allow user to set content-type for http responses ------------------------------------------------- Key: JBREM-653 URL: http://jira.jboss.com/jira/browse/JBREM-653 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4 Reporter: Tom Elrod Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client. Should allow this to be overriden by the user in the same way the response code/message can be (using the response map). -- 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
13
0 / 0

[JBoss JIRA] Created: (JBREM-741) Eliminate unnecessary log.warn() in BisocketServerInvoker

by Ron Sigal (JIRA)

Eliminate unnecessary log.warn() in BisocketServerInvoker --------------------------------------------------------- Key: JBREM-741 URL: http://jira.jboss.com/jira/browse/JBREM-741 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.SP3 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.SP3 As described in the forum reference, the "unrecognized listener ID:" warning from BisocketServerInvoker.destroyControlConnection() can happen when the client and server are in the same JVM, so it should be reduced to DEBUG level. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBREM-732) When server terminates and has clients, when the server comes back up clients that survived, can't connect. Connection refused when trying to connect the control socket.

by Jay Howell (JIRA)

When server terminates and has clients, when the server comes back up clients that survived, can't connect. Connection refused when trying to connect the control socket. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBREM-732 URL: http://jira.jboss.com/jira/browse/JBREM-732 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA (Bluto) Reporter: Jay Howell Assigned To: Tom Elrod A client survives a server outage. When the server comes back up the survivor client tries to re-establish communictions and can't because the server is refusing the control socket connections. New clients are able to connect fine. This happens intermittantly. Here's the stack trace ..... [2007-03-30 10:47:51,770 ERROR] [Thread-10] bisocket.BisocketServerInvoker - [unable to create control connection after 10 retries] java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at java.net.Socket.<init>(Socket.java:366) at java.net.Socket.<init>(Socket.java:179) at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:217) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:328) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1544) at org.jboss.remoting.Client.addCallbackListener(Client.java:1613) at org.jboss.remoting.Client.addListener(Client.java:907) at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221) at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83) at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87) at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82) at com.rbos.fx.eCommerce.spreading.messaging.JMSConnector.makeConnection(JMSConnector.java:166) at com.rbos.fx.eCommerce.spreading.messaging.JMSConnector.getConnection(JMSConnector.java:141) at com.rbos.fx.eCommerce.spreading.messaging.JMSConnector$JMSExceptionListener.onException(JMSConnector.java:188) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:115) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346) -- 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
11
0 / 0

[JBoss JIRA] Created: (JBREM-734) BisocketClientInvoker constructor should get parameters from InvokerLocator as well as configuration map.

by Ron Sigal (JIRA)

BisocketClientInvoker constructor should get parameters from InvokerLocator as well as configuration map. --------------------------------------------------------------------------------------------------------- Key: JBREM-734 URL: http://jira.jboss.com/jira/browse/JBREM-734 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, the constructor just looks at the configuration map passed as a parameter. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBRULES-600) "Otherwise" feature to catch scenarios when no rules fired

by Michael Neale (JIRA)

"Otherwise" feature to catch scenarios when no rules fired ---------------------------------------------------------- Key: JBRULES-600 URL: http://jira.jboss.com/jira/browse/JBRULES-600 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 3.1-m1 Have had a few requests for features when "otherwise" is needed. Basically, in a rule set, when fireAllRules is called, an no "normal" rules activate and fire, rules declared as "otherwise" will then activate, presumably to cater for scenarios that have "fallen through the cracks" in typical business applications. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBRULES-580) no testing tool for the rule base

by Matt Shaw (JIRA)

no testing tool for the rule base --------------------------------- Key: JBRULES-580 URL: http://jira.jboss.com/jira/browse/JBRULES-580 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Eclipse IDE Reporter: Matt Shaw Assigned To: Mark Proctor At present there is no way of testing rule sets dynamically. I propose to develop an eclipse plugin which parses a rule base and allows the business to create scenarios from the rule base and then dynamically create beans which can than be used to input the data for the scenarios. -- 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
2
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 May 2007