NullPointerException in processing

We are using weblogic 8.1 sp4 on HP Tru64 Unix.
The below error is occuring, and i was wondering if there is a patch, or if this is due to bad xml or something.
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
####<Sep 24, 2006 9:46:41 PM EST> <Info> <EJB> <hx74> <wls_elms_prod2> <E4JMS Session Dispatcher (1805305)> <weblogic> <BEA1-6BA370078365> <BEA-010051> <EJB Exception occurred during invocation from home: [email protected]f64 threw exception: java.lang.NullPointerException
java.lang.NullPointerException
     at weblogic.apache.xerces.util.SymbolTable.addSymbol(SymbolTable.java:173)
     at weblogic.apache.xerces.impl.XMLEntityManager$EntityScanner.scanQName(XMLEntityManager.java:2360)
     at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:702)
     at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1477)
     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 com.bea.xbean.store.Root$SaxLoader.load(Root.java:776)
     at com.bea.xbean.store.Root.loadXml(Root.java:1077)
     at com.bea.xbean.store.Root.loadXml(Root.java:1069)
     at com.bea.xbean.store.Root.loadXml(Root.java:1089)
     at com.bea.xbean.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:241)
     at au.com.auspost.elms.xml.elmsCommon.SapPricingDownloadDocument$Factory.parse(Unknown Source)
     at au.com.auspost.elms.dataload.DataLoadManagerBean.processSAPDataLoadXml(DataLoadManagerBean.java:1495)
     at au.com.auspost.elms.dataload.DataLoadManager_79smk0_EOImpl.processSAPDataLoadXml(DataLoadManager_79smk0_EOImpl.java:1052)
     at au.com.auspost.elms.dataload.util.DataLoadUtil.processSAPDataLoadMessage(DataLoadUtil.java:29)
     at au.com.auspost.elms.jms.receiver.SapDataDownloadReceiverBean.onMessage(SapDataDownloadReceiverBean.java:72)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
     at com.tibco.tibjms.TibjmsSession._submit(TibjmsSession.java:2843)
     at com.tibco.tibjms.TibjmsSession._dispatchAsyncMessage(TibjmsSession.java:1428)
     at com.tibco.tibjms.TibjmsSession$Dispatcher.run(TibjmsSession.java:2506)
>

Similar Messages

Error: java.lang.nullPointerException when process is complete

Hello,
I keep getting the below error in the log file when the process is complete, does any one has this error before? The error does not affect the process but it is kind of annoying when looking at the log file. I try to use the other component beside the Foundation>DecisionPoint>execute but I still get the same error.
[5/16/11 14:57:19:047 CDT] 00000047 AWS E com.adobe.workflow.engine.ProcessEngineBMTBean stallAction stalling action-instance: 40746 with message: javax.ejb.TransactionRolledbackLocalException: ; nested exception is: java.lang.NullPointerException
Can any one please advise on how to fix the error above to stop showing in the log file. I am still using LC ES 8.2.1 with SP3.
Thanks,
Han Dao

If you could give a little more info it would help. The web.xml for example, if your mapping it correctly, etc...

NullPointerException when processing *[*] xpath expression

I'm trying to pull only elements that have an element as a
child, using the *[*] xpath expression. When I use MSXML 3.0,
my results are correct. When I use ORAXSL (NT 9i version
downloaded from OTN), I get a NullPointerException. Please see
example below.
<?xml version="1.0"?>
<TABLES>
     <TABLE1>
          <TABLE1_ROW1>TEXT1</TABLE1_ROW1>
          <TABLE1_ROW2>TEXT2</TABLE1_ROW2>
     </TABLE1>
     <TABLE2>
          <TABLE2_ROW1>TEXT3</TABLE2_ROW1>
     </TABLE2>
     <TABLE3>
          <TABLE3_ROW1>TEXT4</TABLE3_ROW1>
     </TABLE3>
</TABLES>
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="text" version="1.0" encoding="UTF-8"
indent="yes"/>
<xsl:key name="elements" match="*[*]" use="name()"/>
<xsl:template match="/">
<xsl:for-each select="//*[generate-id(.)=generate-id(key
('elements',name())[1])]">
<xsl:for-each select="key('elements',name())">
<xsl:if test="position()=1">
<xsl:text>drop table </xsl:text>
<xsl:value-of select="name()"/>
<xsl:text>;
</xsl:text>
</xsl:if>
</xsl:for-each>
</xsl:for-each>
<xsl:text>
exit</xsl:text>
</xsl:template>
</xsl:stylesheet>
MSXML 3.0 OUTPUT:
drop table TABLES;
drop table TABLE1;
drop table TABLE2;
drop table TABLE3;
exit
ORAXSL OUTPUT:
java.lang.NullPointerException
Error occurred while processing test.xml: null
If I change the *[*] to just * then the XSLT will process.

This is a bug. I've filed Bug 2138361 to get this looked into by
development.
The workaround is to avoid using keys, moving the *[*] into the
outer select expression for the for-each:
<xsl:for-each select="//*[*]">
instead of:
<xsl:for-each select="//*[*][generate-id(.) =
                             generate-id(key('elements',name())
[1])]">

NullPointerException while processing clientRequest

I have xml document that I process as client request
<operation>
<code/>
<number/>
<cmpDateTime/>
</operation>
<operation>
<code/>
<number/>
<cmpDateTime/>
</operation>
<operation>
<code/>
<number/>
<cmpDateTime/>
</operation>
How can I check if this array is empty.
I have tried following
if(MyDoc.getOperationArray().length == 0 || MyDoc.getOperationArray == null){
This throws NullPointerException

Thanks all this was resolved I was refering to wrong xml document object.

UCCX 10.6.1 - Expired, Auto-generated Demo license crashing MCVD-LIB_LICENSE startup process?

Anybody else experiencing this?
I upgraded from version 9.0.x to 10.6.1 at the end of December. It generated a Demo License (that wasn't needed) during the upgrade, which expired on Feb 27th.
I restarted the engine on the HA node last night, and it won't start up now.
On start-up, MCVD Log shows:
6953: Mar 09 10:55:03.978 EDT %MCVD-LIB_LICENSE-7-UNK:General Runtime Error in using m_FlexlmParser details are : Exception=java.lang.NullPointerException
The process stops reading/parsing licenses after this and acts like it would if it had no license.
Good thing this wasn't my primary engine.

Yes,
That's what I ended up having to resort to. I had numerous demo licenses across the years because of rapid expansion of call volume (agent seat temp licenses to act as a bridge gap while permanent licenses were purchased and delivered).
It ended up being caused by two demo licenses that expired on the same day, it seems.
Just to add to your answer though... DO NOT DELETE THEM FROM THE GUI. This will put your engines out of service until all offending files are deleted, and may require a reboot even then.
Thanks...

Java Server0 stuck in starting apps state

Dear All,
My J2EE server was up and running, since last 2 days the Java stack [ more importantly the Server0 process] is down (showing yellow in the MMC), the SDM is running, the JAVA dispatcher is running , but the Server0 process is stuck in starting apps phase. I checked the Oracle tablespaces and found that Oracle SAPSR3DB was only 1%, so we increased the same.
When we restarted the ABAP+JAVA stack we again found that our Java Server0 process is yellow phase , our SDM is running, the JAVA dispatcher is running , but the Server0 process starts and then moves to starting framework phase and then gets stuck in the starting apps phase.
My ABAP part is running fine.
On Checking the developer trace for this server 0 process , it says that JLaunchISetState is changing the state from starting application [2] to starting applications [10] where is gets stuck.Have also gone through the latest log files in the J2ee/cluster/server0/log, but could not find any error .
I have tried waiting for long durations, but this has not resolved the issue.The RAM size is 3.5 GB and virtual memory is 12 GB.doesnt reveal any error.Also tried to increase the instance heap size via the config tool [ current value is 1024 , tried changing the value to 2048 , restarted cluster , but same issue again , so reverted back to old value].The OS is windows 2003 server , DB-Oracle 10g.This is a NW2004s stack on which PI 7.0 has been activated.
Have also checked and found all J2EE users i.e. j2ee_admin, J2ee_guest, sapjsf, and all PI related super users unlocked.
Also all DB schema users were found to be unlocked. Also tried increasing the number of threads in the thread manager in config tool.
Also tried increasing the enque/table_space value to 4 times of RAM, but no change in problem.
Checked values of VM parameters, everything seems to be fine.
Please find the Dev_server0 trace file below :-
trc file: "E:\usr\sap\PI7\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
node name   : ID9240450
pid         : 5796
system name : PI7
system nr. : 00
started at : Tue Dec 16 11:29:55 2008
arguments       :
       arg[00] : E:\usr\sap\PI7\DVEBMGS00\exe\jlaunch.exe
       arg[01] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
       arg[02] : -DSAPINFO=PI7_00_server
       arg[03] : pf=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
       arg[04] : -DSAPSTART=1
       arg[05] : -DCONNECT_PORT=2168
       arg[06] : -DSAPSYSTEM=00
       arg[07] : -DSAPSYSTEMNAME=PI7
       arg[08] : -DSAPMYNAME=hcl3SAP_PI7_00
       arg[09] : -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
       arg[10] : -DFRFC_FALLBACK=ON
       arg[11] : -DFRFC_FALLBACK_HOST=localhost
[Thr 5792] Tue Dec 16 11:29:55 2008
[Thr 5792] *** WARNING => INFO: Unknown property [instance.box.number=PI7DVEBMGS00hcl3sap] [jstartxx.c   841]
[Thr 5792] *** WARNING => INFO: Unknown property [instance.en.host=hcl3SAP] [jstartxx.c   841]
[Thr 5792] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
[Thr 5792] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
JStartupReadInstanceProperties: read instance properties [E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host    : hcl3SAP
-> ms port    : 3901
-> OS libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : hcl3SAP
-> ms port    : 3901
-> os libs    : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9240400 : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9240450 : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID9240400            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID9240450            : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\instance.properties
[Thr 5792] Tue Dec 16 11:29:56 2008
[Thr 5792] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5792] JLaunchRequestQueueInit: create pipe listener thread
[Thr 5772] WaitSyncSemThread: Thread 5772 started as semaphore monitor thread.
[Thr 5784] JLaunchRequestFunc: Thread 5784 started as listener thread for np messages.
[Thr 5792] NiInit3: NI already initialized; param 'maxHandles' ignored (1;10002)
[Thr 5792] CPIC (version=700.2006.09.13)
[Thr 5792] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_09
[Thr 5792] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID9240450]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_09
-> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version    : 1.4.2_09-b05
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : E:\usr\sap\PI7\DVEBMGS00\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50021
-> shutdown timeout   : 120000
[Thr 5792] JLaunchISetDebugMode: set debug mode [no]
[Thr 5720] JLaunchIStartFunc: Thread 5720 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=256M
-> arg[ 10]: -XX:PermSize=256M
-> arg[ 11]: -XX:NewSize=171M
-> arg[ 12]: -XX:MaxNewSize=171M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dsys.global.dir=E:\usr\sap\PI7\SYS\global
-> arg[ 25]: -Dapplication.home=E:\usr\sap\PI7\DVEBMGS00\exe
-> arg[ 26]: -Djava.class.path=E:\usr\sap\PI7\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\PI7\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;C:\j2sdk1.4.2_09\bin;E:\usr\sap\PI7\DVEBMGS00\j2ee\os_libs;E:\oracle\PI7\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_09\bin;C:\j2sdk1.4.2_09\jre\bin;E:\usr\sap\PI7\SYS\exe\uc\NTI386
-> arg[ 28]: -Dmemory.manager=1024M
-> arg[ 29]: -Xmx1024M
-> arg[ 30]: -Xms1024M
-> arg[ 31]: -DLoadBalanceRestricted=no
-> arg[ 32]: -Djstartup.mode=JCONTROL
-> arg[ 33]: -Djstartup.ownProcessId=5796
-> arg[ 34]: -Djstartup.ownHardwareId=G1631462527
-> arg[ 35]: -Djstartup.whoami=server
-> arg[ 36]: -Djstartup.debuggable=no
-> arg[ 37]: -DSAPINFO=PI7_00_server
-> arg[ 38]: -DSAPSTART=1
-> arg[ 39]: -DCONNECT_PORT=2168
-> arg[ 40]: -DSAPSYSTEM=00
-> arg[ 41]: -DSAPSYSTEMNAME=PI7
-> arg[ 42]: -DSAPMYNAME=hcl3SAP_PI7_00
-> arg[ 43]: -DSAPPROFILE=E:\usr\sap\PI7\SYS\profile\PI7_DVEBMGS00_hcl3SAP
-> arg[ 44]: -DFRFC_FALLBACK=ON
-> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 46]: -DSAPSTARTUP=1
-> arg[ 47]: -DSAPSYSTEM=00
-> arg[ 48]: -DSAPSYSTEMNAME=PI7
-> arg[ 49]: -DSAPMYNAME=hcl3SAP_PI7_00
-> arg[ 50]: -DSAPDBHOST=hcl3SAP
-> arg[ 51]: -Dj2ee.dbhost=hcl3SAP
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
[Thr 5720] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 4072] Tue Dec 16 11:29:59 2008
[Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4072] Tue Dec 16 11:30:00 2008
[Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4072] JLaunchISetClusterId: set cluster id 9240450
[Thr 4072] Tue Dec 16 11:30:01 2008
[Thr 4072] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4072] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 6392] Tue Dec 16 11:30:28 2008
[Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 6392] Tue Dec 16 11:30:29 2008
[Thr 6392] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.engine.Compress
[Thr 6704] Tue Dec 16 11:30:36 2008
[Thr 6704] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 4072] Tue Dec 16 11:31:48 2008
[Thr 4072] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
Thanks in advance for your time and patience.
Prashant
Edited by: Prashant Vijayadas on Dec 16, 2008 5:14 PM

Hi Jazz,
i cannot seem to find any errors in the default trace files either [ located in usr/sap/<SID>/DVEBMGS/j2ee/cluster/server0/log ]
Please find the default trace files below:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!FILESET[4, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.3.trc]/>
<!NEXTFILE[defaultTrace.5.trc]/>
<!LOGHEADER[END]/>
#1.5#0012793AE40C00440000000C0000121800045DD8487B974B#1229083417427#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)#
#1.5#0012793AE40C00440000000D0000121800045DD8487D650D#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)#
#1.5#0012793AE40C00440000000E0000121800045DD8487D65A5#1229083417552#System.err##System.err#######SAPEngine_System_Thread[impl:5]_69##0#0#Error##Plain###     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)#
#1.5#0012793AE40C002F000000060000121800045DD848DD3380#1229083423878#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C0047000000000000121800045DD849291423#1229083428954#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://hcl3sap.hclt.corp.hcl.in:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.pi7.hcl3sap), due to: HTTP 503: Not Ready#
#1.5#0012793AE40C0047000000010000121800045DD849298BB2#1229083428985#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Not Ready#
#1.5#0012793AE40C0049000000000000121800045DD8492F4B02#1229083429407#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_8##0#0#Error##Plain###HTTP response code: 503 (Not Ready)#
#1.5#0012793AE40C004E000000000000121800045DD8496DB509#1229083433562#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Java###Configuration error in : #2#JDBC_Receiver_CC#<null>#
#1.5#0012793AE40C002F000000090000121800045DD84973B644#1229083433968#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C0050000000020000121800045DD849746B3F#1229083433999#com.sap.engine.services.jndi##com.sap.engine.services.jndi#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
     at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
     at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
     at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
     at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
     at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
     at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
     ... 14 more
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
     ... 17 more
#1.5#0012793AE40C0050000000030000121800045DD849747B70#1229083434015#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Error getting the server-side naming service functionality during getInitialContext operation.#
#1.5#0012793AE40C0051000000000000121800045DD849761D0C#1229083434124#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_1##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
XI
Sender
RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
XI
Sender
RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x70c DBC 0x779cd6c Jet'.#
#1.5#0012793AE40C0050000000040000121800045DD8497B42D4#1229083434452#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_47##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:243)
     at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
     at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
     at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
     at javax.naming.InitialContext.init(InitialContext.java:219)
     at javax.naming.InitialContext.<init>(InitialContext.java:195)
     at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:318)
     at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:344)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:124)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
     at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:70)
     at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:135)
     ... 13 more
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:180)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:172)
     at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:60)
     ... 14 more
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:177)
     ... 17 more
') before. Reconfigure it or restart the JMS service!#1#VASAVI_RCR_JMS_HR#
#1.5#0012793AE40C004E000000020000121800045DD84981BA8C#1229083434874#com.sap.aii.adapter.jdbc.XI2JDBC##com.sap.aii.adapter.jdbc.XI2JDBC.handleDBConnectException(Exception, AlertContextInformation)#######SAPEngine_System_Thread[impl:5]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
#1.5#0012793AE40C0053000000000000121800045DD8498DB60C#1229083435670#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_send_RFC#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
#1.5#0012793AE40C0054000000000000121800045DD8498F2B21#1229083435764#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_MWSOA_SDR:VSD_CC_JDBC]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.111:1521:ORACLE': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153092352)(ERR=12500)(ERROR_STACK=(ERROR=(CODE=12500)(EMFI=4))(ERROR=(CODE=12560)(EMFI=4))(ERROR=(CODE=530)(EMFI=4))(ERROR=(BUF='32-bit Windows Error: 2: No such file or directory'))))#
#1.5#0012793AE40C0053000000010000121800045DD849987C48#1229083436373#com.sap.aii.af.rfc.core.RfcRuntimeManager##com.sap.aii.af.rfc.core.RfcRuntimeManager.channelAdded(Channel channel)#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###can not instantiate RfcPool object - ignoring this channel '''' due to: #2#CC_A_RFCSender#com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts#
#1.5#0012793AE40C0055000000000000121800045DD8499BFF10#1229083436592#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_11##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
#1.5#0012793AE40C0056000000000000121800045DD849BF4E62#1229083438919#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_41##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C0057000000000000121800045DD849C87229#1229083439513#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
#1.5#0012793AE40C0058000000000000121800045DD849D0CAB8#1229083440060#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#FileReceiver_FCC#<null>#
#1.5#0012793AE40C0058000000020000121800045DD849E48706#1229083441356#com.sap.aii.adapter.file.XI2File##com.sap.aii.adapter.file.XI2File.init(Channel, AdminAdapter)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#CC_Receiver1#<null>#
#1.5#0012793AE40C0059000000000000121800045DD84A050EFF#1229083443480#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_119##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C002F0000000C0000121800045DD84A0DD554#1229083444058#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C0058000000040000121800045DD84A1C96B5#1229083445027#com.sap.aii.adapter.file.Conversion##com.sap.aii.adapter.file.Conversion.getTableParaWithErrorDescription(String)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/Conversion#Java###Parameter : not set#1#student.fieldNames#
#1.5#0012793AE40C0058000000060000121800045DD84A3FEB97#1229083447338#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.init(Channel, AdminAdapter, boolean)#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Java###Configuration error in : #2#stu_sender#<null>#
#1.5#0012793AE40C0058000000080000121800045DD84A400FAA#1229083447354#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.start()#######SAPEngine_System_Thread[impl:5]_91##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###File adapter sender channel stu_sender not initalized - could not start#
#1.5#0012793AE40C0054000000020000121800045DD84A48C532#1229083447916#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BS_TST:CC_F1_S]_185##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_F1_S: No suitable sender agreement found#
#1.5#0012793AE40C005A000000000000121800045DD84A68B403#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_257##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C0059000000020000121800045DD84A68C418#1229083450009#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_258##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
#1.5#0012793AE40C005B000000000000121800045DD84A68F232#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_259##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
#1.5#0012793AE40C005C000000000000121800045DD84A68FDA1#1229083450025#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_260##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C005D000000000000121800045DD84A6BAA02#1229083450212#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_263##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
#1.5#0012793AE40C002F0000000F0000121800045DD84AA8C03D#1229083454211#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C005C000000020000121800045DD84B01421F#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRDF:CC_BSRDF]_434##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C005E000000000000121800045DD84B01519A#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRD]_437##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
#1.5#0012793AE40C005F000000000000121800045DD84B015B72#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDE]_439##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
#1.5#0012793AE40C0059000000040000121800045DD84B015DEF#1229083460006#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDG]_436##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
#1.5#0012793AE40C0060000000000000121800045DD84B01C588#1229083460037#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0#####File2XI[:BSRD:CC_BSRDF]_440##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C0061000000000000121800045DD84B037ABA#1229083460146#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:JDBC2JDBC_Sender_BS:JDBC_Sender_CC]_438##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
XI
Sender
RamaSurya.mdb' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=C:
XI
Sender
RamaSurya.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1218 Thread 0x1988 DBC 0x78d1eac Jet'.#
#1.5#0012793AE40C0062000000000000121800045DD84B282C7A#1229083462551#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
#1.5#0012793AE40C0062000000010000121800045DD84B283F6D#1229083462567#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_50##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     ...') before. Reconfigure it or restart the JMS service!#1#CC_PO_RCR#
#1.5#0012793AE40C0063000000000000121800045DD84B284C1A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
#1.5#0012793AE40C0064000000000000121800045DD84B28531A#1229083462567#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
#1.5#0012793AE40C0065000000000000121800045DD84B289AAB#1229083462583#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222#
#1.5#0012793AE40C0066000000000000121800045DD84B2AB132#1229083462723#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222#
#1.5#0012793AE40C0064000000010000121800045DD84B397738#1229083463692#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_56##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     ...') before. Reconfigure it or restart the JMS service!#1#CC_PIP_TO_B2MML#
#1.5#0012793AE40C0066000000010000121800045DD84B39B5F3#1229083463707#com.sap.aii.af.service.jms.WorkerJMSSender##com.sap.aii.af.service.jms.WorkerJMSSender.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_49##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.66:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.66:7222]
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     ...') before. Reconfigure it or restart the JMS service!#1#CC_B2MML_IB#
#1.5#0012793AE40C0063000000010000121800045DD84B39C1BB#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_57##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     ...') before. Reconfigure it or restart the JMS service!#1#CC_S_GR#
#1.5#0012793AE40C0065000000010000121800045DD84B39C67B#1229083463707#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_53##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://10.117.135.41:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://10.117.135.41:7222]
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:669)
     at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:489)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     ...') before. Reconfigure it or restart the JMS service!#1#Sys_GoodsIssueFromStore_JMS_EMS#
#1.5#0012793AE40C002F000000120000121800045DD84B420336#1229083464254#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C0067000000000000121800045DD84B4618D7#1229083464520#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
#1.5#0012793AE40C0068000000000000121800045DD84B483E2D#1229083464660#com.sap.aii.af.service.jms.WorkerImpl##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Java###Unable to create the Queue due to #1#Name not found: 'Inbound_APC_Queue_Order'#
#1.5#0012793AE40C002F000000150000121800045DD84BDB73A2#1229083474297#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_32##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#0012793AE40C006A000000000000121800045DD84C0FEB63#1229083477734#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.handleDBConnectException(Exception)#J2EE_GUEST#0#####JDBC2XI[:BS_F2FBPM_SENDER:CM_SENDER]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Accessing database connection 'jdbc:oracle:thin:@10.117.34.178:1521:DEV' failed: com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@10.117.34.178:1521:DEV': SQLException: Io exception: The Network Adapter could not establish the connection#
#1.5#0012793AE40C006B000000000000121800045DD851C45EB6#1229083573418#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820003]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C006B000000020000121800045DD851C46142#1229083573418#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#44a92fa0c84511dd92ad0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_A_flatefile]_13##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_A_flatefile: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006C000000000000121800045DD851DF9B17#1229083575199#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820005]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C006C000000020000121800045DD851DF9DBA#1229083575199#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFtpList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#45bb3be0c84511dd976d0012793ae40c#File2XI[:BService_MDM_SENDER:Outbound_From_MDM2]_12##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Outbound_From_MDM2: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006D000000000000121800045DD851F43711#1229083576557#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff820007]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C006D000000020000121800045DD851F439AA#1229083576557#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#467eb2f0c84511ddce9a0012793ae40c#File2XI[:BS_Sat:MsgMerge_Sender1_CC]_48##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender1_CC: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006D000000040000121800045DD85210BEE6#1229083578416#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRDF:CC_BSRDF]_545##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C006C000000040000121800045DD852118EE5#1229083578479#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDG]_546##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
#1.5#0012793AE40C006C000000060000121800045DD8522A479D#1229083580087#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDE]_547##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
#1.5#0012793AE40C006D000000060000121800045DD8522AB3A6#1229083580119#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BSRD:CC_BSRD]_548##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRD: No suitable sender agreement found#
#1.5#0012793AE40C006C000000080000121800045DD852509FDA#1229083582602#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#46ff54a0c84511ddb71a0012793ae40c#File2XI[:BSRD:CC_BSRDF]_549##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDF: No suitable sender agreement found#
#1.5#0012793AE40C006E000000000000121800045DD852544076#1229083582836#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000a]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C006E000000020000121800045DD85254AFC8#1229083582868#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4982cb30c84511ddbd890012793ae40c#File2XI[:BS_Sat1:MsgMerge_Sender2_CC]_69##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel MsgMerge_Sender2_CC: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006F000000000000121800045DD852569148#1229083582993#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000b]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C006F000000020000121800045DD852569409#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#499a98f0c84511ddb0c20012793ae40c#File2XI[:BS_PAUDV:CC_PAUDV_SEND]_134##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_PAUDV_SEND: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006E000000040000121800045DD85256A507#1229083582993#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b23f810c84511ddc7d30012793ae40c#File2XI[:BSRDE:CC_BSRDE]_558##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDE: No suitable sender agreement found#
#1.5#0012793AE40C006F000000040000121800045DD85258BFEE#1229083583133#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#0####4b3954d0c84511dd846c0012793ae40c#File2XI[:BSRDG:CC_BSRDG]_562##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_BSRDG: No suitable sender agreement found#
#1.5#0012793AE40C0070000000000000121800045DD8527941A5#1229083585273#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000d]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0070000000020000121800045DD8527943FF#1229083585273#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4b370ae0c84511dd8e0c0012793ae40c#File2XI[:BSystem_TestPractice_Sender:CC_Sending_file]_183##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_Sending_file: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C0071000000000000121800045DD852A635CB#1229083588210#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff82000f]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0071000000020000121800045DD852A63A01#1229083588210#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4c8e3670c84511dd94bf0012793ae40c#File2XI[:BS_PAUD:CC_POAUDSEND]_240##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_POAUDSEND: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C0072000000000000121800045DD852AF7377#1229083588819#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200011]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0072000000020000121800045DD852AF7668#1229083588819#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cad3020c84511ddb7490012793ae40c#File2XI[:BS_SEND2:CC_MERVSEND2]_250##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CC_MERVSEND2: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C0073000000000000121800045DD852BBB4AD#1229083589615#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200013]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0073000000020000121800045DD852BBB87F#1229083589615#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4cdf3ca0c84511dd8c190012793ae40c#File2XI[:BS_BLR:FileSender_BPM]_238##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_BPM: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C0056000000020000121800045DD852BC3912#1229083589647#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200016]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0056000000040000121800045DD852BC3B81#1229083589662#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4d1abf00c84511dda6510012793ae40c#File2XI[:BS_BLR:FWS_SEND_CC]_268##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FWS_SEND_CC: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C0074000000000000121800045DD852CD926F#1229083590787#com.sap.aii.adapter.file.util.AuditLog##com.sap.aii.adapter.file.util.AuditLog.addAuditLog(PublicMessageKey, String, AuditLogStatus, String, String, Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0ffffff8cffffffffffffff8200017]#hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###FILE_ERR_211#
#1.5#0012793AE40C0074000000020000121800045DD852CD94EB#1229083590787#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4e3d9420c84511ddc5950012793ae40c#File2XI[:BS_Sat:FileSender_FCC]_252##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel FileSender_FCC: Sending file failed with java.lang.NullPointerException - continue processing#
#1.5#0012793AE40C006D000000080000121800045DD853948DA4#1229083603829#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#4759f7c0c84511dd8d7b0012793ae40c#File2XI[:BS_DIPANKAR1_SENDER:Sender_CC]_553##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel Sender_CC: Directory
192.168.91.1
D:
SAP_Data does not exist#
#1.5#0012793AE40C0075000000010000121800045DD86BA73EED#1229084007463#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #4446C8DDBF70F1DAB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
#1.5#0012793AE40C0075000000030000121800045DD8861A181C#1229084450980#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#PI7BASIS                        #4F47C8DD65E5F12CB51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_79##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
#1.5#0012793AE40C0076000000010000121800045DD88E669A80#1229084590160#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#SAPSYS                          #9D47C8DD4EE4F161B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
#1.5#0012793AE40C0076000000030000121800045DD899BD67E0#1229084780325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##PI7#RIJUA                           #1448C8DDD335F1E5B51A0012793AE40C#SAPEngine_Application_Thread[impl:3]_95##0#0#Error#1#/System/Server#Plain###bean LCRBEAN_GET_PROFILE_PARAMETER not found#
#1.5#0012793AE40C0078000000010000121800045DD899EAE617#1229084783309#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_24##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
#1.5#0012793AE40C0079000000010000121800045DD899EB397B#1229084783325#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##HE6#SAPSYS                          #81C1A9AA09F24B0894CFA72F264F2842#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Server#Plain###bean SLDJAVA_ACCESSOR_REQUEST not found#
#1.5#0012793AE40C007B000000010000121800045DD8F60F3B22#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: received EOF, connection closed!#
#1.5#0012793AE40C007B000000030000121800045DD8F60F4058#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: receive failed (Connection closed -1)#
#1.5#0012793AE40C007B000000050000121800045DD8F60F425A#1229086329364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: receive failed (Encomi: receive failed (Connection closed -1) -1), flush pending responses#
#1.5#0012793AE40C007C000000000000121800045DD8F6115F52#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset#
#1.5#0012793AE40C007C000000010000121800045DD8F611603B#1229086329505#com.sap.engine.core.cluster.impl6.ms.MSRawConnection##com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage()######b0307110c84b11ddab1b0012793ae40c#SAP J2EE Engine|MS Socket Listener##0#0#Error##Plain###java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.read(MSMessageHeader.java:440)
     at com.sap.engine.core.cluster.impl6.ms.MSMessageObjectImpl.readHeader(MSMessageObjectImpl.java:142)
     at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.receiveRawMessage(MSRawConnection.java:1660)
     at com.sap.engine.core.cluster.impl6.ms.MSListener.run(MSListener.java:86)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#0012793AE40C007B000000070000121800045DD8F61E7D39#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000090000121800045DD8F61E7F00#1229086330364#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 1 times#
#1.5#0012793AE40C007B0000000B0000121800045DD8F64AFC71#1229086333286#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000000D0000121800045DD8F6791AC5#1229086336302#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000000F0000121800045DD8F6A58D15#1229086339224#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000110000121800045DD8F6D20F7F#1229086342130#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000130000121800045DD8F6FE9326#1229086345052#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000150000121800045DD8F72CA0FC#1229086348067#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000170000121800045DD8F75795FA#1229086350880#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000190000121800045DD8F78418D5#1229086353802#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000001B0000121800045DD8F7B3C822#1229086356927#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000001D0000121800045DD8F7E02F82#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000001F0000121800045DD8F7E030C2#1229086359833#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 11 times#
#1.5#0012793AE40C007B000000210000121800045DD8F80CB555#1229086362755#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000230000121800045DD8F83ABD55#1229086365770#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000250000121800045DD8F8674E72#1229086368692#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000270000121800045DD8F893C188#1229086371614#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000290000121800045DD8F8C1CD8A#1229086374630#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000002B0000121800045DD8F8EE5019#1229086377536#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000002D0000121800045DD8F91AD274#1229086380458#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000002F0000121800045DD8F947537E#1229086383379#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000310000121800045DD8F976E8A3#1229086386489#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000330000121800045DD8F9A36A4A#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000350000121800045DD8F9A36B62#1229086389411#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 21 times#
#1.5#0012793AE40C007B000000370000121800045DD8F9D175D4#1229086392426#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000390000121800045DD8F9FDFF04#1229086395348#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000003B0000121800045DD8FA2A7A76#1229086398270#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007F000000010000121800045DD8FA49473F#1229086400285#com.sap.aii.utilxi.prop.impl.BasicPropertySource##com.sap.aii.utilxi.prop.impl.BasicPropertySource#J2EE_GUEST#0##hcl3SAP.HCLT.CORP_PI7_9240450#Guest#158b1d00c84511dd9fed0012793ae40c#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/Applications/ExchangeInfrastructure#Plain###could not sync ExchangeProfile:
Thrown:
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '10.112.132.211:sapgw00' not reached
TIME        Fri Dec 12 18:23:20 2008
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
Connect_PM TYPE=A ASHOST=HCL3SAP SYSNR=00 GWHOST=HCL3SAP GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '10.112.132.211:sapgw00' not reached
TIME        Fri Dec 12 18:23:20 2008
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:989)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3193)
     at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101)
     at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1286)
     at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:193)
     at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177)
     at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165)
     at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:580)
     at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)
     at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52)
     at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0012793AE40C007B0000003D0000121800045DD8FA56FC49#1229086401176#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B0000003F0000121800045DD8FA83A493#1229086404114#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000410000121800045DD8FAB189C5#1229086407113#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib######b01aed40c84b11dd8a150012793ae40c#Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to hcl3SAP/3201/Connection refused: connect)#
#1.5#0012793AE40C007B000000430000121800045DD8FADF9505#1229086410129#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engin

Reg File- Webservice Async-Sync bridge

Hi,
I have File -WS async-Sync scenario.
I have configured the RequestResponseBean-CallSAP-ResponseOnewayBean in my sender CC
When i execute the scenario, the sender channel is throwing Error: java.lang.NullPointerException
When i check the sender channel log, the SOAP call is executing, then
MP: processing local module localejbs/AF_Modules/ResponseOnewayBean,
MP: processing local module localejbs/AF_Modules/ResponseOnewayBean,
MP: exception caught with cause java.lang.NullPointerException,
File processing failed with java.lang.NullPointerException.
Is there any thing specific to be configured while using File adapter.
Thanks in advance.

Hi,
How is the WebService sync-Async implemented are you using any aysnc-sync bridge...
is that process returning the response back in the correct format.. ?
Rajesh

Help debugging POF exception

Hi,
We're just coming to the end of a rather big project and have just replaced some legacy APIs used by the firm's website with APIs that talk to Coherence.
We've had live traffic hitting these services for a few days now, and have successfully processed millions of requests (yay!)
As this has just gone live, I've been keeping a keen eye on server logs and noticed that I had an exception in my Proxy node logs to do with Pof Serialisation.
I can make an API call that will cause this exception on our live servers, but it does not happen on our test system (same versions of code, different data :( )
I was wondering if anyone had any success with debugging exception messages like this...
2012-09-05 23:19:08,292 [Logger@9266502 3.7.1.5] DEBUG Coherence 2012-09-05 23:19:08.292/214382.610 Oracle Coherence GE 3.7.1.5 <D5> ...
An exception occurred while processing a InvokeFilterRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor ...
Wrapped: Failed request execution for DistributedCache service on Member(Id=37 ... : null
at com.tangosol.util.Base.ensureRuntimeException(Base.java:288)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.tagException(Grid.CDB:36)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onInvokeFilterRequest(PartitionedCach
e.CDB:109)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$InvokeFilterRequest.run(PartitionedCa
che.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:66)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
at <process boundary>
at com.tangosol.io.pof.ThrowablePofSerializer.deserialize(ThrowablePofSerializer.java:57)
at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3316)
at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2604)
at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:368)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:1)
at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$QueryResponse.read(PartitionedCache.C
DB:33)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.deserializeMessage(Grid.CDB:19)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: Portable(java.lang.NullPointerException)
at <process boundary>
at com.tangosol.io.pof.ThrowablePofSerializer.deserialize(ThrowablePofSerializer.java:57)
at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3316)
at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2604)
at com.tangosol.io.pof.PortableException.readExternal(PortableException.java:150)
at com.tangosol.io.pof.ThrowablePofSerializer.deserialize(ThrowablePofSerializer.java:59)
at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3316)
at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2604)
at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:368)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:1)
at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$QueryResponse.read(PartitionedCache.C
DB:33)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.deserializeMessage(Grid.CDB:19)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.onNotify(PartitionedService.CDB:3)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache.onNotify(PartitionedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
The only way I think I can get to the bottom of this is by debugging some storage and proxy nodes locally and then loading them with the current set of live data (which is a pain) - then I will set exception breakpoints and see if anything on the stack gives me a clue as to what is going wrong :(
I have looked through the code and cannot see any place where I could be causing a NPException... (I might have missed something - but the code isn't really that complicated)
Does anyone have any tips for debugging this sort of thing (our POF serialisers have been in production for over a year now without any problem like this)?
It would be nice if Coherence logged the POF type number of the thing it was trying to serialise / deseralise when this exception occurs...
Thanks in advance for any advice!
-Bret

Think I got to the bottom of it (had to debug against live data)
Would be nice if the error message was more helpful...

Please help with CMR - strange error.

Hi,
im using xdoclet to generate sun files and i also tried to configure CMR manually in
the ejb-jar.xml but i just cant get it working:
When i try to deploy my app i always get the following strange exception:
[#|2004-12-11T20:50:48.281+0100|SCHWERWIEGEND|sun-appserver-pe8.1|javax.enterpr ise.system.tools.deployment|_ThreadID=13;|Caught java.lang.NullPointerException while processing CMP beans for application [informatrix]; module [informatrix.jar]: null. See log for details.
java.lang.NullPointerException
at com.sun.jdo.spi.persistence.support.ejb.ejbc.EjbConversionHelper.getRealRelatio nRoleDescriptor(EjbConversionHelper.java:363)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.EjbConversionHelper.getRelationRol eDescriptor(EjbConversionHelper.java:357)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.EjbConversionHelper.getInverseFiel dName(EjbConversionHelper.java:227)
at com.sun.jdo.api.persistence.mapping.ejb.MappingFile.completeCmrMappings(Mapping File.java:1636)
at com.sun.jdo.api.persistence.mapping.ejb.MappingFile.intoMappingClasses(MappingF ile.java:131)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.loadMappingClasse s(MappingGenerator.java:460)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.MappingGenerator.generateMapping(M appingGenerator.java:274)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.loadOrCreateMappi ngClasses(JDOCodeGenerator.java:581)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGener ator.java:153)
at com.sun.jdo.spi.persistence.support.ejb.ejbc.JDOCodeGenerator.init(JDOCodeGener ator.java:126)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:143)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:615)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:563)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java :361)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:209)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:286)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:176)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.j ava:107)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:138)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPh ase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeplo ymentService.java:626)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentSe rvice.java:187)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentSe rvice.java:513)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:140)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:168)
|#]
Can anyone explain what do those fields:
name
role-name
cascade-delete
target-ejb
target-role-name
target-cascade-delete
target-multiple
mean.
My scenario is following:
Bean 1 = User
Bean 2 = EmployeeData
Relationship: User has EmployeeData (1:1)
Tables:
Bean 1 mapped to users
Bean 2 mapped to employee_data
Collumns:
Bean 1 references Bean 2 in column pk_login Bean 1-field is login
Bean 2 references Bean 1 in column fk_login Bean 2-field is login
Thanx a lot to anyone who answers.

For the 1:1 relationship, the ejb.xml needs to have the relationship defined
<ejb-relation>
<ejb-relationship-role>
<ejb-relationship-role-name>AEJB-BEJB</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>AEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>b</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>BEJB-AEJB</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>BEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>a</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
For sun-cmp-mappings. xml make sure the column name for the FK of the related bean is defined
<entity-mapping>
<ejb-name>AEJB</ejb-name>
<table-name>AEJB_1X1_BI_BTOB</table-name>
<cmp-field-mapping>
<field-name>id</field-name>
<column-name>ID</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>NAME</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>value</field-name>
<column-name>VALUE</column-name>
</cmp-field-mapping>
<cmr-field-mapping>
<cmr-field-name>b</cmr-field-name>
<column-pair>
<column-name>ID</column-name>
<column-name>BEJB_1X1_BI_BTOB.FK_FOR_AEJB_1X1_BI_BTOB</column-name>
</column-pair>
</cmr-field-mapping>
</entity-mapping>
<entity-mapping>
<ejb-name>BEJB</ejb-name>
<table-name>BEJB_1X1_BI_BTOB</table-name>
<cmp-field-mapping>
<field-name>id</field-name>
<column-name>ID</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>name</field-name>
<column-name>NAME</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>value</field-name>
<column-name>VALUE</column-name>
</cmp-field-mapping>
<cmr-field-mapping>
<cmr-field-name>a</cmr-field-name>
<column-pair>
<column-name>FK_FOR_AEJB_1X1_BI_BTOB</column-name>
<column-name>AEJB_1X1_BI_BTOB.ID</column-name>
</column-pair>
</cmr-field-mapping>

ERPI Data write back not working due to unmapped dimension

Hi,
I am using version 11.1.2.1 of erpi with E-Business version 12. We have a hyperion Planning application. We are trying to write data back to e-business but the process is failing. The data goes into the staging tables but does not go into e-business due to unmapped dimensions. However, all the available dimensions have been mapped. The planning application contains multiple currencies and the hsp_rates dimension is not shown in erpi. We think this could be the unmapped dimension but there is no option to do this.
Has anyone experienced this issue? The hsp_rates is a theory but a probable one since it is in essbase where the data is held.
Thanks,
Nathan

we are unable to use the write-back feature.
it keep give an error as the following :
java.lang.NullPointerException
ERPI Process Start, Process ID: 50
ERPI Logging Level: DEBUG (5)
ERPI Log File: C:\DOCUME~1\hyperion\LOCALS~1\Temp\1\/aif_50.log
Jython Version: 2.1
Java Platform: java1.4.2_08
ERPI Process End, Process ID: 50
any ideas?
Aly

Problame with Runtime.exec()

Hi i am having one problem using Runtime in windows
When Using Runtime.exec to open any file which is inside a folder having a white space character in its name, i am not able to open the application. I am getting an error messsage that file cannot be found.
Following is the code
import java.io.IOException;
class OpenTest{
public static void main(String args[]){
//Folder "dd dd" having white space embedded in its name
//so the error comes
String sRegFilePath = "E:\\AAA\\dd dd\\dd.xls";
try {
Runtime rt = Runtime.getRuntime();
rt.exec("cmd /c start "+sRegFilePath,null,null);
catch(SecurityException se) {
System.err.println( "SecurityException starting process!");
catch(NullPointerException ne) {
System.err.println( "NullPointerException starting process!");
catch(IndexOutOfBoundsException ioobe) {
System.err.println( "IndexOutOfBoundsException starting process!");
catch(IOException e1) {
System.err.println( "IOException starting process!");
}

Hi
Do this
String sRegFilePath = " \"E:\\AAA\\dd dd\\dd.xls\" ";

Error processing createOrderBySpecification java.lang.NullPointerException

Hi there,
I am trying to create order in OSM through SoapUI using CreateOrderBySpecification request. SoapUI is throwing error in response. Message is shown below:
It is a simple request with 2 parameters.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <env:Fault>
         <faultcode>env:Server</faultcode>
         <faultstring>Failed to invoke end component oracle.communications.ordermanagement.ws.OrderManagementWSPortImpl (POJO), operation=CreateOrderBySpecification
-> Failed to invoke method
-> java.lang.NullPointerException</faultstring>
         <detail>
            <java:string xmlns:java="java.io">java.lang.RuntimeException: java.lang.NullPointerException
java.lang.NullPointerException</java:string>
         </detail>
      </env:Fault>
   </env:Body>
</env:Envelope>
The Managed Server logs is throwing error as shown below:
####<Mar 9, 2015 2:24:51 PM EDT> <Notice> <Stdout> <osmtest1.test.com> <OSMTEST1_MS1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9a934abad3e137b8:-48d8df11:14bffbf45e8:-8000-00000000000003c7> <1425925491273> <BEA-000000> <<09-Mar-2015 2:24:51,272 EDT PM> <ERROR> <ws.c> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <Error processing createOrderBySpecification>
java.lang.NullPointerException
        at oracle.communications.ordermanagement.ws.k.a(Unknown Source)
        at oracle.communications.ordermanagement.ws.c.a(Unknown Source)
        at oracle.communications.ordermanagement.ws.OrderManagementWSPortImpl.createOrderBySpecification(Unknown Source)
        at oracle.communications.ordermanagement.ws.OrderManagementWSPortImpl.createOrderBySpecification(Unknown Source)
        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 weblogic.wsee.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:112)
        at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:84)
        at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
        at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
        at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
        at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
        at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
        at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
        at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3748)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3714)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2283)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2182)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)>
Any help is appreciated.
Thanks
Archana Sheshachalam

Hey There,
It is resolved. The problem was with the request message for CreateOrderBySpecification. Remove the unwanted tags and keep only the required tags.
Thanks
Archana

Invoke BPEL process using a java client - NullPointerException

Hi, We are trying to call a BPEL process using a java client from our Web Application. For some reason the BPEL engine just logs a NullPointerException and exits.
The same SOAP request when through SOAP UI tool works great.
Any help in resolving this is highly appreciated!
We are getting the below exception--
<2006-09-22 09:40:53,687> <DEBUG> <default.collaxa.cube.ws> SOAPRequestProvider
java.lang.NullPointerException
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:269)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:129)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
-----------------

Hi,
Please ensure that you include the SOAP Header "SOAPAction" in your request. Most importantly, the value for that should be enclosed within double quotes.
For eg;
req.setRequestHeader("SOAPAction", '"process"');

Could not process due to error: java.lang.NullPointerException

Hello,
I' m receiving this error :
Could not process due to error: java.lang.NullPointerException
I checked mesage monitoring , message status was succesfull and there is not error mesage in SXMB_MONI. Why occured this error?
Thanks in advance
Nurhan

Hi Nurhan,
Sateesh query is right one, even I would like to ask you same question.
Now you know that a particular message mapping is throwing error. This is what you need to investigate further
1. In the mapping which is giving error, is there any UDF linked to the target element "MT_FILE_TG_01_013_LIMIT/ADD/GUNPRO".
2. if the there is an UDF check if it contains codes to access ASMA such as filename or directory,Dynamic configuration, or accessing global parameters. If the UDF is doing so then it will give errors in test tab. you have to deactivate or commnet those lines of code and try again.
3. if there are no UDF linked the target field, then check the source xml using internet explorer. I assume one or more mandatory fields are missing in the source which is being mapped onto target MT_FILE_TG_01_013_LIMIT/ADD/GUNPRO. Find that field and populate the values correctly.
4. Then continue following the method I stated in my earlier post.
Finally one more question are you using a BPM or multimapping in your scenario?
regards
Anupam

Error in file cc attemp to process file due java.lang.NullPointerException

there is an error in file communication channel with error information
*Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
.*please post ur views what might be reason for this type of errors.

Thanks all for your valuable and quick responses.
MY concern is that why it created 1 file 3 times.
i checked the ICF that is green.
THe interface works like this
*the idoc is sent from the SAP system.
*and is received by a BPM in XI
BPM sends the file to a file receiver channel.
*Encryption program picks the file and encryption is done
*Again the file is sent by file sender channel to receiver.
the receiver is supposed to get 3 files but it is getting 9 files.
one file 3 times.
Moreover file receiver channel shows error jave lang null pointer
please send in your views so that the problem can be sorted out ........
Thanks.

NullPointerException in processing

Similar Messages

Maybe you are looking for