March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-6705) AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template"

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6705?page=com.atlassian.jira.plug... ] Charles Crouch moved EMBJOPR-121 to JBAS-6705: ---------------------------------------------- Project: JBoss Application Server (was: Embedded Jopr) Key: JBAS-6705 (was: EMBJOPR-121) Component/s: JMS (JBoss Messaging) (was: Web App/Integration) Fix Version/s: JBossAS-5.1.0.CR1 (was: 1.2) Security: Public > AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template" > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6705 > URL: https://jira.jboss.org/jira/browse/JBAS-6705 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS (JBoss Messaging) > Environment: JBoss AS Branch_5_x r86417, embjopr r259 > Reporter: Farah Juma > Assignee: Charles Crouch > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Attempt to create a new Topic or Queue. The following error occurs: > Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. > Deployment "vfsfile:/home/fjuma/jbossas5/Branch_5_x_extra/build/output/jboss-5.1.0.CR1/server/default/deploy/testTopic-service.xml" is in error due to the following reason(s): java.lang.RuntimeException: No Attribute found with name: downCacheSize for jboss.messaging.destination:service=Topic,name=testTopic, attributes: [DurableMessageCount, Instance, ExpiryQueue, ServerPeer, RedeliveryDelay, NonDurableMessageCount, NonDurableSubscriptionsCount, DurableSubscriptionsCount, Clustered, JNDIName, MaxDeliveryAttempts, MessageCounters, FullSize, AllMessageCount, MaxSize, DownCacheSize, SecurityConfig, CreatedProgrammatically, PageSize, Name, DLQ, AllSubscriptionsCount, MessageCounterHistoryDayLimit] > It looks like attribute names now start with an upper case letter instead of a lower case one. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6665) Server-side thread count steadily increases during AS testsuite runs

by Richard Achmatowicz (JIRA)

Server-side thread count steadily increases during AS testsuite runs --------------------------------------------------------------------- Key: JBAS-6665 URL: https://jira.jboss.org/jira/browse/JBAS-6665 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.1.GA Environment: AS testsuite - not particular to any platform Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Priority: Minor (from an original email) > Hi Rajesh > > Just wanted to let you know about something concerning the AS testsuite. > > I've been having real problems getting the AS 5.0.0 (and 5.0.1) testsuite to run on HPUX without running out of native threads. It won't run to completion without getting an "OutOfMemoryError: unable to create native thread" exception. So I decided to try to find out how many threads are active in the JVM at any one time during a testsuite run. > > I wrote a small modification to XMLJUnitMultipleResultFormatter which gets called before and after every testsuite; it prints out the following statistics: > <test name>: ThreadCounts(current threads, daemon threads,peak thread count,total started), HeapSizes(init,used,committed,max) > > I'm seeing a strange creeping increase in the number of current threads active in the JVM over the life of the 'all' server execution, which is where i'm having the problem with native thread allocation. I would guess from this that some test cases are not releasing threads when finished, although this is only a guess. This is interesting. I would like to know if the HP UX maximum thread count is really low or the AS doesn't release some threads on undeploying the tests. Does a profiler show the list of all active threads when it runs out of active threads? A comparison with a run on RHEL with these metrics enabled will also tell us if we have a problem of threads being free'd on HPUX Can you open a JBAS and assign it to yourself with the below details and the attached log? There should be some interesting comments on this from dev. -- 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

15 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBJCA-79) Findbugs 1.3.7

by Jesper Pedersen (JIRA)

Findbugs 1.3.7 -------------- Key: JBJCA-79 URL: https://jira.jboss.org/jira/browse/JBJCA-79 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha1 Currently in tools/findbugs/lib -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6702) Red on Black Console Colors in Documentation Difficult for the Visually Impaired

by Brian Milnes (JIRA)

Red on Black Console Colors in Documentation Difficult for the Visually Impaired -------------------------------------------------------------------------------- Key: JBAS-6702 URL: https://jira.jboss.org/jira/browse/JBAS-6702 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Affects Versions: JBossAS-5.0.0.GA Reporter: Brian Milnes Priority: Minor Using Red Foreground on Black console boxes in the document is very difficult for the visually impaired. Black lettering on a white background is the most easily read. Perhaps you can try something like Red on White or Red on a very light blue? -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-135) SES url patterns cannot be defined in the servlet mappings

by Luis Majano (JIRA)

SES url patterns cannot be defined in the servlet mappings ---------------------------------------------------------- Key: JBWEB-135 URL: https://jira.jboss.org/jira/browse/JBWEB-135 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Luis Majano Assignee: Remy Maucherat The majority of servlet containers let you define servlet-mappings that can reproduce SES (search engine safe) URL's. Example: http://myhost.com/index.jsp/myvar/value http://myhost.com/index.jsp/entry/hello--there This gives you the ability to create pretty ses url's without the need of an external rewrite tool like mod_rewrite or an ses valve. However, as I am aware of, only Tomcat does not allow these type of servlet mappings. <servlet-mapping> <servlet-name>jsp</servlet-name> <url-pattern>*.jsp/*</url-pattern> </servlet-mapping> The <url-pattern>*.jsp/*</url-pattern> is the one that chokes!! It cannot be defined and used. This to me is a bug as all servlet containers support this type of url-patterns. -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-914) FLUSH: concurrent (partial) flushing blocks

by Bela Ban (JIRA)

FLUSH: concurrent (partial) flushing blocks ------------------------------------------- Key: JGRP-914 URL: https://jira.jboss.org/jira/browse/JGRP-914 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Vladimir Blagojevic Priority: Critical Fix For: 2.6.9, 2.8 Attachments: ConcurrentFlushTest.java See attached unit test -- 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

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-922) FLUSH: let application handle concurrent flushing

by Vladimir Blagojevic (JIRA)

FLUSH: let application handle concurrent flushing ------------------------------------------------- Key: JGRP-922 URL: https://jira.jboss.org/jira/browse/JGRP-922 Project: JGroups Issue Type: Task Affects Versions: 2.7, 2.6, 2.5 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.6.9, 2.8 We decided to allow application handle flush retires rather than handle it within flush itself. The new algorithm is: - Send a START-FLUSH to all members in the target set - Every member sets the flushInProgress flag to true - If this succeeds, the member sends back an OK - Else a FAIL is sent back - If we received OKs from all members, startFlush() succeeded and returns true - If 1 FAIL is received: - Send an ABORT-FLUSH to all members which took part in the flush, causes flushInProgress to be set to false - startFlush() failed and returns false -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-944) JChannel: automatic reconnection might fail

by Bela Ban (JIRA)

JChannel: automatic reconnection might fail ------------------------------------------- Key: JGRP-944 URL: https://jira.jboss.org/jira/browse/JGRP-944 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.6.9, 2.8 Automtatic reconnection is done via the JChannel.CloserThread thread. It essentially closes the channel, then re-opens it and then loops trying to reconnect. However, if there's an exception (e.g. closing or re-opening the channel), the thread terminates and doesn't reconnect the channel, therefore the cluster is not joined. SOLUTION: wrap the close, open and reconnect attempts in try-catch clauses, so exceptions can be handled -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-946) JChannel: automatic reconnect ignores

by Bela Ban (JIRA)

JChannel: automatic reconnect ignores ------------------------------------- Key: JGRP-946 URL: https://jira.jboss.org/jira/browse/JGRP-946 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.6.9, 2.8 The JChannel CloserThread thread should not get started when AUTO_RECONNECT is false. However, the closer is always started and closes and reopens the channel. Reconnect then checks the value of AUTO_RECONNECT, but we should check *before* creating the CloserThread. -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMX-12) Release JBossMX 6.0.0.Beta2

by Adrian Brock (JIRA)

Release JBossMX 6.0.0.Beta2 --------------------------- Key: JBMX-12 URL: https://jira.jboss.org/jira/browse/JBMX-12 Project: JBossMX Issue Type: Task Components: release Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMX.6.0.0.Beta2 -- 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

15 years, 9 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009