Skip to content

Some calls to isSetting() don't specify the sessionID #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2018

Conversation

jasonps01
Copy link
Contributor

I discovered this bug while trying to set different JDBC tables for different sessions.

@chrjohn chrjohn added this to the QFJ 2.0.1 milestone Feb 19, 2018
@chrjohn
Copy link
Member

chrjohn commented Feb 19, 2018

Thanks for the PR. Good catch!

@chrjohn chrjohn changed the title Fix a bug where some calls to isSetting() don't specify the session ID. Some calls to isSetting() don't specify the sessionID Feb 19, 2018
@chrjohn chrjohn merged commit be3b5db into quickfix-j:master Feb 19, 2018
chrjohn pushed a commit that referenced this pull request Feb 19, 2018
…D. (#174)

Some calls to isSetting() don't specify the sessionID
(cherry picked from commit be3b5db)
@chrjohn chrjohn modified the milestones: QFJ 2.0.1, QFJ 2.1.0 Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants