Just cloned from https://github.com/kpavlov/fixio.git. Can't see class fixio.fixprotocol.FieldType in repository.

I'd love to migrate to java 8 but somebody may still use jdk 7 for production.

End of Java 7 Public Updates is April 2015

If somebody is using Java 7, please give rise a voice!

Hi!

I would like to ask you if it is possible with Fixio to send LOGON request along with user credentials. So far I use fixClient.connect() method which has no option like that.

Thanks a lot.

@kouyusanpi:
Request:
8=FIX.4.3|9=184|35=V|49=***|56=***|34=2|50=***|57=***|52=20180305-04:05:04.434|128=***|262=161f4559330|263=1|264=1|265=0|146=1|55=EUR/USD|460=4|167=FOR|267=1|269=0|10=249|

Response:
8=FIX.4.3|9=164|35=Y|34=2|49=***|50=***|52=20180305-04:05:04.570|56=***|57=***|58=RequestValidationError.IncorrectMDEntryType|262=161f4559330|281=3|10=038

See #40

@kouyusanpi:

I am programing FIX,The following question：
Market Data Request: Subscription
8=FIX.4.3|9=205|35=V|34=177|49=quote.TestOrg.TestUser.dev|50=TestOrg|52=201402 2617:03:32.405|56=client.fxgrid.integral.com|128=Broker13|262=3ee|263=1|264=1| 265=0|146=1|55=EUR/USD|460=4|167=FOR|267=2|269=0|269=1|10=059|
the Subscription message has two Tag:269, In the FIXIO that how can i do it. The FixMessageBuilder is Map type.

What happens when the connection is lost? Do I get an exception from FixApplicationAdapter in the following method?

    @Override
    public void exceptionCaught(ChannelHandlerContext ctx, Throwable cause) throws Exception {
        LOGGER.error("Uncaught application exception.", cause);
        ctx.close().sync();
    }

QuickFixJ has a retry mechanism when the connection is lost but I'm unsure there is one here, if there isn't I will probably retry myself with my own rate limiter.

Another question not related, will you give a name to the project with something more searchable? Maybe you can create a small user's list for questions @reactivefix or @netty-fix -suggestions-

As for Maven project maybe group ID something like io.fix

I am very much new to the Stock exchange market. I just started looking into QuickFix and when I am searching for that I found this project is very much useful for me. But I didn't found any API documentation. Can anyone provide me the documents, so that I can start as quick as possible. I will be very graceful if anyone can provide me some more examples than they are already in the project source library. I have already worked with the examples in the library and I can able to see that, only a session is being created.After that nothing is being happening. Can anyone help me how can I place some orders from the initiator to the acceptor and again receive the response back? Some more examples with added order placing will help me a lot. I am very much interested in this project. I am really fed up with QuickFix latency and this the only thing that can help me a lot.

I am also very much new to GitHub. And I am extremely sorry if this is the wrong place to ask such type of questions.

Based on pull request: #27

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency org.apache.maven.plugins:maven-shade-plugin to v3.5.3
• Update dependency org.apache.maven.plugins:maven-source-plugin to v3.3.1
• Update dependency org.apache.maven.plugins:maven-surefire-plugin to v2.22.2
• Update dependency org.assertj:assertj-core to v3.25.3
• Update dependency org.javassist:javassist to v3.30.2-GA
• Update dependency org.mockito:mockito-core to v2.28.2
• Update dependency pl.pragmatists:JUnitParams to v1.1.1
• Update jmh.version to v1.37 (org.openjdk.jmh:jmh-generator-annprocess, org.openjdk.jmh:jmh-core)
• Update dependency net.sf.saxon:Saxon-HE to v12
• Update dependency org.apache.maven.plugins:maven-deploy-plugin to v3
• Update dependency org.apache.maven.plugins:maven-failsafe-plugin to v3
• Update dependency org.apache.maven.plugins:maven-gpg-plugin to v3
• Update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3
• Update dependency org.apache.maven.plugins:maven-release-plugin to v3
• Update dependency org.apache.maven.plugins:maven-surefire-plugin to v3
• Update dependency org.mockito:mockito-core to v5
• Update slf4j monorepo to v2 (major) (org.slf4j:slf4j-simple, org.slf4j:slf4j-api)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency io.netty:netty-all to v4.1.109.Final
• Update dependency junit:junit to v4.13.2
• Update dependency org.sonatype.plugins:nexus-staging-maven-plugin to v1.6.13
• Update slf4j monorepo to v1.7.36 (org.slf4j:slf4j-simple, org.slf4j:slf4j-api)
• Update dependency it.unimi.dsi:fastutil to v8.5.13
• Update dependency net.sf.saxon:Saxon-HE to v9.9.1-8
• Update dependency org.apache.commons:commons-lang3 to v3.14.0
• Update dependency org.apache.maven.plugins:maven-failsafe-plugin to v2.22.2
• Update dependency org.apache.maven.plugins:maven-jar-plugin to v3.4.1
• Update dependency org.apache.maven.plugins:maven-resources-plugin to v3.3.1
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

the source code can not find FieldType class.

Are there any plans to get this project on maven central? It would help give it exposure and make it easier to get started.

https://maven.apache.org/guides/mini/guide-central-repository-upload.html

Hi!

I noticed during my testing that in message header there was no BodyLength tag which is required by the FIX Protocol specification (and I suspect this issue as a reason why I was being constantly disconnected from server).
Also Checksum tag in trailer is always set to 0, don't know if I have to set it somehow or it is a default value.

Thanks in advance for you help.

Also the name fixio? If you do a google search, you get lots of hits, something more unique would be preferred. maybe FIXMsgAPI

comment by Robert J Wolf.

When my MsgSeqNum is 1, I want add it to FixMessageImpl, so I invoke message.add(int tagNum, byte[] value). First I turn MsgSeqNum from int to byte[], The byte array i get is [0, 0, 0, 1], it will go to IntField. In this function, It find if (digit > 9 || digit < 0) It will throw a expetion, but [0, 0, 0, 1] to int.The result is 1, but by the function it throw a exception so I think it will be a bug.

private static void writeField(int fieldNum, String stringValue, ByteBuf out) {
out.writeBytes(Integer.toString(fieldNum).getBytes(CHARSET));
out.writeByte('=');
out.writeBytes(stringValue.getBytes(CHARSET));
out.writeByte(1);
}

i thought the last line should be out.writeByte(';') ?

Hi!

I would like to ask if there is a possiblity in fixio to replace loading of static .properties file for runtime object with set properties, for example Java built-in Properties class?

Hi, can you please also compare fix8 in your wiki page on benchmarking/performance?
Thanks

It should be possible to persist inbound and outbound message sequence numbers for restoring session after disconnect. Add settings similar to QuickFix ResetOnLogon, ResetOnLogout, ResetOnDisconnect, RefreshOnLogon (see http://www.quickfixengine.org/quickfix/doc/html/configuration.html#Session).
Use persisted settings if FixSessionSettingsProvider.resetMsgSeqNum() == false.

use the fix tag number instead of a tag name, it becomes very confusing switching back and forth. This object oriented idea of taking a fix tag number, change it to a name, then use the name everywhere, then finally output a fix tag number again, sounds good in OO theory but is a pain. It would be simpler have the api only based on fix tag numbers.

comment by Robert J Wolf.

API does not actually use tag names (strings).
It uses tag numbers (int) and enums (fixio.fixprotocol.FieldType), generated from FIX 5.0 SP2 specification.
It is possible to use either int or enum in methods like "message.add(tag, value)". Use numbers for non-standard (custom) tags.

It should be possible to add new field to FixMessageBuilder by specifying dataType, tagNum and value, without lookup a FieldType by tagNum.

I have no idea how to get rid of this lookup when parsing message from stream, because there is no information what kind of field should be added to FixMessage.

let the program know the exact order of the individual tags on incoming messages and to control the exact order of the individual tags on outgoing messages. some FIX gateways I have seen mandate an exact order of the individual fix tags and will reject messages. We all know the FIX protocol allows tags in any order but numerous systems cannot handle tags not the desired order

comment by Robert J Wolf.

Field order is defined by their insertion order in FixMessageBuilder, and by order of appearance in the stream for FixMessage due to Fields are stored in ArrayList internally.
To ensure field order in outgoing message, please add them to FixMessageBuilder in that order.

Add a method to fetch a field by index, something like:
FixMessageFragment FixMessage.getByIndex(int index)

Index should be absolute (not relative to message body).