[jira] [Commented] (OFBIZ-12550) Manufacturing Jobshop find screen by default does not show all production runs
[ https://issues.apache.org/jira/browse/OFBIZ-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485029#comment-17485029 ] Hans Bakker commented on OFBIZ-12550: - the same problem exists on the MRP log find where the date is filled by default, also for this a patch attached. > Manufacturing Jobshop find screen by default does not show all production runs > -- > > Key: OFBIZ-12550 > URL: https://issues.apache.org/jira/browse/OFBIZ-12550 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 18.12.05 >Reporter: Hans Bakker >Priority: Critical > Attachments: manufacturingFind.patch, mrpLogFind.patch > > > The manufacturing jobshop find screen has the seach date initialized to > nowdate. > if one wants to see all production runs, one has to clear the date which > should be empty initially -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12550) Manufacturing Jobshop find screen by default does not show all production runs
[ https://issues.apache.org/jira/browse/OFBIZ-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-12550: Attachment: mrpLogFind.patch > Manufacturing Jobshop find screen by default does not show all production runs > -- > > Key: OFBIZ-12550 > URL: https://issues.apache.org/jira/browse/OFBIZ-12550 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 18.12.05 >Reporter: Hans Bakker >Priority: Critical > Attachments: manufacturingFind.patch, mrpLogFind.patch > > > The manufacturing jobshop find screen has the seach date initialized to > nowdate. > if one wants to see all production runs, one has to clear the date which > should be empty initially -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12550) Manufacturing Jobshop find screen by default does not show all production runs
[ https://issues.apache.org/jira/browse/OFBIZ-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-12550: Priority: Critical (was: Major) > Manufacturing Jobshop find screen by default does not show all production runs > -- > > Key: OFBIZ-12550 > URL: https://issues.apache.org/jira/browse/OFBIZ-12550 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 18.12.05 >Reporter: Hans Bakker >Priority: Critical > Attachments: manufacturingFind.patch > > > The manufacturing jobshop find screen has the seach date initialized to > nowdate. > if one wants to see all production runs, one has to clear the date which > should be empty initially -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-12550) Manufacturing Jobshop find screen by default does not show all production runs
[ https://issues.apache.org/jira/browse/OFBIZ-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-12550: Attachment: manufacturingFind.patch > Manufacturing Jobshop find screen by default does not show all production runs > -- > > Key: OFBIZ-12550 > URL: https://issues.apache.org/jira/browse/OFBIZ-12550 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: 18.12.05 >Reporter: Hans Bakker >Priority: Major > Attachments: manufacturingFind.patch > > > The manufacturing jobshop find screen has the seach date initialized to > nowdate. > if one wants to see all production runs, one has to clear the date which > should be empty initially -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-1525) Issue to group security concerns
[ https://issues.apache.org/jira/browse/OFBIZ-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-1525: --- Attachment: (was: manufacturingFind.patch) > Issue to group security concerns > > > Key: OFBIZ-1525 > URL: https://issues.apache.org/jira/browse/OFBIZ-1525 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk, Upcoming Branch >Reporter: Jacques Le Roux >Priority: Critical > > The goal of this virtual issue is only to group together all OFBiz security > issues (pending or closed). > This issue should never be closed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (OFBIZ-1525) Issue to group security concerns
[ https://issues.apache.org/jira/browse/OFBIZ-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-1525: --- Attachment: manufacturingFind.patch > Issue to group security concerns > > > Key: OFBIZ-1525 > URL: https://issues.apache.org/jira/browse/OFBIZ-1525 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk, Upcoming Branch >Reporter: Jacques Le Roux >Priority: Critical > > The goal of this virtual issue is only to group together all OFBiz security > issues (pending or closed). > This issue should never be closed -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (OFBIZ-12550) Manufacturing Jobshop find screen by default does not show all production runs
Hans Bakker created OFBIZ-12550: --- Summary: Manufacturing Jobshop find screen by default does not show all production runs Key: OFBIZ-12550 URL: https://issues.apache.org/jira/browse/OFBIZ-12550 Project: OFBiz Issue Type: Bug Components: manufacturing Affects Versions: 18.12.05 Reporter: Hans Bakker The manufacturing jobshop find screen has the seach date initialized to nowdate. if one wants to see all production runs, one has to clear the date which should be empty initially -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (OFBIZ-11534) Error in uploading large files
[ https://issues.apache.org/jira/browse/OFBIZ-11534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073726#comment-17073726 ] Hans Bakker commented on OFBIZ-11534: - if i remember well, it keeps the whole file in memory? > Error in uploading large files > --- > > Key: OFBIZ-11534 > URL: https://issues.apache.org/jira/browse/OFBIZ-11534 > Project: OFBiz > Issue Type: Bug > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Chandan Khandelwal >Assignee: Jacques Le Roux >Priority: Major > Attachments: OFBIZ-11534.patch > > > There is an issue in uploading large files, I am able to upload files up to 2 > GB successfully but getting an error when trying to upload a file larger than > 2GB. > Example - > 1. Go to party profile - > [https://demo-trunk.ofbiz.apache.org/partymgr/control/viewprofile?partyId=admin] > 2. Try to create a party content with a file larger than 2 GB > 3. Error on console > > java.lang.NegativeArraySizeException: > nulljava.lang.NegativeArraySizeException: null at > org.apache.commons.fileupload.disk.DiskFileItem.get(DiskFileItem.java:308) > ~[commons-fileupload-1.4.jar:1.4] at > org.apache.ofbiz.base.util.UtilHttp.getMultiPartParameterMap(UtilHttp.java:275) > ~[main/:?] at > = > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-10407: Description: Attached an initial docker version from OFBiz copied from our GrowERP production system translated to svn repositories. I propose to create a docker directory in the ofbiz framework root of which a patch is attached. The image result is stored in hub.docker.com under the name ofbiz/full-trunk. It can be started in a docker environment with the following command: docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk and after about 30 seconds it can be show in the browser under: [https://0.0.0.0/catalog/control/main] the image can be created by executing this command in the ofbiz root when the patch is applied: docker build -t ofbiz/full-trunk docker the password to the ofbiz account at hub.docker.com will be supplied upon request. see the discussion in the mailinglist at https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz was: Attached an initial docker version from OFBiz copied from our GrowERP production system translated to svn repositories. I propose to create a docker directory in the ofbiz framework root of which a patch is attached. The image result is stored in hub.docker.com under the name ofbiz/full-trunk. It can be started in a docker environment with the following command: docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk and after about 30 seconds it can be show in the browser under: [https://0.0.0.0/catalog/control/main] the image can be created by executing this command in the ofbiz root when the patch is applied: docker build -t ofbiz/full-trunk docker the password to the ofbiz account at hub.docker.com will be supplied upon request. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > the image can be created by executing this command in the ofbiz root when > the patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > > see the discussion in the mailinglist at > https://markmail.org/message/n7wcgroslj7v3gfe?q=docker+ofbiz > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478547#comment-16478547 ] Hans Bakker commented on OFBIZ-10407: - Yes we need newer copies of these filesor add a script to modify them as was done with entityrngine.properties.further the changeurl.sh was copied by accident and it is questionable if the change url part of initStart is required let first let the community decide if this is acceptable before we put more work in this,. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478370#comment-16478370 ] Hans Bakker commented on OFBIZ-10407: - I changed the priority to major, because installing demo systems (yes even the ofbiz dmo version) should be done with docker to follow these important software developments. Ofbiz also should , as all major open source systems do, provide an official docker image with every release. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-10407: Priority: Major (was: Minor) > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478359#comment-16478359 ] Hans Bakker commented on OFBIZ-10407: - Thanks Deepak for your comments. Yes in GrowERP we are using OFBiz-16 and these files are enabling cache within ofbiz. It will copy these files into the ofbiz system when the dockerimage is starting up. This initial patch for ofbiz is welcoming comments as much as possible because docker not only is the choice for running a system in production but also to do OS independent software development. For your information we are using the docker-machine command to automatically install a docker environment on AWS on a 4 processor 16Gb instance en running 9 small ofbiz/growerp instances on it with excellent performance. examples: antwebsystems.com, productfromthailand,com growerp.com growerpdemo.com I think that the docker production environment is much better than the tenant function in OFBiz and that the tenant function should be removed. Regards, Hans > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Minor > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10407) create a docker image from the ofbiz system
Hans Bakker created OFBIZ-10407: --- Summary: create a docker image from the ofbiz system Key: OFBIZ-10407 URL: https://issues.apache.org/jira/browse/OFBIZ-10407 Project: OFBiz Issue Type: Improvement Reporter: Hans Bakker Attachments: docker.patch Attached an initial docker version from OFBiz copied from our GrowERP production system translated to svn repositories. I propose to create a docker directory in the ofbiz framework root of which a patch is attached. The image result is stored in hub.docker.com under the name ofbiz/full-trunk. It can be started in a docker environment with the following command: docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk and after about 30 seconds it can be show in the browser under: [https://0.0.0.0/catalog/control/main] the image can be created by executing this command in the ofbiz root when the patch is applied: docker build -t ofbiz/full-trunk docker the password to the ofbiz account at hub.docker.com will be supplied upon request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-9831) Use Vaadin as alternative for screens/forms
[ https://issues.apache.org/jira/browse/OFBIZ-9831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-9831: --- Summary: Use Vaadin as alternative for screens/forms (was: Us Vaadin as alternative for screens/forms) > Use Vaadin as alternative for screens/forms > --- > > Key: OFBIZ-9831 > URL: https://issues.apache.org/jira/browse/OFBIZ-9831 > Project: OFBiz > Issue Type: New Feature > Components: ALL APPLICATIONS >Affects Versions: Trunk > Environment: any >Reporter: Hans Bakker >Priority: Minor > Labels: ui, vaadin > Fix For: Trunk > > Attachments: vaadin-test.zip > > > Please find attached the latest version (9 oct 2017) of our vaadin proof on > concept. > put this zip and extract in the plugins directory and read the Readme.txt > file for installation instructions > This is still a work in progress, the latest version can be downloaded with > your preferred GIT client at: git clone > https://gerrit.antwebsystems.com/vaadin-test -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9831) Us Vaadin as alternative for screens/forms
[ https://issues.apache.org/jira/browse/OFBIZ-9831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-9831: --- Attachment: vaadin-test.zip the vaadin-test component > Us Vaadin as alternative for screens/forms > -- > > Key: OFBIZ-9831 > URL: https://issues.apache.org/jira/browse/OFBIZ-9831 > Project: OFBiz > Issue Type: New Feature > Components: ALL APPLICATIONS >Affects Versions: Trunk > Environment: any >Reporter: Hans Bakker >Priority: Minor > Labels: ui, vaadin > Fix For: Trunk > > Attachments: vaadin-test.zip > > > Please find attached the latest version (9 oct 2017) of our vaadin proof on > concept. > put this zip and extract in the plugins directory and read the Readme.txt > file for installation instructions > This is still a work in progress, the latest version can be downloaded with > your preferred GIT client at: git clone > https://gerrit.antwebsystems.com/vaadin-test -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9831) Us Vaadin as alternative for screens/forms
Hans Bakker created OFBIZ-9831: -- Summary: Us Vaadin as alternative for screens/forms Key: OFBIZ-9831 URL: https://issues.apache.org/jira/browse/OFBIZ-9831 Project: OFBiz Issue Type: New Feature Components: ALL APPLICATIONS Affects Versions: Trunk Environment: any Reporter: Hans Bakker Priority: Minor Fix For: Trunk Please find attached the latest version (9 oct 2017) of our vaadin proof on concept. put this zip and extract in the plugins directory and read the Readme.txt file for installation instructions This is still a work in progress, the latest version can be downloaded with your preferred GIT client at: git clone https://gerrit.antwebsystems.com/vaadin-test -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051469#comment-16051469 ] Hans Bakker commented on OFBIZ-9410: Thank you Scott, we always welcome new people to improve our product. > 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 > > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051446#comment-16051446 ] Hans Bakker commented on OFBIZ-9410: As I said, sure this problem needs to be solved, it looks like there is an error in the automatic extension of order subscriptions. However you can use the system even after three errors. Thank you for reporting! Regards, Hans > 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 > > 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)
[jira] [Comment Edited] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051422#comment-16051422 ] Hans Bakker edited comment on OFBIZ-9410 at 6/16/17 5:57 AM: - Ok, i tried it, and i have the same error on screen which should sure be solved. HOWEVER the system is fully functional, so please open your browser and enter: https://localhost:8443/ordermgr Regards, Hans was (Author: hansbak): Ok, i tried it, and i have the same error on screen which should sure be solved. HOWEVER the system is fully functional, so please oprn your brower and enter: https://localhost:8443/ordermgr Regards, Hans > 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 > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051422#comment-16051422 ] Hans Bakker commented on OFBIZ-9410: Ok, i tried it, and i have the same error on screen which should sure be solved. HOWEVER the system is fully functional, so please oprn your brower and enter: https://localhost:8443/ordermgr Regards, Hans > 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 > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051417#comment-16051417 ] Hans Bakker commented on OFBIZ-9410: Ok is see, i was trying the trunk version which works fine, you have used the 16.11.02 version, let me try that. > 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 > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051395#comment-16051395 ] Hans Bakker commented on OFBIZ-9410: The problem is that i cannot reproduce the problem you have. Since it could be related to the performFind service with the iterator not closed, Jacques did some changes there.so i leave it to up to him to shine some light on this > 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 > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051382#comment-16051382 ] Hans Bakker commented on OFBIZ-9410: Ok Scott, more basic, you started the system on linux with: ./gradlew cleanAll loadAll` ./gradlew ofbiz` and waited until the system had started up: command line stops scrolling did you then opened the browser and inserted: https://localhost:8443/ordermgr as url? what kind of response you then got? > 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 > > 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)
[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed
[ https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051373#comment-16051373 ] Hans Bakker commented on OFBIZ-9410: just a question, did you start the browser with the url: https://localhost:8443/ordermgr and not: https://localhost:8080/ordermgr this could give you the header error Regards, Hans Bakker CEO antwebsystems.com > 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 > > 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)
[jira] [Created] (OFBIZ-9257) various problems in SFA
Hans Bakker created OFBIZ-9257: -- Summary: various problems in SFA Key: OFBIZ-9257 URL: https://issues.apache.org/jira/browse/OFBIZ-9257 Project: OFBiz Issue Type: Bug Components: marketing Affects Versions: Trunk Reporter: Hans Bakker Priority: Critical several problems in SFA fixed: 1. leads without contactmech not show in my leads 2. converted leads not show in contacts 3. expired leads and contacts still show 4. various other problems -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OFBIZ-9116) minilanguage error handling problems
[ https://issues.apache.org/jira/browse/OFBIZ-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15662404#comment-15662404 ] Hans Bakker commented on OFBIZ-9116: we use this version 1748628 pretty long now because of the gradle changes. No idea when this worked before it is pretty annoying though! > minilanguage error handling problems > > > Key: OFBIZ-9116 > URL: https://issues.apache.org/jira/browse/OFBIZ-9116 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Trunk >Reporter: Hans Bakker > Fix For: Trunk > > > some errors in mini language code causes the script to stop executing without > giving errors: > 1. 2: entity-one whith not existing fieldmap name: > > from-field="parameters.personPartyId"/> > from-field="skillTypeId"/> > > (partyid should be partyId > we currently use rev 1748628 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
