October 2007 - jboss-jira - Jboss List Archives

[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

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

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

1
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1254) drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api

by Geoffrey De Smet (JIRA)

drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api ----------------------------------------------------------------------------------------------------------- Key: JBRULES-1254 URL: http://jira.jboss.com/jira/browse/JBRULES-1254 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Fix For: 4.0.2 log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves. In examples you'll probably want to make them runtime scoped. slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway. See drools-repository/pom.xml where I 've commented what I propose to change: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <scope>test</scope> </dependency> -- 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

3
5
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

3
2
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

4
11
0 / 0

[JBoss JIRA] Created: (JBRULES-666) JCR to SVN integration

by Michael Neale (JIRA)

JCR to SVN integration ---------------------- Key: JBRULES-666 URL: http://jira.jboss.com/jira/browse/JBRULES-666 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-899) auto import classes from a jar when uploading

by Michael Neale (JIRA)

auto import classes from a jar when uploading --------------------------------------------- Key: JBRULES-899 URL: http://jira.jboss.com/jira/browse/JBRULES-899 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.MR2 Reporter: Michael Neale Assigned To: Michael Neale if package header is empty, slap in imports (assuming there is a way to efficiently work them out/guess them). -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-952) Remove repo reference to http://maven.softeu.cz from POMs

by Eric Miles (JIRA)

Remove repo reference to http://maven.softeu.cz from POMs --------------------------------------------------------- Key: JBRULES-952 URL: http://jira.jboss.com/jira/browse/JBRULES-952 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: Fedora 7, Sun J2SE 1.5.0_12 Reporter: Eric Miles Assigned To: Mark Proctor The reference to a particular repository makes building jbossrules from source a real bear. This is also an issue for someone using jbossrules for the first time as it downloads dependencies, it "hangs" while attempting to download something from this site (maven.softeu.cz). I know there is a workaround for this by either installing the the necessary dependencies in your local repo or in your own remote repo, however this is less than desirable. -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1280) Automatically import types into a package config if no config exists

by Michael Neale (JIRA)

Automatically import types into a package config if no config exists -------------------------------------------------------------------- Key: JBRULES-1280 URL: http://jira.jboss.com/jira/browse/JBRULES-1280 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: FUTURE based on what it finds in the jar. -- 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

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 October 2007