spurious? ERROR level messages

0 views
Skip to first unread message

Conrad Leonard

unread,
Jul 10, 2016, 11:01:18 PM7/10/16
to Stardog
A small thing, but on upgrading from 4.0.3 to 4.1.2 some informational messages that previously appeared in output now appear logged with ERROR level; example output below using an admin connection to create a database via API:

=4.0.3=
2016-07-11 12:50:58,038 [localEventLoopGroup-4-1] INFO  org.apache.shiro.session.mgt.AbstractValidatingSessionManager - Enabling session validation scheduler...
Bulk loading data to new database inMemoryTestDb.
Creating indexes...finished in 00:00:00.003
Loaded 26 triples to inMemoryTestDb from 1 file(s) in 00:00:00.033 @ 0.8K triples/sec.
Successfully created database 'inMemoryTestDb'.
Bulk loading data to new database inMemoryTestDb.
Creating indexes...finished in 00:00:00.003
Loaded 26 triples to inMemoryTestDb from 1 file(s) in 00:00:00.033 @ 0.8K triples/sec.
Successfully created database 'inMemoryTestDb'.


=4.1.2=
2016-07-11 12:59:45,371 [localEventLoopGroup-4-1] INFO  org.apache.shiro.session.mgt.AbstractValidatingSessionManager - Enabling session validation scheduler...
12:59:45.418 [Stardog.Executor-7] ERROR com.complexible.stardog.StardogKernel - Bulk loading data to new database inMemoryTestDb.
12:59:45.443 [Stardog.Executor-7] ERROR com.complexible.stardog.StardogKernel - Creating indexes...finished in 00:00:00.003
12:59:45.457 [Stardog.Executor-7] ERROR com.complexible.stardog.StardogKernel - Loaded 26 triples to inMemoryTestDb from 1 file(s) in 00:00:00.036 @ 0.7K triples/sec.
12:59:46.066 [Stardog.Executor-7] ERROR com.complexible.stardog.StardogKernel - Successfully created database 'inMemoryTestDb'.
Bulk loading data to new database inMemoryTestDb.
Loaded 26 triples to inMemoryTestDb from 1 file(s) in 00:00:00.036 @ 0.7K triples/sec.
Successfully created database 'inMemoryTestDb'.

Evren Sirin

unread,
Jul 11, 2016, 9:50:58 AM7/11/16
to Stardog
Are you using a custom logger config file? Those messages are intended
to be logged at the INFO level but they default to the level of the
underlying Logger which causes this behavior. You can ignore them and
we'll make sure they'll be logged at INFO level in the future.

Best,
Evren
> --
> -- --
> You received this message because you are subscribed to the C&P "Stardog"
> group.
> To post to this group, send email to sta...@clarkparsia.com
> To unsubscribe from this group, send email to
> stardog+u...@clarkparsia.com
> For more options, visit this group at
> http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

Conrad Leonard

unread,
Jul 11, 2016, 8:36:58 PM7/11/16
to Stardog
Hi Evren;
Yep that explains it; I have a logback xml somewhere.
Reply all
Reply to author
Forward
0 new messages