September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-698) Could not maintain metadata on nexus repository

by Tomáš Remeš (JIRA)

Could not maintain metadata on nexus repository ----------------------------------------------- Key: JBBUILD-698 URL: https://issues.jboss.org/browse/JBBUILD-698 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Tomáš Remeš clicking on istack-commons-runtime 1.1.SNAPSHOT.jar gets "Could not maintain metadata. Nexus returned an error: ERROR 500: Internal Server Error" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1356) Error starting shared transport causes future channels using it to fail

by Dennis Reed (JIRA)

Error starting shared transport causes future channels using it to fail ----------------------------------------------------------------------- Key: JGRP-1356 URL: https://issues.jboss.org/browse/JGRP-1356 Project: JGroups Issue Type: Bug Affects Versions: 2.6.20 Reporter: Dennis Reed Assignee: Bela Ban When a shared singleton transport started in Configurator#startProtocolStack throws an exception during TP#start, it is not rolled back. Future channels created with the same singleton transport try to use the failed instance. If there is an exception in start, either: - The transport should be removed or stopped, and future channels should try to start it again - The exception should be saved, and future channels using the same transport should get the same exception when started -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1331) Digest: remove low seqno

by Bela Ban (JIRA)

Digest: remove low seqno ------------------------ Key: JGRP-1331 URL: https://issues.jboss.org/browse/JGRP-1331 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.1 We don't need Digest.Entry.low_seqno for NakReceiverWindow anymore. We only need it for the Retransmitter implementations. If we can remove that last dependency, e.g. by storing the last seqno removed from a retransmitter, we can remove low_seqno from a digest. This is significant, for example if we have 100 nodes, a digest includes 300 longs:(low+highest_received+highest_delivered) * 100. If we remove low_seqno, we only have 200 longs. (These will still be further compressed in a different JIRA). This is important for large clusters, to reduce the size of STABLE messages and views. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
11
0 / 0

[JBoss JIRA] Created: (JGRP-1358) Documentation problem with port_range

by Jean-Philippe Gariepy (JIRA)

Documentation problem with port_range ------------------------------------- Key: JGRP-1358 URL: https://issues.jboss.org/browse/JGRP-1358 Project: JGroups Issue Type: Bug Affects Versions: 2.12 Environment: Linux Reporter: Jean-Philippe Gariepy Assignee: Bela Ban Priority: Minor port_range for TCP is document as infinite if 0. This does not seem to be the case. If I start a second node, I got: Caused by: java.net.BindException: No available port to bind to in range [7800 .. 7800] at org.jgroups.util.Util.createServerSocket(Util.java:3051) at org.jgroups.blocks.TCPConnectionMap.<init>(TCPConnectionMap.java:88) at org.jgroups.blocks.TCPConnectionMap.<init>(TCPConnectionMap.java:55) at org.jgroups.protocols.TCP.createConnectionMap(TCP.java:130) at org.jgroups.protocols.TCP.start(TCP.java:64) at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:990) at org.jgroups.JChannel.startStack(JChannel.java:1784 0 is useful to indicate that only one port should be used (bind_port+0). Magic value for infinite should rather be -1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1659) TestNG arquillian test in as-client mode not working

by Martin Kouba (JIRA)

TestNG arquillian test in as-client mode not working ---------------------------------------------------- Key: AS7-1659 URL: https://issues.jboss.org/browse/AS7-1659 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Martin Kouba Assignee: Andrew Rubinger Priority: Blocker {code} {code} 15:07:52,888 WARN [org.jboss.modules] (MSC service thread 1-1) Failed to define class org.jboss.cditck.arquillian.client.ClientTest in Module "deployment.test.jar:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/jboss/cditck/arquillian/client/ClientTest (Module "deployment.test.jar:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:401) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) at org.jboss.modules.Module.loadModuleClass(Module.java:588) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101) at org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:82) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:81) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) [jboss-as-weld-7.0.1.Final.jar:7.0.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: java.lang.NoClassDefFoundError: org/jboss/arquillian/testng/Arquillian at java.lang.ClassLoader.defineClass1(Native Method) [:1.6.0_22] at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [:1.6.0_22] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [:1.6.0_22] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:397) ... 19 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMETA-336) jboss-ejb3.xml ignores metadata-complete

by Carlo de Wolf (JIRA)

jboss-ejb3.xml ignores metadata-complete ---------------------------------------- Key: JBMETA-336 URL: https://issues.jboss.org/browse/JBMETA-336 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Affects Versions: 7.0.0.Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-1357) Support not only zip but snappy compression algorithm from Google in jgroups replicationSupport not only zip but snappy compression algorithm from Google in jgroups replication. > Snappy is a really fast compression algorithm compared to zip.

by Magnus Magnus (JIRA)

Support not only zip but snappy compression algorithm from Google in jgroups replicationSupport not only zip but snappy compression algorithm from Google in jgroups replication. > Snappy is a really fast compression algorithm compared to zip. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JGRP-1357 URL: https://issues.jboss.org/browse/JGRP-1357 Project: JGroups Issue Type: Feature Request Reporter: Magnus Magnus Assignee: Bela Ban Fix For: 2.4.10, 2.12.2, 3.0 Support not only zip but snappy compression algorithm from Google in jgroups replication. Snappy is a really fast compression algorithm compared to zip. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1697) Methods with arrays in their signature cannot be resolved from the annotation index

by Stuart Douglas (JIRA)

Methods with arrays in their signature cannot be resolved from the annotation index ----------------------------------------------------------------------------------- Key: AS7-1697 URL: https://issues.jboss.org/browse/AS7-1697 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas Priority: Critical Jandex is using [Ljava/lang/String; while the reflection API uses [Ljava.lang.String; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3193) Modify block does not work with variables declared in the consequence

by Edson Tirelli (JIRA)

Modify block does not work with variables declared in the consequence --------------------------------------------------------------------- Key: JBRULES-3193 URL: https://issues.jboss.org/browse/JBRULES-3193 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.3.0.Beta1, 5.2.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.3.0.CR1 Reported by Wolfgang: ======== This rule {code:title=test.drl|borderStyle=solid} rule "test" when $l : ArrayList() from collect (MyClass (attribute == false)); then for(Object o : new ArrayList( $l )) { MyClass o2 = (MyClass) o; modify(o2) { setAttribute(true) } } end {code} does not compile: The method setAttribute(boolean) is undefined for the type Object This, however, works: {code} modify( (MyClass)o) { setAttribute(true) } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1698) EJB @Asynchronous invocations

by Stuart Douglas (JIRA)

EJB @Asynchronous invocations ----------------------------- Key: AS7-1698 URL: https://issues.jboss.org/browse/AS7-1698 Project: Application Server 7 Issue Type: Task Components: EJB Affects Versions: 7.0.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 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 September 2011