October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBID-203) Remove test depencency on JBossXB from jboss-identity-fed-core

by Daniel Bevenius (JIRA)

Remove test depencency on JBossXB from jboss-identity-fed-core -------------------------------------------------------------- Key: JBID-203 URL: https://jira.jboss.org/jira/browse/JBID-203 Project: JBoss Identity Issue Type: Task Components: IDM Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: IDFED-1.0.0.beta3 I added jbossxb as a test dependency as this should be removed. This was a runtime dependency and I'll use a mock in the test instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-111) Restrict Jetty dep to test scope

by Andrew Lee Rubinger (JIRA)

Restrict Jetty dep to test scope -------------------------------- Key: JBBOOT-111 URL: https://jira.jboss.org/jira/browse/JBBOOT-111 Project: JBoss Bootstrap Issue Type: Task Components: impl-mc Affects Versions: impl-mc-2.0.0-alpha-3 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Add proper scoping so we don't leak this out -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7247) Create separate Hudson job for classloader leak tests

by Brian Stansberry (JIRA)

Create separate Hudson job for classloader leak tests ----------------------------------------------------- Key: JBAS-7247 URL: https://jira.jboss.org/jira/browse/JBAS-7247 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 The classloader leak tests can introduce instability into a testsuite run due to their need to try to force SoftReferences out of VM memory. When run without JVMTI available this involves deliberately overflowing memory, which is a) slow b) introduces instability. So, we want to remove these tests from the main testsuite run. But we still want them executed, so create a separate Hudson job to run them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1074) pom.xml

by Bulat Nigmatullin (JIRA)

pom.xml -------- Key: JGRP-1074 URL: https://jira.jboss.org/jira/browse/JGRP-1074 Project: JGroups Issue Type: Patch Reporter: Bulat Nigmatullin Assignee: Bela Ban -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-978) JGroups diagnostics uses hard-coded IPv4 multicast address

by Richard Achmatowicz (JIRA)

JGroups diagnostics uses hard-coded IPv4 multicast address ----------------------------------------------------------- Key: JGRP-978 URL: https://jira.jboss.org/jira/browse/JGRP-978 Project: JGroups Issue Type: Bug Reporter: Richard Achmatowicz Assignee: Bela Ban Priority: Minor Fix For: 2.8 When running JGroups using IPv6 bind and multicast addresses, the following messages appear on the console: > 20:21:36,565 WARN [UDP] failed to join /224.0.75.75:7500 on vif0.0: > java.net.SocketException: No such device > 20:21:36,566 WARN [UDP] failed to join /224.0.75.75:7500 on peth0: > java.net.SocketException: No such device > 20:21:36,566 WARN [UDP] failed to join /224.0.75.75:7500 on xenbr0: > java.net.SocketException: No such device The multicast address 224.0.75.75 is used by the JGroups diagnostics handler (in TP.java) to listen for incoming probe requests. Probe requests are issued from clients using Probe.java to find out which JGroups members are using UDP in a given network. These messages expose two issues: (i) JGroups is trying to join a multicast group on certain Xen virtual interfaces (vif0, peth0, xenbr0) and this is failing (ii) JGroups is using a fixed IPv4 multicast address, despite the fact that IPv6 addresses are being used as bind_addresses and multicast addreses. Something similar to the first issue was addressed in https://jira.jboss.org/jira/browse/JGRP-167.. As for the second issue, shouldn't JGroups use default IP addresses which correspond to the IP mode the JGroups instance has been started in (i.e. if JGroups instance bound to IPv4 bind address, use IPv4 diagnostics multicast address; if JGroups bound to IPv6 global address, use IPv6 global diagnostics multicast address, etc) This may very likely cause problems if JGroups is run in an IPv6 only environment, where IPv4 socket use is disallowed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

2
18
0 / 0

[JBoss JIRA] Created: (JBAS-4595) Inconclusive exception thrown by HttpNamingContextFactory

by Carlo de Wolf (JIRA)

Inconclusive exception thrown by HttpNamingContextFactory --------------------------------------------------------- Key: JBAS-4595 URL: http://jira.jboss.com/jira/browse/JBAS-4595 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Environment: Hudson only Sun VM 1.5.0_12-b04 Ubuntu 6.06 Reporter: Carlo de Wolf Priority: Minor Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA javax.naming.NamingException: Failed to retrieve Naming interface [Root exception is java.net.ConnectException: Connection refused] at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:84) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at org.jboss.ejb3.test.invoker.unit.InvokerTestCase.testHttp(InvokerTestCase.java:55) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.net.ConnectException: Connection refused at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1223) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1217) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:906) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:133) at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:80) ... 26 more 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.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) at sun.net.www.http.HttpClient.New(HttpClient.java:304) at sun.net.www.http.HttpClient.New(HttpClient.java:316) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:1903) at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:573) at java.net.URLConnection.getContentLength(URLConnection.java:468) at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:128) ... 27 more -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2310) Range fact

by Toni Rikkola (JIRA)

Range fact ---------- Key: JBRULES-2310 URL: https://jira.jboss.org/jira/browse/JBRULES-2310 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-verifier Reporter: Toni Rikkola Assignee: Toni Rikkola Fact that could be used to see what ranges are checked for a field of an object type. Currently range coverage is checked with a set of rules, those might provide enough info for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2309) Ability to follow changes done to the knowledge base

by Toni Rikkola (JIRA)

Ability to follow changes done to the knowledge base ---------------------------------------------------- Key: JBRULES-2309 URL: https://jira.jboss.org/jira/browse/JBRULES-2309 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-verifier Reporter: Toni Rikkola Assignee: Toni Rikkola For example Person( age > 18 ) changes to Person( age > 20) Ability to compare the features or follow the changes. Not just that the rule changed, but what changed in the rule. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2308) If only one rule changes it should not be needed to recreate all the data objects

by Toni Rikkola (JIRA)

If only one rule changes it should not be needed to recreate all the data objects --------------------------------------------------------------------------------- Key: JBRULES-2308 URL: https://jira.jboss.org/jira/browse/JBRULES-2308 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-verifier Reporter: Toni Rikkola Assignee: Toni Rikkola The data that is collected from the AST can be saved or used again. It would make things faster if it was possible to just update one rule or content of one resource instead of checking the entire AST everytime it runs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2307) Filterin for the verifier report

by Toni Rikkola (JIRA)

Filterin for the verifier report -------------------------------- Key: JBRULES-2307 URL: https://jira.jboss.org/jira/browse/JBRULES-2307 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-verifier Reporter: Toni Rikkola Assignee: Toni Rikkola Right now verifier reports all the issues that it finds. For huge knowledge bases this means a lot of useless reports and the important ones get lost in to the noise. Would be handy to check out some of the issues that were reported so that they don't appear again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

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