January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3490) IllegalArgumentException when for loop is used for command producing non iterable result

by Erich Duda (JIRA)

Erich Duda created WFCORE-3490: ---------------------------------- Summary: IllegalArgumentException when for loop is used for command producing non iterable result Key: WFCORE-3490 URL: https://issues.jboss.org/browse/WFCORE-3490 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 4.0.0.Alpha5 Reporter: Erich Duda Assignee: Jean-Francois Denise {code} [standalone@embedded /] set name=World [standalone@embedded /] for var in :resolve-expression(expression=Hello $name!) java.lang.IllegalArgumentException {code} As you can see in the example, the commands produce {{IllegalArgumentException}}. Instead of {{IllegalArgumentException}} there should be an error message explaining what is wrong. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3489) CLI completion does not work correctly for control flow commands inside of for loop

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3489?page=com.atlassian.jira.plugi... ] Erich Duda updated WFCORE-3489: ------------------------------- Affects: User Experience > CLI completion does not work correctly for control flow commands inside of for loop > ----------------------------------------------------------------------------------- > > Key: WFCORE-3489 > URL: https://issues.jboss.org/browse/WFCORE-3489 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha5 > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > The issue appears when you write following commands into the CLI. > {code} > [standalone@embedded /] for var in :read-resource > [standalone@embedded /] try > [standalone@embedded /] <TAB> > : cd connect deployment-overlay help module read-attribute set undeploy > alias clear connection-info done history patch read-operation stop-embedded-server unset > attachment command deploy echo if pwd reload try version > batch command-timeout deployment-info echo-dmr ls quit run-batch unalias > {code} > As you can see the completion helper offers a {{try}} command although it should offer {{catch}} command. > This issue is caused by design limitation of CLI. When you type some commands inside of for loop block, they are just added into internal list and they are not evaluated until {{done}} command is called. > The same applies also for other control flow commands such as {{if-else-endif}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1363) IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar

by Francis ANDRE (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1363?page=com.atlassian.jira.plugin... ] Francis ANDRE updated JBJCA-1363: --------------------------------- Priority: Major (was: Blocker) > IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1363 > URL: https://issues.jboss.org/browse/JBJCA-1363 > Project: IronJacamar > Issue Type: Bug > Components: Deployer > Affects Versions: 1.0.17.Final, 1.2.7.Final > Environment: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>"%java_home%\bin\java" -version > java version "1.7.0_80" > Java(TM) SE Runtime Environment (build 1.7.0_80-b15) > Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) > Windows 10 > Reporter: Francis ANDRE > > Hi > Got this exception when deploying a EIS rar > C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>run > =============================================================================== > IronJacamar > IRON_JACAMAR_HOME: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final > JAVA: C:\Program Files\Java\jdk1.7.0_80\bin\java > JAVA_OPTS: -Xmx512m > =============================================================================== > 10:16:49,330 INFO [Fungal] Fungal 0.11.0.Final started > 10:16:49,908 INFO [Version] HV000001: Hibernate Validator 5.0.1.Final > 10:16:50,065 INFO [WebServer] Jetty 8.1.3.v20120416 started > 10:16:50,143 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-xa.rar > 10:16:50,221 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-local.rar > 10:16:50,268 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/scortcicsecirar-3.1.0.rar > 10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/root.war > 10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/console.war > 10:16:50,362 SEVERE [Fungal] Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed: com.github.fungal.spi.deployers.DeployException: Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed > at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:209) > at com.github.fungal.impl.MainDeployerImpl.deploy(MainDeployerImpl.java:144) > at com.github.fungal.impl.KernelImpl$UnitDeployer.run(KernelImpl.java:1947) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.io.IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar > at com.github.fungal.api.util.FileUtil.delete(FileUtil.java:378) > at com.github.fungal.api.util.FileUtil.extract(FileUtil.java:179) > at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:131) > ... 5 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1481) Coverity, Explicit null dereferenced in FileSystemSecurityRealm

by Martin Choma (JIRA)

Martin Choma created ELY-1481: --------------------------------- Summary: Coverity, Explicit null dereferenced in FileSystemSecurityRealm Key: ELY-1481 URL: https://issues.jboss.org/browse/ELY-1481 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Affects Versions: 1.2.0.Beta11 Reporter: Martin Choma There are 2 occurences of call to PasswordFactory.getInstance(algorithm) in FileSystemSecurityRealm where algorithm can be null, because algorithm is optional in wildfly-config.xml {code:xml|title=elytron-1_0_1.xsd} <xsd:complexType name="credential-type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/> <xsd:attribute name="format" type="xsd:string" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="otp-credential-type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/> <xsd:attribute name="hash" type="xsd:string" use="optional"/> <xsd:attribute name="seed" type="xsd:string" use="optional"/> <xsd:attribute name="sequence" type="xsd:string" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> {code} Algorithm is dereferenced in PasswordFactory.getInstance(algorithm) down in {code:java|title=java.security.Provider$ServiceKey.java} private ServiceKey(String type, String algorithm, boolean intern) { this.type = type; this.originalAlgorithm = algorithm; algorithm = algorithm.toUpperCase(ENGLISH); this.algorithm = intern ? algorithm.intern() : algorithm; } {code} [1] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847... [2] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1480) Coverity, Explicit null dereferenced in FileSystemSecurityRealm

by Martin Choma (JIRA)

Martin Choma created ELY-1480: --------------------------------- Summary: Coverity, Explicit null dereferenced in FileSystemSecurityRealm Key: ELY-1480 URL: https://issues.jboss.org/browse/ELY-1480 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Affects Versions: 1.2.0.Beta11 Reporter: Martin Choma There are 2 occurences of call to PasswordFactory.getInstance(algorithm) in FileSystemSecurityRealm where algorithm can be null, because algorithm is optional in wildfly-config.xml {code:xml|title=elytron-1_0_1.xsd} <xsd:complexType name="credential-type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/> <xsd:attribute name="format" type="xsd:string" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="otp-credential-type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/> <xsd:attribute name="hash" type="xsd:string" use="optional"/> <xsd:attribute name="seed" type="xsd:string" use="optional"/> <xsd:attribute name="sequence" type="xsd:string" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> {code} Algorithm is dereferenced in PasswordFactory.getInstance(algorithm) down in {code:java|title=java.security.Provider$ServiceKey.java} private ServiceKey(String type, String algorithm, boolean intern) { this.type = type; this.originalAlgorithm = algorithm; algorithm = algorithm.toUpperCase(ENGLISH); this.algorithm = intern ? algorithm.intern() : algorithm; } {code} [1] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847... [2] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2207: -------------------------------- Affects Version/s: 7.5.0.Final > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final, 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1479) Coverity, Missing call to superclass in AbstractGssapiMechanism

by Martin Choma (JIRA)

Martin Choma created ELY-1479: --------------------------------- Summary: Coverity, Missing call to superclass in AbstractGssapiMechanism Key: ELY-1479 URL: https://issues.jboss.org/browse/ELY-1479 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms Affects Versions: 1.2.0.Beta11 Reporter: Martin Choma super.getNegotiatedProperty() is not called in AbstractGssapiMechanism#getNegotiatedProperty, although it is called in similar cases in Gs2SaslServer, DigestSaslServer, AnonymousSaslClient. {code:java|title=AbstractGssapiMechanism.java} @Override public Object getNegotiatedProperty(String propName) { assertComplete(); switch (propName) { case Sasl.QOP: return selectedQop.getName(); case Sasl.MAX_BUFFER: return Integer.toString(actualMaxReceiveBuffer != 0 ? actualMaxReceiveBuffer : configuredMaxReceiveBuffer); case Sasl.RAW_SEND_SIZE: return Integer.toString(maxBuffer); } return null; } {code} This coverity report is not caused by recent change in AbstractGssapiMechanism but rather Gs2SaslServer and DigestSaslServer [1] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9636) EJB lookup over HTTP times out connection after 60 seconds

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9636?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated WFLY-9636: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/979001#979001 > EJB lookup over HTTP times out connection after 60 seconds > ---------------------------------------------------------- > > Key: WFLY-9636 > URL: https://issues.jboss.org/browse/WFLY-9636 > Project: WildFly > Issue Type: Bug > Components: EJB, IO, Naming > Affects Versions: 11.0.0.Final > Environment: I work with https://developer.jboss.org/people/jaikiran on https://developer.jboss.org/thread/276635 so my Wildfly 11 environment has this fix in it. > Reporter: peter craddock > Assignee: Stuart Douglas > > The code examples and trace logging can be found here https://developer.jboss.org/thread/276840 > I have work round the problem but was asked to raise it for further investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2251) ObjectTypeValidator should not implement AllowedValuesValidator

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2251?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2251: ---------------------------------------- Assignee: Brian Stansberry > ObjectTypeValidator should not implement AllowedValuesValidator > --------------------------------------------------------------- > > Key: WFCORE-2251 > URL: https://issues.jboss.org/browse/WFCORE-2251 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > ObjectTypeValidator is incorrectly implementing AllowedValuesValidator and should not implement it at all. > The values returned from an AllowedValuesValidator are meant to be an enumeration of the *complete* legal values for the attribute. ObjectTypeValidator is simply returning the legal keys for the fields in the object, which are not complete legal values. > The result of this is any attribute that uses this validator (which all complex objects probably do) will report bogus and unnecessary data in the read-resource-description "allowed-values" metadata. Unnecessary because the description of the attribute already includes full details of the fields via the "value-type" metadata. > I'm classifying this as minor because the bogus metadata likely does no harm. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2210) Drools 7.3.0 serialization null pointer exceptions with sliding windows

by Manjunath S Paramesan (JIRA)

Manjunath S Paramesan created DROOLS-2210: --------------------------------------------- Summary: Drools 7.3.0 serialization null pointer exceptions with sliding windows Key: DROOLS-2210 URL: https://issues.jboss.org/browse/DROOLS-2210 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.3.0.Final Reporter: Manjunath S Paramesan Assignee: Mario Fusco Priority: Critical We have a fairly large rule-base with temporal reasoning and sliding windows. While serializing the drools session we observe random null pointer exceptions as see below: Exception in thread "pool-92-thread-98" java.lang.NullPointerException at org.drools.core.rule.SlidingTimeWindow$BehaviorJobContextTimerOutputMarshaller.serialize(SlidingTimeWindow.java:323) at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeTimers(ProtobufOutputMarshaller.java:880) at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.serializeSession(ProtobufOutputMarshaller.java:210) at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeSession(ProtobufOutputMarshaller.java:118) at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:162) at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:146) at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.backupKieSession(DroolsClientImpl.java:743) at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.lambda$processStatefulEvents$0(DroolsClientImpl.java:506) at java.lang.Thread.run(Thread.java:745) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018