icconnector from AOD 7.0.0.1801
Eror on catalina.out:

Feb 17, 2014 8:34:03 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /app/apache-tomcat-7.0.50/webapps/icconnector.war
Feb 17, 2014 8:34:03 PM org.apache.tomcat.util.digester.Digester endElement
SEVERE: End event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tomcat.util.IntrospectionUtils.callMethodN(IntrospectionUtils.java:911)
at org.apache.catalina.startup.CallMethodMultiRule.end(WebRuleSet.java:1021)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1063)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endNamespaceScope(XMLDTDValidator.java:2054)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:2005)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:879)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1789)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2965)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
at org.apache.catalina.startup.ContextConfig.parseWebXml(ContextConfig.java:1901)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1254)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:880)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:378)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5343)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:634)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1074)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalArgumentException: The servlets named [ICConnectorServletRequestID] and [ICConnectorwebServletRequestID] are both mapped to the url-pattern [/RequestID] which is not permitted
at org.apache.catalina.deploy.WebXml.addServletMapping(WebXml.java:292)
... 39 more

Feb 17, 2014 8:34:03 PM org.apache.catalina.startup.ContextConfig parseWebXml
SEVERE: Parse error in application web.xml file at jndi:/localhost/icconnector/WEB-INF/web.xml
org.xml.sax.SAXParseException; systemId: jndi:/localhost/icconnector/WEB-INF/web.xml; lineNumber: 114; columnNumber: 25; Error at (114, 25) : The servlets named [ICConnectorServletRequestID] and [ICConnectorwebServletRequestID] are both mapped to the url-pattern [/RequestID] which is not permitted
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2711)
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2743)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1066)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endNamespaceScope(XMLDTDValidator.java:2054)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:2005)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:879)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1789)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2965)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
at org.apache.catalina.startup.ContextConfig.parseWebXml(ContextConfig.java:1901)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1254)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:880)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:378)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5343)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:634)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1074)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalArgumentException: The servlets named [ICConnectorServletRequestID] and [ICConnectorwebServletRequestID] are both mapped to the url-pattern [/RequestID] which is not permitted
at org.apache.catalina.deploy.WebXml.addServletMapping(WebXml.java:292)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tomcat.util.IntrospectionUtils.callMethodN(IntrospectionUtils.java:911)
at org.apache.catalina.startup.CallMethodMultiRule.end(WebRuleSet.java:1021)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1063)
... 32 more

Feb 17, 2014 8:34:03 PM org.apache.catalina.startup.ContextConfig parseWebXml
SEVERE: Occurred at line 114 column 25
Feb 17, 2014 8:34:03 PM org.apache.catalina.startup.ContextConfig configureStart
SEVERE: Marking this application unavailable due to previous error(s)
Feb 17, 2014 8:34:03 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error getConfigured

Interesting, it hasn't shown up in any of our tomcat 7.0.5 installations. I wonder if the JDK is affecting this. I will test out the config on our end.

Can you go to your icconnector in tomcat to the web-inf dir and edit the web.xml file?

Are you using VOX or HTTPVOX?

if using HTTPVOX, remove these lines:

<servlet id="ICConnector_Servlet_ID1">
<servlet-name>ICConnectorServletRequestID</servlet-name>
<display-name>ICConnector Servlet Web Module Request ID</display-name>
<servlet-class>com.avaya.sce.icconnector.servlet.server.RequestID</servlet-class>
<load-on-startup>5</load-on-startup>
</servlet>

<servlet-mapping id="ServletMapping_2">
<servlet-name>ICConnectorServletRequestID</servlet-name>
<url-pattern>/RequestID</url-pattern>
</servlet-mapping>


If using normal VOX, remove these lines:

<servlet id="ICConnectorweb_Servlet_ID1">
<servlet-name>ICConnectorwebServletRequestID</servlet-name>
<display-name>ICConnectorweb Servlet Web Module Request ID</display-name>
<servlet-class>com.avaya.sce.icconnector.web.servlet.server.RequestID</servlet-class>
<load-on-startup>5</load-on-startup>
</servlet>

<servlet-mapping id="ServletMappingWeb_2">
<servlet-name>ICConnectorwebServletRequestID</servlet-name>
<url-pattern>/RequestID</url-pattern>
</servlet-mapping>


Restart the ICC or Tomcat and it should resolve the issue. Note that you won't be able to use the component (VOX or HTTPVOX) that you disabled, but you should only be using one or the other anyway. I will look into it and might result in a patch if necessary, but this should get you moving.

I can also send you a patch if you don't want to manually make the change. Email me at neilg@avaya.com.

I have already solved the problem in this way.
Just tomcat 7 there is a check on the <url-pattern>
Tomcat 6 did not do it.
I only change <url-pattern> on /RequestID1 for not using Connector.

My workaround in attachment.
For Tomcat7, jdk1.7 (For VRUSM Web Module)
Put it in <>\icconnector\WEB-INF

Hi Neil,

I'm using OD 06.00.13.01, with Tomcat-7 and Java 1.7.

Did you make a patch for this issue? (Something for re-generate the icconnector.war)


I'm upgrading a DD5-application which uses ic via code

if (Boolean.parseBoolean(useVox)) {

	com.avaya.sce.runtime.connectivity.ic.GetVDU getVDU = new com.avaya.sce.runtime.connectivity.ic.GetVDU(sField);

	sValue = (String)getVDU.executeCommand(mySession);

}else {

	com.avaya.sce.runtime.connectivity.ic.web.GetVDU getVDU = new com.avaya.sce.runtime.connectivity.ic.web.GetVDU(sField);

	sValue = (String)getVDU.executeCommand(mySession);

}

Regards,
Marcelo.

Yes, there's a patch but it is against OD 7.0. Can you upgrade to OD 7?

Unfortunately no, I need to upgrade to OD6 :(

I guess in my case I cannot use the workaround that you proposed, right? (Message 18/02/2014 10:25:34)

Yes, you can make the manual change I suggested earlier in this thread. As long as you aren't using both the traditional VOX and the HTTPVox in your apps.

According with the developer, the original application is using both.
The original app was made with OD5 and Tomcat6.

Is there another way to modify and generate the icconnector.war to avoid this issue? (using OD6 - Tomcat 7)