Symantec causes WebLogic to intermittently fail to connect to the database

The Symantec of the DB server rejects the connection established by the WebLogic Server and finds the following content in its log:

23448 2011-10-2 10:42:26 Event Response: No 192.168.0.244 00-00-00-00-00-00-00 0.0.0.0 00-00-00-00-00-00 default 1 2011-10-2 10:41:23 2011-10-2 10:41:23 at 2011-10-2 communication from IP address 192.168.0.244 is prohibited between 10:41:23 and 10:51:23, 2011-10-2.

23449 2011-10-2 10:52:27 Event Response disconnected information no 192.168.0.244 00-00-00-00-00-00-00 0.0.0.0 00-00-00-00-00-00 default 1 2011-10-2 10:51:23 2011-10-2 10:51:23 the Event Response started at 10:41:23, has been released. The communication prohibition time from IP address 192.168.0.244 has reached 600 seconds.

23450 2011-10-2 11:41:12 intrusion protection important incoming TCP 192.168.0.250 00-00-00-00-00-00 0.0.0.0 00-00-00-00-00-00 C: \ windows \ system32 \ ntoskrnl.exe default 1 2011-10-2 11:40:11 2011-10-2 11:40:11 detected [Sid: 23179] OS attack: MSRPC Server Service RPC CVE-2008-4250.

23451 2011-10-2 11:41:12 event response is mainly transmitted without 192.168.0.250 00-00-00-00-00-00-00 0.0.0.0 00-00-00-00-00-00 default 1 2011-10-2 11:40:11 2011-10-2 11:40:11 at 2011-10-2 communication from IP address 192.168.0.250 is forbidden from 11:40:11 to 11:50:11, 2011-10-2.

 
 

The connection pool is set to start at 100, with a maximum value of 200 and an increment of 5. The contraction frequency is 3600 seconds. The process of the Oracle database is 500.

The following content appears in WebLogic logs:

Org. springframework. transaction. cannotcreatetransactionexception: cocould not open hibernate session for transaction; Nested exception is org. hibernate. Exception. genericjdbcexception:Cannot open connection

At org. springframework. Orm. hibernate3.hibernatetransactionmanager. dobegin (hibernatetransactionmanager. Java: 599)

.......

Caused by: org. hibernate. Exception. genericjdbcexception:Cannot open connection

 
 

Caused by: weblogic. JDBC. Extensions. connectiondeadsqlexception: weblogic. Common. resourcepool. resourcedeadexception: cocould not create pool connection. The DBMS driver exception was:The network adapter cocould not establish the connection

 
 

Org. springframework. beans. factory. beancreationexception: Error creating bean with name '_ filterchainproxy': initialization of bean failed; Nested exception is Org. springframework. beans. factory. beancreationexception: Error creating bean with name' _ filterchainlist ': cannot create inner bean' (inner bean) 'of Type [Org. springframework. security. config. orderedfilterbeandefinitiondecorator $ orderedfilterdecorator] while setting bean property 'filters 'with key [10]; Nested exception is Org. springframework. beans. factory. beancreationexception: Error creating bean with name '(inner bean) # 2': cannot resolve reference to bean 'filtersecurityinterceptor' while setting constructor argument; Nested exception is Org. springframework. beans. factory. beancreationexception: Error creating bean with name 'filtersecurityinterceptor 'defined in class path resource [system/security. XML]: cannot resolve reference to bean 'filterinvocationdefinitionsource' while setting bean property 'objectdefinitionsource'; Nested exception is Org. springframework. beans. factory. beancreationexception: Error creating bean with name 'filterinvocationdefinitionsource': factorybean threw exception on Object creation; Nested exception is Org. springframework. JDBC. cannotgetjdbcconnectionexception: cocould not get JDBC connection; Nested exception is weblogic. JDBC. extensions. pooldisabledsqlexception: weblogic. common. resourcepool. resourcedisabledexception:Pool JDBC Data Source-0 is suincluded, cannot allocate resources to applications ..