April 2011 - jboss-jira - Jboss List Archives

[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

12 years, 9 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

12 years, 9 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

12 years, 9 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

12 years, 9 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

12 years, 9 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

12 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8987) Filter SLF4J (including impl classes), add dep on org.slf4j and/or org.slf4j.ext

by David Lloyd (JIRA)

Filter SLF4J (including impl classes), add dep on org.slf4j and/or org.slf4j.ext -------------------------------------------------------------------------------- Key: JBAS-8987 URL: https://issues.jboss.org/browse/JBAS-8987 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

12 years, 9 months

7
9
0 / 0

[JBoss JIRA] Created: (HIBERNATE-120) Hibernate maps type "timestamp" to Mysql's type "datetime" not "timestamp"

by zhou yanming (JIRA)

Hibernate maps type "timestamp" to Mysql's type "datetime" not "timestamp" -------------------------------------------------------------------------- Key: HIBERNATE-120 URL: https://jira.jboss.org/jira/browse/HIBERNATE-120 Project: Hibernate Integration Issue Type: Bug Reporter: zhou yanming Assignee: Steve Ebersole Priority: Critical datetime will trim millisecond record.setLastModified(new Date(1250053078708)); session.save(record); .... record = session.load(record.getId()); System.out.println(record.getLastModified()); // here is 125005307000 not expected 1250053078708 -- 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

12 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9106) In domain mode, prevent end-user access to and visibility of most configuration write operations

by Brian Stansberry (JIRA)

In domain mode, prevent end-user access to and visibility of most configuration write operations ------------------------------------------------------------------------------------------------ Key: JBAS-9106 URL: https://issues.jboss.org/browse/JBAS-9106 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 In domain mode most (almost certainly all) server level operations that update the persistent configuration should not be directly accessible by the end user and should not appear in the results of the read-resource-description, read-operation-names or read-operation-description operations if executed against a server-level resource. They can only be invoked by the host controller that is responsible for the server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- 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

12 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011