June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8954: ------------------------------------ Except for the datasource definitions, is there anything else Oracle specific in the test case? Obviously, there is something different on weblogic versus WildFly, because you are reporting this issue. I have not yet heard of any application compatibility differences when it comes to the weblogic JPA container versus the WildFly JPA container but that is always a possibility. As you point out, the difference could be in the (JTA) transaction managers. If you like, you could enable TRACE logging for the JPA container, which should show a bit more of what is going on. You could also enable the transaction manager TRACE logging also, which can be verbose but useful when combined with the JPA trace logging. [Example of enabling logging is here|https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPA...]. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2170) GOOGLE_PING2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2170?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2170: --------------------------- Fix Version/s: (was: 4.1) > GOOGLE_PING2 > ------------ > > Key: JGRP-2170 > URL: https://issues.jboss.org/browse/JGRP-2170 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.4 > > > New version of GOOGLE_PING based on the official Google Cloud Storage APIs [1]. The existing GOOGLE_PING protocol extends S3_PING which I want to deprecate, so creating GOOGLE_PING2 is a prerequisite to that. > Hosting will be at jgroups-extras: https://github.com/jgroups-extras/jgroups-google > [1] https://cloud.google.com/storage/docs/apis -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2882) Review & fix xml persistence of elytron subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2882?page=com.atlassian.jira.plugi... ] Tomaz Cerar reopened WFCORE-2882: --------------------------------- only part 1 is done. > Review & fix xml persistence of elytron subsystem > ------------------------------------------------- > > Key: WFCORE-2882 > URL: https://issues.jboss.org/browse/WFCORE-2882 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 3.0.0.Beta27 > > > Elytron subsystem uses a mess of parsers and duplicate code in them. > Go trough all parsers and unify attribute persistence with rest of the server. > also get rid as much of custom parser code as possible. > Update XSDs where appropriate to follow common model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1805) It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1805?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1805: ----------------------------------------------- Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1422216|https://bugzilla.redhat.com/show_bug.cgi?id=1422216] from POST to ASSIGNED > It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1805 > URL: https://issues.jboss.org/browse/WFLY-1805 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Labels: ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1622) NPE when compiling DMN file from test DMNRuntimeTest.testNoPrefix on IBM JDK

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1622?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1622: --------------------------------------- I think this problem might be related also to fail of test method DMNRuntimeTest.testPMMLFunctionContext which fails with this output [1]. The compilation should produce compilation error that PMML function definitions are not supported, but the error is not produced, because compilation "detects" the PMML function as FEEL. This is caused probably by wrong unmarshalling on IBM JDK, because from debugging it can be seen that here [2] the condition is true, because _kindStr_ is null, because it is wrongly read from the model as null. [1] https://gist.github.com/baldimir/f1099f66796e58707fc82624370ce9b5 [2] https://github.com/kiegroup/drools/blob/49be6c816880f64262eb0cdb08bcb5930... > NPE when compiling DMN file from test DMNRuntimeTest.testNoPrefix on IBM JDK > ---------------------------------------------------------------------------- > > Key: DROOLS-1622 > URL: https://issues.jboss.org/browse/DROOLS-1622 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Labels: reported-by-qe > Fix For: 7.1.0.Final > > > When running test [1] on IBM JDK, the test fails with this output [2]. > [1] https://github.com/kiegroup/drools/blob/32822e243a237cf26f26830a895035b97... > [2] https://gist.github.com/baldimir/969bd8f72665ff0e4244350abaed1ef4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2198) Reduce log level for RequestCorrelator "channel is not connected" error during shutdown

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JGRP-2198?page=com.atlassian.jira.plugin.... ] Peter Palaga updated JGRP-2198: ------------------------------- Summary: Reduce log level for RequestCorrelator "channel is not connected" error during shutdown (was: resolve or reduce log level for RequestCorrelator "channel is not connected" error during shutdown) > Reduce log level for RequestCorrelator "channel is not connected" error during shutdown > --------------------------------------------------------------------------------------- > > Key: JGRP-2198 > URL: https://issues.jboss.org/browse/JGRP-2198 > Project: JGroups > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > This is a followup of JGRP-1958. > While the fix for JGRP-1958 https://github.com/belaban/JGroups/commit/03d7c93145f6a9314c2380f5ad66bdc... > removed the stack trace, the error message is still logged as SEVERE. > [~shay1680], [~jbilek] and [~dereed] all agree that the log level should be reduced to WARN. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2198) resolve or reduce log level for RequestCorrelator "channel is not connected" error during shutdown

by Peter Palaga (JIRA)

Peter Palaga created JGRP-2198: ---------------------------------- Summary: resolve or reduce log level for RequestCorrelator "channel is not connected" error during shutdown Key: JGRP-2198 URL: https://issues.jboss.org/browse/JGRP-2198 Project: JGroups Issue Type: Bug Reporter: Peter Palaga Assignee: Peter Palaga This is a followup of JGRP-1958. While the fix for JGRP-1958 https://github.com/belaban/JGroups/commit/03d7c93145f6a9314c2380f5ad66bdc... removed the stack trace, the error message is still logged as SEVERE. [~shay1680], [~jbilek] and [~dereed] all agree that the log level should be reduced to WARN. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1550) wildfly-init-redhat.sh script does not work on RHEL 5 OS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1550?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1550: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1328146|https://bugzilla.redhat.com/show_bug.cgi?id=1328146] from VERIFIED to CLOSED > wildfly-init-redhat.sh script does not work on RHEL 5 OS > -------------------------------------------------------- > > Key: WFCORE-1550 > URL: https://issues.jboss.org/browse/WFCORE-1550 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 2.2.0.CR2 > Reporter: Vlado Pakan > Assignee: Vlado Pakan > Fix For: 3.0.0.Alpha2 > > > Wildfly start-up script $JBOSS_HOME/docs/contrib/scripts/init.d/wildfly-init-redhat.sh tries to get successful start timestamp using following command: > grep -o '[0-9]*' $JBOSS_MARKERFILE > This however does not work on RHEL 5 OS, as grep-2.5.1 does not return regular expression result correctly when used with -o option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1958) RequestCorrelator "channel is not connected" error during shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1958?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1958: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1399195|https://bugzilla.redhat.com/show_bug.cgi?id=1399195] from VERIFIED to CLOSED > RequestCorrelator "channel is not connected" error during shutdown > ------------------------------------------------------------------ > > Key: JGRP-1958 > URL: https://issues.jboss.org/browse/JGRP-1958 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.12 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.5 > > > Error logged during shutdown of a channel due to RequestCorrelator failing to send a reply: > ERROR [org.jgroups.protocols.UNICAST2] (OOB-17,shared=tcp) couldn't deliver OOB message [dst: server1/web, src: server2/web (4 headers), size=62 bytes, flags=OOB|DONT_BUNDLE|RSVP]: java.lang.IllegalStateException: channel is not connected > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:617) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:544) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:391) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:249) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:600) [jgroups-3.2.12.Final-redhat-1.jar:3.2.12.Final-redhat-1] > [incoming JGroups message] > It appears to just be a timing issue between shutdown of the channel and RequestCorrelator processing the message, which triggers a response message. > It would be good to either avoid triggering the exception in the first place, or suppress the error log during shutdown. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2678) LDAP credential is revealed when error occurs at startup

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2678?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2678: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1443122|https://bugzilla.redhat.com/show_bug.cgi?id=1443122] from VERIFIED to CLOSED > LDAP credential is revealed when error occurs at startup > -------------------------------------------------------- > > Key: WFCORE-2678 > URL: https://issues.jboss.org/browse/WFCORE-2678 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Environment: - EAP 6.4.13 > Reporter: Hisanobu Okuda > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta16 > > > When an error occurs at startup, LDAP credential is shown in the log file. It should not appear. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 June 2017