What is this: "WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware"

Forum|Forum|1 year ago
December 9, 2024
2 replies
1441 views

Version: Windchill 12.1

Use Case: N/A

Description:

These rows appear in MS log for any user (user.name), what is this about? No hits in knowledge base search.

2024-12-09 13:56:35,295 INFO [ajp-nio-127.0.0.1-8010-exec-20] wt.system.err user.name - WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware
2024-12-09 13:56:35,780 INFO [ajp-nio-127.0.0.1-8010-exec-18] wt.system.err user.name - WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware
2024-12-09 13:56:37,702 INFO [ajp-nio-127.0.0.1-8010-exec-11] wt.system.err user.name - WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware
2024-12-09 13:56:47,004 INFO [ajp-nio-127.0.0.1-8010-exec-13] wt.system.err user.name - WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware
2024-12-09 13:56:47,287 INFO [ajp-nio-127.0.0.1-8010-exec-12] wt.system.err user.name - WARNING: Supplied DOM uses namespaces, but is not created as namespace-aware

Announcements

avillanueva

23-Emerald I

I did see this come up on google searches so I do not think this is Windchill specific. Can you add more information about when this is occurring and any recent system changes that were made. Is this just a warning?

H

HJ1

Author

15-Moonstone

I don't know yet what's the user action (assuming it is) triggering this. It's a recent upgrade to Windchill 12.1.2.5. During testing there weren't so many users to test with, so didn't see this at all.

"just a warning", hehe 😂 There's so many in MS log labeled "ERROR" which in the end have no meaning according to endless surfing of support articles that who knows what's relevant. 2 days of looking at MS log after upgrade takes away 2 years of life expectancy....

Yes the rows start with "INFO" and then there's the "WARNING" as in the examples I sent here.

H

HJ1

Author

15-Moonstone

Ok,

had a hunch and tried downloading an Office document from a WTDoc through Desktop Integration. That's causing these to appear in MethodServer log. Nothing strange about the download and opening the file to Word, business as usual. Revise, checkout and checkin ok.