Tag Info

New answers tagged

0

Solved. We stopped then restarted the HTTP Server through the Weblogic Enterprise Manager, then copied the lastinvocation log into a new .cmd file. We added that .cmd file as a Windows service using NSSM, then set it to Automatic(Delayed Start) in Windows services. Pretty ugly workaround, but it seems to work fine.


0

Oracle says this isn't possible. If you have an Oracle support account you can look at Doc ID 1946552.1 and Bug 17694797, which state that it's not possible, Oracle has known about it since 2013, and are still reviewing whether or not they should do anything about it.


0

WebLogic uses certicom as the SSL provider by default. On version 10.3.3, they've added JSSE support. I haven't seen this specific error you're seeing, but maybe enabling JSSE will resolve it for you. You configure it at the server level, under Server > Configuration > SSL tab > Advanced tab


0

You can configure it in the console, under the default realm -> configuration -> user lockout. Here's the documentation (I'm assuming wls 12c): http://docs.oracle.com/cd/E24329_01/web.1211/e24422/domain.htm#SECMG414


0

This behavior is actually expected. The managed server replicates the local LDAP from the Admin Server during startup, so your managed servers actually have the old weblogic user in there. By the way, there are ways to decrypt the passwords stored in boot.properties, if you have the data in SerializedSystemIni.dat so you could have done that instead of ...


0

How long are you actually waiting? Your configuration means you could have to wait up to 10 minutes, since test frequency is set to 600 seconds (10 minutes). Connection creation retry frequency relates to a scenario in which you restarted weblogic during the DB outage (or any other trouble connecting to the DB) and the data source didn't get created during ...


0

If your managed servers are on the same host, I believe there is no native way to find this out. If they're on different hosts, you can use the machine column on v$session on Oracle side to identify where it's coming from. The other option is to use some monitoring/profiling tool. I'm not sure which ones would tell you the session id on the database but ...



Top 50 recent answers are included