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

Add trace support when using JDBC CallableStatements #1541

Closed
Xylus opened this issue Feb 16, 2016 · 0 comments · Fixed by #1555
Closed

Add trace support when using JDBC CallableStatements #1541

Xylus opened this issue Feb 16, 2016 · 0 comments · Fixed by #1555
Assignees
Milestone

Comments

@Xylus
Copy link
Contributor

Xylus commented Feb 16, 2016

Current JDBC tracers do not propagate server information when using CallableStatement, and results in rendering an unknown_db node. Adding an interceptor for CallableStatement similar to what's done for PrepareStatement should fix the issue.

@Xylus Xylus self-assigned this Feb 16, 2016
@Xylus Xylus added this to the 1.5.2 milestone Feb 16, 2016
Xylus added a commit to Xylus/pinpoint that referenced this issue Feb 25, 2016
Xylus added a commit to Xylus/pinpoint that referenced this issue Feb 25, 2016
Xylus added a commit to Xylus/pinpoint that referenced this issue Feb 25, 2016
dawidmalina pushed a commit to dawidmalina/pinpoint that referenced this issue Mar 20, 2016
dawidmalina pushed a commit to dawidmalina/pinpoint that referenced this issue Mar 20, 2016
dawidmalina pushed a commit to dawidmalina/pinpoint that referenced this issue Mar 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant