cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

Creating serialization filter

rleir
17-Peridot

Creating serialization filter

Hi team

tl;dr this is what you see if the Oracle server did not get started.  crisis over ..

 

We did a VM rollback to a snapshot. Now, starting Windchill, ServerManager gets stuck and the last log entry is :

INFO [main] wt.system.err - INFO: Creating serialization filter from !bsh.XThis;!bsh.Interpreter;.........

 

No MethodServers get started. Windchill is not using any CPU and very little memory.

Oracle docs tell me: 

The Java serialization filtering mechanism screens incoming streams of serialized objects to help improve security and robustness. Filters can validate incoming ...

 

What is happening here?  How can I get Windchill started again?

ACCEPTED SOLUTION

Accepted Solutions
rleir
17-Peridot
(To:avillanueva)

The solution was as I implied it the tl;dr line: just make sure the database is running! Yes, the serialization filter is normal (it was in an 'Info' log entry). So if your Windchill is not coming up and this is the last log entry ... go start the database! And since it's probably in a VM, check that the NIC is enabled (your admin will understand that). 

View solution in original post

3 REPLIES 3
avillanueva
22-Sapphire II
(To:rleir)

How far did it get? Did it validate that it could connect to the database?

avillanueva
22-Sapphire II
(To:rleir)

I just checked my dev server and I see the same message. I think this is normal and not related to your issue.

rleir
17-Peridot
(To:avillanueva)

The solution was as I implied it the tl;dr line: just make sure the database is running! Yes, the serialization filter is normal (it was in an 'Info' log entry). So if your Windchill is not coming up and this is the last log entry ... go start the database! And since it's probably in a VM, check that the NIC is enabled (your admin will understand that). 

Announcements


Top Tags