January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1032) WebSphere JMS on Kie server produces errors in log

by Karel Suta (JIRA)

Karel Suta created DROOLS-1032: ---------------------------------- Summary: WebSphere JMS on Kie server produces errors in log Key: DROOLS-1032 URL: https://issues.jboss.org/browse/DROOLS-1032 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 6.4.x Environment: WebSphere 8.5.5.7 Reporter: Karel Suta Assignee: Maciej Swiderski Attachments: stacktrace.txt When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment. It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there. Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... Maybe would be good to reduce log level there to be able to filter out this error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-851) Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-851?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-851: ------------------------------------------------ Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1248156|https://bugzilla.redhat.com/show_bug.cgi?id=1248156] from ON_QA to VERIFIED > Remoting Subsystem RemoteOutboundConnectionService is caching ConnectionURI causing issues when DNS changes > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-851 > URL: https://issues.jboss.org/browse/WFCORE-851 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Brad Maxwell > Assignee: Filippe Spolti > Fix For: 2.0.5.CR1 > > > Description of problem: > EJB CLient was configured with DNS FQDN to configure access to a remote EJB. If run a simple test adding an entry in /etc/hosts file pointing that FQDN to localhost for tests everything works. However, after finish the tests and remove the entry, the client still connects to localhost instead of resolve the new IP address. Even adding networkaddress.cache.ttl=30 inside security settings didn't work too. > How reproducible: > Everytime you use DNS names to connect to a remote EJB. > Steps to Reproduce: > 1. Configure a simple client that connects to a remote EJB using dns name > 2. add an entry in /etc/hosts mapping the dns name to localhost > 3. run the client code > 4. remove the entry in /etc/hosts > 5. run the client code again > Actual results: > EJB remote is still reached from localhost > Expected results: > After changing DNS record EJB will be reached in this new address -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2005) Probe: more detailed information about RPCs

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2005?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2005: --------------------------- Description: {{probe.sh rpcs}} currently only returns the number of multicasts, anycasts and unicasts (async and sync) since the last reset. Add 3 additional keys: * rpcs-enable-details: captures detailed information from now on. This is not enabled by default as capturing this information is costly (hashmap put/get, timing of RPCs etc) * rpcs-disable-details: disables capturing of details * rpcs-details: dumps detailed information (needs to be enabled before) ** For async RPCs: number of RPCs for every destination (unicast or multicast) ** For sync RPCs: ditto, plus min/max/avg invocation times was: {{probe.sh rpcs}} currently only returns the number of multicasts, anycasts and unicasts (async and sync) since the last reset. Add 3 additional keys: * rpcs-enable-details: captures detailed information from now on. This is not enabled by default as capturing this information is costly (hashmap put/get, timing of RPCs etc) * rpcs-disable-details: disables capturing of details * rpcs-details: dumps detailed information (needs to be enabled before) > Probe: more detailed information about RPCs > ------------------------------------------- > > Key: JGRP-2005 > URL: https://issues.jboss.org/browse/JGRP-2005 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8 > > > {{probe.sh rpcs}} currently only returns the number of multicasts, anycasts and unicasts (async and sync) since the last reset. Add 3 additional keys: > * rpcs-enable-details: captures detailed information from now on. This is not enabled by default as capturing this information is costly (hashmap put/get, timing of RPCs etc) > * rpcs-disable-details: disables capturing of details > * rpcs-details: dumps detailed information (needs to be enabled before) > ** For async RPCs: number of RPCs for every destination (unicast or multicast) > ** For sync RPCs: ditto, plus min/max/avg invocation times -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2005) Probe: more detailed information about RPCs

by Bela Ban (JIRA)

Bela Ban created JGRP-2005: ------------------------------ Summary: Probe: more detailed information about RPCs Key: JGRP-2005 URL: https://issues.jboss.org/browse/JGRP-2005 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.6.8 {{probe.sh rpcs}} currently only returns the number of multicasts, anycasts and unicasts (async and sync) since the last reset. Add 3 additional keys: * rpcs-enable-details: captures detailed information from now on. This is not enabled by default as capturing this information is costly (hashmap put/get, timing of RPCs etc) * rpcs-disable-details: disables capturing of details * rpcs-details: dumps detailed information (needs to be enabled before) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2004) Probe improvements

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2004?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2004. ---------------------------- Resolution: Done > Probe improvements > ------------------ > > Key: JGRP-2004 > URL: https://issues.jboss.org/browse/JGRP-2004 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8 > > > * Make {{-cluster}} an option: this was currently handled by a ProbeHandler, so {{probe.sh -cluster one jmx=UDP.num}} would *not* discard requests for clusters other than "one" > * Add by default the local address, physical address, cluster size, version and cluster name to every response -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2004) Probe improvements

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2004?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2004: -------------------------------- Example: 4 nodes {noformat} [belasmac] /Users/bela$ probe.sh jmx=UDP.num_bat -- sending probe on /224.0.75.75:7500 #1 (148 bytes): local_addr=belasmac-52236 [ip=127.0.0.1:63826, version=3.6.8-SNAPSHOT, cluster=default, 2 mbr(s)] UDP={num_batches_received=4, num_batches_sent=3} #2 (154 bytes): local_addr=belasmac-7515 [ip=127.0.0.1:50794, version=3.6.8-SNAPSHOT, cluster=config-cluster, 2 mbr(s)] UDP={num_batches_received=0, num_batches_sent=0} #3 (155 bytes): local_addr=belasmac-27207 [ip=127.0.0.1:64697, version=3.6.8-SNAPSHOT, cluster=config-cluster, 2 mbr(s)] UDP={num_batches_received=0, num_batches_sent=0} #4 (147 bytes): local_addr=belasmac-1882 [ip=127.0.0.1:59167, version=3.6.8-SNAPSHOT, cluster=default, 2 mbr(s)] UDP={num_batches_received=6, num_batches_sent=2} 4 responses (4 matches, 0 non matches) {noformat} {noformat} [belasmac] /Users/bela$ probe.sh -cluster config-.* jmx=UDP.num_bat -- sending probe on /224.0.75.75:7500 #1 (155 bytes): local_addr=belasmac-27207 [ip=127.0.0.1:64697, version=3.6.8-SNAPSHOT, cluster=config-cluster, 2 mbr(s)] UDP={num_batches_received=0, num_batches_sent=0} #2 (154 bytes): local_addr=belasmac-7515 [ip=127.0.0.1:50794, version=3.6.8-SNAPSHOT, cluster=config-cluster, 2 mbr(s)] UDP={num_batches_received=0, num_batches_sent=0} 2 responses (2 matches, 0 non matches) {noformat} The second example gets members to drop probe requests directed to clusters other than those starting with "config-" > Probe improvements > ------------------ > > Key: JGRP-2004 > URL: https://issues.jboss.org/browse/JGRP-2004 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8 > > > * Make {{-cluster}} an option: this was currently handled by a ProbeHandler, so {{probe.sh -cluster one jmx=UDP.num}} would *not* discard requests for clusters other than "one" > * Add by default the local address, physical address, cluster size, version and cluster name to every response -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2004) Probe improvements

by Bela Ban (JIRA)

Bela Ban created JGRP-2004: ------------------------------ Summary: Probe improvements Key: JGRP-2004 URL: https://issues.jboss.org/browse/JGRP-2004 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.6.8 * Make {{-cluster}} an option: this was currently handled by a ProbeHandler, so {{probe.sh -cluster one jmx=UDP.num}} would *not* discard requests for clusters other than "one" * Add by default the local address, physical address, cluster size, version and cluster name to every response -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6028) Fix messaging migration warnings

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-6028: --------------------------------- Summary: Fix messaging migration warnings Key: WFLY-6028 URL: https://issues.jboss.org/browse/WFLY-6028 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.0.0.CR5 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 10.0.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-720) KIE Server: enable automated testing on WebLogic 12

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-720?page=com.atlassian.jira.plugin... ] Petr Široký resolved DROOLS-720. -------------------------------- Fix Version/s: 6.3.0.Final Resolution: Done This has been implemented by [~ksuta] some time ago. See https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... and the oracle-wls-12 profile. > KIE Server: enable automated testing on WebLogic 12 > --------------------------------------------------- > > Key: DROOLS-720 > URL: https://issues.jboss.org/browse/DROOLS-720 > Project: Drools > Issue Type: Task > Components: kie server > Affects Versions: 6.2.0.CR4 > Reporter: Petr Široký > Assignee: Karel Suta > Fix For: 6.3.0.Final > > > The `kie-server-tests` module does not have Cargo config for WebLogic. Cargo supports this container, so we should add the `wlc12x` profile to enable easy testing of the KIE Server also on WebLogic. > http://cargo.codehaus.org/WebLogic+12.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-720) KIE Server: enable automated testing on WebLogic 12

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-720?page=com.atlassian.jira.plugin... ] Petr Široký reassigned DROOLS-720: ---------------------------------- Assignee: Karel Suta (was: Petr Široký) > KIE Server: enable automated testing on WebLogic 12 > --------------------------------------------------- > > Key: DROOLS-720 > URL: https://issues.jboss.org/browse/DROOLS-720 > Project: Drools > Issue Type: Task > Components: kie server > Affects Versions: 6.2.0.CR4 > Reporter: Petr Široký > Assignee: Karel Suta > > The `kie-server-tests` module does not have Cargo config for WebLogic. Cargo supports this container, so we should add the `wlc12x` profile to enable easy testing of the KIE Server also on WebLogic. > http://cargo.codehaus.org/WebLogic+12.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016