[JBoss JIRA] (DROOLS-106) Using the same pattern in and out of a sliding windows causes an NPE if a join is involved
by Davide Sottara (JIRA)
Davide Sottara created DROOLS-106:
-------------------------------------
Summary: Using the same pattern in and out of a sliding windows causes an NPE if a join is involved
Key: DROOLS-106
URL: https://issues.jboss.org/browse/DROOLS-106
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Beta1, 5.5.0.Final
Reporter: Davide Sottara
Assignee: Edson Tirelli
In cases like the following:
$primary : StockTick( $name : company ) over window:length(4)
accumulate (
$tick : StockTick( company == $name )
count( $tick ) )
A NPE is raised:
java.lang.NullPointerException
at org.drools.core.util.index.RightTupleIndexHashTable.remove(RightTupleIndexHashTable.java:363)
at org.drools.reteoo.AccumulateNode.retractRightTuple(AccumulateNode.java:318)
at org.drools.rule.SlidingLengthWindow.assertFact(SlidingLengthWindow.java:116)
--
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
11 years, 9 months
[JBoss JIRA] (DROOLS-105) Indexing may be broken with unification queries
by Davide Sottara (JIRA)
Davide Sottara created DROOLS-105:
-------------------------------------
Summary: Indexing may be broken with unification queries
Key: DROOLS-105
URL: https://issues.jboss.org/browse/DROOLS-105
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.Beta1, 5.5.0.Final
Reporter: Davide Sottara
Assignee: Mario Fusco
In a query such as:
query foo( String $name, Foo $f )
Bar( name == $name, $id : val )
$f := Foo( id == $id )
end
assuming that Foo is insert first, it will be (right) indexed using the
value of its id property and its (this) hashcode
when the query is later being evaluated, however, the unbound output
variable $f will be considered by the join node, resulting in a mismatch.
--
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
11 years, 9 months
[JBoss JIRA] (AS7-6949) NPE in RootResourceIterator
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6949?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6949:
----------------------------------
Description:
Intermittent testsuite failures, e.g.
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
Log shows this repeatedly:
[0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
RootResourceIterator.doIterate is reading the resource twice:
{code}
for (ResourceEntry entry : current.getChildren(type)) {
final PathElement pathElement = entry.getPathElement();
final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
final PathAddress childAddress = address.append(pathElement);
doIterate(child, childAddress);
}
{code}
The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
was:
Intermittent testsuite failures, e.g.
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
Log shows this repeatedly:
[4/18/13 7:17:27 PM] Brian Stansberry: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
RootResourceIterator.doIterate is reading the resource twice:
{code}
for (ResourceEntry entry : current.getChildren(type)) {
final PathElement pathElement = entry.getPathElement();
final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
final PathAddress childAddress = address.append(pathElement);
doIterate(child, childAddress);
}
{code}
The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
> NPE in RootResourceIterator
> ---------------------------
>
> Key: AS7-6949
> URL: https://issues.jboss.org/browse/AS7-6949
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> Intermittent testsuite failures, e.g.
> http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
> Log shows this repeatedly:
> [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> RootResourceIterator.doIterate is reading the resource twice:
> {code}
> for (ResourceEntry entry : current.getChildren(type)) {
> final PathElement pathElement = entry.getPathElement();
> final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
> final PathAddress childAddress = address.append(pathElement);
> doIterate(child, childAddress);
> }
> {code}
> The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
--
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
11 years, 9 months
[JBoss JIRA] (AS7-6949) NPE in RootResourceIterator
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6949?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6949:
----------------------------------
Description:
Intermittent testsuite failures, e.g.
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
Log shows this repeatedly:
[4/18/13 7:17:27 PM] Brian Stansberry: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
RootResourceIterator.doIterate is reading the resource twice:
{code}
for (ResourceEntry entry : current.getChildren(type)) {
final PathElement pathElement = entry.getPathElement();
final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
final PathAddress childAddress = address.append(pathElement);
doIterate(child, childAddress);
}
{code}
The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
Environment: (was: Intermittent testsuite failures, e.g.
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
Log shows this repeatedly:
[4/18/13 7:17:27 PM] Brian Stansberry: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
RootResourceIterator.doIterate is reading the resource twice:
{code}
for (ResourceEntry entry : current.getChildren(type)) {
final PathElement pathElement = entry.getPathElement();
final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
final PathAddress childAddress = address.append(pathElement);
doIterate(child, childAddress);
}
{code}
The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.)
> NPE in RootResourceIterator
> ---------------------------
>
> Key: AS7-6949
> URL: https://issues.jboss.org/browse/AS7-6949
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Alpha1
>
>
> Intermittent testsuite failures, e.g.
> http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
> Log shows this repeatedly:
> [4/18/13 7:17:27 PM] Brian Stansberry: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
> at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> RootResourceIterator.doIterate is reading the resource twice:
> {code}
> for (ResourceEntry entry : current.getChildren(type)) {
> final PathElement pathElement = entry.getPathElement();
> final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
> final PathAddress childAddress = address.append(pathElement);
> doIterate(child, childAddress);
> }
> {code}
> The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
--
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
11 years, 9 months
[JBoss JIRA] (AS7-6949) NPE in RootResourceIterator
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6949:
-------------------------------------
Summary: NPE in RootResourceIterator
Key: AS7-6949
URL: https://issues.jboss.org/browse/AS7-6949
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, JMX
Environment: Intermittent testsuite failures, e.g.
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/684...
Log shows this repeatedly:
[4/18/13 7:17:27 PM] Brian Stansberry: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55)
at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39)
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103)
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116)
at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220)
at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
RootResourceIterator.doIterate is reading the resource twice:
{code}
for (ResourceEntry entry : current.getChildren(type)) {
final PathElement pathElement = entry.getPathElement();
final Resource child = current.getChild(pathElement); // why this call since "entry" and "child" should be the same object
final PathAddress childAddress = address.append(pathElement);
doIterate(child, childAddress);
}
{code}
The problem is "child" is null, which is possible with a dynamic resource. So, either "entry" should be used, or, if there is some reason for the 2nd read, a check for null is needed before the recursive doIterate call.
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 8.0.0.Alpha1
--
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
11 years, 9 months
[JBoss JIRA] (DROOLS-104) Queries do not work with class literals
by Davide Sottara (JIRA)
Davide Sottara created DROOLS-104:
-------------------------------------
Summary: Queries do not work with class literals
Key: DROOLS-104
URL: https://issues.jboss.org/browse/DROOLS-104
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.5.0.Final
Reporter: Davide Sottara
Assignee: Mario Fusco
Fix For: 5.5.1.Final, 6.0.0.Final
It is not possible to use class literals as query input parameters
query test( Class $c )
...
end
rule "X"
when
...
test( MyClass.class ; )
then
...
end
--
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
11 years, 9 months
[JBoss JIRA] (AS7-6611) Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6611?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6611:
----------------------------------
Assignee: (was: Brian Stansberry)
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Alpha1)
> Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder
> ----------------------------------------------------------------------------------------
>
> Key: AS7-6611
> URL: https://issues.jboss.org/browse/AS7-6611
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Brian Stansberry
> Fix For: 8.0.0.CR1
>
>
> steps to reproduce:
> ...
> {code}jboss-eap-6.0\bin>set JAVA_HOME=c:\dummy
> jboss-eap-6.0\bin>standalone.bat
> Calling "W:\tmp\pk\jboss-eap-6.0\bin\standalone.conf.bat"
> >{code}
> ...
> batch script will end on this line (standalone.bat)
> l:73 "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> On linux we get at least error message:
> ./standalone.sh: line 178: /home/dummy/bin/java: No such file or directory
--
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
11 years, 9 months
[JBoss JIRA] (AS7-6662) Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6662?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6662:
----------------------------------
Assignee: (was: Brian Stansberry)
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Alpha1)
> Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder.
> -----------------------------------------------------------------------------------------
>
> Key: AS7-6662
> URL: https://issues.jboss.org/browse/AS7-6662
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brian Stansberry
> Priority: Minor
> Fix For: 8.0.0.CR1
>
>
> steps to reproduce:
> ...
> {code}jboss-eap-6.0\bin>set JAVA_HOME=c:\dummy
> jboss-eap-6.0\bin>standalone.bat
> Calling "W:\tmp\pk\jboss-eap-6.0\bin\standalone.conf.bat"
> jboss-eap-6.0\bin>{code}
> ...
> batch script will end on this line (standalone.bat)
> l:73 "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
> On linux we get at least error message:
> ./standalone.sh: line 178: /home/dummy/bin/java: No such file or directory
--
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
11 years, 9 months
[JBoss JIRA] (AS7-462) Patching system
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-462?page=com.atlassian.jira.plugin.sy... ]
Brian Stansberry updated AS7-462:
---------------------------------
Assignee: Emanuel Muckenhuber (was: Brian Stansberry)
> Patching system
> ---------------
>
> Key: AS7-462
> URL: https://issues.jboss.org/browse/AS7-462
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Labels: rhq
> Fix For: 8.0.0.Beta1
>
>
> "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them.
> This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good.
--
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
11 years, 9 months