Topic
1 reply Latest Post - ‏2012-11-15T22:36:14Z by SystemAdmin
SystemAdmin
SystemAdmin
9855 Posts
ACCEPTED ANSWER

Pinned topic Dispatcher throwing SAX Parse Exception when loading AL

‏2012-11-15T00:41:53Z |
Hi All,

Recently, i built a WebService Adapter which has createUser, deleteuser methods and so on. I built the JAR file with the AL XML files, service.def, schema ,customLabels, Account and service form and imported into ITIM. Profile Installation is successful. When i trigger createAccount in ITIM - Request is reaching the dispatcher, but dispatcher is unable to load AL because of the follwing error: ><com.ibm.di.dispatcher.FAIL_LOAD_AL><http://WinCorAdd, Invalid byte 1 of 1-byte UTF-8 sequence.]>>]></LogText>

FYI, ADD is working properly when i manually run the Assembly in TDI UI. Looks, like XML or service def error. I looked into the file content, everything looked fine.
I attached the JAR file contents. Please help me out if you have any pointers.

Detailed Log:

<Trace Level="MIN">
<Time Millis="1352937532472"> 2012.11.15 10:58:52.472+11:00</Time>
<Server Format="IP">aaunswt143.aut01.cbaitest01.com</Server>
<ProductId>CTGIM</ProductId>
<Component>com.ibm.itim.remoteservices.provider.itdiprovider</Component>
<ProductInstance>server1</ProductInstance>
<LogText><![CDATA[Error during loading assembly line: <<com.ibm.di.dispatcher.remote.exception.ALLoadException><statusCode=2><reasonCode=100><com.ibm.di.dispatcher.FAIL_LOAD_AL><http://WinCorAdd, Invalid byte 1 of 1-byte UTF-8 sequence.]>>]></LogText>
<Source FileName="com.ibm.itim.remoteservices.provider.itdiprovider.ItdiServiceProvider" Method="loadALconfig"/>
<Thread>Default : 110</Thread>
<Exception><![CDATA[<<com.ibm.di.dispatcher.remote.exception.ALLoadException><statusCode=2><reasonCode=100><com.ibm.di.dispatcher.FAIL_LOAD_AL><http://WinCorAdd, Invalid byte 1 of 1-byte UTF-8 sequence.>>
at com.ibm.di.dispatcher.rmi.RMIDispatcherImpl.loadAL(RMIDispatcherImpl.java:1093)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:310)
at sun.rmi.transport.Transport$1.run(Transport.java:171)
at java.security.AccessController.doPrivileged(AccessController.java:284)
at sun.rmi.transport.Transport.serviceCall(Transport.java:167)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:547)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:802)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:661)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:736)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:263)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:239)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
at com.ibm.di.dispatcher.rmi.RMIDispatcherImpl_Stub.loadAL(Unknown Source)
at com.ibm.itim.remoteservices.provider.itdiprovider.ItdiServiceProvider.loadALconfig(ItdiServiceProvider.java:1884)
at com.ibm.itim.remoteservices.provider.itdiprovider.ItdiServiceProvider.getTCB(ItdiServiceProvider.java:2165)
at com.ibm.itim.remoteservices.provider.itdiprovider.ItdiServiceProvider.execAssemblyLine(ItdiServiceProvider.java:1559)
at com.ibm.itim.remoteservices.provider.itdiprovider.ItdiServiceProvider.add(ItdiServiceProvider.java:458)
at com.ibm.itim.remoteservices.ejb.mediation.Connector.addRemote(Connector.java:2598)
at com.ibm.itim.remoteservices.ejb.mediation.Connector.access$1600(Connector.java:115)
at com.ibm.itim.remoteservices.ejb.mediation.Connector$RequestTypeAdd.executeRemote(Connector.java:804)
at com.ibm.itim.remoteservices.ejb.mediation.Connector$RequestTypeProcess.execute(Connector.java:496)
at com.ibm.itim.remoteservices.ejb.mediation.Connector.add(Connector.java:1782)
at com.ibm.itim.remoteservices.ejb.mediation.PendingMessage.executeStoredRequest(PendingMessage.java:1168)
at com.ibm.itim.remoteservices.ejb.mediation.PendingMessage.isServiceAlive(PendingMessage.java:751)
at com.ibm.itim.remoteservices.ejb.mediation.PendingMessage.testServiceAndRestartProcesses(PendingMessage.java:695)
at com.ibm.itim.remoteservices.ejb.mediation.PendingMessage.testService(PendingMessage.java:547)
at com.ibm.itim.remoteservices.ejb.mediation.PendingMessage.execute(PendingMessage.java:358)
at com.ibm.itim.remoteservices.ejb.mediation.ExtensionMessageHandler.onMessage(ExtensionMessageHandler.java:60)
at com.ibm.itim.messaging.mdb.MessageHandlerBean.handleMessage(MessageHandlerBean.java:136)
at com.ibm.itim.messaging.mdb.EJSLocalStatelessenroleejb_BeanManagedMessageHand_9f57a42d.handleMessage(Unknown Source)
at com.ibm.itim.messaging.mdb.NonTransactedMessageListenerBean.onMessage(NonTransactedMessageListenerBean.java:171)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1014)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:747)
at $Proxy0.onMessage(Unknown Source)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint(JmsJcaEndpointInvokerImpl.java:201)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:788)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:585)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:419)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
]]></Exception>
</Trace>
Thanks in Advance !!
Updated on 2012-11-15T22:36:14Z at 2012-11-15T22:36:14Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    9855 Posts
    ACCEPTED ANSWER

    Re: Dispatcher throwing SAX Parse Exception when loading AL

    ‏2012-11-15T22:36:14Z  in response to SystemAdmin
    Hi All,
    I sorted it out, the error was due to misinterpretation of apostrophe as special character. Fixed it now.

    Thanks !!