Github user justinleet commented on the issue:
https://github.com/apache/incubator-metron/pull/332
The Taxii HttpClient closes connections in callTaxiiService as seen here:
https://github.com/TAXIIProject/java-taxii/blob/master/src/main/java/org/mitre/taxii/client/HttpClient.java#L335
Because TaxiiHandler attempted to reuse a closed connection, the error was
seen. The fix is just to ensure the connection is created fresh before each
call. Integration test is updated to just call the run() method twice without
caring about results to ensure that the connection doesn't explode.
In addition, this was tested in quick-dev using a slightly modified version
(to work with Vagrant) of
https://community.hortonworks.com/articles/59698/pushing-stixtaxii-feeds-from-opentaxii-server-into.html,
where the playbook was run with
`ansible-playbook
--private-key=./vagrant/quick-dev-platform/.vagrant/machines/node1/virtualbox/private_key
-i 192.168.66.121, playbooks/install-opentaxii.yml -e
ansible_python_interpreter=python -e ansible_user=vagrant -vvvv`
with the IP being quick-dev's IP and the install-opentaxii script modified
to reflect this.
After the change, polling continues until ended and hbase dumps grow as new
records are added.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
