October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-207) Factor out container and classloading projects from mc

by Scott M Stark (JIRA)

Factor out container and classloading projects from mc ------------------------------------------------------ Key: JBMICROCONT-207 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-207 Project: JBoss MicroContainer Issue Type: Task Affects Versions: JBossMC-2.0.0.Beta4 Reporter: Scott M Stark Fix For: JBossMC-2.0.0.CR1 There is a circular dependency between aop and mc due to aop depending on the container project. Both the container and classloader projects need to be moved out of the mc. -- 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 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-206) The JMXLifecycleCallback should be registering with the ServiceController inside the appserver

by Adrian Brock (JIRA)

The JMXLifecycleCallback should be registering with the ServiceController inside the appserver ---------------------------------------------------------------------------------------------- Key: JBMICROCONT-206 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-206 Project: JBoss MicroContainer Issue Type: Sub-task Components: General Affects Versions: JBossMC-2.0.0.Beta4 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 The JMXLifecycleCallback needs to be made extensible so that in JBossAS we can do the registration with the ServiceController instead of directly with the MBeanServer. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-959) Investigate performance delta with MR3 and 3.0.6

by Michael Neale (JIRA)

Investigate performance delta with MR3 and 3.0.6 ------------------------------------------------ Key: JBRULES-959 URL: http://jira.jboss.com/jira/browse/JBRULES-959 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.0.MR3 Reporter: Michael Neale Assigned To: Michael Neale // Rule execution time test // I give the DRL one fact of class BOBOMessage (made final due to Michael's suggestion) // The "message" member of my BOBOMessage fact contains a random combination of the keywords the rule is designed to match // A random BOBOMessage like that is generated before every execution // MR3's performance: 11:43:01,135 INFO [RuleLoadBean] Average rule execution time in ms: 2.3991 // What is measured: ruleBase = rsl.getGroupRuleBase(group); // That retrieves the RuleBase from the cache StatelessSession session = ruleBase.newStatelessSession(); session.execute(toBeAsserted.get(group.getId()).toArray()); // 3.0.6's performance: 12:09:40,446 INFO [RuleLoadBean] Average rule execution time in ms: 0.7726 // What is measured: ruleBase = rsl.getGroupRuleBase(group); // That retrieves the RuleBase from the cache WorkingMemory wm = ruleBase.newWorkingMemory(); for (Iterator j = toBeAsserted.get(group.getId()).iterator(); j.hasNext();) wm.assertObject(j.next()); wm.fireAllRules(); // The DRL: package com.smsc.mitto.rules import com.smsc.mitto.rules.client.BOBOMessage; import java.lang.String; rule "14" salience 0 activation-group "14" when m : BOBOMessage( message matches ".*BOBO.*") then System.out.println( "BOBO WAS SEEN" ); System.out.println( "BOBO WAS REALLY SEEN, DUDE" ); drools.setFocus( "17" ); end rule "17" salience -20 agenda-group "17" activation-group "17" when m : BOBOMessage( message matches ".*CACA.*") then System.out.println( "CACA WAS SEEN" ); drools.setFocus( "19" ); end rule "19" salience -10 agenda-group "19" activation-group "19" when m : BOBOMessage( message matches ".*BABA.*") then System.out.println( "BABA WAS SEEN" ); drools.setFocus( "21" ); end rule "19false" salience -20 agenda-group "19" activation-group "19" when eval(true) then drools.setFocus( "21" ); end rule "21" salience -20 agenda-group "21" activation-group "21" when m : BOBOMessage( message matches ".*BIBI.*") then System.out.println( "BIBI WAS SEEN" ); drools.setFocus( "23" ); end rule "21false" salience -30 agenda-group "21" activation-group "21" when eval(true) then drools.setFocus( "23" ); end rule "17false" salience -30 agenda-group "17" activation-group "17" when eval(true) then drools.setFocus( "23" ); end rule "23" salience -30 agenda-group "23" activation-group "23" when m : BOBOMessage( message matches ".*POOP.*") then System.out.println( "POOP WAS SEEN" ); drools.setFocus( "25" ); end rule "23false" salience -40 agenda-group "23" activation-group "23" when eval(true) then drools.setFocus( "25" ); end rule "14false" salience -10 agenda-group "14" activation-group "14" when eval(true) then drools.setFocus( "25" ); end rule "25" salience -10 agenda-group "25" activation-group "25" when m : BOBOMessage( message matches ".*SUPER.*") then System.out.println( "SUPER WAS SEEN" ); end -- 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 months

4
8
0 / 0

[JBoss JIRA] Created: (JGRP-444) RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH

by Michael Newcomb (JIRA)

RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH ----------------------------------------------------------------- Key: JGRP-444 URL: http://jira.jboss.com/jira/browse/JGRP-444 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: 2.5 alpha 2 Reporter: Michael Newcomb Assigned To: Bela Ban private void handleRequest(Message req, Header hdr) { ... rsp=req.makeReply(); if(rsp_buf != null) rsp.setBuffer(rsp_buf); rsp_hdr=new Header(Header.RSP, hdr.id, false, name); rsp.putHeader(name, rsp_hdr); // *************** patch ***************** // can't check for FLUSH.FlushHeader.BYPASS_FLUSH because it has package protection, so just check for FLUSH header // if (req.getHeader(org.jgroups.protocols.pbcast.FLUSH.NAME) != null) { rsp.putHeader(org.jgroups.protocols.pbcast.FLUSH.NAME, new org.jgroups.protocols.pbcast.FLUSH.FlushHeader(org.jgroups.protocols.pbcast.FLUSH.FlushHeader.FLUSH_BYPASS)); } // *************** patch ***************** if(log.isTraceEnabled()) log.trace(new StringBuffer("sending rsp for ").append(rsp_hdr.id).append(" to ").append(rsp.getDest())); ... } -- 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 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4242) Port Hibernate depoyer to VDF

by Scott M Stark (JIRA)

Port Hibernate depoyer to VDF ----------------------------- Key: JBAS-4242 URL: http://jira.jboss.com/jira/browse/JBAS-4242 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Hibernate service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.Beta3 The current hibernate integration tests are broken in jboss5 trunk, and the deployer needs to be ported to the VDF (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework). This really should be done in concert with the ejb3 deployer refactoring as there should be minimal duplication of the various deployment aspects related to persistence. -- 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 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1307) Update and expand documentation for decision tables to show actual uses for all keywords

by John Scott (JIRA)

Update and expand documentation for decision tables to show actual uses for all keywords ---------------------------------------------------------------------------------------- Key: JBRULES-1307 URL: http://jira.jboss.com/jira/browse/JBRULES-1307 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2, Reporter: John Scott Priority: Minor I'm trying to implement a decision table for implementing some very simple rules. Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method. I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description: "Indicates that if there cell values in this column, the no-loop attribute should be set" In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive. Which column? What values? The no-loop attribute SHOULD be set? Would it be possible to show an example of where and how each of these keywords would be used? These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these. I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this. Thanks -- 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 months

4
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-257) Not efficient admin view

by Ryszard Kozmik (JIRA)

Not efficient admin view ------------------------ Key: JBFORUMS-257 URL: http://jira.jboss.com/jira/browse/JBFORUMS-257 Project: JBoss Forums Issue Type: Bug Components: Forum Model Layer, Forum View Layer Reporter: Ryszard Kozmik Fix For: 1.0.1 RC, 1.1.0 Alpha When having lots of forums/categories in database, admin view breaks due to model layer problems. Probably something was messed up while doing view refactoring. -- 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 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-697) First concurrent call doesn't throw exception

by Carlo de Wolf (JIRA)

First concurrent call doesn't throw exception --------------------------------------------- Key: EJBTHREE-697 URL: http://jira.jboss.com/jira/browse/EJBTHREE-697 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD Concurrency check is in the server interceptor, while identity is established in the proxy after the first call. So if the first call is concurrent no exception is thrown. (see unit test concurrent) -- 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 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-826) JBoss Remoting logs at ERROR and WARN in many places

by Tim Fox (JIRA)

JBoss Remoting logs at ERROR and WARN in many places ---------------------------------------------------- Key: JBREM-826 URL: http://jira.jboss.com/jira/browse/JBREM-826 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tim Fox Fix For: 2.4.0.Beta1 (Pinto) In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate. JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs. There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd Failover in JBoss Messaging is a good example. In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless. However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example: @main 08:01:30,648 INFO [ServerManagement] Waiting for server to die @main 08:01:30,953 INFO [ServerManagement] server 1 killed and dead @Timer-3 08:01:31,253 ERROR [SocketClientInvoker] Got marshalling exception, exiting java.net.SocketException: end of file at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) @Thread-9 08:01:31,277 WARN [ClientClusteredConnectionFactoryDelegate] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152) at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168) at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:93) at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452) Caused by: java.net.ConnectException: Connection refused 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 org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525) ... 9 more @Thread-9 08:01:31,299 WARN [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat] SERVER 0 STDOUT: @Timer-4 08:01:31,301 ERROR [SocketClientInvoker] Got marshalling exception, exiting SERVER 0 STDOUT: java.net.SocketException: end of file SERVER 0 STDOUT: at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577) SERVER 0 STDOUT: at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413) SERVER 0 STDOUT: at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) @Thread-9 08:01:31,320 WARN [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed sending disconnect for client lease for client with session ID 3j001-bj8ucn-f8e4sbxc-1-f8e4sbxd-2 SERVER 0 STDOUT: at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133) SERVER 0 STDOUT: at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308) SERVER 0 STDOUT: at java.util.TimerThread.mainLoop(Timer.java:512) SERVER 0 STDOUT: at java.util.TimerThread.run(Timer.java:462) @Thread-9 08:01:31,345 WARN [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?cli This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience. If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config. In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated. -- 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 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1286) Incorrect information in section 2.5.7.3. Agenda Filters

by Sergey Manukyan (JIRA)

Incorrect information in section 2.5.7.3. Agenda Filters -------------------------------------------------------- Key: JBRULES-1286 URL: http://jira.jboss.com/jira/browse/JBRULES-1286 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Manual Affects Versions: 4.0.2 Reporter: Sergey Manukyan Assigned To: Mark Proctor CORRECTION #1 Manual states : To use a filter specify it while calling FireAllRules. The following example will filter out all rules ending with the text "Test": workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) ); Should be: To use a filter specify it while calling FireAllRules. The following example will only allow activation of rules ending with the text "Test". All others will be filtered out.: workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) ); CORRECTION #2 Manual states : RuleNameEndWithAgendaFilter Should be : RuleNameEndsWithAgendaFilter -- 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 months

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