I am using Quickfixj 1.5.3 and receiving NewOrderSingle message. The message got rejected since some tags are missing but I don't want miss those messages.
My Initiator configured as
RejectInvalidMessage=N, ValidateFieldsHaveValues=N, UseDataDictionary=N.
How can I process those messages in quickfixj?
You need to configure your DataDictionary (xml file) to reflect all of the fields that your counterparty might put in there. Nearly all counterparties make modifications to the default FIX messages and fields, and you need to modify your DD so that the QF engine knows about those modifications.
Your counterparty should have a spec that tells you what messages and fields they use. Review that spec and make sure your DD matches.
Thanks for your reply. The mistake was mine, There was a jar conflict, mistakenly I kept quickfix 1.4.0 and 1.5.3 jars in my lib folder. Once I removed the 1.4.0 jar, its started behaving as expected. Applogise for my mistakes.
Related
I've a question about the upgrade of Kentico V11 --> V12.
After the correct migration, I got these errors messages (20 times).
When I'll check the website, all design are blank. I just have the menu link without design.
I already re-sign the macro.
I've check all version of CMS.*.dll --> V12.
Do you have any idea for this blocking issue ?
Kind regards !
The error message
did you resign all the macros after the upgrade?
Typically there are a few things which can cause this. First being the hash salt changed in the web.config. If this changed, you need to resign your macros. Even if your hash salt hasn't changed the easiest thing is to go to System > Macros and check both boxes and resign all the macros.
The second thing, highly unlikely, would be you need to clear your browsers cache. Sometimes JS errors arise from the upgrade and cause problems with the system not running code.
What is the entire error message? What is the source URL and where is the code which is throwing the error? Isn't it possible it is coming from some transformation? I am asking since there were some API changes and the GetFileUrlFromAlias method was removed. See the API changes. You may want to use the Code upgrade tool to detect such changes.
I just give you a feedback.
The problem seems to be during the migration...
Due to the VPN low speed, that possible there was some timeout for many steps. (mandatory because the COVID19 =( )
I just get the database on my local computer and redone the migration, and all seems to be good now.
Thank you for your help on this subject :)
Take care of you in this period !
I have 1000+ files marked for add that I would like to submit using perforce. During the submit everything seems to work fine but after an hour or so into the submit, using the p4v client, I get an error saying "unable to connect to server...as user... try reconnecting"
This seems to happen every time I the p4v client to submit. Also tried using the commandline and get this message after a while into the submit saying "ssl send failed", "cannot find file specified WSAECONNABORT"
I suspect it has to do with SSL: I am currently hosting my perforce server on assembla.com as they wont give me the option to disable SSL. Is this an SSL problem?
How can I go about solving this?
Pretty desperate and grateful for help.
I've tried the following to no avail:
uninstalling and reinstalling
downgrading p4v client versions,
x86 and x64 bit versions of the p4v client
Ethernet instead of WiFi
During the submit everything is fine:
After about an hour I get this error:
If I press the "close p4v" button, this pops up:
Since p4v is giving me all these errors, I try to submit vi
commandline but still get error about an hour into the submit saying:
SOLVED IT! instead of trying to submit all the files marked for adds in one big chunk, I submitting it in small portions at a time like 300 or so instead of submitting all 1000+ files at a time.
so to recap the solution to this problem is submit in small portions instead of submitting them all at once.
I hope this helps anybody!
Sounds like the Perforce server is running out of resources. In Perforce, submits are atomic; It either totally works or totally fails. With such a large submit, if the server ran out of memory, or temporary disk space or something, and choked, the submit would fail. As you found, submitting in more manageable chunks doesn't trigger it.
This godforsaken error in eclipse won't die. I've tried everything mentioned here and elsewhere to get rid of it, but it won't go away and now I can't use the web service utility in eclipse because it complains about this "problem", which apparently isn't really a problem, but it is with m2e, which for the most part is useful.
First off, the error message, if you can call it that, is not very helpful. Whichever component generates that, could you produce something more meaningful?
Anyway, I've tried deleting the problems in eclipse, but they only come back. I've re-worked poms and updated the versions of the maven-ear-plugin to 2.3.2, all to no avail (and seriously, wouldn't that just be trying to skirt the real issue?). I've tried creating and updating a lifecylcle-mapping-metadata.xml file to ignore the org.codehaus.plexus -> plexus-archiver -> manifest goal. Nothing works.
What exactly is causing this message and what is the RIGHT way to diagnose the underlying cause and then solve it? Any insight would be most greatly appreciated.
This is caused by m2eclipse-mavenarchiver invoking the mavenarchiver plugin merge method by reflection. The method was removed in mavenarchiver 2.4, breaking m2eclipse-mavenarchiver.
This issue was fixed in m2eclipse-mavenarchiver 0.17.0 you can install from https://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.17.0/N/LATEST/
(URL updated to HTTPS)
I've been trying to get the following Eclipselink samples to work, with less than 0% success:
A)
http://wiki.eclipse.org/EclipseLink/Examples/JPARS/Simple
B)
git://git.eclipse.org/gitroot/eclipselink/examples/mysports.git
Both samples are quite recent and should work "out of the box". My results:
A) starts and deploys on glassfish, but application is totally unresponsive
B) does not deploy, since glassfish does not find the data-source mentioned in the persistence xml's: java:global/mysports
For both I tried to get information on how they are supposed to work, but after two days of searching for documentation, I can safely state: there is literally NOTHING documented.
For A) I am totally clueless, there is nothing to configure for this sample, but the provided URLs for interacting with the REST service always return with 404 and no log or error message whatsoever.
For B) Beside the broken data source (I guess my fault), I tried setting default JDBC data-sources, to see if at least the REST service itself works: it looks dead, I get exceptions when opening the sample JSF pages (the reference variables inside the pages all resolve to NULL).
Anybody ever tried to actually run these samples? I am totally frustrated after many hours of being far away to anything testable...
Maybe some questions as a starting point:
- How does the JPA-RS get registered in the appserver? how do I tell if it was at all? And which URL it maps to?
- How does this magic "java:global/mysports" data source work?
- The maven configuration acts funny, I couldn't get any of the two samples to properly debug (no breakpoints were hit at any point in time). Any ideas?
If you are using Glassfish earlier than Glassfish 4.0 (http://dlc.sun.com.edgesuite.net/glassfish/4.0/promoted/) you will need to download newer version of EclipseLink 2.4.2 binaries from http://www.eclipse.org/eclipselink/downloads/nightly.php (2.4.2 Nightly Build Results) and replace following files under $GLASSFISH_HOME/glassfish/modules with corresponding jars you downloaded above:
org.eclipse.persistence.antlr.jar
org.eclipse.persistence.jpa.jar
org.eclipse.persistence.asm.jar
org.eclipse.persistence.jpa.modelgen.jar
org.eclipse.persistence.core.jar
org.eclipse.persistence.oracle.jar
javax.persistence.jar
org.eclipse.persistence.dbws.jar
org.eclipse.persistence.jpa.jpql.jar
Make sure you clear Glassfish osgi cache by removing the $GLASSFISH_HOME\glassfish\domains\your_domain\osgi-cache directory after you replaced the bundles listed above, and before you restart the Glassfish.
These are both advanced examples, unless you are looking for these specific features, I would recommend starting out with simpler examples.
There are many EclipseLink JPA examples documented here,
http://wiki.eclipse.org/EclipseLink/Examples
Most of the examples are still in SVN here,
http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/
For documentation on the JPA-RS examples see,
http://wiki.eclipse.org/EclipseLink/Examples/JPA#JPA-RS
Try adding question to the example's wiki discussion page if you are having specific problems.
The MySports example is very advanced. Unless you are looking for extendable entities and multi-tenancy, I would not recommend starting with this example.
To add to James' comments, if you are specifically interested in JPA-RS, perhaps these additional comments will help. I also recommend asking questions on the wiki discussion page.
JPA-RS gets registered in the appserver by the existence of the org.eclipse.persistence.jpars_[version].jar in the WEB-INF/lib directory. This jar contains the web-fragment.xml which is what defines the JPA-RS service. You will know if it was deployed if the following URL pattern returns persistence unit metadata:
http://<server>:<port>/<applicationName>/persistence
Some additional documentation for JPA-RS:
- http://www.eclipse.org/eclipselink/documentation/2.4/solutions/restful_jpa001.htm
- wiki.eclipse.org/EclipseLink/Development/2.4.0/JPA-RS/REST-API
One thing that will help you debug is to view the Glassfish server log. If you are running in Eclipse, right click on your Glassfish server in the Server view, go to Glassfish->View Log File, which will open the server log in your console view. This will show you what is happening with deployment, and will alert you to any errors. Also be sure to double check your URLs.
Ok, ladies. A friend of mine had the brilliant idea of forcing ALL logging on eclipselink-jpars library (by setting this value in every single file we could think of) and indeed we found an exception that is FOR NO GOOD REASON hidden in the lowest log level:
javax.xml.bind.PropertyException: name: eclipselink.json.include-root value: false
Whatever that means, but that again convinces me that I will not use this feature/lib for the time being. An exception should be visible on all log levels, especially if I go down to FINE (as stated in the samples!)! I almost lost three days just because of this.
When accessing IMAP mail (with nnimap) in GNUS, the Summary buffer often lists messages or that are actually no longer present in the group.
Selecting any of these messages/articles results in an 'Article canceled or expired' error message. Quiting and restarting gnus doesn't change this (or refreshing with C-u M-g).
I can remove these articles from the Summary list by quiting gnus, and removing the ~/News directory and .newsrc.eld file, and then restarting gnus.
Is there anyway of getting the same result without reverting to deleting the files and directories?
Disable the "agent" feature. This caches things and requires its own tweaking (I haven't done it personally).
Go to the server buffer (type "^" in the group buffer) go over your imap server line and type J r to remove the agent.
You could try upgrading your version of Gnus. I used to have this problem a lot (along with every other user, it seems) and Lars did a massive rewrite of the IMAP code sometime this spring which seems to have fixed the problem here.