February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SASL-28) Release JBoss SASL 1.0.0.GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-28: ------------------------------------ Summary: Release JBoss SASL 1.0.0.GA Key: SASL-28 URL: https://issues.jboss.org/browse/SASL-28 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Beta10 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (JGRP-1422) TP: reduce "no physical address for X; dropping message" warnings

by Bela Ban (JIRA)

Bela Ban created JGRP-1422: ------------------------------ Summary: TP: reduce "no physical address for X; dropping message" warnings Key: JGRP-1422 URL: https://issues.jboss.org/browse/JGRP-1422 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 This warning is caused by A attempting to send a unicast message to B, but the physical (IP) address of B is not in the cache (TP.logical_addr_cache). The logical_addr_cache is populated at startup, during the discovery phase. However, when we have 20 members and (PING.)num_initial_members is 3, we'll return after 3 responses. If we for example have {A,B,C,D,E,F,G,H} with A being the coordinator, a new joiner X returns after reception of (say) discovery responses of F, B and G. If X next tries to send a JOIN request to A, it will fail and drop the (unicast) request as the IP address for A is not yet present. Event worse: if X attempts to invoke a unicast RPC to any member P for which it doesn't have the IP address, and does *not* send any more messages (e.g. in a separate thread to P), then the RPC will timeout, unless we use UNICAST, which - using a positive ack scheme - keeps retransmitting the request until P sends an ack. The problem is that - when we don't have an IP address for P - we send a discovery request to fetch the IP address, but *drop* the current request. There are 2 levels at which we can fix this problem: #1 Make sure we receive at least the IP address of the coordinator at startup This is done by making sure (in the above example) that A's IP address is part of the response set before we return from the discovery phase. Note that when we send a discovery request, everybody will reply, but if we return after reception of the replies from B, F and G, we won't have the coordinator's address to send a JOIN request to. So #1 makes sure that we only return after having the coordinator's IP address. Note that this can still lead to problems when trying to send a unicast message to a different member, whose IP address we don't yet have ! This is solved in #2 below. #2 When asking for the IP address of P, don't drop the current message to P, but loop for a short time until the address has been fetched We don't block here, but simply loop for a limited time, in order to wait for the IP address. In most cases, this is not even necessary because #1 reduces the chances of an IP address not being available, but if it is, usually fetching an IP address takes a few millisconds. Looping just reduces the chances that we have to run into a timeout with a blocking unicast RPC, or wait until stability flushes the pending unicast, causing it to be retransmitted. Note that we increase the wait time on every loop iteration, to prevent discovery storms. Plus, we also stagger the discovery request: if 2 threads T1 and T2 trigger a discovery at time 30 and 120 respectively, then T2 will *not* send a discovery request, as it also has the IP address by means of the discovery request triggered by T1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-3603) Release and upgrade org.jboss.remoting3.remoting-jmx to GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3603: ------------------------------------- Summary: Release and upgrade org.jboss.remoting3.remoting-jmx to GA Key: AS7-3603 URL: https://issues.jboss.org/browse/AS7-3603 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3602) Release and upgrade org.jboss.com.sun.httpserver to GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3602: ------------------------------------- Summary: Release and upgrade org.jboss.com.sun.httpserver to GA Key: AS7-3602 URL: https://issues.jboss.org/browse/AS7-3602 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3594) Windows path problems with resource builder

by Jason Greene (JIRA)

Jason Greene created AS7-3594: --------------------------------- Summary: Windows path problems with resource builder Key: AS7-3594 URL: https://issues.jboss.org/browse/AS7-3594 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Jason Greene Assignee: Thomas Diesler Fix For: 7.1.0.Final From: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-windows... Caused by: java.lang.IllegalStateException: java.io.FileNotFoundException: C:\Users\jenkins\jenkins-work\workspace\as7-master-windows-build\build\target\jboss-as-7.1.0.Final-SNAPSHOT\modules\rg\jboss\netty\main\netty-3.2.6.Final.jar (The system cannot find the path specified) at org.jboss.osgi.resolver.v2.spi.URLBasedResource.getContent(URLBasedResource.java:96) [jbosgi-repository-api-1.0.4.jar:1.0.4] at org.jboss.osgi.resolver.v2.XResourceBuilder.create(XResourceBuilder.java:95) [jbosgi-repository-api-1.0.4.jar:1.0.4] at org.jboss.as.osgi.service.ModuleIdentityArtifactProvider.findProviders(ModuleIdentityArtifactProvider.java:133) [jboss-as-osgi-service-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 16 more Caused by: java.io.FileNotFoundException: C:\Users\jenkins\jenkins-work\workspace\as7-master-windows-build\build\target\jboss-as-7.1.0.Final-SNAPSHOT\modules\rg\jboss\netty\main\netty-3.2.6.Final.jar (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) [rt.jar:1.6.0_30] at java.io.FileInputStream.<init>(FileInputStream.java:120) [rt.jar:1.6.0_30] at org.jboss.osgi.resolver.v2.spi.URLBasedResource.getContent(URLBasedResource.java:91) [jbosgi-repository-api-1.0.4.jar:1.0.4] ... 18 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3500) Add org/w3c/dom/views to the javax.api module

by Robert Reimann (JIRA)

Robert Reimann created AS7-3500: ----------------------------------- Summary: Add org/w3c/dom/views to the javax.api module Key: AS7-3500 URL: https://issues.jboss.org/browse/AS7-3500 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Please add the org/w3c/dom/views path to the javax.api module. {code} <path name="org/w3c/dom/views"/> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1291) UserTransaction not exposed in JDNI

by Juergen Zimmermann (JIRA)

UserTransaction not exposed in JDNI ----------------------------------- Key: AS7-1291 URL: https://issues.jboss.org/browse/AS7-1291 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey In JBoss 6 UserTransaction was exposed in JNDI named as java:comp/UserTransaction. Thus an Arquillian test method could be encapsulated in one single transaction: * lookup() the UserTransaction * begin() inside @Before * commit() inside @After Unfortunately, JBoss 7 doesn't have a JNDI entry for UserTransaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
11
0 / 0

[JBoss JIRA] (JBRULES-3372) kbase.addKnowledgePackages() infinite loop

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3372: ----------------------------------------- Summary: kbase.addKnowledgePackages() infinite loop Key: JBRULES-3372 URL: https://issues.jboss.org/browse/JBRULES-3372 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.4.0.Beta2 Reporter: Esteban Aliverti Assignee: Mark Proctor Attachments: testProject.zip I have attached a simple project containing just 1 rule and some model classes. The rule is compiled ok, but when I try to add the generated package to a kbase, an infinite-loop (or what it seems like an infinite-loop) occurs. If you remove some of the patterns in the rule, everything works fine. I have debugged up to RuleTerminalNode.networkUpdated(). The execution never returns from that method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-3598) It's impossible to add and activate resource adapter after .rar deployment

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-3598: ---------------------------------------- Summary: It's impossible to add and activate resource adapter after .rar deployment Key: AS7-3598 URL: https://issues.jboss.org/browse/AS7-3598 Project: Application Server 7 Issue Type: Bug Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.0.Final 1.Deploy .rar archive 2.Add resource-adapters subsytem configuration for this .rar by DMR API 3.Try to proceed "activate" operation. Get error: "rar is not deployed yet" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

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 February 2012