-
Notifications
You must be signed in to change notification settings - Fork 9
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
roc.DefaultConnection log level #3
Comments
Hello, <dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.12</version>
</dependency> Maybe you will have to add an implementation of slf4j as indicated in their documentation https://www.slf4j.org/docs.html <dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.1.3</version>
<scope>test</scope>
</dependency> Then in test you should be able to use log config file of logback. May I ask why are you using our library ? What is your use case ? Maybe we can help you to achieve what you are trying to do ? |
👋 Hi. The PR mentioned above shows an example of how to control what is logged by the opc-da subsystem. TL;DR
The statically init it:
Then configure the logger level as usual. Best, Andrea |
J-Interop can't work properly after Microsoft applied DCOM hardening. You can check link here on this issue. Alternatively, you can try this solution to retrieve OPC data back in Java. It utilizes network transportation layer to access data, so there is no 3rd party Java library or SDK required. IMO, it is simple and straightforward. Cheers! |
Hello, I'm seeing log messages like this:
Jul 26, 2019 4:19:10 PM rpc.DefaultConnection processOutgoing
INFO:
Sending REQUEST
...how can I control this log level? I have found these methods:
...but how can I get the JISystem instance?
Thanks!
The text was updated successfully, but these errors were encountered: