[RuntimeComponent] user segment is empty defaulting

I'm getting a "[RuntimeComponent] user segment is empty defaulting" warning message in the application log. I'm looking for a way to suppress the message from the log or a fix for the runtime component that's generating the message. Any assistance you can provide is appreciated.

Find more posts tagged with

Comments

Rick Poulin

Gimme the name of the java class, and package.

But.. why do you care to have that suppressed?

Charles8

Part of the problem is that I'm new to the TeamSite/LiveSite environment, so I don't know where things are loacted. The message "[RuntimeComponent] user segment is empty defaulting" is all I see in the log. I have been checking the different components that we have, but haven't found any leads to where this message is coming from. As far as why I want it supressed from the log, removing this messages would reduce the size of our log in half. Your assistance with this is appreciated.

Rick Poulin

Which log file are you looking at?

There should be a timestamp and a class name in front of every instance of this message. If there isn't, someone might have tinkered with your log4j configuration for some reason. Assuming we're talking about the runtime side, post your Interwoven/LiveSiteDisplayServices/runtime/web/WEB-INF/classes/log4j.xml

Charles8

I'm looking at the WebSphere SysteOut.log. I did find a LiveSite log that does have the class that I think you were asking for:

[com.interwoven.livesite.runtime.model.page.RuntimeComponent]

Also I found a log4j.xml file and attaching.

Charles8

I'm looking at the WebSphere SysteOut.log. I did find a LiveSite log that does have the class that I think you were asking for:

[com.interwoven.livesite.runtime.model.page.RuntimeComponent]

Also I found a log4j.xml file and attaching.

Rick Poulin

The 'easy' fix is to add a rule in your log4j.xml as follows, to "mute" WARN messages from this class:

<category name="com.interwoven.livesite.runtime.model.page.RuntimeComponent">
<priority value="ERROR" />
</category>

It doesn't look like you'd miss much today (assuming v7.4.0) but you might in the future.

The real fix would be to change your UserProfileService (or in the data repository) to set a proper default segment called "Primary" on the offending users, rather than leaving it as an empty list.

Charles8

Thanks for your assistance with this. I'm going to do some research on the userProfileServices so I can set the default segment, as I do agree this being the best solution.