January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1365) Statistics not updated when a connection listener is destroyed

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1365?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on JBJCA-1365: --------------------------------------- This issue is a regression caused when the fix for JBJCA-1354 was ported to branch 1.0. > Statistics not updated when a connection listener is destroyed > -------------------------------------------------------------- > > Key: JBJCA-1365 > URL: https://issues.jboss.org/browse/JBJCA-1365 > Project: IronJacamar > Issue Type: Bug > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > In Ironjacamar 1.0.4, there is a regression caused by JBJCA-1354 fix. > Whenever a connection is closed, and the corresponding tx connection listener is removed from the pool, the managed connection pool is not notified and that causes the statistics to go inconsistent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1365) Statistics not updated when a connection listener is destroyed

by Flavia Rainone (JIRA)

Flavia Rainone created JBJCA-1365: ------------------------------------- Summary: Statistics not updated when a connection listener is destroyed Key: JBJCA-1365 URL: https://issues.jboss.org/browse/JBJCA-1365 Project: IronJacamar Issue Type: Bug Reporter: Flavia Rainone Assignee: Flavia Rainone In Ironjacamar 1.0.4, there is a regression caused by JBJCA-1354 fix. Whenever a connection is closed, and the corresponding tx connection listener is removed from the pool, the managed connection pool is not notified and that causes the statistics to go inconsistent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2229) Error shown every time GDT editor opened in Firefox and IE11

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2229?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2229: --------------------------------- Component/s: Guided Decision Table Editor > Error shown every time GDT editor opened in Firefox and IE11 > ------------------------------------------------------------ > > Key: DROOLS-2229 > URL: https://issues.jboss.org/browse/DROOLS-2229 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Environment: - Firefox browser > - IE11 > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Blocker > > The following error appears every time I create new / open existing GDT > in Firefox (tested with latest 57.0.1 as well as with latest 52 esr) or IE11 but it works fine on chrome. > "Unable to complete your request. The following exception occurred: (String) : ReferenceError: window is not defined (http://localhost:8080/decision-central/verifier/D1F31C11AAF94D26DDBD99679...)." > Reproducible 100% with RHDM ER1 using Firefox and IE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2229) Error shown every time GDT editor opened in Firefox and IE11

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2229?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHDM-260 to DROOLS-2229: ------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-2229 (was: RHDM-260) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Affects Build: (was: ER1) Affects Version/s: (was: 7.0.0.GA) QE Status: NEW Fix Version/s: (was: 7.0.0.GA) > Error shown every time GDT editor opened in Firefox and IE11 > ------------------------------------------------------------ > > Key: DROOLS-2229 > URL: https://issues.jboss.org/browse/DROOLS-2229 > Project: Drools > Issue Type: Bug > Environment: - Firefox browser > - IE11 > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Blocker > > The following error appears every time I create new / open existing GDT > in Firefox (tested with latest 57.0.1 as well as with latest 52 esr) or IE11 but it works fine on chrome. > "Unable to complete your request. The following exception occurred: (String) : ReferenceError: window is not defined (http://localhost:8080/decision-central/verifier/D1F31C11AAF94D26DDBD99679...)." > Reproducible 100% with RHDM ER1 using Firefox and IE -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1008) KieServer to update container for SNAPSHOT kjar

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugi... ] Martin Weiler commented on DROOLS-1008: --------------------------------------- Just for the records, this issue seems to be similar to https://issues.jboss.org/browse/RHBPMS-5076 which has been fixed recently on 6.5.x. > KieServer to update container for SNAPSHOT kjar > ----------------------------------------------- > > Key: DROOLS-1008 > URL: https://issues.jboss.org/browse/DROOLS-1008 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 6.2.0.Final, 6.3.0.Final > Reporter: Andrew Collins > Assignee: Mario Fusco > Attachments: snapshot_kjar_reproducer.patch > > > General: > When a kjar has a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup, regardless of settings.xml snapshot updatePolicy setting. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow() or recycling the JVM, which will both fetch the new artifact from the remote repository and reload the kmodule in the KieServer JVM. > Steps to reproduce: > * KieServer and Business Central deployed to separate JVMs, pointing to independent maven repositories. Snapshot updatePolicy should be "always" in KieServer settings.xml. > * Deploy new kjar snapshot from Business Central to remote artifactory. (unique version "1") > * Start KieServer (verify new snapshot version is pulled from remote) > * Deploy new kjar snapnshot. (unique version "2") > Expected behavior: > * Creating a new container, or invoking updateReleaseId() on existing container will pull latest snapshot from remote artifactory. > Actual Behavior > * Creating a new container, or invoking updateReleaseId() on existing container, does not query remote artifactory for latest snapshots. > Workaround: > * Forcing a KieScanner.scanNow() will fetch new snapshot from remote artifactory. > * Or, restarting KieScanner JVM will fetch new snapshot from remote artifactory. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9646) Wsconsume is not able to generate jar file from wsdl

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9646?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-9646: ---------------------------------- Fix Version/s: 12.0.0.Alpha1 > Wsconsume is not able to generate jar file from wsdl > ---------------------------------------------------- > > Key: WFLY-9646 > URL: https://issues.jboss.org/browse/WFLY-9646 > Project: WildFly > Issue Type: Bug > Components: Scripts, Web Services > Reporter: Marek Kopecký > Assignee: Alessio Soldano > Priority: Blocker > Fix For: 12.0.0.Alpha1 > > > *Description:* > Wsconsume is able to generate jar file from wsdl on WildFly 11. On WildFly master, wsconsume doesn't create any files in "out" folder. It leads to Exception from wsdl2java tool. > *Steps to reproduce:* > # cd $\{JBOSS_HOME\}/bin > # # download Echo1.wsdl, Echo1Service.wsdl and Echo1Service_schema1.xsd files, these files are attached to this jira > # mkdir out > # ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl > *Actual results:* > {noformat} > [mkopecky@dhcp-10-40-4-226 bin]$ ./wsconsume.sh -j wsClientShort.jar -p org.jboss.test.script -o out Echo1Service.wsdl > Could not find log4j.properties or log4j.xml configuration, logging to console. > Loading FrontEnd jaxws ... > Loading DataBinding jaxb ... > wsdl2java -clientjar wsClientShort.jar -compile -exsh false -p org.jboss.test.script -d /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583 -verbose -classdir /home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out -allowElementReferences file:/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/Echo1Service.wsdl > wsdl2java - Apache CXF 3.1.12 > JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava > org.apache.cxf.tools.common.ToolException: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read") > at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:423) > at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313) > at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298) > at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108) > at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96) > at org.jboss.modules.Module.run(Module.java:344) > at org.jboss.modules.Main.main(Main.java:525) > Caused by: java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.08/wfly.08/bin/out/tmp3507583/org/jboss/test/script/package-info.java" "read") > at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) > at java.security.AccessController.checkPermission(AccessController.java:884) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at java.io.File.isDirectory(File.java:844) > at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:69) > at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:64) > at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromFiles(JavacFileManager.java:785) > at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromStrings(JavacFileManager.java:185) > at org.apache.cxf.common.util.Compiler.useJava6Compiler(Compiler.java:192) > at org.apache.cxf.common.util.Compiler.compileFiles(Compiler.java:141) > at org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:123) > at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:306) > at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164) > at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:415) > ... 8 more > [mkopecky@dhcp-10-40-4-226 bin]$ ll out/ > total 0 > [mkopecky@dhcp-10-40-4-226 bin]$ > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9643) Getting Internal server error on exception if the rest service content type is "application/xml"

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9643?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on WFLY-9643: --------------------------------------- [~gopalams] , could you please provider a reproducer app for this? > Getting Internal server error on exception if the rest service content type is "application/xml" > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9643 > URL: https://issues.jboss.org/browse/WFLY-9643 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Gopal krishna > Assignee: Alessio Soldano > > We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". > we didnt see this issue in jboss 7 and WAS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2228) [Guided Decision Table] Rename Set the field value with Work Item parameter column

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2228?page=com.atlassian.jira.plugi... ] Michael Anstis moved RHDM-259 to DROOLS-2228: --------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-2228 (was: RHDM-259) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Decision Table Editor (was: Business Central) Affects Build: (was: ER2) Affects Version/s: 7.5.0.Final (was: 7.0.0) QE Status: NEW > [Guided Decision Table] Rename Set the field value with Work Item parameter column > ---------------------------------------------------------------------------------- > > Key: DROOLS-2228 > URL: https://issues.jboss.org/browse/DROOLS-2228 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Trivial > Labels: bxms-bughunt-7-la-er2 > Original Estimate: 1 day > Remaining Estimate: 1 day > > The column *Set the field value with Work Item parameter* actually set the field with Work Item result so maybe it could be renamed to *Set the field value with Work Item result*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2228) [Guided Decision Table] Rename Set the field value with Work Item parameter column

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2228?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2228: ----------------------------------- Sprint: 2018 Week 01-02 > [Guided Decision Table] Rename Set the field value with Work Item parameter column > ---------------------------------------------------------------------------------- > > Key: DROOLS-2228 > URL: https://issues.jboss.org/browse/DROOLS-2228 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Trivial > Labels: bxms-bughunt-7-la-er2 > Original Estimate: 1 day > Remaining Estimate: 1 day > > The column *Set the field value with Work Item parameter* actually set the field with Work Item result so maybe it could be renamed to *Set the field value with Work Item result*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1369) FIPS mode, Elytron HTTP DIGEST authentication mechanism not fips compliant

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1369?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1369: --------------------------------------- Our biggest gap here is likely to be clients not supporting the new digests. > FIPS mode, Elytron HTTP DIGEST authentication mechanism not fips compliant > -------------------------------------------------------------------------- > > Key: ELY-1369 > URL: https://issues.jboss.org/browse/ELY-1369 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.2.0.Beta3 > Reporter: Jan Kalina > Assignee: Jan Kalina > Fix For: 1.2.0.Beta11 > > > Elytron HTTP DIGEST authentication comply to rfc2617 - which means MD5 is used by default (it means it is hardcode, with no way to configure another hash algorithm). But MD5 could make troubles in fips environment [5]. > {code:java|title=DigestAuthenticationMechanism.java} > String algorithm = convertToken(ALGORITHM, responseTokens.get(ALGORITHM)); > if (MD5.equals(algorithm) == false) { > throw log.mechUnsupportedAlgorithm(getMechanismName(), algorithm); > } > {code} > There exists proposed rfc7616 which makes algorithm configurable, work on new DIGEST features are covered by [1]. [~dlofthouse] is it planned for [1] to target 7.1? > [1] https://issues.jboss.org/browse/ELY-286 > [2] https://developer.jboss.org/wiki/ElytronHTTPDigestNonceHandling-Design > [3] https://tools.ietf.org/html/rfc2617 > [4] https://tools.ietf.org/html/rfc7616 > [5] https://access.redhat.com/support/cases/#/case/01761455 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
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 January 2018