March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HIBERNATE-144) somes images have 404 on doc site

by Jared Morgan (JIRA)

[ https://issues.jboss.org/browse/HIBERNATE-144?page=com.atlassian.jira.plu... ] Jared Morgan moved JBDOCS-355 to HIBERNATE-144: ----------------------------------------------- Project: Hibernate Integration (was: Documentation) Key: HIBERNATE-144 (was: JBDOCS-355) Issue Type: Bug (was: Feature Request) Security: (was: Public) > somes images have 404 on doc site > --------------------------------- > > Key: HIBERNATE-144 > URL: https://issues.jboss.org/browse/HIBERNATE-144 > Project: Hibernate Integration > Issue Type: Bug > Reporter: Emmanuel Borlet > Assignee: Jared Morgan > Priority: Minor > > hello, > on this pages images have 404 : > http://docs.jboss.org/hibernate/orm/4.1/devguide/en-US/html/ch16.html > http://docs.jboss.org/hibernate/orm/4.3/devguide/en-US/html/ch16.html > Cordialement > Emmanuel Borlet -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-144) somes images have 404 on doc site

by Jared Morgan (JIRA)

[ https://issues.jboss.org/browse/HIBERNATE-144?page=com.atlassian.jira.plu... ] Jared Morgan commented on HIBERNATE-144: ---------------------------------------- Hi Emmanuel Thanks for taking the time for logging this bug. Looks like this book is missing some image files. Let me see if I can re-route this issue to the Hibernate project so they can fix the issue. Thanks for your help with keeping JBoss.org docs accurate. Cheers Jared > somes images have 404 on doc site > --------------------------------- > > Key: HIBERNATE-144 > URL: https://issues.jboss.org/browse/HIBERNATE-144 > Project: Hibernate Integration > Issue Type: Bug > Reporter: Emmanuel Borlet > Assignee: Jared Morgan > Priority: Minor > > hello, > on this pages images have 404 : > http://docs.jboss.org/hibernate/orm/4.1/devguide/en-US/html/ch16.html > http://docs.jboss.org/hibernate/orm/4.3/devguide/en-US/html/ch16.html > Cordialement > Emmanuel Borlet -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3163) EAP audit log should display the EAP version instead of the AS version

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3163?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-3163: -------------------------------------- Assignee: Brian Stansberry (was: John Doyle) > EAP audit log should display the EAP version instead of the AS version > ---------------------------------------------------------------------- > > Key: WFLY-3163 > URL: https://issues.jboss.org/browse/WFLY-3163 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > EAP audit log should display the EAP version instead of the AS version > Currently the audit log shows the AS version number instead of the EAP version. Example: > Feb 13 07:55:43 efjkffglk000000719 syslogappname[553]: 2014-02-13 07:55:43 - {"type" : "core", "r/o" : false, "booting" : false, "version" : "7.3.0.Final-redhat-14", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "10.10.10.250/10.10.10.250", "success" : true, "ops" : [{"address" : [{ "host" : "master" },{ "core-service" : "management" },{ "access" : "audit" },{ "logger" : "audit-log" }], "operation" : "write-attribute", "name" : "enabled", "value" : false, "operation-headers" : {"caller-type" : "user", "access-mechanism" : "NATIVE", "domain-uuid" : "fead80e4-690d-4bcf-af71-ecaf30f98381", "push-to-servers" : null}}]} > "version" : "7.3.0.Final-redhat-14" > This should show: > "version" : "6.2.1.GA" > There's a request that it show something like "6.2 CP01" but that is a patch file name, not a software version, and is unknown to the software. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3163) EAP audit log should display the EAP version instead of the AS version

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3163?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3163: ----------------------------------- > EAP audit log should display the EAP version instead of the AS version > ---------------------------------------------------------------------- > > Key: WFLY-3163 > URL: https://issues.jboss.org/browse/WFLY-3163 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Brian Stansberry > > EAP audit log should display the EAP version instead of the AS version > Currently the audit log shows the AS version number instead of the EAP version. Example: > Feb 13 07:55:43 efjkffglk000000719 syslogappname[553]: 2014-02-13 07:55:43 - {"type" : "core", "r/o" : false, "booting" : false, "version" : "7.3.0.Final-redhat-14", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "10.10.10.250/10.10.10.250", "success" : true, "ops" : [{"address" : [{ "host" : "master" },{ "core-service" : "management" },{ "access" : "audit" },{ "logger" : "audit-log" }], "operation" : "write-attribute", "name" : "enabled", "value" : false, "operation-headers" : {"caller-type" : "user", "access-mechanism" : "NATIVE", "domain-uuid" : "fead80e4-690d-4bcf-af71-ecaf30f98381", "push-to-servers" : null}}]} > "version" : "7.3.0.Final-redhat-14" > This should show: > "version" : "6.2.1.GA" > There's a request that it show something like "6.2 CP01" but that is a patch file name, not a software version, and is unknown to the software. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3163) EAP 6.2 audit log should display the EAP version instead of the AS version

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3163?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved PRODMGT-721 to WFLY-3163: ------------------------------------------------ Project: WildFly (was: Product Management) Key: WFLY-3163 (was: PRODMGT-721) Issue Type: Bug (was: Feature Request) Workflow: GIT Pull Request workflow (was: JBoss Platforms RFE Workflow v2) Affects Version/s: 8.0.0.Final (was: 6) Component/s: Domain Management (was: Enterprise Application Platform (EAP)) Security: Public > EAP 6.2 audit log should display the EAP version instead of the AS version > -------------------------------------------------------------------------- > > Key: WFLY-3163 > URL: https://issues.jboss.org/browse/WFLY-3163 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: John Doyle > > EAP audit log should display the EAP version instead of the AS version > Currently the audit log shows the AS version number instead of the EAP version. Example: > Feb 13 07:55:43 efjkffglk000000719 syslogappname[553]: 2014-02-13 07:55:43 - {"type" : "core", "r/o" : false, "booting" : false, "version" : "7.3.0.Final-redhat-14", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "10.10.10.250/10.10.10.250", "success" : true, "ops" : [{"address" : [{ "host" : "master" },{ "core-service" : "management" },{ "access" : "audit" },{ "logger" : "audit-log" }], "operation" : "write-attribute", "name" : "enabled", "value" : false, "operation-headers" : {"caller-type" : "user", "access-mechanism" : "NATIVE", "domain-uuid" : "fead80e4-690d-4bcf-af71-ecaf30f98381", "push-to-servers" : null}}]} > "version" : "7.3.0.Final-redhat-14" > This should show: > "version" : "6.2.1.GA" > There's a request that it show something like "6.2 CP01" but that is a patch file name, not a software version, and is unknown to the software. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3163) EAP audit log should display the EAP version instead of the AS version

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3163?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3163: ----------------------------------- Summary: EAP audit log should display the EAP version instead of the AS version (was: EAP 6.2 audit log should display the EAP version instead of the AS version) > EAP audit log should display the EAP version instead of the AS version > ---------------------------------------------------------------------- > > Key: WFLY-3163 > URL: https://issues.jboss.org/browse/WFLY-3163 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: John Doyle > > EAP audit log should display the EAP version instead of the AS version > Currently the audit log shows the AS version number instead of the EAP version. Example: > Feb 13 07:55:43 efjkffglk000000719 syslogappname[553]: 2014-02-13 07:55:43 - {"type" : "core", "r/o" : false, "booting" : false, "version" : "7.3.0.Final-redhat-14", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "10.10.10.250/10.10.10.250", "success" : true, "ops" : [{"address" : [{ "host" : "master" },{ "core-service" : "management" },{ "access" : "audit" },{ "logger" : "audit-log" }], "operation" : "write-attribute", "name" : "enabled", "value" : false, "operation-headers" : {"caller-type" : "user", "access-mechanism" : "NATIVE", "domain-uuid" : "fead80e4-690d-4bcf-af71-ecaf30f98381", "push-to-servers" : null}}]} > "version" : "7.3.0.Final-redhat-14" > This should show: > "version" : "6.2.1.GA" > There's a request that it show something like "6.2 CP01" but that is a patch file name, not a software version, and is unknown to the software. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3162) audit syslog handler should be able to automatically reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3162?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3162: ----------------------------------- Assignee: (was: John Doyle) > audit syslog handler should be able to automatically reconnect > -------------------------------------------------------------- > > Key: WFLY-3162 > URL: https://issues.jboss.org/browse/WFLY-3162 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > > When the syslog server goes down, WF will retry (up to 10 times we believe) to reconnect but will then give up. You can manually force a reconnect by issuing: > /host=master/core-service=management/access=audit/syslog-handler=mysyslog:recycle > This request is to make it possible to automate this and make it configurable at which interval it should try and reconnect -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3162) audit syslog handler should be able to automatically reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3162?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3162: ----------------------------------- Labels: EAP (was: ) > audit syslog handler should be able to automatically reconnect > -------------------------------------------------------------- > > Key: WFLY-3162 > URL: https://issues.jboss.org/browse/WFLY-3162 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Labels: EAP > > When the syslog server goes down, WF will retry (up to 10 times we believe) to reconnect but will then give up. You can manually force a reconnect by issuing: > /host=master/core-service=management/access=audit/syslog-handler=mysyslog:recycle > This request is to make it possible to automate this and make it configurable at which interval it should try and reconnect -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3162) audit syslog handler should be able to automatically reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3162?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved PRODMGT-773 to WFLY-3162: ------------------------------------------------ Project: WildFly (was: Product Management) Key: WFLY-3162 (was: PRODMGT-773) Workflow: GIT Pull Request workflow (was: JBoss Platforms RFE Workflow v2) Affects Version/s: 8.0.0.Final (was: 6) Component/s: Domain Management (was: Enterprise Application Platform (EAP)) Security: Public > audit syslog handler should be able to automatically reconnect > -------------------------------------------------------------- > > Key: WFLY-3162 > URL: https://issues.jboss.org/browse/WFLY-3162 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: John Doyle > > When the syslog server goes down, WF will retry (up to 10 times we believe) to reconnect but will then give up. You can manually force a reconnect by issuing: > /host=master/core-service=management/access=audit/syslog-handler=mysyslog:recycle > This request is to make it possible to automate this and make it configurable at which interval it should try and reconnect -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1801) DuplicateTest fails when testing OOB multicast to all three senders

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1801?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1801: ------------------------------------------- I managed to reproduce this issue locally on my Windows 7 partition, which, thankfully, is also slow as the machines in the QA lab. To recap, the failures occur for both TCP and UDP, and involve OOB multicast messages. Messages from one of the senders do not get through. Here are some new debugging results: - disable the OOB thread pool, the tests always pass on both UDP and TCP - enable the OOB thread pool, I always seem to get at least one failure on both TCP and UDP So, it appears this issue has something to do with use of the OOB thread pool. I also noticed that the assertion which is failing (the assertion which checks that at least some messages from all three senders has arrived) is checked after 10 seconds. Because this is not a performance test, there is no harm in extending this timeout to, say, 60 seconds. > DuplicateTest fails when testing OOB multicast to all three senders > ------------------------------------------------------------------- > > Key: JGRP-1801 > URL: https://issues.jboss.org/browse/JGRP-1801 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Windows (18), Solaris (2), RHEL(1) where (x) is the number of failures seen > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.14 > > > DuplicateTest does the following: > - creates three channels containing the DUPL layer called c1, c2, c3 > - DUPL is used to duplicate messages sent > - channel receiver for channel each keeps a map of messages received from each sender > - channels send messages: regular, OOB, or mixed > - the test checks that the messages received by each channel are correct in number and in order > The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: > {noformat} > Error Message > expected size=3, msgs: [C2, C1] > Stacktrace > java.lang.AssertionError > at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) > at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) > {noformat} -- 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

12 years, 1 month

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 March 2014