July 2011 - jboss-jira - Jboss List Archives

[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, 4 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, 4 months

7
12
0 / 0

[JBoss JIRA] Created: (AS7-1382) Ensure domain security is fully manageable

by Darran Lofthouse (JIRA)

Ensure domain security is fully manageable ------------------------------------------ Key: AS7-1382 URL: https://issues.jboss.org/browse/AS7-1382 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 At the moment the management operations are fairly coarse based on the operations generated from parsing the XML, these should be enhanced to allow more fine grained management from the admin clients. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (AS7-714) Provide datasource metrics

by Heiko Braun (JIRA)

Provide datasource metrics -------------------------- Key: AS7-714 URL: https://issues.jboss.org/browse/AS7-714 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
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, 4 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, 4 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, 4 months

7
13
0 / 0

[JBoss JIRA] Created: (AS7-969) JVM resource description doesn't match operation return value

by Heiko Braun (JIRA)

JVM resource description doesn't match operation return value ------------------------------------------------------------- Key: AS7-969 URL: https://issues.jboss.org/browse/AS7-969 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Reading a JVM resource description returns this: {noformat} [domain@localhost:9999 /] /server-group=main-server-group/jvm=default:read-resource { "outcome" => "success", "result" => { "type" => undefined, "agent-lib" => undefined, "agent-path" => undefined, "env-classpath-ignored" => undefined, "environment-variables" => undefined, "heap-size" => "64m", "max-heap-size" => "512m", "java-agent" => undefined, "java-home" => undefined, "jvm-options" => undefined, "permgen-size" => undefined, "max-permgen-size" => undefined, "stack-size" => undefined }, "compensating-operation" => undefined } {noformat} However the resource description looks different. It describes certain elements as children, some of the are missing at all ('max-heap-size"') {noformat} [domain@localhost:9999 /] /server-group=main-server-group/jvm=default:read-resource-description { "outcome" => "success", "result" => { "type" => OBJECT, "description" => "The JVM configuration for managed processes / servers.", "attributes" => { "agent-lib" => { "type" => STRING, "description" => "The JVM agent lib.", "access-type" => "read-write", "storage" => "configuration" }, "agent-path" => { "type" => STRING, "description" => "The JVM agent path.", "access-type" => "read-write", "storage" => "configuration" }, "env-classpath-ignored" => { "type" => BOOLEAN, "description" => "Ignore the environment classpath.", "access-type" => "read-write", "storage" => "configuration" }, "environment-variables" => { "type" => LIST, "value-type" => UNDEFINED, "description" => "The JVM environment variables.", "access-type" => "read-write", "storage" => "configuration" }, "java-agent" => { "type" => STRING, "description" => "The java agent.", "access-type" => "read-write", "storage" => "configuration" }, "java-home" => { "type" => STRING, "description" => "The java home", "access-type" => "read-write", "storage" => "configuration" }, "jvm-options" => { "type" => LIST, "value-type" => STRING, "description" => "The JVM options.", "access-type" => "read-only", "storage" => "configuration" }, "stack-size" => { "type" => STRING, "description" => "The JVM stack size settings.", "access-type" => "read-write", "storage" => "configuration" }, "type" => { "type" => STRING, "description" => "The JVM type can be either SUN or IBM", "access-type" => "read-only", "storage" => "configuration" } }, "children" => { "heap-size" => { "type" => OBJECT, "description" => "The Heap size settings allocated by the JVM.", "attributes" => { "size" => STRING, "max-size" => STRING } }, "permgen-size" => { "type" => OBJECT, "description" => "The JVM PermGen settings.", "attributes" => { "size" => STRING, "max-size" => STRING } } } }, "compensating-operation" => undefined } {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
9
0 / 0

[JBoss JIRA] Created: (AS7-799) Wrong Classloader Used When Deserializing Persisted Sessions

by Benjamin Browning (JIRA)

Wrong Classloader Used When Deserializing Persisted Sessions ------------------------------------------------------------ Key: AS7-799 URL: https://issues.jboss.org/browse/AS7-799 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Benjamin Browning Assignee: Jason Greene The org.jboss.as.web:main module's classloader is being used when deserializing persisted sessions instead of the deployment's classloader. This leads to errors like the one below when any classes are referenced in the session that aren't in the dependency list of org/jboss/as/web/main/module.xml. 21:02:50,824 ERROR [org.apache.catalina.session.ManagerBase] (MSC service thread 1-1) ClassNotFoundException while loading persisted sessions: java.lang.ClassNotFoundException: org.jboss.weld.context.conversation.ConversationIdGenerator from [Module "org.jboss.as.web:main" from local module loader @32b0bad7 (roots: /Users/bbrowning/src/torquebox/integration-tests/target/integ-dist/jboss/modules)]: java.lang.ClassNotFoundException: org.jboss.weld.context.conversation.ConversationIdGenerator from [Module "org.jboss.as.web:main" from local module loader @32b0bad7 (roots: /Users/bbrowning/src/torquebox/integration-tests/target/integ-dist/jboss/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) [:1.0.0.Beta17] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) [:1.0.0.Beta17] at java.lang.Class.forName0(Native Method) [:1.6.0_24] at java.lang.Class.forName(Class.java:247) [:1.6.0_24] at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:603) [:1.6.0_24] at org.apache.catalina.util.CustomObjectInputStream.resolveClass(CustomObjectInputStream.java:78) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1574) [:1.6.0_24] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1495) [:1.6.0_24] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1731) [:1.6.0_24] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) [:1.6.0_24] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) [:1.6.0_24] at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1429) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:934) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:395) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.session.StandardManager.load(StandardManager.java:322) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.session.StandardManager.start(StandardManager.java:633) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:459) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3776) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:61) [jboss-as-web-7.0.0.Beta3.jar:7.0.0.Beta3] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2831) The zips should contain a README_DEPENDENCIES.txt file generated by the build

by Geoffrey De Smet (JIRA)

The zips should contain a README_DEPENDENCIES.txt file generated by the build ----------------------------------------------------------------------------- Key: JBRULES-2831 URL: https://issues.jboss.org/browse/JBRULES-2831 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: FUTURE We're removing the current README_DEPENDENCIES.txt file because it contains a lot of incorrect, misleading info. But we'd still like to give the users that file, but correct. The only decent way to keep it correct is to generate it of the build. In theory we could just take the output of mvn dependency:tree but maybe maven has a better report. Until we do that, the users will have to rely on our released poms, which contain correct info. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
4
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 July 2011