February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7682) Move jboss-stdio installation to the start of bootstrap process

by David Lloyd (JIRA)

Move jboss-stdio installation to the start of bootstrap process --------------------------------------------------------------- Key: JBAS-7682 URL: https://jira.jboss.org/jira/browse/JBAS-7682 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M2 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7503) Upgrade JBoss Messaging to 1.4.3.GA

by Brian Stansberry (JIRA)

Upgrade JBoss Messaging to 1.4.3.GA ----------------------------------- Key: JBAS-7503 URL: https://jira.jboss.org/jira/browse/JBAS-7503 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Brian Stansberry Priority: Critical Fix For: JBossAS-6.0.0.M2 Need to update trunk to at least the JBM version used in 6.0.0.M1. -- 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, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAOP-764) I'm deployed the PlanList all relavent classes. and it deployed successfully but when i used that process in Now i got the blank screen.

by masoom ali (JIRA)

I'm deployed the PlanList all relavent classes. and it deployed successfully but when i used that process in Now i got the blank screen. ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBAOP-764 URL: https://jira.jboss.org/jira/browse/JBAOP-764 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: masoom ali -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7601) Change the defaults to useDLQ=false for JBoss Messaging

by Toshiya Kobayashi (JIRA)

Change the defaults to useDLQ=false for JBoss Messaging ------------------------------------------------------- Key: JBAS-7601 URL: https://jira.jboss.org/jira/browse/JBAS-7601 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service, JMS (JBoss Messaging) Affects Versions: JBossAS-5.1.0.GA Reporter: Toshiya Kobayashi Assignee: Jesper Pedersen According to Adrian's comment on JBAS-7465: ==== However, if the jms product already supports DLQ processing then you should disable the DLQ processing in the MDB. i.e. useDLQ=false. It is duplicate work and not as "reliable" as the jms product handling internally, e.g. if the jms connection breaks between sending the message to the DLQ and ACKing the dead message, you'll eventually end up with the message twice in the DLQ. The feature only exists because JBossMQ did not have internal DLQ processing. ==== The defaults should be "useDLQ=false" for JBoss Messaging and in its document encourage users to use JBM settings instead. I created this JIRA as Feature Request because I couldn't reproduce buggy behaviour reported in JBPAPP-3352 against AS 5.1, but I think this change is still desirable for AS, too. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7635) org.jboss.test.jpa.test.WebClassesJPAUnitTestCase.testWebJPA failure

by Scott Marlow (JIRA)

org.jboss.test.jpa.test.WebClassesJPAUnitTestCase.testWebJPA failure -------------------------------------------------------------------- Key: JBAS-7635 URL: https://jira.jboss.org/jira/browse/JBAS-7635 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Scott Marlow Assignee: Carlo de Wolf http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-testSui... junit.framework.AssertionFailedError: expected:<200> but was:<500> at org.jboss.test.jpa.test.AbstractWebJPATest.accessURL(AbstractWebJPATest.java:62) at org.jboss.test.jpa.test.AbstractWebJPATest.testWebJPA(AbstractWebJPATest.java:48) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) 2010-01-18 16:13:42,673 ERROR [org.jboss.test.jpa.servlet.TestServlet] (http-127.0.0.1-8080-2) Error in servlet: java.lang.IllegalArgumentException: Unknown entity: org.jboss.test.jpa.support.TestEntity at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:446) at org.jboss.jpa.impl.tx.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:206) at org.jboss.test.jpa.servlet.TestServlet.doGet(TestServlet.java:69) ... (http://pastebin.com/m3e17ecf0) -- 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, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-6628) Remove EJB3 Configurations from AS

by Andrew Lee Rubinger (JIRA)

Remove EJB3 Configurations from AS ---------------------------------- Key: JBAS-6628 URL: https://jira.jboss.org/jira/browse/JBAS-6628 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-5.1.0.CR1, JBossAS-6.0.0.Alpha1 Deployers, JPA Configs, etc should be supplied by EJB3 component and removed from the AS build (where there are currently duplicates) -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7479) Unable to set checkInterval init-param to 0 for 'jsp' servlet

by James Livingston (JIRA)

Unable to set checkInterval init-param to 0 for 'jsp' servlet ------------------------------------------------------------- Key: JBAS-7479 URL: https://jira.jboss.org/jira/browse/JBAS-7479 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA, JBossAS-4.2.3.GA Reporter: James Livingston Assignee: Remy Maucherat If you attempt to set the checkInterval init-param to 0 in jboss-web.deployer/conf/web.xml (4.2) or deployers/jbossweb.deployer/web.xml (5.1) you receive a warning 'Warning: Invalid value for the initParam checkInterval. Will use the default value of "300" seconds' despite the comments indicating it is a valid value. What seems to have happened is that a while back we copied the org.apache.jasper.EmbeddedServletOptions class to org.jboss.web.tomcat.service.jasper.JspServletOptions so that we could override tldLocationsCache. Some time later, a Tomcat bug[0] in that class got fixed, but our copied code didn't get the fix applied. The relevant change is removing the "if (this.checkInterval == 0)" block, so that 0 is an acceptable value. If we did want to disallow 0, then it is buggy because it gets left as 0 if the init-param is not present or is a non-numeric value. [0] https://issues.apache.org/bugzilla/show_bug.cgi?id=41265 -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7662) web-profile test results are not classified

by Carlo de Wolf (JIRA)

web-profile test results are not classified ------------------------------------------- Key: JBAS-7662 URL: https://jira.jboss.org/jira/browse/JBAS-7662 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: JBossAS-6.0.0.M2 The test results of the web-profile test are stored in the default files (thus overwriting previous results). -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7588) Investigate org.jboss.test.ejb.lifecycle.test failures

by jaikiran pai (JIRA)

Investigate org.jboss.test.ejb.lifecycle.test failures ------------------------------------------------------ Key: JBAS-7588 URL: https://jira.jboss.org/jira/browse/JBAS-7588 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai -- 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, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBAS-4585) Properties not being correctly parsed on JCA

by Clebert Suconic (JIRA)

Properties not being correctly parsed on JCA -------------------------------------------- Key: JBAS-4585 URL: http://jira.jboss.com/jira/browse/JBAS-4585 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Clebert Suconic Fix For: JBossAS-5.0.0.Beta3 -- 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, 11 months

9
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2010