January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=comments#action_12349926 ] Manik Surtani commented on JBCACHE-664: --------------------------------------- Will use java 5 concurrent libs. Need to hang on to concurrent.jar if we ship with jgroups 2.4.x. If we ship with 2.5, we could ditch concurrent.jar. > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0.GA > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0.BETA1, 2.0.0.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=all ] Manik Surtani updated JBCACHE-664: ---------------------------------- Fix Version/s: 2.0.0.BETA1 > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0.GA > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0.BETA1, 2.0.0.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=comments#action_12349927 ] Manik Surtani commented on JBCACHE-664: --------------------------------------- Reopened due to bug in current JBoss Retro (1.0.4.GA as well as snapshot): jbossretro: [mkdir] Created dir: /home/manik/Code/JBossCache200/output/classes14 [retro] Exception in thread "main" java.lang.NullPointerException [retro] at org.jboss.ant.tasks.retro.Weaver.rewriteEnum(Weaver.java:580) [retro] at org.jboss.ant.tasks.retro.Weaver.doWeave(Weaver.java:463) [retro] at org.jboss.ant.tasks.retro.Weaver.compileFile(Weaver.java:415) [retro] at org.jboss.ant.tasks.retro.Weaver.weave(Weaver.java:328) [retro] at org.jboss.ant.tasks.retro.Weaver.main(Weaver.java:110) > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0.GA > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0.BETA1, 2.0.0.GA > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.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

19 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3974) Remove versioned jars

by Dimitris Andreadis (JIRA)

Remove versioned jars --------------------- Key: JBAS-3974 URL: http://jira.jboss.com/jira/browse/JBAS-3974 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Get rid of versioned jars: commons-digester-1.6 commons-lang-2.1 bsh-3.0 antlr-xx -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-730) Failover valve fails to close

by Ovidiu Feodorov (JIRA)

Failover valve fails to close ----------------------------- Key: JBMESSAGING-730 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-730 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.Beta2 Attachments: messaging-clustering-client.log @Thread-31 23:42:54,734 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:192.168.1.101:2986] got new view [192.168.1.101:2986|2] [192.168.1.101:2986] @Thread-31 23:42:54,734 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:192.168.1.101:2986]: I am the failover node for node 1 that crashed @Thread-31 23:42:54,765 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[0:Clustered JMS:192.168.1.101:2986]: server side fail over is now complete @Thread-2 23:42:57,843 WARN [LeasePinger] Error sending lease ping to server for client invoker with session ID 5c4o12t-aoerq4-ewrfzj7d-1-ewrg14t5-2k @Thread-2 23:43:28,109 WARN [LeasePinger] Error sending lease ping to server for client invoker with session ID 5c4o12t-aoerq4-ewrfzj7d-1-ewrg062a-1m @Thread-2 23:43:58,390 WARN [LeasePinger] Error sending lease ping to server for client invoker with session ID 5c4o12t-aoerq4-ewrfzj7d-1-ewrfzmsp-p @Thread-2 23:44:29,078 WARN [LeasePinger] Error sending lease ping to server for client invoker with session ID 5c4o12t-aoerq4-ewrfzj7d-1-ewrg14t5-2k @Thread-17 23:45:10,187 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:15,187 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:20,187 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:25,203 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:30,203 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:35,203 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:40,203 WARN [Valve] Couldn't close valve, trying again java.lang.Exception at org.jboss.jms.client.FailoverValve.close(FailoverValve.java:156) at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:77) at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:56) at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83) at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:172) @Thread-17 23:45:45,203 WARN [Valve] Couldn't close valve, trying again -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-729) Multiple successive failover tests grind to a halt because of Remoting ConnectionValidator bug(s)

by Ovidiu Feodorov (JIRA)

Multiple successive failover tests grind to a halt because of Remoting ConnectionValidator bug(s) ------------------------------------------------------------------------------------------------- Key: JBMESSAGING-729 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-729 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-89) Allow Specifying Custom Interceptors in XML Configuration

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=all ] Manik Surtani updated JBCACHE-89: --------------------------------- Fix Version/s: 2.1.0.GA (was: 2.0.0.GA) Priority: Major (was: Critical) Pushing this back to 2.1.0 > Allow Specifying Custom Interceptors in XML Configuration > --------------------------------------------------------- > > Key: JBCACHE-89 > URL: http://jira.jboss.com/jira/browse/JBCACHE-89 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Daniel Gredler > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > Original Estimate: 1 day > Time Spent: 30 minutes > Remaining Estimate: 7 hours, 30 minutes > > It would be nice to be able to add interceptors via the XML configuration files. Indeed, in TreeCache.java the following comment exists, which may indicate that this feature is already planned: > // Create the interceptors in the correct order (later to be defined in XML file) > createInterceptorChain(); > A possible example configuration would be: > <server> > <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" /> > <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache"> > ... > <attribute name="Interceptors"> > <interceptor>com.foo.project.MyInterceptor</interceptor> > </attribute> > ... > </mbean> > </server> > Something along the lines of the following method would then be able to add the custom interceptors (in TreeCache.java): > public void setInterceptors(Element interceptors) throws Exception { > NodeList list = interceptors.getChildNodes(); > for(int i = 0; i < list.getLength(); i++) { > org.w3c.dom.Node node = list.item(i); > if(node.getNodeType() != org.w3c.dom.Node.ELEMENT_NODE) > continue; > NodeList children = node.getChildNodes(); > if(children.getLength() != 1) > continue; > org.w3c.dom.Node childNode = list.item(0); > if(childNode.getNodeType() != org.w3c.dom.Node.TEXT_NODE) > continue; > String className = childNode.getNodeValue(); > if(className == null || className.length() == 0) > continue; > Interceptor interceptor = createInterceptor(className); > addInterceptor(interceptor_chain, interceptor); > } > } -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-593) JBoss Cache features for JBoss AS 5.0

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-593?page=all ] Manik Surtani closed JBCACHE-593. --------------------------------- Fix Version/s: 2.0.0.ALPHA2 Resolution: Done > JBoss Cache features for JBoss AS 5.0 > ------------------------------------- > > Key: JBCACHE-593 > URL: http://jira.jboss.com/jira/browse/JBCACHE-593 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP1 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Fix For: 2.0.0.ALPHA2, 2.0.0.GA > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-322) Remove dead code

by Mark Little (JIRA)

Remove dead code ---------------- Key: JBESB-322 URL: http://jira.jboss.com/jira/browse/JBESB-322 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.0 CR2 Make sure any tests are updated too. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-321) cleanup org.jboss.soa.esb.listeners.message package

by Mark Little (JIRA)

cleanup org.jboss.soa.esb.listeners.message package --------------------------------------------------- Key: JBESB-321 URL: http://jira.jboss.com/jira/browse/JBESB-321 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 -- 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, 4 months

2
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 January 2007