June 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-730) Arquillian Managed Container Startup Timeout Message is wrong

by Andrew Rubinger (JIRA)

Arquillian Managed Container Startup Timeout Message is wrong ------------------------------------------------------------- Key: AS7-730 URL: https://issues.jboss.org/browse/AS7-730 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Andrew Rubinger Assignee: Andrew Rubinger Fix For: 7.0.0.CR1 Caused by: java.util.concurrent.TimeoutException: Managed server was not started within [0] ms at org.jboss.as.arquillian.container.managed.JBossAsManagedContainer.start(JBossAsManagedContainer.java:121) ... 74 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Updated: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package

by Alessandro Lazarotti (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ] Alessandro Lazarotti updated JBRULES-3063: ------------------------------------------ Fix Version/s: FUTURE Affects Version/s: 5.1.1.FINAL Component/s: drools-compiler > Drools should not allow set two rules with the same name for the same package > ----------------------------------------------------------------------------- > > Key: JBRULES-3063 > URL: https://issues.jboss.org/browse/JBRULES-3063 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: drools-compiler > Affects Versions: 5.1.1.FINAL > Reporter: Alessandro Lazarotti > Assignee: Tihomir Surdilovic > Priority: Minor > Fix For: FUTURE > > > Drools should not allow set two rules with the same name for the same package > As expected, Drools does not allow us to define two rules with the same name in a same DRL file. > But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence. > From documentation: > "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1] > [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB... > Different behavior for a similar action is not good. Both should alert user about a rule name repeated. > For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ] Toshiya Kobayashi moved BRMS-597 to JBRULES-3063: ------------------------------------------------- Project: Drools (was: JBoss Enterprise BRMS Platform) Key: JBRULES-3063 (was: BRMS-597) Affects Version/s: (was: 5.1.0 GA) Component/s: (was: BRE) Fix Version/s: (was: future) > Drools should not allow set two rules with the same name for the same package > ----------------------------------------------------------------------------- > > Key: JBRULES-3063 > URL: https://issues.jboss.org/browse/JBRULES-3063 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Alessandro Lazarotti > Assignee: Tihomir Surdilovic > Priority: Minor > > Drools should not allow set two rules with the same name for the same package > As expected, Drools does not allow us to define two rules with the same name in a same DRL file. > But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence. > From documentation: > "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1] > [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB... > Different behavior for a similar action is not good. Both should alert user about a rule name repeated. > For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (LOGTOOL-19) Var args not being implemented for BasicLogger

by James Perkins (JIRA)

Var args not being implemented for BasicLogger ---------------------------------------------- Key: LOGTOOL-19 URL: https://issues.jboss.org/browse/LOGTOOL-19 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.Beta8 When extending basic logger the var arg methods are not implementing var args. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9399) URL.getContent() returns VirtualFile instead of ImageProducer in JBoss AS 6.0.0.FINAL

by Nathan Blomquist (JIRA)

URL.getContent() returns VirtualFile instead of ImageProducer in JBoss AS 6.0.0.FINAL ------------------------------------------------------------------------------------- Key: JBAS-9399 URL: https://issues.jboss.org/browse/JBAS-9399 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: 6.0.0.Final Environment: Windows XP Reporter: Nathan Blomquist URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When the same jar is used from within JBoss, a VirtualFile is returned which then causes a ClassCastException. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (LOGTOOL-18) Suppress deprecated logging warnings

by James Perkins (JIRA)

Suppress deprecated logging warnings ------------------------------------ Key: LOGTOOL-18 URL: https://issues.jboss.org/browse/LOGTOOL-18 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.Beta8 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-1924) Pressing button Graph Dataset in Snapshot breaks JBoss AS

by Niels Bischof (JIRA)

[ https://issues.jboss.org/browse/JBAS-1924?page=com.atlassian.jira.plugin.... ] Niels Bischof commented on JBAS-1924: ------------------------------------- It seems, the system property java.awt.headless=true has to be set to work around this problem. The line: JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true" in /etc/sysconfig/jboss fixed the problem for me (on JBoss-6.0.0.Final). BTW, the problem is not a new one: https://issues.jboss.org/browse/SOA-227 > Pressing button Graph Dataset in Snapshot breaks JBoss AS > --------------------------------------------------------- > > Key: JBAS-1924 > URL: https://issues.jboss.org/browse/JBAS-1924 > Project: Legacy JBoss Application Server 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.2 Final > Environment: #CPU: 1 > OS: Linux 2.4.21-215-default (i386) > JVM Version: 1.4.2-b28 (Sun Microsystems Inc.) > JVM Name: Java HotSpot(TM) Server VM > Version: 4.0.2(build: CVSTag=JBoss_4_0_2 date=200505022023) > Reporter: Werner Frerichs > > I created A Snapshot for FreeMemory with the web-console with Time Period 1000, start the snapshot in the web-console wih Start Snapshot and wait for a few minutes. Pressing the button Show Dataset show me the values. > When Pressing the button Show Dataset in the web-console Jboss breaks immediatly and killed every running JBoss tasks. In the console where I started Jboss stand the following: > X11 connection rejected because of wrong authentication. > In the Logfile from Jboss for STDOUT stand the following: > X connection to localhost:12.0 broken (explicit kill or server shutdown). > In server/all/log/server.log I cannot find anything belong to this error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2112) Cannot build Drools IDE w/ OpenJDK 6 (vm crashes)

by Nick Boldt (JIRA)

Cannot build Drools IDE w/ OpenJDK 6 (vm crashes) ------------------------------------------------- Key: JBRULES-2112 URL: https://jira.jboss.org/jira/browse/JBRULES-2112 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Boldt Assignee: Mark Proctor Drools 5.0.x can compile with OpenJDK6; Drools 5.1 cannot. See attached logs. This prevents the JBoss Tools build from being able to run locally on Fedora w/ the out-of-box JVM (Open JDK 6). -- 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

15 years

6
9
0 / 0

[JBoss JIRA] Created: (JBNAME-55) jnp-client.jar doesn't have proper information in MANIFEST.MF

by Peter Skopek (JIRA)

jnp-client.jar doesn't have proper information in MANIFEST.MF ------------------------------------------------------------- Key: JBNAME-55 URL: https://issues.jboss.org/browse/JBNAME-55 Project: JBoss Naming Issue Type: Bug Components: jnp-client Reporter: Peter Skopek While checking if build contains proper version of jboss security jars, I have found that some of the jars don't have proper information in MANIFEST.MF and jar-versions.xml. jnp-client.jar MANIFEST.MF contains for example this: Manifest-Version: 1.0 Specification-Title: @specification.title@ Archiver-Version: Plexus Archiver Built-By: mockbuild Created-By: @java.vm.version@ (@java.vm.vendor@) Specification-Version: @specification.version@ Implementation-Vendor-Id: @implementation.vendor.id@ Implementation-URL: @implementation.url@ Build-Jdk: 1.5.0_20 Ant-Version: Apache Ant 1.7.1 Implementation-Title: @implementation.title@ Specification-Vendor: @specification.vendor@ Implementation-Version: @implementation.version@ Implementation-Vendor: @implementation.vendor@ Can this be fixed, please? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (AS7-875) Rename connector subsystem

by Jesper Pedersen (JIRA)

Rename connector subsystem -------------------------- Key: AS7-875 URL: https://issues.jboss.org/browse/AS7-875 Project: Application Server 7 Issue Type: Task Components: JCA Affects Versions: 7.0.0.Beta3 Reporter: Jesper Pedersen Assignee: Stefano Maestri Priority: Critical Fix For: 7.0.0.CR1 Rename the "connector" subsystem to "ironjacamar" such that it is clear what the subsystem is. The internal names can stay the same - that can be changed later. Sources stay under connector/. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
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 June 2011