Solved

error initializing acl filter

Posted on 2010-11-19
3
496 Views
Last Modified: 2013-12-10
We get an error message while logiing in to the application. ACL filter is defined in the web.xml file and tthe below error message is thrown in the init() method of the Access Control Filter which gets invoked when you restart the application/server/JVM


INFO: ##########################
 INFO: Initializing Access Control Filter. Activation status is: false
 INFO: ##########################
FATAL: IOException:
java.net.SocketException: Socket Closed
      at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:177)
      at java.net.Socket.setTcpNoDelay(Socket.java:783)
      at weblogic.net.http.HttpClient.openServer(HttpClient.java:305)
      at weblogic.net.http.HttpClient.openServer(HttpClient.java:354)
      at weblogic.net.http.HttpClient.<init>(HttpClient.java:139)
      at weblogic.net.http.HttpClient.New(HttpClient.java:212)
      at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:140)
      at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:319)
      at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:28)
      at java.net.URL.openStream(URL.java:913)
      at weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:836)
      at weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:796)
      at weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:275)
      at weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:841)
      at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
      at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
      at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
      at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
      at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
      at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
      at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
      at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
      at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
      at com.pfizer.ost.util.WebXmlParser.doParseFile(WebXmlParser.java:56)
      at com.pfizer.ost.filters.AccessControlFilter.parseACLFiles(AccessControlFilter.java:581)
      at com.pfizer.ost.filters.AccessControlFilter.init(AccessControlFilter.java:552)
      at weblogic.servlet.internal.WebAppServletContext$FilterInitAction.run(WebAppServletContext.java:7074)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
      at weblogic.servlet.internal.WebAppServletContext.registerFilter(WebAppServletContext.java:3091)
      at weblogic.servlet.internal.WebAppServletContext.initFilters(WebAppServletContext.java:3062)
      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3380)
      at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:6262)
      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:892)
      at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
      at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
      at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2169)
      at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3111)
      at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1769)
      at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:352)
      at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
      at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
      at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
      at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
      at weblogic.Server.main(Server.java:32)
FATAL: ##########################
FATAL: WARNING! SECURITY INIT FAILURE! Could not PARSE web xml or ost ACL! Security override engaged! Access to the application has been disabled for all users!
FATAL: ##########################
0
Comment
Question by:shylu
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 35

Expert Comment

by:girionis
ID: 34188433
The problem seems to be with your web.xml. You have defined somethign that the server does not like. Can you post it?
0
 

Accepted Solution

by:
shylu earned 0 total points
ID: 37488350
ACL was not needed, and is removed from the web.xml
0
 

Author Closing Comment

by:shylu
ID: 37514299
ACL was not needed, and is removed from the web.xml
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
JTable - RowFilter & Columns Header. 3 143
Can I clean log of  running tomcat 7 server ? 3 127
some methods private some are not 8 222
multithreading example 7 135
This exercise is about for the following scenario: Dmgr and One node with 2 application server. Each application server contains it owns application. Application server name as follows server1 contains app1 server2 contains app1 Prereq…
Most of the developers using Tomcat find it easy to configure the datasource in Server.xml and use the JNDI name in the code to get the connection.  So the default connection pool using DBCP (or any other framework) is made available and the life go…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question