[JBoss JIRA] Created: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
5:48 p.m.
org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC
paths properly
--------------------------------------------------------------------------------------------------------
Key: JBAS-3775
URL: http://jira.jboss.com/jira/browse/JBAS-3775
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
Xerces-J 2.6.2
Reporter: David Kilzer
Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object
containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run
outside of JBoss. The particular code run under JBoss was started through a
Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but
the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the
culprit (file path changed to protect the innocent):
java.io.FileNotFoundException: \c$\path\to\file.xml
at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
at java.net.URL.openStream(URL.java:1007)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
[...]
Here is some sample code that should reproduce the issue. Note the path used to create
the java.io.File object.
File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
DocumentBuilderFactory factory = new
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlFile); // exception thrown under JBossAS
The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
[ http://jira.jboss.com/jira/browse/JBAS-3775?page=comments#action_12345487 ]
David Kilzer commented on JBAS-3775:
------------------------------------
The simple workaround is to open a java.io.FileInputStream to the java.io.File object
containing the UNC path and use javax.xml.parsers.DocumentBuilder.parse(InputStream)
instead.
org.jboss.net.protocol.file.FileURLConnection does not handle opening
InputStreams to UNC paths properly
--------------------------------------------------------------------------------------------------------
Key: JBAS-3775
URL: http://jira.jboss.com/jira/browse/JBAS-3775
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
Xerces-J 2.6.2
Reporter: David Kilzer
Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object
containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run
outside of JBoss. The particular code run under JBoss was started through a
Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but
the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the
culprit (file path changed to protect the innocent):
java.io.FileNotFoundException: \c$\path\to\file.xml
at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
at java.net.URL.openStream(URL.java:1007)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
[...]
Here is some sample code that should reproduce the issue. Note the path used to create
the java.io.File object.
File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
DocumentBuilderFactory factory = new
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlFile); // exception thrown under JBossAS
The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
[ http://jira.jboss.com/jira/browse/JBAS-3775?page=comments#action_12349230 ]
Vadim Kopichenko commented on JBAS-3775:
----------------------------------------
I do have the same annoing problem using quartz both with jboss 4.0.4.GA and 4.0.5.GA.
File quartz_jobs.xml is placed in root of ear.
But QuartzInitializerServlet fails to find it from included war.
As workaround I had to place this file also inside the war.
Here is the stacktrace:
java.io.FileNotFoundException:
at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:94)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:103)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1572)
at
org.quartz.xml.JobSchedulingDataProcessor.processFile(JobSchedulingDataProcessor.java:496)
at
org.quartz.xml.JobSchedulingDataProcessor.processFileAndScheduleJobs(JobSchedulingDataProcessor.java:565)
at
org.quartz.plugins.xml.JobInitializationPlugin.processFile(JobInitializationPlugin.java:392)
at
org.quartz.plugins.xml.JobInitializationPlugin.start(JobInitializationPlugin.java:324)
at
org.quartz.plugins.SchedulerPluginWithUserTransactionSupport.start(SchedulerPluginWithUserTransactionSupport.java:144)
at org.quartz.core.QuartzScheduler.startPlugins(QuartzScheduler.java:2139)
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:450)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:146)
at
org.quartz.ee.servlet.QuartzInitializerServlet.init(QuartzInitializerServlet.java:165)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3951)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4225)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy31.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at
org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at
org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy32.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
org.jboss.net.protocol.file.FileURLConnection does not handle opening
InputStreams to UNC paths properly
--------------------------------------------------------------------------------------------------------
Key: JBAS-3775
URL: http://jira.jboss.com/jira/browse/JBAS-3775
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
Xerces-J 2.6.2
Reporter: David Kilzer
Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object
containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run
outside of JBoss. The particular code run under JBoss was started through a
Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but
the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the
culprit (file path changed to protect the innocent):
java.io.FileNotFoundException: \c$\path\to\file.xml
at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
at java.net.URL.openStream(URL.java:1007)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
[...]
Here is some sample code that should reproduce the issue. Note the path used to create
the java.io.File object.
File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
DocumentBuilderFactory factory = new
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlFile); // exception thrown under JBossAS
The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:03 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly
[ http://jira.jboss.com/jira/browse/JBAS-3775?page=all ]
Dimitris Andreadis closed JBAS-3775.
------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
Resolution: Done
Assignee: Dimitris Andreadis
This shouldn't be an issue anymore as the
org.jboss.net.protocol.file.FileURLConnection was dropped, see JBCOMMON-55
org.jboss.net.protocol.file.FileURLConnection does not handle opening
InputStreams to UNC paths properly
--------------------------------------------------------------------------------------------------------
Key: JBAS-3775
URL: http://jira.jboss.com/jira/browse/JBAS-3775
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
Xerces-J 2.6.2
Reporter: David Kilzer
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.CR1
Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object
containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run
outside of JBoss. The particular code run under JBoss was started through a
Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but
the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the
culprit (file path changed to protect the innocent):
java.io.FileNotFoundException: \c$\path\to\file.xml
at
org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
at
org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
at java.net.URL.openStream(URL.java:1007)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
[...]
Here is some sample code that should reproduce the issue. Note the path used to create
the java.io.File object.
File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"):
DocumentBuilderFactory factory = new
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
DocumentBuilder builder = factory.newDocumentBuilder();
Document document = builder.parse(xmlFile); // exception thrown under JBossAS
The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6056
days inactive
6655
days old
3 comments
3 participants
participants (3)
-
David Kilzer (JIRA) -
Dimitris Andreadis (JIRA) -
Vadim Kopichenko (JIRA)