October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1613) NPE in TranslatingSuspendableChannel.scheduleReadTask

by Ondrej Zizka (JIRA)

NPE in TranslatingSuspendableChannel.scheduleReadTask ----------------------------------------------------- Key: AS7-1613 URL: https://issues.jboss.org/browse/AS7-1613 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final Reporter: Ondrej Zizka Assignee: Alexey Loubyansky Happened after a while of inactivity (if that matters). [standalone@localhost:9999 interface=public] cd .. [standalone@localhost:9999 /] cd .. [standalone@localhost:9999 /] ls extension core-service path subsystem system-property deployment interface socket-binding-group [standalone@localhost:9999 /] Exception in thread "pool-1-thread-21" java.lang.NullPointerException at org.xnio.channels.TranslatingSuspendableChannel.scheduleReadTask(TranslatingSuspendableChannel.java:253) at org.xnio.channels.TranslatingSuspendableChannel.resumeReads(TranslatingSuspendableChannel.java:233) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication$2.run(ClientConnectionOpenListener.java:498) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] (AS7-2022) TS: Coverage reports

by Ondrej Zizka (Created) (JIRA)

TS: Coverage reports -------------------- Key: AS7-2022 URL: https://issues.jboss.org/browse/AS7-2022 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka There are some coverage jobs in Hudson: * Aggregated: https://hudson.qa.jboss.com/hudson//view/JBoss%20AS/job/jboss-as7-code-co... * Per module: https://hudson.qa.jboss.com/hudson/view/JBoss AS/job/JBoss-AS-7.0.x-unit-coverage/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
42
0 / 0

[JBoss JIRA] Created: (JBRULES-2791) Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager

by Anatoly Polinsky (JIRA)

Spring's JpaTransactionManager should be used instead of both: DroolsSpringTransactionManager and DroolsSpringJpaManager ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-2791 URL: https://jira.jboss.org/browse/JBRULES-2791 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL, FUTURE Environment: Spring Based Applications Reporter: Anatoly Polinsky Assignee: Mark Proctor Instead of having two different components: "DroolsSpringTransactionManager" and "DroolsSpringJpaManager" that aim to do the work of "org.springframework.orm.jpa.JpaTransactionManager", and trying to fit a JTA model into it, the Spring's "JpaTransactionManager" itself should be used. And instead of manually managing and constantly getting references to a "proper entity manager" from JpaManger within a SingleSessionCommandService, a @PersistenceContext should be injected. This will decouple SingleSessionCommandService from JpaManager interface, and will allow _any_ JPA provider to inject an entity manager. It has more benefits, such as trust in underline JPA providers ( e.g. Hibernate ) and Spring Transaction Management capabilities to manage the process that they are actually excellent at. /Anatoly -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-114) Warning for non File URLs should also check for vfszip URLs

by Darran Lofthouse (JIRA)

Warning for non File URLs should also check for vfszip URLs ----------------------------------------------------------- Key: JBCOMMON-114 URL: https://jira.jboss.org/browse/JBCOMMON-114 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.17.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.2.18.GA Within the resolveSystemIDasURL method the following check is performed: - if (warnOnNonFileURLs && url.getProtocol().equalsIgnoreCase("file") == false) { log.warn("Trying to resolve systemId as a non-file URL: " + systemId); } With the introduction of vfszip URLs from JBoss 5 these should also be checked and the warning skipped if it is a vfszip URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-123) CLONE - Release jboss-common-core 2.2.18

by Dimitris Andreadis (JIRA)

CLONE - Release jboss-common-core 2.2.18 ---------------------------------------- Key: JBCOMMON-123 URL: https://issues.jboss.org/browse/JBCOMMON-123 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.18.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] (AS7-2436) clear screen doesn't work on windows 7

by Alexey Loubyansky (Created) (JIRA)

clear screen doesn't work on windows 7 -------------------------------------- Key: AS7-2436 URL: https://issues.jboss.org/browse/AS7-2436 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Following the discussion [jboss-as7-dev] AS 7.1.0 - jboss-admin : cls/clear command not working I am using Windows 7 64 bit and it is not working. On 31/10/2011 11:53 PM, Alexey Loubyansky wrote: > > No, it is expected to work. It does work on linux and remember verifying > > it on vista. CLI uses jline to manage the terminal. This is what its > > clearScreen impl looks like > > > > /** > > * Clear the screen by issuing the ANSI "clear screen" code. > > */ > > public boolean clearScreen() throws IOException { > > if (!terminal.isANSISupported()) { > > return false; > > } > > > > // send the ANSI code to clear the screen > > printString(((char) 27) + "[2J"); > > flushConsole(); > > > > // then send the ANSI code to go to position 1,1 > > printString(((char) 27) + "[1;1H"); > > flushConsole(); > > > > redrawLine(); > > > > return true; > > } > > > > Maybe the terminal doesn't support ANSI? > > > > On 10/30/2011 07:35 AM, Vimal Kansal wrote: >> >> I am using jboss-admin on windows 7 64 bit and both cls/clear are not >> >> working : they just don't do anything. I wonder if the command is just a >> >> place holder for now? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-9232) Store config file comments in the model

by Brian Stansberry (JIRA)

Store config file comments in the model --------------------------------------- Key: JBAS-9232 URL: https://issues.jboss.org/browse/JBAS-9232 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry 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

13 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (AS7-1682) Add a test to ensure Stateless and message driven beans work fine in the absence of a pool

by jaikiran pai (JIRA)

Add a test to ensure Stateless and message driven beans work fine in the absence of a pool ------------------------------------------------------------------------------------------ Key: AS7-1682 URL: https://issues.jboss.org/browse/AS7-1682 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.0.2.Final Starting AS 7.0.1, we allow users to disable pooling for Stateless and Message driven beans. We need a test to ensure it works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1275) Multiple moves win a step (moves without direct tabu property relations)

by Geoffrey De Smet (JIRA)

Multiple moves win a step (moves without direct tabu property relations) ------------------------------------------------------------------------ Key: JBRULES-1275 URL: http://jira.jboss.com/jira/browse/JBRULES-1275 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Currently only one move can win a step. If moves are evaluated not on their score, but on "the difference in score", it probably won't be a bad idea to take a low number of improving moves that have not tabu property's in common and do a step of all of them instead of just one, especially in the beginning. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1328) SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured

by Geoffrey De Smet (JIRA)

SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured -------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1328 URL: http://jira.jboss.com/jira/browse/JBRULES-1328 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Because AbstractAccepter references LocalSearchSolver references the drools RuleBase references stuff that isn't Serializable... -- 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, 10 months

1
4
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 October 2011