[JBoss JIRA] (AS7-6634) Complete support for OSGi Blueprint
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-6634?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-6634:
--------------------------------
Comment: was deleted
(was: The problem is that Managed*DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows. ARQ's stop is supposed to shutdown the server 'nicely', for abrupt termination there is jvmKill().
This was probably implemented like this incorrectly assuming that on windows, the process is sent SIGTERM like on *NIX-based OSes but there is no such thing on windows and the process is terminated immediately.
This shows up only in clustered tests, compared to other tests which dont rely on the shutdown sequence to be completed, but clustering testsuite relies on shutdown to disconnect the channel and leave the cluster without FD having to kick in.)
> Complete support for OSGi Blueprint
> -----------------------------------
>
> Key: AS7-6634
> URL: https://issues.jboss.org/browse/AS7-6634
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi
> Reporter: Thomas Diesler
>
> R5 TCK compliance for Blueprint
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6620) DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-6620?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar commented on AS7-6620:
-------------------------------------
The problem is that Managed*DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows. ARQ's stop is supposed to shutdown the server 'nicely', for abrupt termination there is jvmKill().
This was probably implemented like this incorrectly assuming that on windows, the process is sent SIGTERM like on *NIX-based OSes but there is no such thing on windows and the process is terminated immediately.
This shows up only in clustered tests, compared to other tests which dont rely on the shutdown sequence to be completed, but clustering testsuite relies on shutdown to disconnect the channel and leave the cluster without FD having to kick in.
> DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows
> ---------------------------------------------------------------------------------------------
>
> Key: AS7-6620
> URL: https://issues.jboss.org/browse/AS7-6620
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.2.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> This might be due to historical reasons for the TS to run faster, but this messes up clustering tests since shutdown is part of the test.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (DROOLS-54) A query after an eval inside an OR causes a ClassCastException
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-54?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-54.
-------------------------------
Fix Version/s: 5.6
6.0.0.Alpha1
Resolution: Done
> A query after an eval inside an OR causes a ClassCastException
> --------------------------------------------------------------
>
> Key: DROOLS-54
> URL: https://issues.jboss.org/browse/DROOLS-54
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> A query after an OR containing an eval on one of its branch, like in the following DRL, causes a ClassCastException
> {code}
> declare Holder
> str : String
> end
> declare Bean
> val : String
> end
> declare Mock end
> rule "Init"
> when
> then
> insert( new Bean( "xyz" ) );
> insert( new Holder( "xyz" ) );
> insert( new Mock() );
> end
> query mock( Mock $m ) $m := Mock() end
> rule "Check"
> when
> $b : Bean( $t : val )
> ( Holder( $t ; ) or eal( $t.startsWith( "abc" ) ) )
> mock( $m ; )
> then
> System.out.println( $m );
> end
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history
by Ståle Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ]
Ståle Pedersen commented on AS7-6426:
-------------------------------------
no, it was just too late to be included into that version im afraid.
> Jboss-cli crashes on Windows on backslash in history
> ----------------------------------------------------
>
> Key: AS7-6426
> URL: https://issues.jboss.org/browse/AS7-6426
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: Jarkko Rantavuori
> Assignee: Alexey Loubyansky
>
> Note: seems to apply to latest snapshot only, not to 7.1.1.
> If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with
> java.lang.NumberFormatException: For input string: "1B"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.<init>(Integer.java:677)
> at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120)
> at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.PrintWriter.flush(PrintWriter.java:320)
> at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89)
> at org.jboss.aesh.console.Console.drawLine(Console.java:923)
> at org.jboss.aesh.console.Console.redrawLine(Console.java:902)
> at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:476)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (DROOLS-54) A query after an eval inside an OR causes a ClassCastException
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-54:
---------------------------------
Summary: A query after an eval inside an OR causes a ClassCastException
Key: DROOLS-54
URL: https://issues.jboss.org/browse/DROOLS-54
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
A query after an OR containing an eval on one of its branch, like in the following DRL, causes a ClassCastException
{code}
declare Holder
str : String
end
declare Bean
val : String
end
declare Mock end
rule "Init"
when
then
insert( new Bean( "xyz" ) );
insert( new Holder( "xyz" ) );
insert( new Mock() );
end
query mock( Mock $m ) $m := Mock() end
rule "Check"
when
$b : Bean( $t : val )
( Holder( $t ; ) or eal( $t.startsWith( "abc" ) ) )
mock( $m ; )
then
System.out.println( $m );
end
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history
by Jarkko Rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ]
Jarkko Rantavuori commented on AS7-6426:
----------------------------------------
Np. Does that mean the fix is included in (the coming version of) AS7 too? If I'd want to test that, would it be 7.2.0.Final-prerelease1? Didn't find a branch for it in github, just the tag.
> Jboss-cli crashes on Windows on backslash in history
> ----------------------------------------------------
>
> Key: AS7-6426
> URL: https://issues.jboss.org/browse/AS7-6426
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: Jarkko Rantavuori
> Assignee: Alexey Loubyansky
>
> Note: seems to apply to latest snapshot only, not to 7.1.1.
> If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with
> java.lang.NumberFormatException: For input string: "1B"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.<init>(Integer.java:677)
> at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120)
> at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.PrintWriter.flush(PrintWriter.java:320)
> at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89)
> at org.jboss.aesh.console.Console.drawLine(Console.java:923)
> at org.jboss.aesh.console.Console.redrawLine(Console.java:902)
> at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:476)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> Press any key to continue . . .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months