July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9419) Add jndi alias for new JBossAS7 default DS

by Ales Justin (JIRA)

Add jndi alias for new JBossAS7 default DS ------------------------------------------ Key: JBAS-9419 URL: https://issues.jboss.org/browse/JBAS-9419 Project: Legacy JBoss Application Server 6 Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: 6.0.0.Final Reporter: Ales Justin Assignee: Ales Justin Fix For: 6.1.0 Allow for the same examples that are deployable on JBossAS7 and depend on new default DS jndi name (java:jboss/datasources/ExampleDS) to be deployable on JBossAS6 as well. This means adding an alias that binds the two jndi names. (java:jboss/datasources/ExampleDS --> java:/DefaultDS) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1319) size-rotating-file-handler fails with error if encoding isn't set in the configuration

by jaikiran pai (JIRA)

size-rotating-file-handler fails with error if encoding isn't set in the configuration -------------------------------------------------------------------------------------- Key: AS7-1319 URL: https://issues.jboss.org/browse/AS7-1319 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: jaikiran pai Assignee: jaikiran pai The following size-rotating-file-handler configuration {code:xml} <size-rotating-file-handler name="FILE2" autoflush="true"> <level name="TRACE"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <rotate-size value="2048"/> <max-backup-index value="5"/> </size-rotating-file-handler> {code} fails with {code} 20:10:42,402 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.logging.handler.FILE2: org.jboss.msc.service.StartException in service jboss.logging.handler.FILE2: java.io.UnsupportedEncodingException: undefined at org.jboss.as.logging.SizeRotatingFileHandlerService.start(SizeRotatingFileHandlerService.java:70) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: java.io.UnsupportedEncodingException: undefined at java.util.logging.Handler.setEncoding(Handler.java:130) [:1.6.0_21] at org.jboss.logmanager.handlers.OutputStreamHandler.setEncoding(OutputStreamHandler.java:90) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.as.logging.SizeRotatingFileHandlerService.start(SizeRotatingFileHandlerService.java:68) ... 5 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-631) Fungal 0.10.0.Beta2

by Jesper Pedersen (JIRA)

Fungal 0.10.0.Beta2 ------------------- Key: JBJCA-631 URL: https://issues.jboss.org/browse/JBJCA-631 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.1.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-628) EntirePool doesn't clean up

by Jesper Pedersen (JIRA)

EntirePool doesn't clean up --------------------------- Key: JBJCA-628 URL: https://issues.jboss.org/browse/JBJCA-628 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.0.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.1.Final, 1.1.0.Alpha1 If an "EntirePool" policy or flush(true) is triggered the permits aren't cleaned up -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-629) AvailableCount incorrect

by Jesper Pedersen (JIRA)

AvailableCount incorrect ------------------------ Key: JBJCA-629 URL: https://issues.jboss.org/browse/JBJCA-629 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.0.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.1.Final, 1.1.0.Alpha1 The AvailableCount statistics is incorrectly calculated and not updated in all cases -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-630) JBoss LogManager 1.2.0.GA

by Jesper Pedersen (JIRA)

JBoss LogManager 1.2.0.GA ------------------------- Key: JBJCA-630 URL: https://issues.jboss.org/browse/JBJCA-630 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.1.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-619) Change getState semantics

by Vladimir Blagojevic (JIRA)

Change getState semantics ------------------------- Key: JGRP-619 URL: http://jira.jboss.com/jira/browse/JGRP-619 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.4, 2.3, 2.2.9 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer. We have to simplify this process! State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener. This issue is closely related to revamping of channel state transfer callbacks - JGRP-563 -- 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

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JGRP-1344) Replace ChannelException with Exception

by Bela Ban (JIRA)

Replace ChannelException with Exception --------------------------------------- Key: JGRP-1344 URL: https://issues.jboss.org/browse/JGRP-1344 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 public void JChannel.connect(String cluster) throws ChannelException --> throws Exception This is more generic, and we can still throw ChannelClosedExceptions (needs to be listed in the javadoc) This way, we don't have to wrap an Exception received from state transfer (fetching state or setting state) into a StateTransferException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1335) Collapse setState and getState callbacks

by Vladimir Blagojevic (JIRA)

Collapse setState and getState callbacks ---------------------------------------- Key: JGRP-1335 URL: https://issues.jboss.org/browse/JGRP-1335 Project: JGroups Issue Type: Feature Request Affects Versions: 2.12, 2.11, 2.10, 2.9, 2.6 Reporter: Vladimir Blagojevic Assignee: Bela Ban Fix For: 3.0 Currently we maintain two sets of getState and setState callbacks, one for byte based transfer and the other for stream based transfer. Users had to implement both types of callbacks if the wanted to interchange STREAMING_STATE_TRANSFER and STATE_TRANSFER. If we use only stream based callbacks we can simplify client code and users can choose what type of transfer they want as a protocol option of STREAMING_STATE_TRANSFER. Finally, we could potentially drop STATE_TRANSFER all together. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1201) test for en/diable xa datasources

by Stefano Maestri (JIRA)

test for en/diable xa datasources --------------------------------- Key: AS7-1201 URL: https://issues.jboss.org/browse/AS7-1201 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 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 July 2011