After upgrading to Ktor 3.0.0 i have started to ge...

# ktor

[mudasar187]

After upgrading to Ktor 3.0.0 i have started to get this output everytime I am starting my application:

13:29:36 [] [ead-1] INFO io.ktor.server.Application
                : Application started: class io.ktor.server.application.Application(0x7e1eb1bb) [
    class io.ktor.server.application.hooks.CallFailed$install$1
    class io.ktor.server.application.hooks.CallFailed$install$1
    class io.ktor.server.application.hooks.CallFailed$install$1
    class io.ktor.server.plugins.callid.CallIdSetup$install$1
    class io.ktor.server.application.hooks.CallSetup$install$1
    class io.ktor.server.plugins.calllogging.MDCHookKt$MDCHook$1$install$1
    class io.ktor.server.application.hooks.Metrics$install$1
    class io.ktor.server.engine.BaseApplicationEngineKt$installDefaultTransformationChecker$1
    class io.ktor.server.plugins.calllogging.MDCHookKt$MDCHook$1$install$1
    class io.ktor.server.engine.BaseApplicationEngineKt$installDefaultInterceptors$2
    class io.ktor.server.routing.RoutingRoot$Plugin$install$1
    class io.ktor.server.plugins.statuspages.BeforeFallback$install$1
    class io.ktor.server.engine.BaseApplicationEngineKt$installDefaultInterceptors$1
]

My Application.kt

fun main() {
    embeddedServer(Netty, port = 8080, module = Application::module).start(true)
}

fun Application.module() {
    val applicationState = ApplicationState()
    val useAuthentication = PropertiesConfig.Configuration().useAuthentication

    applicationLifeCycleConfig(applicationState)
    commonConfig()
    securityConfig(useAuthentication)
    routingConfig(useAuthentication, applicationState)
}

Any idea what makes this output?

[Aleksei Tirman [JB]]

It's a Pipeline.toString() method, which lists all of its interceptors (Application is a ApplicationCallPipeline ).

[mudasar187]

So its a normal output behaviour ?

[Aleksei Tirman [JB]]

It might be okay for the INFO level logs. I am not sure.

[Chris Searle]

I've had the same - just not had time to dig in to it.

I do wonder if there's any easy way to find out whats triggering the CallFailed lines.

The app itself seems to run perfectly.

[Aleksei Tirman [JB]]

These are just interceptors for the CallFailed hook.

[Chris Searle]

As in - I've been reading it wrong? I read that as the call to install failed - but its the installation of call failed itself.

Oh well.

I knew I should have spent more time digging in - been a bit too busy :)

[Aleksei Tirman [JB]]

Here is an issue for reference.

[Chris Searle]

Is there an access needed? I can see KTOR-7325 and KTOR-7327 but KTOR-7326 gives a 404 error.

[Aleksei Tirman [JB]]

I've changed the visibility so you can open it now

[Chris Searle]

Super. Thanks