April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9027) Identify all public APIs

by David Lloyd (JIRA)

Identify all public APIs ------------------------ Key: JBAS-9027 URL: https://issues.jboss.org/browse/JBAS-9027 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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
9
0 / 0

[JBoss JIRA] Created: (JBAS-7994) Clean up quartz messages in AS startup log

by Paul Gier (JIRA)

Clean up quartz messages in AS startup log ------------------------------------------ Key: JBAS-7994 URL: https://jira.jboss.org/jira/browse/JBAS-7994 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.CR1 The recent updates to quartz have added more noise to the console log. These messages should be written only to the log file and not the console. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-9257) BridgeLogger implementation of Logger does not support Level.OFF or null as parameter values for setLevel method

by Antonio Montanana (JIRA)

BridgeLogger implementation of Logger does not support Level.OFF or null as parameter values for setLevel method ---------------------------------------------------------------------------------------------------------------- Key: JBAS-9257 URL: https://issues.jboss.org/browse/JBAS-9257 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 6.0.0.M2 Reporter: Antonio Montanana Assignee: David Lloyd Deploying our application on the JBoss 6.0.0 application server we encounter the following NullPointerException (NPE) also logged in the log\server.log file: 2011-03-17 12:52:18,269 ERROR [filenet_error.engine.com.filenet.engine.tasks.TaskManager] (TaskManager$RootTask_RootTask_ScheduledPoolExecutor_9) TaskManager$RootTask:RootTask running with error , with message null: java.lang.NullPointerException at org.jboss.logmanager.log4j.LevelMapping.getLevelFor(LevelMapping.java:65) [:6.0.0.Final] at org.jboss.logmanager.log4j.BridgeLogger.setPriority(BridgeLogger.java:199) [:6.0.0.Final] at org.jboss.logmanager.log4j.BridgeLogger.setLevel(BridgeLogger.java:194) [:6.0.0.Final] at com.filenet.engine.util.Logger.removeTraceLoggerLevel(Logger.java:377) ... The com.filenet.engine.util.Logger.removeTraceLoggerLevel method executes the following two lines of code: org.apache.log4j.Logger traceLogger = getLog4JTraceLogger(subsystem, traceFlag); traceLogger.setLevel(null); Note the setLevel method is passing in a null parameter value (supported by org.apache.log4j.Logger.setLevel) to remove the specified logging level. We've verified that the JBoss LevelMapping.getLevelFor method throws the NPE as a result of the null parameter value passed into setLevel (changing the parameter value to another level (e.g. Level.DEBUG) eliminates the exception). The setLevel(null) code executed with no exceptions in JBoss 5.1.0 and earlier versions of the server and is supported by org.apache.log4j.Logger.setLevel. It appears that the logging mechanism has changed significantly in JBoss 6.0, there is now a BridgeLogger class that extends the org.apache.log4j.Logger class providing the implementation of the setLevel method. That implementation appears to have omitted support for "null" as a parameter value and causes the NPE. Further testing indicates that the Level.OFF value is also not supported either - leaving no way to remove the logging level. We would like to see support for "null" and Level.OFF added to the BridgeLogger extension of Logger. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8781) Can't parse JSF TLD

by Stan Silvert (JIRA)

Can't parse JSF TLD ------------------- Key: JBAS-8781 URL: https://issues.jboss.org/browse/JBAS-8781 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 7.0.0.Alpha1 Reporter: Stan Silvert Assignee: Remy Maucherat WAR to reproduce is attached. 15:32:07,764 ERROR [org.jboss.as.server.deployment] (pool-3-thread-1) Caught exc eption handling update (param is 10cd5140-b773-49da-97ab-0fb055b56141): java.lan g.RuntimeException: Failed to process deployment chain. at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe ploymentStartStopHandler.java:203) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl oymentStartStopHandler.java:87) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl oymentStartStopHandler.java:71) at org.jboss.as.model.ServerDeploymentStartStopHandler.redeploy(ServerDe ploymentStartStopHandler.java:117) at org.jboss.as.model.ServerModelDeploymentFullReplaceUpdate.applyUpdate (ServerModelDeploymentFullReplaceUpdate.java:68) at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl e.applyUpdate(ServerUpdateController.java:430) at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl e.access$200(ServerUpdateController.java:400) at org.jboss.as.server.mgmt.ServerUpdateController.applyUpdates(ServerUp dateController.java:189) at org.jboss.as.server.mgmt.ServerUpdateController.executeUpdates(Server UpdateController.java:142) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl$2.run (ServerDeploymentManagerImpl.java:218) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) [:1.6.0_18] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) [:1.6.0_18] at java.lang.Thread.run(Thread.java:619) [:1.6.0_18] Caused by: org.jboss.as.deployment.unit.DeploymentUnitProcessingException: Faile d to parse "/C:/projects/as7trunk/jboss-as/build/target/jboss-7.0.0.Alpha2/bin/c ontent/mojarra2.0-bundled.war/WEB-INF/lib/jsf-impl-2.0.3-b05.jar/META-INF/html_b asic.tld" at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl dParsingDeploymentProcessor.java:118) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds (TldParsingDeploymentProcessor.java:97) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processDepl oyment(TldParsingDeploymentProcessor.java:77) at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(D eploymentChainImpl.java:50) at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe ploymentStartStopHandler.java:201) ... 12 more Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.met adata.web.spec.BodyContentType. JSP at java.lang.Enum.valueOf(Enum.java:196) [:1.6.0_18] at org.jboss.metadata.web.spec.BodyContentType.valueOf(BodyContentType.j ava:32) at org.jboss.as.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataP arser.java:111) at org.jboss.as.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataP arser.java:200) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl dParsingDeploymentProcessor.java:116) ... 16 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (JBAS-9363) Make available JBoss AS source code and checksum(s) for download

by jaikiran pai (JIRA)

Make available JBoss AS source code and checksum(s) for download ----------------------------------------------------------------- Key: JBAS-9363 URL: https://issues.jboss.org/browse/JBAS-9363 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: jaikiran pai Fix For: 7.0.0.CR1 JBoss AS source code for AS7 isn't currently made available at http://www.jboss.org/jbossas/downloads.html. We should start uploading the source (and other other artifacts like checksum) for our releases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JBAS-7674) Windows file locking problem with the data/jnp-service.url file

by Brian Stansberry (JIRA)

Windows file locking problem with the data/jnp-service.url file --------------------------------------------------------------- Key: JBAS-7674 URL: https://jira.jboss.org/jira/browse/JBAS-7674 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 In some circumstances, windows is reporting the AS is holding a lock on the data/jnp-service.url file when it isn't running. -- 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, 5 months

5
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1456) Messages stuck in being-delivered state in cluster

by Justin Bertram (JIRA)

Messages stuck in being-delivered state in cluster -------------------------------------------------- Key: JBMESSAGING-1456 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1456 Project: JBoss Messaging Issue Type: Bug Reporter: Justin Bertram Assignee: Tim Fox Priority: Critical Messages become "stuck" in being-delivered state when clients use a clustered XA connection factory in a cluster of at least 2 nodes. JBoss setup: -2 nodes of JBoss EAP 4.3 CP02 -commented out "ClusterPullConnectionFactory" in messaging-service.xml to prevent message redistribution and eliminate the "message suckers" as the potential culprit -MySQL backend using the default mysql-persistence-service.xml (from <JBOSS_HOME>/docs/examples/jms) Client setup: -both nodes have a client which is a separate process (i.e. not inside JBoss) -clients are Spring based -one client produces and consumes, the other client just consumes -both clients use the ClusteredXAConnectionFactory from the default connection-factories-service.xml -both clients publish to and consume from "queue/testDistributedQueue" -clients are configured to send persistent messages, use AUTO_ACKNOWLEDGE, and transacted sessions Symptoms of the issue: -when running the clients I watch the JMX-Console for the "queue/testDistributedQueue" -as the consumers pull messages off the queue I can see the MessageCount and DeliveringCount go to 0 every so often -after a period of time (usually a few hours) the MessageCount and DeliveringCount never go back to 0 -I "kill" the clients and wait for the DeliveringCount to go to 0, but it never does -after the clients are killed the ConsumerCount for the queue will drop, but never to 0 when messages are "stuck" -a thread dump reveals at least one JBM server session that is apparently stuck (it never goes away) - ostensibly this is the consumer that is showing in the JMX-Console for "queue/testDistributedQueue" -a "killall -3 java" doesn't produce anything from the clients so I know their dead -nothing is in any DLQ or expiry queue -the database contains as many rows in the JBM_MSG and JBM_MSG_REF tables as the DeliveringCount in the JMX-Console -rebooting the node with the stuck messages frees the messages to be consumed (i.e. un-sticks them) Other notes: -nothing else is happening on either node but running the client and running JBoss -this only appears to happen when a clustered connection factory is used. I tested using a normal connection factory and after 24 hours couldn't reproduce a stuck message. -- 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, 5 months

11
102
0 / 0

[JBoss JIRA] Created: (JBAS-9206) Filter Apache CXF and dependencies

by Alessio Soldano (JIRA)

Filter Apache CXF and dependencies ---------------------------------- Key: JBAS-9206 URL: https://issues.jboss.org/browse/JBAS-9206 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8988) Filter log4j, add dep on org.apache.log4j

by David Lloyd (JIRA)

Filter log4j, add dep on org.apache.log4j ----------------------------------------- Key: JBAS-8988 URL: https://issues.jboss.org/browse/JBAS-8988 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8986) Filter apache commons-logging, add dep on org.apache.commons.logging

by David Lloyd (JIRA)

Filter apache commons-logging, add dep on org.apache.commons.logging -------------------------------------------------------------------- Key: JBAS-8986 URL: https://issues.jboss.org/browse/JBAS-8986 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd 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, 5 months

5
7
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