Commented by: Roman Rokytskyy (rrokytskyy)

How do you tested it? Is it some Java code? Or is it an application? How can I reproduce the issue?

Commented by: Christoph Theuring (ctheuring)

hello Roman,

sorry for *very* late responce to your question ... I'm in the last days of my large project ...
To your question:
Its a Java application called Adito online -> http://www.adito.de.
TextBLOBs with UTF8 showed in the client windows with charset ISO.
Now we have a bugfixing (or workaround?) to this. The software developer Adito changed their code ... but I didn't know what they changed ...
For me the difference is, that we now start the application-server with this command in a shell:
----snip--------
#⁠!/bin/bash
../../jre/jre6/bin/java -server -Djava.awt.headless=true -Dadito.interbase.clobcharset=UTF-8 -Xms256m -Xmx1024m -cp ../../system/serverlicense.jar:server.jar:mail.jar:concurrent.jar:crystalclear.jar:cclib.jar:cc-viewer.jar:jfreechartcc.jar:jcommon.jar:js.jar:jdom.jar:ical4j.jar:commons-codec.jar:commons-httpclient.jar:commons-logging.jar:exchange.jar:log4j.jar:xbean.jar:commons-io.jar:joda-time.jar:images.jar:flamingo.jar de.adito.aditoweb.server.Server ../../config/serverconfig.xml
--------snapp-------
the difference no is the parameter -Dadito.interbase.clobcharset=UTF-8
(remark: the name interbase may be result of private issues ...)
Starting the adito-server with this -> all is ok (TextBLOBs are showed with charset UTF8)

I didn't know - because I can't look into the application code - if
- JDBC returns correct charset UTF-8 (and the Adito-application makes something wrong)
or
- JDBC returns another charset i.e. ISO ... (and this would be a bug of Jaybird)
something about the enviroment:
- 2 servers - one application and one database both running with ubuntu64server 10.04 LTS
- both servers run on clustered VMware ESX-server(s)
- firebird64 v2.5.0 with http://FreeAdhocUDF.so
- client on WindowsXP SP2 /SP3
- Java JRE 1.6_24 on server and clients
- clients run an application-client - not i.e. in firefox

I hope you understand the problem ... and could figure it out :-)
Thanks for your assistance.

Christoph Theuring

Commented by: @mrotteveel

Assuming the connection character set was NONE, this should no longer occurs with Jaybird 3, as we now explicitly use the blob character set to decode.