Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide ability to see REMOTE_PROCESS name and REMOTE_PID in MON$ATTACHMENTS when doing connect via JDBC [JDBC334] #380

Closed
firebird-automations opened this issue Dec 16, 2013 · 6 comments

Comments

@firebird-automations
Copy link

Submitted by: @pavel-zotov

Duplicates JDBC118
Duplicates JDBC225
Is duplicated by CORE5979

Attachments:
FbConnExploring.zip

Currently we can NOT see such info - there are NULLs in both fields.
It will be useful for debug purposes to have ability of watching for them.

@firebird-automations
Copy link
Author

Modified by: @pavel-zotov

Attachment: FbConnExploring.zip [ 12404 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

This feature already exists (since Jaybird 2.1.6, see JDBC118 and http://jaybirdwiki.firebirdsql.org/jaybird/doku.php?id=download:older#jaybird_2.1.6 ).

There are two options:
* Set the system properties org.firebirdsql.jdbc.processName and org.firebirdsql.jdbc.pid on the commandline
* Add the connection properties process_name and process_id

It is currently not possible to get the actual PID of the process automatically as - at least at the time of implementation - there was no platform independent method of obtaining the pid. JDBC225 will look into that.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue duplicates JDBC118 [ JDBC118 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue duplicates JDBC225 [ JDBC225 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue is duplicated by CORE5979 [ CORE5979 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants