You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussed with Roman in Firebird-java. Thread "Process name in monitoring tables with Jaybird?" from July 15th, 2008.
Jaybird should set the proper DPB so that the remote process ID and the remote process name is shown for Jaybird applications in FB 2.1 monitoring tables (MON$ATTACHMENTS). Regarding the remote process name, we came to the following solution:
* If a particular -D parameter is present, use this one
* If this particular -D parameter is NOT present:
- Use the classname with the entire package information, if it fits into DPB / VARCHAR(253).
- If it doesn't fit into that, make a substring of the class name from right to left.
The only platform independent solution turns out to be via the -D property, therefore two new properties: org.firebirdsql.jdbc.pid and org.firebirdsql.jdbc.processName. If they are specified, values are passed to Firebird 2.1. Also the behavior with previous versions of FB is undefined, so use them with care.
Submitted by: Thomas Steinmaurer (tsteinmaurer)
Assigned to: Roman Rokytskyy (rrokytskyy)
Is duplicated by JDBC334
Relate to JDBC225
Discussed with Roman in Firebird-java. Thread "Process name in monitoring tables with Jaybird?" from July 15th, 2008.
Jaybird should set the proper DPB so that the remote process ID and the remote process name is shown for Jaybird applications in FB 2.1 monitoring tables (MON$ATTACHMENTS). Regarding the remote process name, we came to the following solution:
* If a particular -D parameter is present, use this one
* If this particular -D parameter is NOT present:
- Use the classname with the entire package information, if it fits into DPB / VARCHAR(253).
- If it doesn't fit into that, make a substring of the class name from right to left.
Commits: 59d59e2
The text was updated successfully, but these errors were encountered: