|
Attention! Read the forum rules carefully before posting a topic.
Try to find an answer in Wiki before asking a question.
Submit programming questions in this forum only.
Off topics are strictly forbidden.
Any topics which do not satisfy these rules will be deleted.
| Upgrading 2.4.1 to 2.4.3 causes problem |
|
[MosheElisha]
|
| Post subject: Upgrading 2.4.1 to 2.4.3 causes problem |
Post rating: 0
|
Posted: Mon 14 Dec, 2009, 21:19
|
|
User rating: 0
Joined: Wed 28 Oct, 2009, 10:25
Posts: 13
|
|
Hey,
I've tried upgrading my version by updating the jars:
JForex-API-2.4.1.jar - > JForex-API-2.4.3.jar
jForex-1.8.2.8.jar -> jForex-2.0.5.jar
and added nlink-1.jar
Since I did I am having a lot of problems connecting to the API.
Some connections immediately disconnect, some gets stuck, some are throwing handshake close, etc.
Please instruct me so I could provide you with helpful logging and information.
Thanks
|
|
|
|
|
 |
|
API Support
|
| Post subject: Re: Upgrading from 2.4.1 to 2.4.3 causes connection diffuculties |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 10:16
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
|
Hi,
to get log information start a Java Control Panel. Choose an Advanced tab. From a tree choose Java console and expand it. Click on a radio button Show console (see controlPanel.png). Press Ok.
Every time, when you start JForex, the console window is shown up (see console.png). It is possible to see any exception in this window
| Attachments: |
controlPanel.png [19.72 KiB]
Downloaded 693 times
|
console.png [34.31 KiB]
Downloaded 678 times
|
|
DISCLAIMER: Dukascopy Bank SA's waiver of responsability - Documents, data or information available on
this webpage may be posted by third parties without Dukascopy Bank SA being obliged to make any control
on their content. Anyone accessing this webpage and downloading or otherwise making use of any document,
data or information found on this webpage shall do it on his/her own risks without any recourse against
Dukascopy Bank SA in relation thereto or for any consequences arising to him/her or any third party from
the use and/or reliance on any document, data or information found on this webpage.
|
|
|
|
|
|
|
|
[MosheElisha]
|
| Post subject: Re: Upgrading from 2.4.1 to 2.4.3 causes connection diffuculties |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 10:19
|
|
User rating: 0
Joined: Wed 28 Oct, 2009, 10:25
Posts: 13
|
|
Hey,
I am using the JForex API jars with a Java swing application I wrote. I am not running it as an applet.
|
|
|
|
|
|
|
API Support
|
| Post subject: Re: Upgrading from 2.4.1 to 2.4.3 causes connection diffuculties |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 10:34
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
|
|
|
|
|
|
[MosheElisha]
|
| Post subject: Re: Upgrading from 2.4.1 to 2.4.3 causes connection diffuculties |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 11:28
|
|
User rating: 0
Joined: Wed 28 Oct, 2009, 10:25
Posts: 13
|
|
The scenario is connecting, onConnect start strategy and set instruments.
Attached are the logs at DEBUG level.
| Attachments: |
logs.zip [36.41 KiB]
Downloaded 506 times
|
|
DISCLAIMER: Dukascopy Bank SA's waiver of responsability - Documents, data or information available on
this webpage may be posted by third parties without Dukascopy Bank SA being obliged to make any control
on their content. Anyone accessing this webpage and downloading or otherwise making use of any document,
data or information found on this webpage shall do it on his/her own risks without any recourse against
Dukascopy Bank SA in relation thereto or for any consequences arising to him/her or any third party from
the use and/or reliance on any document, data or information found on this webpage.
|
|
|
|
|
|
|
|
API Support
|
| Post subject: Re: JFOREX-1388: Upgrading 2.4.1 to 2.4.3 causes problem |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 15:17
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
Unfortunately there is no information about disconnects. Could you please wait until you get disconnects or other problems that you have. Also please add the following lines to your log4j.properties file: log4j.category.com.dukascopy=DEBUG
#Filter for dukascopy transport logs
log4j.category.com.dukascopy.transport.client=INFO
|
|
|
|
|
|
|
[MosheElisha]
|
| Post subject: Re: JFOREX-1388: Upgrading 2.4.1 to 2.4.3 causes problem |
Post rating: 0
|
Posted: Tue 15 Dec, 2009, 15:39
|
|
User rating: 0
Joined: Wed 28 Oct, 2009, 10:25
Posts: 13
|
|
Although there is no disconnect the program did not work as expected. For example, the method onAccount was not invoked at any point and the log is filled with "WARN com.dukascopy.transport.client.m - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME".
The log4j.properties that was used was already with the following lines:
log4j.category.com.dukascopy=DEBUG
log4j.category.com.dukascopy.transport.client=DEBUG
|
|
|
|
|
|
|
[MosheElisha]
|
| Post subject: Re: JFOREX-1388: Upgrading 2.4.1 to 2.4.3 causes problem |
Post rating: 0
|
Posted: Wed 16 Dec, 2009, 06:43
|
|
User rating: 0
Joined: Wed 28 Oct, 2009, 10:25
Posts: 13
|
|
Hey,
I think my connecting problem were caused because I invoked Client.setSubscribedInstruments in the first onAccount invocation instead of in the ISystemListener.onConnect before Client.startStrategy.
I will send logs of disconnections if they occur.
Thanks.
|
|
|
|
|
|
 
|
Pages: [
1
]
|
|
|
|
|
