<div dir="ltr"><div><div>One of complains we got is about undertow & web subsystem sharing good amount of message ids and messages in general.<br></div>Given that web subsystem will be removed soonish, does it make sense to change ids for undertow or just keep the old ones (given that they have not changed at all)<br>
<br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 3, 2013 at 4:42 PM, Kabir Khan <span dir="ltr"><<a href="mailto:kabir.khan@jboss.com" target="_blank">kabir.khan@jboss.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I also had a vague thought about this. Perhaps the logging annotation processor could be changed to dump a target/logging-ids.txt file for each subsystem, which we could then use to do a check at the end of the build.<br>
<div><div class="h5">On 3 Jul 2013, at 15:19, Jaikiran Pai wrote:<br>
<br>
> I wonder, if we could somehow integrate these checks and maintaining of<br>
> the range, within the build. I _think_ it should be possible to do it,<br>
> but I haven't thought much about it yet.<br>
><br>
> -Jaikiran<br>
> On Wednesday 03 July 2013 07:47 PM, Brian Stansberry wrote:<br>
>> On 7/3/13 4:56 AM, Darran Lofthouse wrote:<br>
>>> Hi all,<br>
>>><br>
>>> Recently we have had some issues reported where logging IDs are<br>
>>> suspected to be duplicates.<br>
>>><br>
>>> Can I suggest that one thing we do need is to update the page tracking<br>
>>> the reserved ID's to make it easier to identify what block is available<br>
>>> next?<br>
>>><br>
>>> <a href="https://community.jboss.org/wiki/LoggingIds" target="_blank">https://community.jboss.org/wiki/LoggingIds</a><br>
>>><br>
>>> Would it would be easier if the ranges column was sequential, if a<br>
>>> subsystem takes multiple allocations then it should just appear in the<br>
>>> list more than once.<br>
>> If I understand what you're saying correctly, what you describe is the<br>
>> way it's meant to be. A quick scan shows it follows that pattern, except<br>
>> for CMP which didn't have multiple lines in the table. I fixed that. If<br>
>> there are others that don't follow the pattern they should be fixed.<br>
>><br>
>>> At the moment to find a free block you need to<br>
>>> scan up and down the page to check the subsequent allocations.<br>
>>><br>
>>> Regards,<br>
>>> Darran Lofthouse.<br>
>>> _______________________________________________<br>
>>> wildfly-dev mailing list<br>
>>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
>>><br>
>><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br>
</div></div>---------------------------------------<br>
Kabir Khan<br>
Prinicipal Software Engineer<br>
JBoss by Red Hat<br>
<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>