0

Hi everyone: I am running an java application in a windows xp toshiba computer. My application works fine in an windows 2000 compaq deskpro computer but in the toshiba one I get a strange exception. I think the problem is something with the parser and that makes the second error appear. The whole error is copied down, thanks for your help!
Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\usuario>cd escritorio\cmapisdk\examples\bin

C:\Documents and Settings\usuario\Escritorio\cmapisdk\examples\bin>
C:\Documents and Settings\usuario\Escritorio\cmapisdk\examples\bin>runtutorial

C:\Documents and Settings\usuario\Escritorio\cmapisdk\examples\bin>echo off
28/06/2005 09:42:50 AM com.avaya.mvap.svcproxy.prov.ServiceProviderBuilder getSe
rviceProviderType
INFO: REQUESTED SERVICE_PROVIDER=null
28/06/2005 09:42:51 AM com.avaya.mvap.svcproxy.prov.RemoteServiceProvider initSe
rviceProviderImpl
INFO: CMAPI SERVER IP=192.168.20.60: CMAPI SERVER PORT=4721
28/06/2005 09:42:58 AM com.avaya.mvap.svcproxy.prov.ServiceProviderBuilder getCm
apiServiceProvider
INFO: SERVICE PROVIDER = com.avaya.mvap.svcproxy.prov.RemoteServiceProvider
28/06/2005 09:42:58 AM sampleapps.station.AvayaStationImpl init
ADVERTENCIA: pds=com.avaya.mvap.svcproxy.PhysicalDeviceServicesProxy
startup of xml parser
Using the fast crimson parser
Exception in thread "QueuedExecutor" javax.xml.parsers.FactoryConfigurationError
: Provider org.apache.crimson.jaxp.SAXParserFactoryImpl could not be instantiate
d: java.lang.NullPointerException
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at org.exolab.castor.util.LocalConfiguration.getParser(LocalConfiguratio
n.java:299)
at org.exolab.castor.util.LocalConfiguration.getParser(LocalConfiguratio
n.java:254)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:542)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:487)
at com.avaya.mvcs.proxy.CstaUnmarshaller.unmarshal(CstaUnmarshaller.java
:98)
at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorTh
read.run(CstaUnmarshallerNode.java:167)
at com.avaya.common.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor
.java:88)
at java.lang.Thread.run(Unknown Source)
28/06/2005 09:43:58 AM com.avaya.mvcs.proxy.XmlGatewayClient handleRequest
ADVERTENCIA: The request=session[-1] com.avaya.csta.binding.GetDeviceId@cf829d,
id=1, timed out after 60.0 seconds
Probable causes:
1. The cmapi.ClientProxyTimeout has been overridden, and is too short.
2. The server has become overloaded...
3. Network connectivity may have become unstable.
4. The health of the server may become unstable.
Possible resolutions:
1. Increase the cmapi.ClientProxyTimeout value in cmapi-user-configuration.prope
rties
2. Reduce the load (connections) on the server.
3. Verify network connectivity.
4. Verify the health of the server.
Could not start the tutorial app
ch.ecma.csta.errors.CstaException: Request: session[-1] com.avaya.csta.binding.G
etDeviceId@cf829d timed out
at com.avaya.mvap.svcproxy.ServiceProxy.marshallRequest(ServiceProxy.jav
a:250)
at com.avaya.mvap.svcproxy.DeviceServicesProxy.getDeviceID(DeviceService
sProxy.java:130)
at sampleapps.station.AvayaStationImpl.getID(AvayaStationImpl.java:596)
at sampleapps.station.AvayaStationImpl.init(AvayaStationImpl.java:148)
at sampleapps.tutorial.TutorialApp.bootstrap(TutorialApp.java:183)
at sampleapps.tutorial.TutorialApp.main(TutorialApp.java:112)
Caused by: com.avaya.mvcs.proxy.XmlGatewayClient$TimeoutException: Request: sess
ion[-1] com.avaya.csta.binding.GetDeviceId@cf829d timed out
at com.avaya.mvcs.proxy.XmlGatewayClient$TimeoutTask.run(XmlGatewayClien
t.java:454)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

2
Contributors
1
Reply
2
Views
12 Years
Discussion Span
Last Post by freesoft_2000
This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.