New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Michael Brohl-3
Hi all,

I think we should do a 16.11.03 release with the bug fix, what do you think?

Regards,

Michael Brohl
ecomify GmbH
www.ecomify.de


Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):

>      [ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051531#comment-16051531 ]
>
> Jacques Le Roux commented on OFBIZ-9410:
> ----------------------------------------
>
> Hi Scott,
>
> I'm very sorry for this error in our 16.01.02 release, thank you for your report!
>
> This was in broken by OFBIZ-8202 with r1787949 and fixed in the same issue with r1798179, thank you Deepak!
>
> I think I missed to attach a patch for easier fix. I will do here and in OFBIZ-8202.
>
> Now I'm surprised that you encouter the same issue in R13.07. I guess it's another one, could you please check and report? Thanks!
>
>> Software not usable all standard installs failed
>> -------------------------------------------------
>>
>>                  Key: OFBIZ-9410
>>                  URL: https://issues.apache.org/jira/browse/OFBIZ-9410
>>              Project: OFBiz
>>           Issue Type: Bug
>>           Components: ALL COMPONENTS
>>     Affects Versions: Release Branch 13.07, 16.11.02
>>          Environment: Several Linux Versions all Java 1.8
>> 1.3 and 1.6 OFBiz
>>             Reporter: Scott Provost
>>              Fix For: Upcoming Release
>>
>>          Attachments: OFBIZ-9410.patch
>>
>>
>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor process
>> INFO: Error parsing HTTP request header
>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>> at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor process
>> INFO: Error parsing HTTP request header
>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>> at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor process
>> INFO: Error parsing HTTP request header
>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>> at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Jacques Le Roux
Administrator
Hi,

I totally agree, and as quickly as possible. Thanks to Daniel Coric, I was able to fix it in a reasonable time (facepalm, how did I miss to backport)

But letting our official last release with such a bug is really pulling down our work, as OFBIZ-9410 shows

Jacques


Le 16/06/2017 à 09:55, Michael Brohl a écrit :

> Hi all,
>
> I think we should do a 16.11.03 release with the bug fix, what do you think?
>
> Regards,
>
> Michael Brohl
> ecomify GmbH
> www.ecomify.de
>
>
> Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):
>>      [
>> https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051531#comment-16051531 
>> ]
>>
>> Jacques Le Roux commented on OFBIZ-9410:
>> ----------------------------------------
>>
>> Hi Scott,
>>
>> I'm very sorry for this error in our 16.01.02 release, thank you for your report!
>>
>> This was in broken by OFBIZ-8202 with r1787949 and fixed in the same issue with r1798179, thank you Deepak!
>>
>> I think I missed to attach a patch for easier fix. I will do here and in OFBIZ-8202.
>>
>> Now I'm surprised that you encouter the same issue in R13.07. I guess it's another one, could you please check and report? Thanks!
>>
>>> Software not usable all standard installs failed
>>> -------------------------------------------------
>>>
>>>                  Key: OFBIZ-9410
>>>                  URL: https://issues.apache.org/jira/browse/OFBIZ-9410
>>>              Project: OFBiz
>>>           Issue Type: Bug
>>>           Components: ALL COMPONENTS
>>>     Affects Versions: Release Branch 13.07, 16.11.02
>>>          Environment: Several Linux Versions all Java 1.8
>>> 1.3 and 1.6 OFBiz
>>>             Reporter: Scott Provost
>>>              Fix For: Upcoming Release
>>>
>>>          Attachments: OFBIZ-9410.patch
>>>
>>>
>>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor process
>>> INFO: Error parsing HTTP request header
>>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>>     at java.lang.Thread.run(Thread.java:748)
>>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor process
>>> INFO: Error parsing HTTP request header
>>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>>     at java.lang.Thread.run(Thread.java:748)
>>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor process
>>> INFO: Error parsing HTTP request header
>>>   Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
>>> java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>>     at java.lang.Thread.run(Thread.java:748)
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.4.14#64029)
>
>

Reply | Threaded
Open this post in threaded view
|

Re: New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Jacopo Cappellato-5
I am going to start the process to issue the new release today.

Jacopo

On Fri, Jun 16, 2017 at 10:31 AM, Jacques Le Roux <
[hidden email]> wrote:

> Hi,
>
> I totally agree, and as quickly as possible. Thanks to Daniel Coric, I was
> able to fix it in a reasonable time (facepalm, how did I miss to backport)
>
> But letting our official last release with such a bug is really pulling
> down our work, as OFBIZ-9410 shows
>
> Jacques
>
>
>
> Le 16/06/2017 à 09:55, Michael Brohl a écrit :
>
>> Hi all,
>>
>> I think we should do a 16.11.03 release with the bug fix, what do you
>> think?
>>
>> Regards,
>>
>> Michael Brohl
>> ecomify GmbH
>> www.ecomify.de
>>
>>
>> Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):
>>
>>>      [ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.
>>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
>>> l&focusedCommentId=16051531#comment-16051531 ]
>>>
>>> Jacques Le Roux commented on OFBIZ-9410:
>>> ----------------------------------------
>>>
>>> Hi Scott,
>>>
>>> I'm very sorry for this error in our 16.01.02 release, thank you for
>>> your report!
>>>
>>> This was in broken by OFBIZ-8202 with r1787949 and fixed in the same
>>> issue with r1798179, thank you Deepak!
>>>
>>> I think I missed to attach a patch for easier fix. I will do here and in
>>> OFBIZ-8202.
>>>
>>> Now I'm surprised that you encouter the same issue in R13.07. I guess
>>> it's another one, could you please check and report? Thanks!
>>>
>>> Software not usable all standard installs failed
>>>> -------------------------------------------------
>>>>
>>>>                  Key: OFBIZ-9410
>>>>                  URL: https://issues.apache.org/jira/browse/OFBIZ-9410
>>>>              Project: OFBiz
>>>>           Issue Type: Bug
>>>>           Components: ALL COMPONENTS
>>>>     Affects Versions: Release Branch 13.07, 16.11.02
>>>>          Environment: Several Linux Versions all Java 1.8
>>>> 1.3 and 1.6 OFBiz
>>>>             Reporter: Scott Provost
>>>>              Fix For: Upcoming Release
>>>>
>>>>          Attachments: OFBIZ-9410.patch
>>>>
>>>>
>>>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor
>>>> process
>>>> INFO: Error parsing HTTP request header
>>>>   Note: further occurrences of HTTP header parsing errors will be
>>>> logged at DEBUG level.
>>>> java.lang.IllegalArgumentException: Invalid character found in method
>>>> name. HTTP method names must be tokens
>>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
>>>> Line(AbstractNioInputBuffer.java:233)
>>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>>>> tractHttp11Processor.java:1017)
>>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>>>> .process(AbstractProtocol.java:684)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>>>> (NioEndpoint.java:1519)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
>>>> NioEndpoint.java:1475)
>>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>>> Executor.java:1142)
>>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>>> lExecutor.java:617)
>>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>>>> run(TaskThread.java:61)
>>>>     at java.lang.Thread.run(Thread.java:748)
>>>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor
>>>> process
>>>> INFO: Error parsing HTTP request header
>>>>   Note: further occurrences of HTTP header parsing errors will be
>>>> logged at DEBUG level.
>>>> java.lang.IllegalArgumentException: Invalid character found in method
>>>> name. HTTP method names must be tokens
>>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
>>>> Line(AbstractNioInputBuffer.java:233)
>>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>>>> tractHttp11Processor.java:1017)
>>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>>>> .process(AbstractProtocol.java:684)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>>>> (NioEndpoint.java:1519)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
>>>> NioEndpoint.java:1475)
>>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>>> Executor.java:1142)
>>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>>> lExecutor.java:617)
>>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>>>> run(TaskThread.java:61)
>>>>     at java.lang.Thread.run(Thread.java:748)
>>>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor
>>>> process
>>>> INFO: Error parsing HTTP request header
>>>>   Note: further occurrences of HTTP header parsing errors will be
>>>> logged at DEBUG level.
>>>> java.lang.IllegalArgumentException: Invalid character found in method
>>>> name. HTTP method names must be tokens
>>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
>>>> Line(AbstractNioInputBuffer.java:233)
>>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>>>> tractHttp11Processor.java:1017)
>>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
>>>> .process(AbstractProtocol.java:684)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
>>>> (NioEndpoint.java:1519)
>>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
>>>> NioEndpoint.java:1475)
>>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>>> Executor.java:1142)
>>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>>> lExecutor.java:617)
>>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
>>>> run(TaskThread.java:61)
>>>>     at java.lang.Thread.run(Thread.java:748)
>>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.4.14#64029)
>>>
>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Deepak Dixit-3
Hi Jacopo,

I am planning to commit OFBIZ-9413 (Update Currency Uom data ) in
release16.11 as well.
Could you please wait till EOD today.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Mon, Jun 19, 2017 at 10:42 AM, Jacopo Cappellato <
[hidden email]> wrote:

> I am going to start the process to issue the new release today.
>
> Jacopo
>
> On Fri, Jun 16, 2017 at 10:31 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
> > Hi,
> >
> > I totally agree, and as quickly as possible. Thanks to Daniel Coric, I
> was
> > able to fix it in a reasonable time (facepalm, how did I miss to
> backport)
> >
> > But letting our official last release with such a bug is really pulling
> > down our work, as OFBIZ-9410 shows
> >
> > Jacques
> >
> >
> >
> > Le 16/06/2017 à 09:55, Michael Brohl a écrit :
> >
> >> Hi all,
> >>
> >> I think we should do a 16.11.03 release with the bug fix, what do you
> >> think?
> >>
> >> Regards,
> >>
> >> Michael Brohl
> >> ecomify GmbH
> >> www.ecomify.de
> >>
> >>
> >> Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):
> >>
> >>>      [ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.
> >>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
> >>> l&focusedCommentId=16051531#comment-16051531 ]
> >>>
> >>> Jacques Le Roux commented on OFBIZ-9410:
> >>> ----------------------------------------
> >>>
> >>> Hi Scott,
> >>>
> >>> I'm very sorry for this error in our 16.01.02 release, thank you for
> >>> your report!
> >>>
> >>> This was in broken by OFBIZ-8202 with r1787949 and fixed in the same
> >>> issue with r1798179, thank you Deepak!
> >>>
> >>> I think I missed to attach a patch for easier fix. I will do here and
> in
> >>> OFBIZ-8202.
> >>>
> >>> Now I'm surprised that you encouter the same issue in R13.07. I guess
> >>> it's another one, could you please check and report? Thanks!
> >>>
> >>> Software not usable all standard installs failed
> >>>> -------------------------------------------------
> >>>>
> >>>>                  Key: OFBIZ-9410
> >>>>                  URL: https://issues.apache.org/
> jira/browse/OFBIZ-9410
> >>>>              Project: OFBiz
> >>>>           Issue Type: Bug
> >>>>           Components: ALL COMPONENTS
> >>>>     Affects Versions: Release Branch 13.07, 16.11.02
> >>>>          Environment: Several Linux Versions all Java 1.8
> >>>> 1.3 and 1.6 OFBiz
> >>>>             Reporter: Scott Provost
> >>>>              Fix For: Upcoming Release
> >>>>
> >>>>          Attachments: OFBIZ-9410.patch
> >>>>
> >>>>
> >>>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.
> AbstractHttp11Processor
> >>>> process
> >>>> INFO: Error parsing HTTP request header
> >>>>   Note: further occurrences of HTTP header parsing errors will be
> >>>> logged at DEBUG level.
> >>>> java.lang.IllegalArgumentException: Invalid character found in method
> >>>> name. HTTP method names must be tokens
> >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> >>>> Line(AbstractNioInputBuffer.java:233)
> >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> >>>> tractHttp11Processor.java:1017)
> >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> >>>> .process(AbstractProtocol.java:684)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> >>>> (NioEndpoint.java:1519)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> >>>> NioEndpoint.java:1475)
> >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> >>>> Executor.java:1142)
> >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> >>>> lExecutor.java:617)
> >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> >>>> run(TaskThread.java:61)
> >>>>     at java.lang.Thread.run(Thread.java:748)
> >>>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.
> AbstractHttp11Processor
> >>>> process
> >>>> INFO: Error parsing HTTP request header
> >>>>   Note: further occurrences of HTTP header parsing errors will be
> >>>> logged at DEBUG level.
> >>>> java.lang.IllegalArgumentException: Invalid character found in method
> >>>> name. HTTP method names must be tokens
> >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> >>>> Line(AbstractNioInputBuffer.java:233)
> >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> >>>> tractHttp11Processor.java:1017)
> >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> >>>> .process(AbstractProtocol.java:684)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> >>>> (NioEndpoint.java:1519)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> >>>> NioEndpoint.java:1475)
> >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> >>>> Executor.java:1142)
> >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> >>>> lExecutor.java:617)
> >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> >>>> run(TaskThread.java:61)
> >>>>     at java.lang.Thread.run(Thread.java:748)
> >>>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.
> AbstractHttp11Processor
> >>>> process
> >>>> INFO: Error parsing HTTP request header
> >>>>   Note: further occurrences of HTTP header parsing errors will be
> >>>> logged at DEBUG level.
> >>>> java.lang.IllegalArgumentException: Invalid character found in method
> >>>> name. HTTP method names must be tokens
> >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> >>>> Line(AbstractNioInputBuffer.java:233)
> >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> >>>> tractHttp11Processor.java:1017)
> >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> >>>> .process(AbstractProtocol.java:684)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> >>>> (NioEndpoint.java:1519)
> >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> >>>> NioEndpoint.java:1475)
> >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> >>>> Executor.java:1142)
> >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> >>>> lExecutor.java:617)
> >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> >>>> run(TaskThread.java:61)
> >>>>     at java.lang.Thread.run(Thread.java:748)
> >>>>
> >>>
> >>>
> >>> --
> >>> This message was sent by Atlassian JIRA
> >>> (v6.4.14#64029)
> >>>
> >>
> >>
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Jacopo Cappellato-5
yes, thank you.

Jacopo

On Mon, Jun 19, 2017 at 7:28 AM, Deepak Dixit <
[hidden email]> wrote:

> Hi Jacopo,
>
> I am planning to commit OFBIZ-9413 (Update Currency Uom data ) in
> release16.11 as well.
> Could you please wait till EOD today.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
> www.hotwax.co
>
> On Mon, Jun 19, 2017 at 10:42 AM, Jacopo Cappellato <
> [hidden email]> wrote:
>
> > I am going to start the process to issue the new release today.
> >
> > Jacopo
> >
> > On Fri, Jun 16, 2017 at 10:31 AM, Jacques Le Roux <
> > [hidden email]> wrote:
> >
> > > Hi,
> > >
> > > I totally agree, and as quickly as possible. Thanks to Daniel Coric, I
> > was
> > > able to fix it in a reasonable time (facepalm, how did I miss to
> > backport)
> > >
> > > But letting our official last release with such a bug is really pulling
> > > down our work, as OFBIZ-9410 shows
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 16/06/2017 à 09:55, Michael Brohl a écrit :
> > >
> > >> Hi all,
> > >>
> > >> I think we should do a 16.11.03 release with the bug fix, what do you
> > >> think?
> > >>
> > >> Regards,
> > >>
> > >> Michael Brohl
> > >> ecomify GmbH
> > >> www.ecomify.de
> > >>
> > >>
> > >> Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):
> > >>
> > >>>      [ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.
> > >>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
> > >>> l&focusedCommentId=16051531#comment-16051531 ]
> > >>>
> > >>> Jacques Le Roux commented on OFBIZ-9410:
> > >>> ----------------------------------------
> > >>>
> > >>> Hi Scott,
> > >>>
> > >>> I'm very sorry for this error in our 16.01.02 release, thank you for
> > >>> your report!
> > >>>
> > >>> This was in broken by OFBIZ-8202 with r1787949 and fixed in the same
> > >>> issue with r1798179, thank you Deepak!
> > >>>
> > >>> I think I missed to attach a patch for easier fix. I will do here and
> > in
> > >>> OFBIZ-8202.
> > >>>
> > >>> Now I'm surprised that you encouter the same issue in R13.07. I guess
> > >>> it's another one, could you please check and report? Thanks!
> > >>>
> > >>> Software not usable all standard installs failed
> > >>>> -------------------------------------------------
> > >>>>
> > >>>>                  Key: OFBIZ-9410
> > >>>>                  URL: https://issues.apache.org/
> > jira/browse/OFBIZ-9410
> > >>>>              Project: OFBiz
> > >>>>           Issue Type: Bug
> > >>>>           Components: ALL COMPONENTS
> > >>>>     Affects Versions: Release Branch 13.07, 16.11.02
> > >>>>          Environment: Several Linux Versions all Java 1.8
> > >>>> 1.3 and 1.6 OFBiz
> > >>>>             Reporter: Scott Provost
> > >>>>              Fix For: Upcoming Release
> > >>>>
> > >>>>          Attachments: OFBIZ-9410.patch
> > >>>>
> > >>>>
> > >>>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.
> > AbstractHttp11Processor
> > >>>> process
> > >>>> INFO: Error parsing HTTP request header
> > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > >>>> logged at DEBUG level.
> > >>>> java.lang.IllegalArgumentException: Invalid character found in
> method
> > >>>> name. HTTP method names must be tokens
> > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> > >>>> Line(AbstractNioInputBuffer.java:233)
> > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> > >>>> tractHttp11Processor.java:1017)
> > >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> > >>>> .process(AbstractProtocol.java:684)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> > >>>> (NioEndpoint.java:1519)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> > >>>> NioEndpoint.java:1475)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > >>>> Executor.java:1142)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > >>>> lExecutor.java:617)
> > >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> > >>>> run(TaskThread.java:61)
> > >>>>     at java.lang.Thread.run(Thread.java:748)
> > >>>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.
> > AbstractHttp11Processor
> > >>>> process
> > >>>> INFO: Error parsing HTTP request header
> > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > >>>> logged at DEBUG level.
> > >>>> java.lang.IllegalArgumentException: Invalid character found in
> method
> > >>>> name. HTTP method names must be tokens
> > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> > >>>> Line(AbstractNioInputBuffer.java:233)
> > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> > >>>> tractHttp11Processor.java:1017)
> > >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> > >>>> .process(AbstractProtocol.java:684)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> > >>>> (NioEndpoint.java:1519)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> > >>>> NioEndpoint.java:1475)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > >>>> Executor.java:1142)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > >>>> lExecutor.java:617)
> > >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> > >>>> run(TaskThread.java:61)
> > >>>>     at java.lang.Thread.run(Thread.java:748)
> > >>>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.
> > AbstractHttp11Processor
> > >>>> process
> > >>>> INFO: Error parsing HTTP request header
> > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > >>>> logged at DEBUG level.
> > >>>> java.lang.IllegalArgumentException: Invalid character found in
> method
> > >>>> name. HTTP method names must be tokens
> > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequest
> > >>>> Line(AbstractNioInputBuffer.java:233)
> > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
> > >>>> tractHttp11Processor.java:1017)
> > >>>>     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler
> > >>>> .process(AbstractProtocol.java:684)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> > >>>> (NioEndpoint.java:1519)
> > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(
> > >>>> NioEndpoint.java:1475)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > >>>> Executor.java:1142)
> > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > >>>> lExecutor.java:617)
> > >>>>     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.
> > >>>> run(TaskThread.java:61)
> > >>>>     at java.lang.Thread.run(Thread.java:748)
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> This message was sent by Atlassian JIRA
> > >>> (v6.4.14#64029)
> > >>>
> > >>
> > >>
> > >>
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: New release 16.11.03? was: Re: [jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

Deepak Dixit-3
Thanks Jacopo,

Currency UOM work has been committed at R16.11 at r#1799196,
Buildbot reported failure but its due to xmlrpc and soap test case.
So we are good to go.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Mon, Jun 19, 2017 at 11:40 AM, Jacopo Cappellato <
[hidden email]> wrote:

> yes, thank you.
>
> Jacopo
>
> On Mon, Jun 19, 2017 at 7:28 AM, Deepak Dixit <
> [hidden email]> wrote:
>
> > Hi Jacopo,
> >
> > I am planning to commit OFBIZ-9413 (Update Currency Uom data ) in
> > release16.11 as well.
> > Could you please wait till EOD today.
> >
> > Thanks & Regards
> > --
> > Deepak Dixit
> > www.hotwaxsystems.com
> > www.hotwax.co
> >
> > On Mon, Jun 19, 2017 at 10:42 AM, Jacopo Cappellato <
> > [hidden email]> wrote:
> >
> > > I am going to start the process to issue the new release today.
> > >
> > > Jacopo
> > >
> > > On Fri, Jun 16, 2017 at 10:31 AM, Jacques Le Roux <
> > > [hidden email]> wrote:
> > >
> > > > Hi,
> > > >
> > > > I totally agree, and as quickly as possible. Thanks to Daniel Coric,
> I
> > > was
> > > > able to fix it in a reasonable time (facepalm, how did I miss to
> > > backport)
> > > >
> > > > But letting our official last release with such a bug is really
> pulling
> > > > down our work, as OFBIZ-9410 shows
> > > >
> > > > Jacques
> > > >
> > > >
> > > >
> > > > Le 16/06/2017 à 09:55, Michael Brohl a écrit :
> > > >
> > > >> Hi all,
> > > >>
> > > >> I think we should do a 16.11.03 release with the bug fix, what do
> you
> > > >> think?
> > > >>
> > > >> Regards,
> > > >>
> > > >> Michael Brohl
> > > >> ecomify GmbH
> > > >> www.ecomify.de
> > > >>
> > > >>
> > > >> Am 16.06.17 um 09:45 schrieb Jacques Le Roux (JIRA):
> > > >>
> > > >>>      [ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.
> > > >>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
> > > >>> l&focusedCommentId=16051531#comment-16051531 ]
> > > >>>
> > > >>> Jacques Le Roux commented on OFBIZ-9410:
> > > >>> ----------------------------------------
> > > >>>
> > > >>> Hi Scott,
> > > >>>
> > > >>> I'm very sorry for this error in our 16.01.02 release, thank you
> for
> > > >>> your report!
> > > >>>
> > > >>> This was in broken by OFBIZ-8202 with r1787949 and fixed in the
> same
> > > >>> issue with r1798179, thank you Deepak!
> > > >>>
> > > >>> I think I missed to attach a patch for easier fix. I will do here
> and
> > > in
> > > >>> OFBIZ-8202.
> > > >>>
> > > >>> Now I'm surprised that you encouter the same issue in R13.07. I
> guess
> > > >>> it's another one, could you please check and report? Thanks!
> > > >>>
> > > >>> Software not usable all standard installs failed
> > > >>>> -------------------------------------------------
> > > >>>>
> > > >>>>                  Key: OFBIZ-9410
> > > >>>>                  URL: https://issues.apache.org/
> > > jira/browse/OFBIZ-9410
> > > >>>>              Project: OFBiz
> > > >>>>           Issue Type: Bug
> > > >>>>           Components: ALL COMPONENTS
> > > >>>>     Affects Versions: Release Branch 13.07, 16.11.02
> > > >>>>          Environment: Several Linux Versions all Java 1.8
> > > >>>> 1.3 and 1.6 OFBiz
> > > >>>>             Reporter: Scott Provost
> > > >>>>              Fix For: Upcoming Release
> > > >>>>
> > > >>>>          Attachments: OFBIZ-9410.patch
> > > >>>>
> > > >>>>
> > > >>>> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.
> > > AbstractHttp11Processor
> > > >>>> process
> > > >>>> INFO: Error parsing HTTP request header
> > > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > > >>>> logged at DEBUG level.
> > > >>>> java.lang.IllegalArgumentException: Invalid character found in
> > method
> > > >>>> name. HTTP method names must be tokens
> > > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.
> parseRequest
> > > >>>> Line(AbstractNioInputBuffer.java:233)
> > > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.
> process(Abs
> > > >>>> tractHttp11Processor.java:1017)
> > > >>>>     at org.apache.coyote.AbstractProtocol$
> AbstractConnectionHandler
> > > >>>> .process(AbstractProtocol.java:684)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> doRun
> > > >>>> (NioEndpoint.java:1519)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> run(
> > > >>>> NioEndpoint.java:1475)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPool
> > > >>>> Executor.java:1142)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoo
> > > >>>> lExecutor.java:617)
> > > >>>>     at org.apache.tomcat.util.threads.TaskThread$
> WrappingRunnable.
> > > >>>> run(TaskThread.java:61)
> > > >>>>     at java.lang.Thread.run(Thread.java:748)
> > > >>>> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.
> > > AbstractHttp11Processor
> > > >>>> process
> > > >>>> INFO: Error parsing HTTP request header
> > > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > > >>>> logged at DEBUG level.
> > > >>>> java.lang.IllegalArgumentException: Invalid character found in
> > method
> > > >>>> name. HTTP method names must be tokens
> > > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.
> parseRequest
> > > >>>> Line(AbstractNioInputBuffer.java:233)
> > > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.
> process(Abs
> > > >>>> tractHttp11Processor.java:1017)
> > > >>>>     at org.apache.coyote.AbstractProtocol$
> AbstractConnectionHandler
> > > >>>> .process(AbstractProtocol.java:684)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> doRun
> > > >>>> (NioEndpoint.java:1519)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> run(
> > > >>>> NioEndpoint.java:1475)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPool
> > > >>>> Executor.java:1142)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoo
> > > >>>> lExecutor.java:617)
> > > >>>>     at org.apache.tomcat.util.threads.TaskThread$
> WrappingRunnable.
> > > >>>> run(TaskThread.java:61)
> > > >>>>     at java.lang.Thread.run(Thread.java:748)
> > > >>>> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.
> > > AbstractHttp11Processor
> > > >>>> process
> > > >>>> INFO: Error parsing HTTP request header
> > > >>>>   Note: further occurrences of HTTP header parsing errors will be
> > > >>>> logged at DEBUG level.
> > > >>>> java.lang.IllegalArgumentException: Invalid character found in
> > method
> > > >>>> name. HTTP method names must be tokens
> > > >>>>     at org.apache.coyote.http11.AbstractNioInputBuffer.
> parseRequest
> > > >>>> Line(AbstractNioInputBuffer.java:233)
> > > >>>>     at org.apache.coyote.http11.AbstractHttp11Processor.
> process(Abs
> > > >>>> tractHttp11Processor.java:1017)
> > > >>>>     at org.apache.coyote.AbstractProtocol$
> AbstractConnectionHandler
> > > >>>> .process(AbstractProtocol.java:684)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> doRun
> > > >>>> (NioEndpoint.java:1519)
> > > >>>>     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.
> run(
> > > >>>> NioEndpoint.java:1475)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPool
> > > >>>> Executor.java:1142)
> > > >>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoo
> > > >>>> lExecutor.java:617)
> > > >>>>     at org.apache.tomcat.util.threads.TaskThread$
> WrappingRunnable.
> > > >>>> run(TaskThread.java:61)
> > > >>>>     at java.lang.Thread.run(Thread.java:748)
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> This message was sent by Atlassian JIRA
> > > >>> (v6.4.14#64029)
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> >
>