From wildfly-mail-list at quantentunnel.de Thu Jun 1 07:36:46 2017 From: wildfly-mail-list at quantentunnel.de (wildfly-mail-list at quantentunnel.de) Date: Thu, 1 Jun 2017 13:36:46 +0200 Subject: [wildfly-dev] Joining the dev-community and try to get involved Message-ID: An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/313c56cf/attachment.html From ttarrant at redhat.com Thu Jun 1 08:04:05 2017 From: ttarrant at redhat.com (Tristan Tarrant) Date: Thu, 1 Jun 2017 14:04:05 +0200 Subject: [wildfly-dev] WildFly's HipChat room Message-ID: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Hi all, I've complained in the past about the WildFly's team decision to move to HipChat, but I've always been able to access the chat room as a guest using the link provided on the homepage [1] Unfortunately that link no longer works, since it expects me to register with an e-mail account. Considering HipChat's stupid policy that disallows a single account to join multiple groups, I'm unwilling to "sacrifice" an e-mail address just for the few situations in which I need to get hold of one of you. Please fix it. Tristan [1] https://www.hipchat.com/gSW9XYz69 -- Tristan Tarrant Infinispan Lead JBoss, a division of Red Hat From david.lloyd at redhat.com Thu Jun 1 08:52:18 2017 From: david.lloyd at redhat.com (David M. Lloyd) Date: Thu, 1 Jun 2017 07:52:18 -0500 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <7f023bb9-1e86-5571-2855-d4aa6ce46a6d@redhat.com> At some point the link changed to https://www.hipchat.com/gGkjcXNgm for the developers room, so maybe that is a part of the problem. On 06/01/2017 07:04 AM, Tristan Tarrant wrote: > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. > > Tristan > > [1] https://www.hipchat.com/gSW9XYz69 > -- - DML From eduardo.santanadasilva at gmail.com Thu Jun 1 08:56:48 2017 From: eduardo.santanadasilva at gmail.com (=?UTF-8?Q?Eduardo_Sant=C2=B4Ana_da_Silva?=) Date: Thu, 1 Jun 2017 09:56:48 -0300 Subject: [wildfly-dev] Joining the dev-community and try to get involved In-Reply-To: References: Message-ID: You can check those links! http://www.jboss.org/get-involved/ http://wildfly.org/joinus/ 2017-06-01 8:36 GMT-03:00 : > > Hi there, > > I am using the wildfly maven plugin and ran into an NPE, as far as i know, > seems to be a bug. > The wildfly project page (https://docs.jboss.org/ > wildfly/plugins/maven/latest/mail-lists.html) does not give much > information about how to get involved, only this mailinglist and Jira ( > https://issues.jboss.org/projects/WFMP) for bugtracking. > > So maybe you can help me: > * How to file the bug. In Jira, should I use the "Red Hat Developer > Feedback (RHDFEED)" since it's the only project I can choose for a new > issue (the project I want to file the bug is "Wildfly Maven Plugin" though)? > * Since I already got into the code, I could provide a potential bugfix as > well. If possible, how is the correct way to create a pull request? > > If there's any tutorial about how to get involved that I missed, please be > so kind to share it with me and excuse my disturbance (-: > > Regards > Markus > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- ___________________________ Eduardo Sant'Ana da Silva - Ph.D. Researcher / IT Consultant -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/c83f7608/attachment-0001.html From tomaz.cerar at gmail.com Thu Jun 1 09:02:26 2017 From: tomaz.cerar at gmail.com (=?UTF-8?B?VG9tYcW+IENlcmFy?=) Date: Thu, 1 Jun 2017 15:02:26 +0200 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: Looks like Hipchat reset the urls for guest login https://blog.hipchat.com/2017/04/27/hipchat-security-notice-followup/ https://www.hipchat.com/gGkjcXNgm and https://www.hipchat.com/gFOhnVQke should work as for registration goes, you can create account with + notation which can be mapped back to your account. so you create account with mail ttarrant+wildfly at redhat.com and it should work. Hipchat client supports logging into multiple accounts for a while now. -- tomaz On Thu, Jun 1, 2017 at 2:04 PM, Tristan Tarrant wrote: > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. > > Tristan > > [1] https://www.hipchat.com/gSW9XYz69 > -- > Tristan Tarrant > Infinispan Lead > JBoss, a division of Red Hat > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/dd26e232/attachment.html From mazz at redhat.com Thu Jun 1 09:07:07 2017 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 1 Jun 2017 09:07:07 -0400 (EDT) Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <2070246001.26444542.1496322427977.JavaMail.zimbra@redhat.com> +1000 :) ----- Original Message ----- > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. > > Tristan > > [1] https://www.hipchat.com/gSW9XYz69 > -- > Tristan Tarrant > Infinispan Lead > JBoss, a division of Red Hat > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > From rsvoboda at redhat.com Thu Jun 1 09:11:48 2017 From: rsvoboda at redhat.com (Rostislav Svoboda) Date: Thu, 1 Jun 2017 09:11:48 -0400 (EDT) Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <183128027.26448535.1496322708845.JavaMail.zimbra@redhat.com> I think you could try to register using ttarrant+wildfly at redhat.com address is you are on gmail. https://www.cs.rutgers.edu/~watrous/plus-signs-in-email-addresses.html Rostislav ----- Original Message ----- > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. > > Tristan > > [1] https://www.hipchat.com/gSW9XYz69 > -- > Tristan Tarrant > Infinispan Lead > JBoss, a division of Red Hat > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > From asoldano at redhat.com Thu Jun 1 09:36:46 2017 From: asoldano at redhat.com (Alessio Soldano) Date: Thu, 1 Jun 2017 15:36:46 +0200 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <1ac20a9a-3dad-a9a6-4b6e-086a79d11988@redhat.com> Il 01/06/2017 14:04, Tristan Tarrant ha scritto: > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. Similar problem here, with the team split over 2 different hipchat groups... Cheers Alessio From darran.lofthouse at jboss.com Thu Jun 1 09:40:03 2017 From: darran.lofthouse at jboss.com (Darran Lofthouse) Date: Thu, 1 Jun 2017 14:40:03 +0100 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <1137b6c5-69d8-4d6d-fe45-38d8b34ba564@jboss.com> It is likely just an out of date link on the homepage as I think HipChat reset all the guest URLs. On 01/06/17 13:04, Tristan Tarrant wrote: > Hi all, > > I've complained in the past about the WildFly's team decision to move to > HipChat, but I've always been able to access the chat room as a guest > using the link provided on the homepage [1] > Unfortunately that link no longer works, since it expects me to register > with an e-mail account. Considering HipChat's stupid policy that > disallows a single account to join multiple groups, I'm unwilling to > "sacrifice" an e-mail address just for the few situations in which I > need to get hold of one of you. > > Please fix it. > > Tristan > > [1] https://www.hipchat.com/gSW9XYz69 > From jason.greene at redhat.com Thu Jun 1 09:50:43 2017 From: jason.greene at redhat.com (Jason Greene) Date: Thu, 1 Jun 2017 08:50:43 -0500 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <7f023bb9-1e86-5571-2855-d4aa6ce46a6d@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> <7f023bb9-1e86-5571-2855-d4aa6ce46a6d@redhat.com> Message-ID: Yeah I just tested both links on wildfly.org and they work fine. > On Jun 1, 2017, at 7:52 AM, David M. Lloyd wrote: > > At some point the link changed to https://www.hipchat.com/gGkjcXNgm for > the developers room, so maybe that is a part of the problem. > > On 06/01/2017 07:04 AM, Tristan Tarrant wrote: >> Hi all, >> >> I've complained in the past about the WildFly's team decision to move to >> HipChat, but I've always been able to access the chat room as a guest >> using the link provided on the homepage [1] >> Unfortunately that link no longer works, since it expects me to register >> with an e-mail account. Considering HipChat's stupid policy that >> disallows a single account to join multiple groups, I'm unwilling to >> "sacrifice" an e-mail address just for the few situations in which I >> need to get hold of one of you. >> >> Please fix it. >> >> Tristan >> >> [1] https://www.hipchat.com/gSW9XYz69 >> > > > -- > - DML > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat From tomaz.cerar at gmail.com Thu Jun 1 09:57:28 2017 From: tomaz.cerar at gmail.com (=?UTF-8?B?VG9tYcW+IENlcmFy?=) Date: Thu, 1 Jun 2017 15:57:28 +0200 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <7f023bb9-1e86-5571-2855-d4aa6ce46a6d@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> <7f023bb9-1e86-5571-2855-d4aa6ce46a6d@redhat.com> Message-ID: I've updated wildfly.org website to point to new URLs. -- tomaz On Thu, Jun 1, 2017 at 2:52 PM, David M. Lloyd wrote: > At some point the link changed to https://www.hipchat.com/gGkjcXNgm for > the developers room, so maybe that is a part of the problem. > > On 06/01/2017 07:04 AM, Tristan Tarrant wrote: > > Hi all, > > > > I've complained in the past about the WildFly's team decision to move to > > HipChat, but I've always been able to access the chat room as a guest > > using the link provided on the homepage [1] > > Unfortunately that link no longer works, since it expects me to register > > with an e-mail account. Considering HipChat's stupid policy that > > disallows a single account to join multiple groups, I'm unwilling to > > "sacrifice" an e-mail address just for the few situations in which I > > need to get hold of one of you. > > > > Please fix it. > > > > Tristan > > > > [1] https://www.hipchat.com/gSW9XYz69 > > > > > -- > - DML > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/95c6596d/attachment-0001.html From ehugonne at redhat.com Thu Jun 1 11:36:13 2017 From: ehugonne at redhat.com (Emmanuel Hugonnet) Date: Thu, 1 Jun 2017 17:36:13 +0200 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <183128027.26448535.1496322708845.JavaMail.zimbra@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> <183128027.26448535.1496322708845.JavaMail.zimbra@redhat.com> Message-ID: Works also without gmail account :) Multiple accounts doesn't work with the gnu/linux client as far as I know :( Emmanuel Le 01/06/2017 ? 15:11, Rostislav Svoboda a ?crit : > I think you could try to register using ttarrant+wildfly at redhat.com address is you are on gmail. > https://www.cs.rutgers.edu/~watrous/plus-signs-in-email-addresses.html > > Rostislav > > ----- Original Message ----- >> Hi all, >> >> I've complained in the past about the WildFly's team decision to move to >> HipChat, but I've always been able to access the chat room as a guest >> using the link provided on the homepage [1] >> Unfortunately that link no longer works, since it expects me to register >> with an e-mail account. Considering HipChat's stupid policy that >> disallows a single account to join multiple groups, I'm unwilling to >> "sacrifice" an e-mail address just for the few situations in which I >> need to get hold of one of you. >> >> Please fix it. >> >> Tristan >> >> [1] https://www.hipchat.com/gSW9XYz69 >> -- >> Tristan Tarrant >> Infinispan Lead >> JBoss, a division of Red Hat >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature Url : http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/eb23a9aa/attachment.bin From ttarrant at redhat.com Thu Jun 1 11:41:21 2017 From: ttarrant at redhat.com (Tristan Tarrant) Date: Thu, 1 Jun 2017 17:41:21 +0200 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> Message-ID: <02ef9706-9dbc-6fc5-e000-c805cca0c05f@redhat.com> On 6/1/17 3:02 PM, Toma? Cerar wrote: > as for registration goes, you can create account with + notation which > can be mapped back to your account. > > so you create account with mail ttarrant+wildfly at redhat.com > > and it should work. Nice, didn't know about that extension. > Hipchat client supports logging into multiple accounts for a while now. Implementing multiple logins instead of single-sign-on is not a fix: it's a workaround :) Tristan -- Tristan Tarrant Infinispan Lead JBoss, a division of Red Hat From tdiesler at redhat.com Thu Jun 1 11:54:10 2017 From: tdiesler at redhat.com (Thomas Diesler) Date: Thu, 1 Jun 2017 17:54:10 +0200 Subject: [wildfly-dev] WildFly-Camel-4.7.0 released Message-ID: <97E48029-BDC7-467A-B8A6-A6FA36D6D544@redhat.com> Folks, I?m happy to announce that wildfly-camel-4.7.0 has been released. WildFly-Camel 4.7.0 provides Camel-2.19.0 integration with WildFly-10.1.0 This is another upgrade release for supported Camel components, with a stong focus on AWS and other cloud services. Additional components in the supported set are: ? camel-ahc ? camel-ahc-ws ? camel-ahc-wss ? camel-aws-cw ? camel-aws-ddb ? camel-aws-ddbstream ? camel-aws-ec2 ? camel-aws-kinesis ? camel-aws-s3 ? camel-aws-sdb ? camel-aws-ses ? camel-aws-sns ? camel-aws-sqs ? camel-aws-swf ? camel-box ? camel-coap ? camel-couchdb ? camel-dropbox ? camel-facebook ? camel-github ? camel-http4s ? camel-influxdb ? camel-kubernetes ? camel-reactive-streams ? camel-rest-swagger ? camel-sjms2 Component upgrades include ? Camel-2.19.0 ? HawtIO-1.5.1 ? WildFly-Swarm-2017.6.0 In addition to that, we also resolved a number of other tasks and bugfixes . For details please see the 4.7.0 Milestone . Enjoy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/b2c32505/attachment.html From jperkins at redhat.com Thu Jun 1 11:58:28 2017 From: jperkins at redhat.com (James Perkins) Date: Thu, 1 Jun 2017 08:58:28 -0700 Subject: [wildfly-dev] Joining the dev-community and try to get involved In-Reply-To: References: Message-ID: On Thu, Jun 1, 2017 at 4:36 AM, wrote: > > Hi there, > > I am using the wildfly maven plugin and ran into an NPE, as far as i know, > seems to be a bug. > The wildfly project page (https://docs.jboss.org/ > wildfly/plugins/maven/latest/mail-lists.html) does not give much > information about how to get involved, only this mailinglist and Jira ( > https://issues.jboss.org/projects/WFMP) for bugtracking. > > So maybe you can help me: > * How to file the bug. In Jira, should I use the "Red Hat Developer > Feedback (RHDFEED)" since it's the only project I can choose for a new > issue (the project I want to file the bug is "Wildfly Maven Plugin" though)? > To file a bug for the wildfly-maven-plugin you can use the WFMP JIRA project, https://issues.jboss.org/projects/WFMP. > * Since I already got into the code, I could provide a potential bugfix as > well. If possible, how is the correct way to create a pull request? > The GitHub repo is here, https://github.com/wildfly/wildfly-maven-plugin, and pull requests are always welcome :) > > If there's any tutorial about how to get involved that I missed, please be > so kind to share it with me and excuse my disturbance (-: > > Regards > Markus > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- James R. Perkins JBoss by Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/ae98c9cc/attachment.html From sanne at hibernate.org Thu Jun 1 14:26:08 2017 From: sanne at hibernate.org (Sanne Grinovero) Date: Thu, 1 Jun 2017 19:26:08 +0100 Subject: [wildfly-dev] WildFly's HipChat room In-Reply-To: <02ef9706-9dbc-6fc5-e000-c805cca0c05f@redhat.com> References: <3a8a6352-6da4-0323-80d2-d48e9119659a@redhat.com> <02ef9706-9dbc-6fc5-e000-c805cca0c05f@redhat.com> Message-ID: On 1 Jun 2017 6:11 pm, "Tristan Tarrant" wrote: On 6/1/17 3:02 PM, Toma? Cerar wrote: > as for registration goes, you can create account with + notation which > can be mapped back to your account. > > so you create account with mail ttarrant+wildfly at redhat.com > > and it should work. Nice, didn't know about that extension. N.B. That's not an extension but part of the email standard. So the solution is not limited to Gmail users. I use it since ever when registering on websites so I know who's leaking my email... Unfortunately some websites don't allow it as they use a buggy Validator. > Hipchat client supports logging into multiple accounts for a while now. Implementing multiple logins instead of single-sign-on is not a fix: it's a workaround :) Tristan -- Tristan Tarrant Infinispan Lead JBoss, a division of Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170601/3dfb464e/attachment-0001.html From rory.odonnell at oracle.com Fri Jun 2 06:36:23 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 2 Jun 2017 11:36:23 +0100 Subject: [wildfly-dev] Announcing: Early-Access builds of JDK 9 for Alpine Linux/musl at jdk.java.net/9/ Message-ID: Hi Jason/Tomaz, ** *Announcing: Early-Access builds of JDK 9 for Alpine Linux/musl at jdk.java.net/9/ [1] * * As of today there are pre-built Early-Access (EA) JDK binaries for Alpine Linux/musl at jdk.java.net/9/** o look for ?Alpine Linux?. [1] * The Alpine Linux build is compatible with linux distributions that use the musl C library. *[2]* Feedback is very welcome via the portola-dev mailing list, remembering to subscribe to the mailing list first. *Proposed schedule change for JDK 9 [3]* JDK 9 Project continues to work toward the current goal of producing an initial Release Candidate build on 22 June. This proposal is to adjust the GA date in order to accommodate the additional time required to move through the JCP process. To be specific, we propose to move the GA date out by eight weeks, from 27 July to 21 September. Rgds,Rory [1] http://mail.openjdk.java.net/pipermail/portola-dev/2017-June/000191.html [2] http://www.musl-libc.org/ [3] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-May/005864.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170602/8af84b4f/attachment.html From david.lloyd at redhat.com Wed Jun 7 14:11:15 2017 From: david.lloyd at redhat.com (David M. Lloyd) Date: Wed, 7 Jun 2017 13:11:15 -0500 Subject: [wildfly-dev] WildFly Client Configuration and schema Message-ID: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> Something that has come up in a JIRA issue [1] is the question of whether the WildFly Client Configuration file should use a schema for its root element. The root of the "wildfly-client.xml" file is presently a single, namespace-less element named "configuration". The content of this element is a sequence of library-specific configuration, like this: The question is, should there be a schema for that root element? The entire schema would be something like: Then you'd have to put the configuration namespace in as well: WDYT? Is it worth having a whole schema/namespace for a single element? [1] https://issues.jboss.org/browse/ELY-1098 -- - DML From david.lloyd at redhat.com Wed Jun 7 17:35:44 2017 From: david.lloyd at redhat.com (David M. Lloyd) Date: Wed, 7 Jun 2017 16:35:44 -0500 Subject: [wildfly-dev] Minor API change Message-ID: This Elytron pull request [1] introduces a minor API change for users of modifiable security realms who iterate the identities within the realm. This change affects one test in wildfly-core. I have a commit [2] which, if [1] is accepted, I will relay into a pull request for wildfly-core which allows the test to compile and run with both the old and new code. If anyone sees a problem with changing this API, please let me know ASAP. [1] https://github.com/wildfly-security/wildfly-elytron/pull/872 [2] https://github.com/dmlloyd/wildfly-core/commit/835930eddca8d -- - DML From ropalka at redhat.com Thu Jun 8 03:15:31 2017 From: ropalka at redhat.com (Richard Opalka) Date: Thu, 8 Jun 2017 09:15:31 +0200 Subject: [wildfly-dev] WildFly Client Configuration and schema In-Reply-To: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> References: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> Message-ID: <1013265f-f008-71be-fb02-60946bf7bf4f@redhat.com> On 06/07/2017 08:11 PM, David M. Lloyd wrote: > WDYT? Is it worth having a whole schema/namespace for a single element? > > [1] https://issues.jboss.org/browse/ELY-1098 No Rio From jperkins at redhat.com Thu Jun 8 12:21:51 2017 From: jperkins at redhat.com (James Perkins) Date: Thu, 8 Jun 2017 09:21:51 -0700 Subject: [wildfly-dev] WildFly Client Configuration and schema In-Reply-To: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> References: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> Message-ID: I think from a users perspective it wouldn't hurt to have one. It's like documentation if you know how it works it's not useful. However if you're just trying to learn how it works it can be helpful. :) On Wed, Jun 7, 2017 at 11:11 AM, David M. Lloyd wrote: > Something that has come up in a JIRA issue [1] is the question of > whether the WildFly Client Configuration file should use a schema for > its root element. > > The root of the "wildfly-client.xml" file is presently a single, > namespace-less element named "configuration". The content of this > element is a sequence of library-specific configuration, like this: > > > > > > > > > > > > The question is, should there be a schema for that root element? The > entire schema would be something like: > > > > > > > > Then you'd have to put the configuration namespace in as well: > > > > > > > > > > > > WDYT? Is it worth having a whole schema/namespace for a single element? > > [1] https://issues.jboss.org/browse/ELY-1098 > -- > - DML > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- James R. Perkins JBoss by Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170608/0ce50b71/attachment.html From darran.lofthouse at jboss.com Fri Jun 9 06:07:26 2017 From: darran.lofthouse at jboss.com (Darran Lofthouse) Date: Fri, 9 Jun 2017 11:07:26 +0100 Subject: [wildfly-dev] WildFly Client Configuration and schema In-Reply-To: References: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> Message-ID: <461646f7-968d-c075-e668-c82c78122f53@jboss.com> The point is the schema will not be helpful - the configuration element can contain any element from any other namespace so from reading the schema all you will know is the element is called 'configuration', you will know it's namespace and you know it can contain anything. If we do add this we will probably want it in by mid next week at the latest - if we are mandating the namespace is specified we will want some time to find any existing config files that don't contain it. Regards, Darran Lofthouse. On 08/06/17 17:21, James Perkins wrote: > I think from a users perspective it wouldn't hurt to have one. It's like > documentation if you know how it works it's not useful. However if > you're just trying to learn how it works it can be helpful. :) > > On Wed, Jun 7, 2017 at 11:11 AM, David M. Lloyd > wrote: > > Something that has come up in a JIRA issue [1] is the question of > whether the WildFly Client Configuration file should use a schema for > its root element. > > The root of the "wildfly-client.xml" file is presently a single, > namespace-less element named "configuration". The content of this > element is a sequence of library-specific configuration, like this: > > > > > > > > > > > > The question is, should there be a schema for that root element? The > entire schema would be something like: > > > > > > > > Then you'd have to put the configuration namespace in as well: > > > > > > > > > > > > WDYT? Is it worth having a whole schema/namespace for a single element? > > [1] https://issues.jboss.org/browse/ELY-1098 > > -- > - DML > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > > > -- > James R. Perkins > JBoss by Red Hat > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > From jperkins at redhat.com Fri Jun 9 11:01:35 2017 From: jperkins at redhat.com (James Perkins) Date: Fri, 9 Jun 2017 08:01:35 -0700 Subject: [wildfly-dev] WildFly Client Configuration and schema In-Reply-To: <461646f7-968d-c075-e668-c82c78122f53@jboss.com> References: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> <461646f7-968d-c075-e668-c82c78122f53@jboss.com> Message-ID: It's really the description of the single tag that would be of benefit IMO. I suppose though really that could be documented elsewhere. I don't really have a strong opinion one way or the other on it. On Fri, Jun 9, 2017 at 3:07 AM, Darran Lofthouse wrote: > The point is the schema will not be helpful - the configuration element > can contain any element from any other namespace so from reading the schema > all you will know is the element is called 'configuration', you will know > it's namespace and you know it can contain anything. > > If we do add this we will probably want it in by mid next week at the > latest - if we are mandating the namespace is specified we will want some > time to find any existing config files that don't contain it. > > Regards, > Darran Lofthouse. > > > > On 08/06/17 17:21, James Perkins wrote: > >> I think from a users perspective it wouldn't hurt to have one. It's like >> documentation if you know how it works it's not useful. However if >> you're just trying to learn how it works it can be helpful. :) >> >> On Wed, Jun 7, 2017 at 11:11 AM, David M. Lloyd > > wrote: >> >> Something that has come up in a JIRA issue [1] is the question of >> whether the WildFly Client Configuration file should use a schema for >> its root element. >> >> The root of the "wildfly-client.xml" file is presently a single, >> namespace-less element named "configuration". The content of this >> element is a sequence of library-specific configuration, like this: >> >> >> >> >> >> >> >> >> >> >> >> The question is, should there be a schema for that root element? The >> entire schema would be something like: >> >> >> >> >> >> >> >> Then you'd have to put the configuration namespace in as well: >> >> >> >> >> >> >> >> >> >> >> >> WDYT? Is it worth having a whole schema/namespace for a single >> element? >> >> [1] https://issues.jboss.org/browse/ELY-1098 >> >> -- >> - DML >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> >> >> >> >> >> -- >> James R. Perkins >> JBoss by Red Hat >> >> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> >> -- James R. Perkins JBoss by Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170609/3f666c97/attachment-0001.html From darran.lofthouse at jboss.com Fri Jun 9 11:56:01 2017 From: darran.lofthouse at jboss.com (Darran Lofthouse) Date: Fri, 9 Jun 2017 16:56:01 +0100 Subject: [wildfly-dev] WildFly Client Configuration and schema In-Reply-To: References: <94e8ca40-5fac-6fe6-86a6-a851d481f1e3@redhat.com> <461646f7-968d-c075-e668-c82c78122f53@jboss.com> Message-ID: <2518bf93-9480-07c7-7542-f2ea82ed35c3@jboss.com> We probably do want to make sure we list somewhere the known supported types that can be used in a configuration element. On 09/06/17 16:01, James Perkins wrote: > It's really the description of the single tag that would be of benefit > IMO. I suppose though really that could be documented elsewhere. I don't > really have a strong opinion one way or the other on it. > > On Fri, Jun 9, 2017 at 3:07 AM, Darran Lofthouse > > wrote: > > The point is the schema will not be helpful - the configuration > element can contain any element from any other namespace so from > reading the schema all you will know is the element is called > 'configuration', you will know it's namespace and you know it can > contain anything. > > If we do add this we will probably want it in by mid next week at > the latest - if we are mandating the namespace is specified we will > want some time to find any existing config files that don't contain it. > > Regards, > Darran Lofthouse. > > > > On 08/06/17 17:21, James Perkins wrote: > > I think from a users perspective it wouldn't hurt to have one. > It's like > documentation if you know how it works it's not useful. However if > you're just trying to learn how it works it can be helpful. :) > > On Wed, Jun 7, 2017 at 11:11 AM, David M. Lloyd > > >> > wrote: > > Something that has come up in a JIRA issue [1] is the > question of > whether the WildFly Client Configuration file should use a > schema for > its root element. > > The root of the "wildfly-client.xml" file is presently a single, > namespace-less element named "configuration". The content > of this > element is a sequence of library-specific configuration, > like this: > > > > > > > > > > > > The question is, should there be a schema for that root > element? The > entire schema would be something like: > > > > > > > > Then you'd have to put the configuration namespace in as well: > > > > > > > > > > > > WDYT? Is it worth having a whole schema/namespace for a > single element? > > [1] https://issues.jboss.org/browse/ELY-1098 > > > > -- > - DML > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > > > > > -- > James R. Perkins > JBoss by Red Hat > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > > > -- > James R. Perkins > JBoss by Red Hat From asoldano at redhat.com Wed Jun 14 05:42:56 2017 From: asoldano at redhat.com (Alessio Soldano) Date: Wed, 14 Jun 2017 11:42:56 +0200 Subject: [wildfly-dev] JSON-P 1.1 and JSON-B 1.0 support Message-ID: <7d225c1a-ed20-c957-2a79-b13254efb07e@redhat.com> Hi, wrt to [1][2], has anything already been discussed and/or implemented? Any plans / decision on relying on specific third party libraries? Asking as that touches JAX-RS 2.1, which the RESTEasy team is currently working on. Cheers Alessio [1] https://issues.jboss.org/browse/WFLY-6460 [2] https://issues.jboss.org/browse/WFLY-7185 From rory.odonnell at oracle.com Fri Jun 16 06:17:38 2017 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 16 Jun 2017 11:17:38 +0100 Subject: [wildfly-dev] JDK 9 EA Build 174 & JDK 8u152 b04 are available on jdk.java.net Message-ID: Hi Jason/Tomaz, *JDK 9 Early Access* build 174 is available at : - jdk.java.net/9/ A summary of all the changes in this build are listed here . Changes which were introduced since the last availability email that may be of interest : * b172 - JDK-8179014 : JFileChooser with Windows look and feel crashes on win 10 * b173 - JDK-8180582 : the bind to rmiregistry is rejected by registryFilter even though registryFilter is set * b174 - JDK-8181702 : deprecate for removal the following tool modules:jdk.xml.bind and jdk.xml.ws *JDK 9 Schedule Update* * The new GA date for JDK 9 is now set to 2017-09-21 [1] * We have updated the OpenJDK JDK 9 project page [2] with the new milestones and GA date. *JDK 8u152 Early Access* build 04 is available at : - jdk.java.net/8/ A summary of all the changes in this build are listed here . Information and schedules specific to OpenJDK 8u152 release [3] Rgds,Rory [1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005867.html [2] http://openjdk.java.net/projects/jdk9/ [3] http://openjdk.java.net/projects/jdk8u/releases/8u152.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170616/1456a7e7/attachment.html From jperkins at redhat.com Fri Jun 16 12:06:08 2017 From: jperkins at redhat.com (James Perkins) Date: Fri, 16 Jun 2017 09:06:08 -0700 Subject: [wildfly-dev] JSON-P 1.1 and JSON-B 1.0 support In-Reply-To: <7d225c1a-ed20-c957-2a79-b13254efb07e@redhat.com> References: <7d225c1a-ed20-c957-2a79-b13254efb07e@redhat.com> Message-ID: Hi Alessio, Sorry for the late reply I must have missed this message. Anyway for JSON-P 1.0 we just use the RI. I was planning on just using the RI for 1.1and JSON-B as well. Both JSR's are final. I haven't however tried to integrate them at this point, but I don't see any obvious issues with just using the RI. On Wed, Jun 14, 2017 at 2:42 AM, Alessio Soldano wrote: > Hi, > > wrt to [1][2], has anything already been discussed and/or implemented? > Any plans / decision on relying on specific third party libraries? > Asking as that touches JAX-RS 2.1, which the RESTEasy team is currently > working on. > > Cheers > > Alessio > > > [1] https://issues.jboss.org/browse/WFLY-6460 > > [2] https://issues.jboss.org/browse/WFLY-7185 > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- James R. Perkins JBoss by Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170616/b1762df4/attachment.html From asoldano at redhat.com Fri Jun 16 12:38:02 2017 From: asoldano at redhat.com (Alessio Soldano) Date: Fri, 16 Jun 2017 18:38:02 +0200 Subject: [wildfly-dev] JSON-P 1.1 and JSON-B 1.0 support In-Reply-To: References: <7d225c1a-ed20-c957-2a79-b13254efb07e@redhat.com> Message-ID: <467ce4ba-475f-f45e-c5cb-b41ae9e77ff6@redhat.com> OK, thanks! Il 16/06/2017 18:06, James Perkins ha scritto: > Hi Alessio, > Sorry for the late reply I must have missed this message. Anyway for > JSON-P 1.0 we just use the RI. I was planning on just using the RI for > 1.1and JSON-B as well. Both JSR's are final. I haven't however tried > to integrate them at this point, but I don't see any obvious issues > with just using the RI. > > On Wed, Jun 14, 2017 at 2:42 AM, Alessio Soldano > wrote: > > Hi, > > wrt to [1][2], has anything already been discussed and/or implemented? > Any plans / decision on relying on specific third party libraries? > Asking as that touches JAX-RS 2.1, which the RESTEasy team is > currently > working on. > > Cheers > > Alessio > > > [1] https://issues.jboss.org/browse/WFLY-6460 > > > [2] https://issues.jboss.org/browse/WFLY-7185 > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > > > -- > James R. Perkins > JBoss by Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170616/fd17defb/attachment.html From kkhan at redhat.com Sat Jun 17 06:12:25 2017 From: kkhan at redhat.com (Kabir Khan) Date: Sat, 17 Jun 2017 11:12:25 +0100 Subject: [wildfly-dev] Test Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170617/336245fb/attachment-0001.html From kabir.khan at jboss.com Thu Jun 22 02:35:28 2017 From: kabir.khan at jboss.com (Kabir Khan) Date: Thu, 22 Jun 2017 07:35:28 +0100 Subject: [wildfly-dev] AuditLog Test failures/JBoss Modules. In-Reply-To: References: Message-ID: <4E622EAB-FAD2-442D-B4FA-FF5D3D2795D4@jboss.com> See below. I have been seeing this a bit recently, At least the JMXAuditLogTestCase failure is due to that JBoss Modules has a WeakReference to the ServiceLoaders. When the weak reference is cleared this results (via the WeakReference's ReferenceQueue and the ModuleLoader's Reaper) in a call to unregister the MBean associated with the ServiceLoader, which shows up as an additional unexpected entry in the AuditLog. This clearing of the weak reference is unpredictable and can happen at any time. I plan to fix this test test today, and to add a better message to the AuditLogBootingSyslogTest. Example failures: https://ci.wildfly.org/viewLog.html?buildId=65226&buildTypeId=WildFlyCore_PullRequestWindows https://ci.wildfly.org/viewLog.html?buildId=65225&buildTypeId=WildFlyCore_PullRequest > On 22 Jun 2017, at 00:55, James R. Perkins wrote: > > Hmm... ...kind of weird that two log related tests failed however these are audit log tests which this should touch at all. retest this please. > > ? > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. > From darran.lofthouse at jboss.com Tue Jun 27 05:38:14 2017 From: darran.lofthouse at jboss.com (Darran Lofthouse) Date: Tue, 27 Jun 2017 09:38:14 +0000 Subject: [wildfly-dev] Upgrade to WildFly Elytron 1.1.0.Beta54 Message-ID: For any components with a dependency on WildFly Elytron I would recommend upgrading to the 1.1.0.Beta54 release which was released last week to double check all API usage is up to date. We don't expect many more changes now as we are heading into the candidate release this week but if any changes are required we will e-mail this list first. One change we do know is on it's way is next week we will be removing PrincipalDecoder from the project entirely, this is one of the earliest APIs we added but has now been superseded by the principal transformers represented by Function. Regards, Darran Lofthouse. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170627/299f8de4/attachment.html From mmusgrov at redhat.com Wed Jun 28 07:31:46 2017 From: mmusgrov at redhat.com (Michael Musgrove) Date: Wed, 28 Jun 2017 12:31:46 +0100 Subject: [wildfly-dev] Runtime only resources Message-ID: We have a transaction case where the customer is trying to delete a (transaction log) model resource via the CLI and is seeing the error: "was directly invoked by the user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain." This is coming from ControllerLogger#modelUpdateNotAuthorized (in wildfly-core) because we define the resource as *not* being runtime only: public boolean isRuntime() {return false;} My question is should we be defining the resource as a runtime resource or should we tell the customer not to delete the resouce from the controller? Thanks, Mike -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. JBoss, by Red Hat Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170628/1946c877/attachment.html From mmusgrov at redhat.com Wed Jun 28 09:27:17 2017 From: mmusgrov at redhat.com (Michael Musgrove) Date: Wed, 28 Jun 2017 14:27:17 +0100 Subject: [wildfly-dev] Runtime only resources In-Reply-To: References: Message-ID: The operation used to work and I suspect that the root cause is WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the fix for the transaction subsystem is https://issues.jboss.org/browse/JBEAP-11651. It would be great if someone with more knowledge than I of the domain model could verify my hypothesis. On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove wrote: > We have a transaction case where the customer is trying to delete a > (transaction log) model resource via the CLI and is seeing the error: > > "was directly invoked by the user. User operations are not permitted to > directly update the persistent configuration of a server in a managed > domain." > > This is coming from ControllerLogger#modelUpdateNotAuthorized (in > wildfly-core) because we define the resource as *not* being runtime only: > > public boolean isRuntime() {return false;} > > My question is should we be defining the resource as a runtime resource or > should we tell the customer not to delete the resouce from the controller? > > Thanks, > Mike > > > -- > Michael Musgrove > Transactions Team > e: mmusgrov at redhat.com > > Our mission:To be the catalyst in communities of customers, contributors, > and partners creating better technology the open source way. > > JBoss, by Red Hat > Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale > Road, Co. Cork. > Registered in the Companies Registration Office, Parnell House, 14 Parnell > Square, Dublin 1, Ireland, No.304873 > Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, > Keith Phelan, Matt Parson (USA) > -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. JBoss, by Red Hat Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170628/cde87562/attachment.html From brian.stansberry at redhat.com Wed Jun 28 12:51:43 2017 From: brian.stansberry at redhat.com (Brian Stansberry) Date: Wed, 28 Jun 2017 11:51:43 -0500 Subject: [wildfly-dev] Runtime only resources In-Reply-To: References: Message-ID: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> I?ll have a look. > On Jun 28, 2017, at 8:27 AM, Michael Musgrove wrote: > > The operation used to work and I suspect that the root cause is WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the fix for the transaction subsystem is https://issues.jboss.org/browse/JBEAP-11651. It would be great if someone with more knowledge than I of the domain model could verify my hypothesis. > > On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove wrote: > We have a transaction case where the customer is trying to delete a (transaction log) model resource via the CLI and is seeing the error: > > "was directly invoked by the user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain." > > This is coming from ControllerLogger#modelUpdateNotAuthorized (in wildfly-core) because we define the resource as *not* being runtime only: > > public boolean isRuntime() {return false;} > > My question is should we be defining the resource as a runtime resource or should we tell the customer not to delete the resouce from the controller? > > Thanks, > Mike > > > -- > Michael Musgrove > Transactions Team > e: mmusgrov at redhat.com > > Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. > > JBoss, by Red Hat > Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. > Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 > Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) > > > > -- > Michael Musgrove > Transactions Team > e: mmusgrov at redhat.com > > Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. > > JBoss, by Red Hat > Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. > Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 > Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) > _______________________________________________ > wildfly-dev mailing list > wildfly-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- Brian Stansberry Manager, Senior Principal Software Engineer JBoss by Red Hat From brian.stansberry at redhat.com Wed Jun 28 13:17:26 2017 From: brian.stansberry at redhat.com (Brian Stansberry) Date: Wed, 28 Jun 2017 12:17:26 -0500 Subject: [wildfly-dev] Runtime only resources In-Reply-To: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> References: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> Message-ID: <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> What is the operation they are trying to invoke? LogStoreResource itself isn?t runtime-only but its children are. The ?delete? operations on the ?transactions? and ?participants? children will trigger a check that could lead to ControllerLogger#modelUpdateNotAuthorized, but those resources are runtime-only. One possibibility is the child they are trying to delete is already gone (these are dynamic) so perhaps since it?s non-existent the fact that it?s runtime-only is not being detected. I?ll work up a quick improvement that will help with that. > On Jun 28, 2017, at 11:51 AM, Brian Stansberry wrote: > > I?ll have a look. > >> On Jun 28, 2017, at 8:27 AM, Michael Musgrove wrote: >> >> The operation used to work and I suspect that the root cause is WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the fix for the transaction subsystem is https://issues.jboss.org/browse/JBEAP-11651. It would be great if someone with more knowledge than I of the domain model could verify my hypothesis. >> >> On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove wrote: >> We have a transaction case where the customer is trying to delete a (transaction log) model resource via the CLI and is seeing the error: >> >> "was directly invoked by the user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain." >> >> This is coming from ControllerLogger#modelUpdateNotAuthorized (in wildfly-core) because we define the resource as *not* being runtime only: >> >> public boolean isRuntime() {return false;} >> >> My question is should we be defining the resource as a runtime resource or should we tell the customer not to delete the resouce from the controller? >> >> Thanks, >> Mike >> >> >> -- >> Michael Musgrove >> Transactions Team >> e: mmusgrov at redhat.com >> >> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. >> >> JBoss, by Red Hat >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. >> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) >> >> >> >> -- >> Michael Musgrove >> Transactions Team >> e: mmusgrov at redhat.com >> >> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. >> >> JBoss, by Red Hat >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. >> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > -- > Brian Stansberry > Manager, Senior Principal Software Engineer > JBoss by Red Hat > > > -- Brian Stansberry Manager, Senior Principal Software Engineer JBoss by Red Hat From mmusgrov at redhat.com Wed Jun 28 13:19:58 2017 From: mmusgrov at redhat.com (Michael Musgrove) Date: Wed, 28 Jun 2017 18:19:58 +0100 Subject: [wildfly-dev] Runtime only resources In-Reply-To: <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> References: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> Message-ID: Thanks for looking into this. The operation they are running is: [domain at jboss7.pro.intra.rs.gov.br:9990 /] /host=host-jbosshost7-1/server=GPD1/subsystem=transactions/log-store=log-store/transactions=0\:ffff0afc4420\:3b2568af\:594b9528\::delete() { "outcome" => "failed", "result" => undefined, "failure-description" => "WFLYCTL0249: Opera??o 'delete' marcada no recurso '[ (\"subsystem\" => \"transactions\"), (\"log-store\" => \"log-store\"), (\"transactions\" => \"0:ffff0afc4420:3b2568af:594b9528:\") ]' foi diretamente invocada pelo usu?rio. As opera??es do usu?rio n?o s?o permitidas para atualizar diretamente a configura??o persistente de um servidor no domain controller.", "rolled-back" => true } On Wed, Jun 28, 2017 at 6:17 PM, Brian Stansberry < brian.stansberry at redhat.com> wrote: > What is the operation they are trying to invoke? > > LogStoreResource itself isn?t runtime-only but its children are. The > ?delete? operations on the ?transactions? and ?participants? children will > trigger a check that could lead to ControllerLogger#modelUpdateNotAuthorized, > but those resources are runtime-only. > > One possibibility is the child they are trying to delete is already gone > (these are dynamic) so perhaps since it?s non-existent the fact that it?s > runtime-only is not being detected. I?ll work up a quick improvement that > will help with that. > > > > On Jun 28, 2017, at 11:51 AM, Brian Stansberry < > brian.stansberry at redhat.com> wrote: > > > > I?ll have a look. > > > >> On Jun 28, 2017, at 8:27 AM, Michael Musgrove > wrote: > >> > >> The operation used to work and I suspect that the root cause is > WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the > fix for the transaction subsystem is https://issues.jboss.org/ > browse/JBEAP-11651. It would be great if someone with more knowledge than > I of the domain model could verify my hypothesis. > >> > >> On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove > wrote: > >> We have a transaction case where the customer is trying to delete a > (transaction log) model resource via the CLI and is seeing the error: > >> > >> "was directly invoked by the user. User operations are not permitted to > directly update the persistent configuration of a server in a managed > domain." > >> > >> This is coming from ControllerLogger#modelUpdateNotAuthorized (in > wildfly-core) because we define the resource as *not* being runtime only: > >> > >> public boolean isRuntime() {return false;} > >> > >> My question is should we be defining the resource as a runtime resource > or should we tell the customer not to delete the resouce from the > controller? > >> > >> Thanks, > >> Mike > >> > >> > >> -- > >> Michael Musgrove > >> Transactions Team > >> e: mmusgrov at redhat.com > >> > >> Our mission:To be the catalyst in communities of customers, > contributors, and partners creating better technology the open source way. > >> > >> JBoss, by Red Hat > >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, > Kinsale Road, Co. Cork. > >> Registered in the Companies Registration Office, Parnell House, 14 > Parnell Square, Dublin 1, Ireland, No.304873 > >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael > O'Neill, Keith Phelan, Matt Parson (USA) > >> > >> > >> > >> -- > >> Michael Musgrove > >> Transactions Team > >> e: mmusgrov at redhat.com > >> > >> Our mission:To be the catalyst in communities of customers, > contributors, and partners creating better technology the open source way. > >> > >> JBoss, by Red Hat > >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, > Kinsale Road, Co. Cork. > >> Registered in the Companies Registration Office, Parnell House, 14 > Parnell Square, Dublin 1, Ireland, No.304873 > >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael > O'Neill, Keith Phelan, Matt Parson (USA) > >> _______________________________________________ > >> wildfly-dev mailing list > >> wildfly-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > -- > > Brian Stansberry > > Manager, Senior Principal Software Engineer > > JBoss by Red Hat > > > > > > > > -- > Brian Stansberry > Manager, Senior Principal Software Engineer > JBoss by Red Hat > > > > -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. JBoss, by Red Hat Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170628/3acfdedc/attachment.html From brian.stansberry at redhat.com Wed Jun 28 13:36:14 2017 From: brian.stansberry at redhat.com (Brian Stansberry) Date: Wed, 28 Jun 2017 12:36:14 -0500 Subject: [wildfly-dev] Runtime only resources In-Reply-To: References: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> Message-ID: https://github.com/wildfly/wildfly/compare/master...bstansberry:tx-runtime-only is the quick improvement I mentioned. https://ci.wildfly.org/viewLog.html?buildId=66224&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments is a custom CI job for that branch. (I?ve done no testing locally other than checking the transactions module compiles.) I don?t see how that op would get to ControllerLogger#modelUpdateNotAuthorized though, unless the transactions=0\:ffff0afc4420\:3b2568af\:594b9528\: resource doesn?t exist. If it doesn?t then the op would fail anyway, just with a different message. > On Jun 28, 2017, at 12:19 PM, Michael Musgrove wrote: > > Thanks for looking into this. The operation they are running is: > > [domain at jboss7.pro.intra.rs.gov.br:9990 /] /host=host-jbosshost7-1/server=GPD1/subsystem=transactions/log-store=log-store/transactions=0\:ffff0afc4420\:3b2568af\:594b9528\::delete() > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0249: Opera??o 'delete' marcada no recurso '[ > (\"subsystem\" => \"transactions\"), > (\"log-store\" => \"log-store\"), > (\"transactions\" => \"0:ffff0afc4420:3b2568af:594b9528:\") > ]' foi diretamente invocada pelo usu?rio. As opera??es do usu?rio n?o s?o permitidas para atualizar diretamente a configura??o persistente de um servidor no domain controller.", > "rolled-back" => true > } > > On Wed, Jun 28, 2017 at 6:17 PM, Brian Stansberry wrote: > What is the operation they are trying to invoke? > > LogStoreResource itself isn?t runtime-only but its children are. The ?delete? operations on the ?transactions? and ?participants? children will trigger a check that could lead to ControllerLogger#modelUpdateNotAuthorized, but those resources are runtime-only. > > One possibibility is the child they are trying to delete is already gone (these are dynamic) so perhaps since it?s non-existent the fact that it?s runtime-only is not being detected. I?ll work up a quick improvement that will help with that. > > > > On Jun 28, 2017, at 11:51 AM, Brian Stansberry wrote: > > > > I?ll have a look. > > > >> On Jun 28, 2017, at 8:27 AM, Michael Musgrove wrote: > >> > >> The operation used to work and I suspect that the root cause is WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the fix for the transaction subsystem is https://issues.jboss.org/browse/JBEAP-11651. It would be great if someone with more knowledge than I of the domain model could verify my hypothesis. > >> > >> On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove wrote: > >> We have a transaction case where the customer is trying to delete a (transaction log) model resource via the CLI and is seeing the error: > >> > >> "was directly invoked by the user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain." > >> > >> This is coming from ControllerLogger#modelUpdateNotAuthorized (in wildfly-core) because we define the resource as *not* being runtime only: > >> > >> public boolean isRuntime() {return false;} > >> > >> My question is should we be defining the resource as a runtime resource or should we tell the customer not to delete the resouce from the controller? > >> > >> Thanks, > >> Mike > >> > >> > >> -- > >> Michael Musgrove > >> Transactions Team > >> e: mmusgrov at redhat.com > >> > >> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. > >> > >> JBoss, by Red Hat > >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. > >> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 > >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) > >> > >> > >> > >> -- > >> Michael Musgrove > >> Transactions Team > >> e: mmusgrov at redhat.com > >> > >> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. > >> > >> JBoss, by Red Hat > >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. > >> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 > >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) > >> _______________________________________________ > >> wildfly-dev mailing list > >> wildfly-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > > -- > > Brian Stansberry > > Manager, Senior Principal Software Engineer > > JBoss by Red Hat > > > > > > > > -- > Brian Stansberry > Manager, Senior Principal Software Engineer > JBoss by Red Hat > > > > > > > -- > Michael Musgrove > Transactions Team > e: mmusgrov at redhat.com > > Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. > > JBoss, by Red Hat > Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. > Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 > Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) -- Brian Stansberry Manager, Senior Principal Software Engineer JBoss by Red Hat From brian.stansberry at redhat.com Wed Jun 28 17:14:31 2017 From: brian.stansberry at redhat.com (Brian Stansberry) Date: Wed, 28 Jun 2017 16:14:31 -0500 Subject: [wildfly-dev] Runtime only resources In-Reply-To: References: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> Message-ID: https://github.com/wildfly/wildfly/pull/10258 will result in the correct failure message when ?delete? is invoked against a non-existing resource. > On Jun 28, 2017, at 12:36 PM, Brian Stansberry wrote: > > https://github.com/wildfly/wildfly/compare/master...bstansberry:tx-runtime-only is the quick improvement I mentioned. > > https://ci.wildfly.org/viewLog.html?buildId=66224&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments is a custom CI job for that branch. (I?ve done no testing locally other than checking the transactions module compiles.) > > I don?t see how that op would get to ControllerLogger#modelUpdateNotAuthorized though, unless the transactions=0\:ffff0afc4420\:3b2568af\:594b9528\: resource doesn?t exist. If it doesn?t then the op would fail anyway, just with a different message. > >> On Jun 28, 2017, at 12:19 PM, Michael Musgrove wrote: >> >> Thanks for looking into this. The operation they are running is: >> >> [domain at jboss7.pro.intra.rs.gov.br:9990 /] /host=host-jbosshost7-1/server=GPD1/subsystem=transactions/log-store=log-store/transactions=0\:ffff0afc4420\:3b2568af\:594b9528\::delete() >> { >> "outcome" => "failed", >> "result" => undefined, >> "failure-description" => "WFLYCTL0249: Opera??o 'delete' marcada no recurso '[ >> (\"subsystem\" => \"transactions\"), >> (\"log-store\" => \"log-store\"), >> (\"transactions\" => \"0:ffff0afc4420:3b2568af:594b9528:\") >> ]' foi diretamente invocada pelo usu?rio. As opera??es do usu?rio n?o s?o permitidas para atualizar diretamente a configura??o persistente de um servidor no domain controller.", >> "rolled-back" => true >> } >> >> On Wed, Jun 28, 2017 at 6:17 PM, Brian Stansberry wrote: >> What is the operation they are trying to invoke? >> >> LogStoreResource itself isn?t runtime-only but its children are. The ?delete? operations on the ?transactions? and ?participants? children will trigger a check that could lead to ControllerLogger#modelUpdateNotAuthorized, but those resources are runtime-only. >> >> One possibibility is the child they are trying to delete is already gone (these are dynamic) so perhaps since it?s non-existent the fact that it?s runtime-only is not being detected. I?ll work up a quick improvement that will help with that. >> >> >>> On Jun 28, 2017, at 11:51 AM, Brian Stansberry wrote: >>> >>> I?ll have a look. >>> >>>> On Jun 28, 2017, at 8:27 AM, Michael Musgrove wrote: >>>> >>>> The operation used to work and I suspect that the root cause is WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the fix for the transaction subsystem is https://issues.jboss.org/browse/JBEAP-11651. It would be great if someone with more knowledge than I of the domain model could verify my hypothesis. >>>> >>>> On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove wrote: >>>> We have a transaction case where the customer is trying to delete a (transaction log) model resource via the CLI and is seeing the error: >>>> >>>> "was directly invoked by the user. User operations are not permitted to directly update the persistent configuration of a server in a managed domain." >>>> >>>> This is coming from ControllerLogger#modelUpdateNotAuthorized (in wildfly-core) because we define the resource as *not* being runtime only: >>>> >>>> public boolean isRuntime() {return false;} >>>> >>>> My question is should we be defining the resource as a runtime resource or should we tell the customer not to delete the resouce from the controller? >>>> >>>> Thanks, >>>> Mike >>>> >>>> >>>> -- >>>> Michael Musgrove >>>> Transactions Team >>>> e: mmusgrov at redhat.com >>>> >>>> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. >>>> >>>> JBoss, by Red Hat >>>> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. >>>> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 >>>> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) >>>> >>>> >>>> >>>> -- >>>> Michael Musgrove >>>> Transactions Team >>>> e: mmusgrov at redhat.com >>>> >>>> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. >>>> >>>> JBoss, by Red Hat >>>> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. >>>> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 >>>> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) >>>> _______________________________________________ >>>> wildfly-dev mailing list >>>> wildfly-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev >>> >>> -- >>> Brian Stansberry >>> Manager, Senior Principal Software Engineer >>> JBoss by Red Hat >>> >>> >>> >> >> -- >> Brian Stansberry >> Manager, Senior Principal Software Engineer >> JBoss by Red Hat >> >> >> >> >> >> >> -- >> Michael Musgrove >> Transactions Team >> e: mmusgrov at redhat.com >> >> Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. >> >> JBoss, by Red Hat >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. >> Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) > > -- > Brian Stansberry > Manager, Senior Principal Software Engineer > JBoss by Red Hat > > > -- Brian Stansberry Manager, Senior Principal Software Engineer JBoss by Red Hat From mmusgrov at redhat.com Thu Jun 29 04:45:15 2017 From: mmusgrov at redhat.com (Michael Musgrove) Date: Thu, 29 Jun 2017 09:45:15 +0100 Subject: [wildfly-dev] Runtime only resources In-Reply-To: References: <841DF20B-AB8C-4588-B65D-5EDC0DEE12EE@redhat.com> <3A39AB80-14EB-4CA7-847F-1A902CDE6B72@redhat.com> Message-ID: Thanks Brian for the analysis and the fix. On Wed, Jun 28, 2017 at 10:14 PM, Brian Stansberry < brian.stansberry at redhat.com> wrote: > https://github.com/wildfly/wildfly/pull/10258 will result in the correct > failure message when ?delete? is invoked against a non-existing resource. > > > On Jun 28, 2017, at 12:36 PM, Brian Stansberry < > brian.stansberry at redhat.com> wrote: > > > > https://github.com/wildfly/wildfly/compare/master... > bstansberry:tx-runtime-only is the quick improvement I mentioned. > > > > https://ci.wildfly.org/viewLog.html?buildId=66224&tab=buildResultsDiv& > buildTypeId=WF_WildFlyCoreIntegrationExperiments is a custom CI job for > that branch. (I?ve done no testing locally other than checking the > transactions module compiles.) > > > > I don?t see how that op would get to ControllerLogger#modelUpdateNotAuthorized > though, unless the transactions=0\:ffff0afc4420\:3b2568af\:594b9528\: > resource doesn?t exist. If it doesn?t then the op would fail anyway, just > with a different message. > > > >> On Jun 28, 2017, at 12:19 PM, Michael Musgrove > wrote: > >> > >> Thanks for looking into this. The operation they are running is: > >> > >> [domain at jboss7.pro.intra.rs.gov.br:9990 /] /host=host-jbosshost7-1/ > server=GPD1/subsystem=transactions/log-store=log-store/transactions=0\: > ffff0afc4420\:3b2568af\:594b9528\::delete() > >> { > >> "outcome" => "failed", > >> "result" => undefined, > >> "failure-description" => "WFLYCTL0249: Opera??o 'delete' marcada no > recurso '[ > >> (\"subsystem\" => \"transactions\"), > >> (\"log-store\" => \"log-store\"), > >> (\"transactions\" => \"0:ffff0afc4420:3b2568af:594b9528:\") > >> ]' foi diretamente invocada pelo usu?rio. As opera??es do usu?rio n?o > s?o permitidas para atualizar diretamente a configura??o persistente de um > servidor no domain controller.", > >> "rolled-back" => true > >> } > >> > >> On Wed, Jun 28, 2017 at 6:17 PM, Brian Stansberry < > brian.stansberry at redhat.com> wrote: > >> What is the operation they are trying to invoke? > >> > >> LogStoreResource itself isn?t runtime-only but its children are. The > ?delete? operations on the ?transactions? and ?participants? children will > trigger a check that could lead to ControllerLogger#modelUpdateNotAuthorized, > but those resources are runtime-only. > >> > >> One possibibility is the child they are trying to delete is already > gone (these are dynamic) so perhaps since it?s non-existent the fact that > it?s runtime-only is not being detected. I?ll work up a quick improvement > that will help with that. > >> > >> > >>> On Jun 28, 2017, at 11:51 AM, Brian Stansberry < > brian.stansberry at redhat.com> wrote: > >>> > >>> I?ll have a look. > >>> > >>>> On Jun 28, 2017, at 8:27 AM, Michael Musgrove > wrote: > >>>> > >>>> The operation used to work and I suspect that the root cause is > WFCORE-2858 (Roll out READ_ONLY + RUNTIME_ONLY ops to the domain) and the > fix for the transaction subsystem is https://issues.jboss.org/ > browse/JBEAP-11651. It would be great if someone with more knowledge than > I of the domain model could verify my hypothesis. > >>>> > >>>> On Wed, Jun 28, 2017 at 12:31 PM, Michael Musgrove < > mmusgrov at redhat.com> wrote: > >>>> We have a transaction case where the customer is trying to delete a > (transaction log) model resource via the CLI and is seeing the error: > >>>> > >>>> "was directly invoked by the user. User operations are not permitted > to directly update the persistent configuration of a server in a managed > domain." > >>>> > >>>> This is coming from ControllerLogger#modelUpdateNotAuthorized (in > wildfly-core) because we define the resource as *not* being runtime only: > >>>> > >>>> public boolean isRuntime() {return false;} > >>>> > >>>> My question is should we be defining the resource as a runtime > resource or should we tell the customer not to delete the resouce from the > controller? > >>>> > >>>> Thanks, > >>>> Mike > >>>> > >>>> > >>>> -- > >>>> Michael Musgrove > >>>> Transactions Team > >>>> e: mmusgrov at redhat.com > >>>> > >>>> Our mission:To be the catalyst in communities of customers, > contributors, and partners creating better technology the open source way. > >>>> > >>>> JBoss, by Red Hat > >>>> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, > Kinsale Road, Co. Cork. > >>>> Registered in the Companies Registration Office, Parnell House, 14 > Parnell Square, Dublin 1, Ireland, No.304873 > >>>> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael > O'Neill, Keith Phelan, Matt Parson (USA) > >>>> > >>>> > >>>> > >>>> -- > >>>> Michael Musgrove > >>>> Transactions Team > >>>> e: mmusgrov at redhat.com > >>>> > >>>> Our mission:To be the catalyst in communities of customers, > contributors, and partners creating better technology the open source way. > >>>> > >>>> JBoss, by Red Hat > >>>> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, > Kinsale Road, Co. Cork. > >>>> Registered in the Companies Registration Office, Parnell House, 14 > Parnell Square, Dublin 1, Ireland, No.304873 > >>>> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael > O'Neill, Keith Phelan, Matt Parson (USA) > >>>> _______________________________________________ > >>>> wildfly-dev mailing list > >>>> wildfly-dev at lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev > >>> > >>> -- > >>> Brian Stansberry > >>> Manager, Senior Principal Software Engineer > >>> JBoss by Red Hat > >>> > >>> > >>> > >> > >> -- > >> Brian Stansberry > >> Manager, Senior Principal Software Engineer > >> JBoss by Red Hat > >> > >> > >> > >> > >> > >> > >> -- > >> Michael Musgrove > >> Transactions Team > >> e: mmusgrov at redhat.com > >> > >> Our mission:To be the catalyst in communities of customers, > contributors, and partners creating better technology the open source way. > >> > >> JBoss, by Red Hat > >> Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, > Kinsale Road, Co. Cork. > >> Registered in the Companies Registration Office, Parnell House, 14 > Parnell Square, Dublin 1, Ireland, No.304873 > >> Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael > O'Neill, Keith Phelan, Matt Parson (USA) > > > > -- > > Brian Stansberry > > Manager, Senior Principal Software Engineer > > JBoss by Red Hat > > > > > > > > -- > Brian Stansberry > Manager, Senior Principal Software Engineer > JBoss by Red Hat > > > > -- Michael Musgrove Transactions Team e: mmusgrov at redhat.com Our mission:To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. JBoss, by Red Hat Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork. Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873 Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170629/a35d81ab/attachment.html