[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
[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
[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
[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