April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-443) Release drools binaries with debug information

by Juergen none (JIRA)

Release drools binaries with debug information ---------------------------------------------- Key: JBRULES-443 URL: http://jira.jboss.com/jira/browse/JBRULES-443 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial Would it be possible to supply a debug-build of the binaries in addition to the existing downloads (where at least the drools jar files are without debug-info)? -- 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

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9075) Ability to specify rollout plans via the CLI

by Brian Stansberry (JIRA)

Ability to specify rollout plans via the CLI -------------------------------------------- Key: JBAS-9075 URL: https://issues.jboss.org/browse/JBAS-9075 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 Handle rollout plans as detailed in http://community.jboss.org/docs/DOC-16336. In Beta1 these would probably work via :some-op(foo=bar,rollout-plan={...complicated DMR...}). This task is to look for something more user friendly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
7
0 / 0

[JBoss JIRA] Created: (JBAS-9090) Ensure all subsystems have a proper "remove" operation

by Brian Stansberry (JIRA)

Ensure all subsystems have a proper "remove" operation ------------------------------------------------------ Key: JBAS-9090 URL: https://issues.jboss.org/browse/JBAS-9090 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Validate remove handling for all subsystems. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
10
0 / 0

[JBoss JIRA] Created: (JGRP-1002) Merge: make the coordinator remain the same if possible after a merge

by Bela Ban (JIRA)

Merge: make the coordinator remain the same if possible after a merge --------------------------------------------------------------------- Key: JGRP-1002 URL: https://jira.jboss.org/jira/browse/JGRP-1002 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 When we have {C, A, B} and split into {C,A} and {B}, then a merge will produce {A,B,C}. Therefore the coord is moved from C to A. For certain apps, e.g. JBoss singletons, this is not good, as we're moving the singleton services from a perfectly healthy node to a different node. GOAL: come up with a deterministic policy of picking a coord such that we minimize coord switching if the existing coord is still member of the cluster. This depends on or is related to the flexible coord pick policy JIRA issue -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8698) Datasource XAExceptions leads to corrupt Transaction Context on thread

by Anders Welen (JIRA)

Datasource XAExceptions leads to corrupt Transaction Context on thread ---------------------------------------------------------------------- Key: JBAS-8698 URL: https://jira.jboss.org/browse/JBAS-8698 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Remoting, Transaction Manager Integration (Arjuna) Affects Versions: 6.0.0.CR1, JBossAS-5.1.0.GA, JBossAS-4.2.1.GA Reporter: Anders Welen Assignee: Scott Stark Attachments: TestCase3850.tar When MySQL throws a "com.mysql.jdbc.jdbc2.optional.MysqlXAException" when called from a remote client the server thread doesn't seem to be cleaned up of transaction context data. All calls that reusing the thread will fail with the following exception: org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95) at se.redpill.TestCase3850Bean.runTest(TestCase3850Bean.java:22) ... ... ... >From what I can see the "MysqlXAException" (implements XAException) will not be caught in "com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.java". (Can it be some kind of classloading problem?) As the result the thread will not be cleaned of transaction information and "broken" when reused. This seems only to occur for remote clients (If the client calls within the JVM it seems to work) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-7965) jta resource recovery problem

by Nicolae Petridean (JIRA)

jta resource recovery problem ----------------------------- Key: JBAS-7965 URL: https://jira.jboss.org/jira/browse/JBAS-7965 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager (Arjuna) Reporter: Nicolae Petridean Assignee: Jonathan Halliday Priority: Critical Hi all, i noticed that there is some problems with the transaction recovery in JBOSS. When a number of warnings like this : "WARN oggerI18N om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa Could not find new XAResource to use for recovering non-serializable XAResource" appear , at some time the exceptions mechanism is affected (the exceptions are not thrown anymore). If the application uses timers those are also blocked (the timeouts dont appear anymore), it seems that the transcations that are not finished are blocking the timers. Why aren't those transactions just ended after some specific time ? Or is there another way to deal with the situation ? Thanks in advance, Nicu -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7930) Set the port_range on JGroups stacks to 1

by Brian Stansberry (JIRA)

Set the port_range on JGroups stacks to 1 ----------------------------------------- Key: JBAS-7930 URL: https://jira.jboss.org/jira/browse/JBAS-7930 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M4 Lock down the ports. Do this for M4 as it may lead to testsuite troubles on slaves until we identify ports where there aren't conflicts. -- 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, 6 months

7
12
0 / 0

[JBoss JIRA] Created: (JBAS-8632) Domain interface should include versions

by Heiko Rupp (JIRA)

Domain interface should include versions ---------------------------------------- Key: JBAS-8632 URL: https://jira.jboss.org/browse/JBAS-8632 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Heiko Rupp The domain interface should for all servers provide the exact version of the server. This should contain also CP and FP tags. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

14
23
0 / 0

[JBoss JIRA] Created: (JBAS-9074) High level commands for common domain mode tasks

by Brian Stansberry (JIRA)

High level commands for common domain mode tasks ------------------------------------------------ Key: JBAS-9074 URL: https://issues.jboss.org/browse/JBAS-9074 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 High level commands to simplify command domain-mode tasks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
6
0 / 0

[JBoss JIRA] Created: (JBAS-6532) TCLFilter doesn't work in jboss 5 with war's in any documented way

by robert lazarski (JIRA)

TCLFilter doesn't work in jboss 5 with war's in any documented way ------------------------------------------------------------------ Key: JBAS-6532 URL: https://jira.jboss.org/jira/browse/JBAS-6532 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-5.0.0.GA Environment: jdk 6, linux Reporter: robert lazarski Assignee: Scott M Stark Reading this doc: http://www.jboss.org/community/docs/DOC-12203 Indicates a *-exp.war syntax is needed for TCLFilter war use, but there are no files of that type on my system running jboss 5. I've tried all the possible combinations I can think of, posted the problem to the forum, and the result is always that the file sizes and contents of the log files generated are exactly the same for the different war's, ie, no separated content. Here's my current config: <appender name="penguinLog" class="org.apache.log4j.FileAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler> <param name="Append" value="false"/> <param name="File" value="${jboss.server.home.dir}/log/penguinLog.log"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/> </layout> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="true"/> <param name="DeployURL" value="penguin"/> </filter> </appender> <appender name="wtfLog" class="org.apache.log4j.FileAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler> <param name="Append" value="false"/> <param name="File" value="${jboss.server.home.dir}/log/wtfLog.log"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p %c{1} %m%n"/> </layout> <filter class="org.jboss.logging.filter.TCLFilter"> <param name="AcceptOnMatch" value="true"/> <param name="DeployURL" value="wtf-exp.war"/> </filter> </appender> <root> <appender-ref ref="CONSOLE"/> <appender-ref ref="FILE"/> <appender-ref ref="penguinLog"/> <appender-ref ref="wtfLog"/> </root> -- 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, 7 months

7
13
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 April 2011