Process Stuck at Start Activity
I have a BPM process (11g) that is being called by another application as a service. Whenever my process is invoked, it just gets stuck at the Start activity. The invoking application is passing some parameters to the process. Has anyone run into this problem before where the process is stuck at the Start activity? If so, what kind of things should I look at to debug this issue?
Thanks.
-muktech
So can you see the instance of the process created in Enterprise Manager? If so, does it get stuck in Running mode or does it resolve to Completed or Faulted ever?
If it completes, you should be able to see the data and look at your BPM flow with the path the instance took highlighted. If it faults, then you will most likely not be able to see any of this data because you won't be able to open the instance.
Make sure that Enterprise Manager is configured in Developer mode, not Production. This way it will save the XML data at every stage of the process.
Similar Messages
-
Why does a BPM Process fail at the Start Activity?
Hello All,
We're currently working on a Dev environement (WLS 10.3), where we're experiencing issues with BPM Processes that fail at the start node. The error observed is a "Null Pointer Exception" despite there definteily being parameters passed into the process.
I've observed the trace in the EM after invoking the process and notice that the process fails as soon as it enters the start activity.
One of the possible explanations could be an out of memory issue. Has anyone experienced this before?
BPM : SOA Suite 11g.
Thank you.If you have memory - issues, you should look at the Weblogic-logs.
-
Process must contain a start activity with no 'in' transitions.
382: Design Validation generated 1 warning(s). You may save invalid definitions but they should not be used in running process.
352: Process must contain a start activity with no 'in' transitions.
What it mean ???Does the activity that you have marked as a 'Start' node have any in transitions?
Does the little green arrow appear on the icon to show that the property has been set correctly?
Matt
WorkflowFAQ.com - the ONLY independent resource for Oracle Workflow development
Alpha review chapters from my book "Developing With Oracle Workflow" are available via my website http://www.workflowfaq.com
Have you read the blog at http://www.workflowfaq.com/blog ?
WorkflowFAQ support forum: http://forum.workflowfaq.com -
I am having problems launching the standalone version of Lightroom 6 after I have gone through the install and activation process? Lightroom starts to open but "hangs" before any photos in the catalgue are displayed. I have contacted the chat support twice but they have not been able to fix the problem.
I went through the activation process yesterday and shut down my PC when I went to bed last evening. When I got up this morning and turned my PC on and then started Lightrom 6 (I upgraded from version 5) it started to launch but then just hung and became "not responsive". I I then uninstalled and then reinstalled the product today but the same thing happened. What is weird is that when I install from the standalone file I downloaded when I purchased the upgrade it looks like it's downloading the software again over the Internet? I have been having these problems for the last four or five days. I have contacted the chat support folks twice and they were able to get it working but whatever they did did not last as the problem reappeared again once the PC was shut down and then started up again.
-
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 PMHi 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 -
Calling BPM Sub Process from another BPM Process - Stuck at Sub Process
Hi
JDeveloper 11.1.1.6, BPM 11.1.1.6, WLS 10.3.6
I am trying to Call a BPM Process from another BPM Process. Both the processes are defined in the same BPM Project.
Both the Processes have 'None' Start and End activities.
The 'Parent Process' has a 'Call Activity' which calls the 'Sub Process'.
The Sub process takes a parameter of payload object as input and returns output (also same payload object)
I have passed the payload object from parent to sub process in the 'Data Associations'.
The Start and End activities in the sub process also have the data associations set where I am passing the payload object from parent process to child process.
When I run the process and see the Enterprise Manager console - Audit Trail / Flow tabs,
Flow Tab - The progress of the process is showing only till the Calling of the sub process in the Parent Process. It does not show the Sub Process.
Audit Trail Tab - Shows that the Sub Process is called but has not reached to the End of the Sub process.
The audit trail does not have links to the sub process activities.
I cannot see any exceptions as well in the audit trail.
How can I find out why the process is stuck? Or what is going on in the process?
Please let me know if my explanation is not clear?
Thanks for any help
Regards
SameerThanks for replying.
I have another Sub Process with Start and End events as Message Events and used Send Task and Receive Task (Implementation : Process Call) in the Main process to invoke the sub process asynchronously.
Then, the Sub Process is shown in the 'Flow Trace' as child of the main process.
In this particular one, I used 'Call Activity' to call the sub process.
So the Audit trail is showing the sub process as a child.
But what I was trying to say is that the audit trail did not have links to the entries in the 'Event' column (in Enterprice manager - instance window). (like Instance entered activity, Instance left activity etc).
I was intending to use these links to see the payload information and try to debug if there is any problem with the code.
The actual problem I was trying to say in the post is that, even after the user responds to the activity (User Task - Approval) in the Sub process,
the audit trail is not proceeding further.
In the Sub process definition, after the user task, there is End with none implementation.
Hope it is clear now.
Thanks and Regards
Sameer -
Cannot install Windows 7 Pro; gets stuck on "Starting Windows" screen
I have read dozens of posts on this topic but none has helped yet.
My system has Windows 8 with UEFI. I want to install Windows 7 Pro on another partition. I have turned off Secure Boot in the UEFI/BIOS. When I try to install Windows 7 Pro from a DVD it shows "windows is loading files" and then gets stuck on "Starting Windows"
for ever. This happens even when no USB peripherals are attached.
I have already wasted many days on this. I hope someone can help.
Thanks!Hi friends of the internet
I have been reading several forums regarding the issue of installing windows 7 (64 bit) to a computer that have had windows 8 installed previously or just a GPT formatted disk.
My Case:
Windows version installed: Windows 7 Professional N with Service Pack 1 (x64) or Windows 7 Professional (x64)
Computer used: Samsung laptop
Model Code: NP53U4C-A02SE
See the specks here:
http://www.samsung.com/dk/consumer/computer-peripherals/notebook/notebook/NP535U4C-A02SE-spec
Create a USB install disk that not freezes at ”starting windows” screen:
First I followed this great guide (Thanks Daniel):
http://
hodgin.ca/2012/10/02/creating-a-uefibios-windows-7-usb-and-installing-to-gpt-partitions/
STOP AFTER STEP 13!
1. Open a command line in administrator mode
2. run DISKPART
3. type LIST DISK
4. Look for the disk number that represents your USB drive
5. type SELECT DISK # where # represents the number of your USB drive. Get this right or you will wipe a different drive out.
6. type CLEAN
7. type CREATE PARTITION PRIMARY
8. type SELECT PARTITION 1
9. type ACTIVE
10. type FORMAT fs=fat32 quick
11. type assign
12. The drive should now be formatted and marked as active and fat32. Do not format the drive as NTFS or you will only be able to boot into the installer in BIOS mode.
13. Now you will need to copy the contents of the windows 7 install dvd to the USB with a regular copy paste from windows explorer.
Here comes a very weird hack... I do not know why it works, but I think it is all about flash drive data structure. I did these steps on a win 7 prof. computer.
(Let’s assume it’s drive E:)
Make a copy of your e:\efi\microsoft folder to e.g. your desktop.
Delete the e:\efi folder
Copy the \efi folder from a windows 8 installation disk (I used Windows 8 (x64) Professional) to the e:\efi folder. Sorry I cannot provide this for you.
Here comes the weird part. Then delete e:\efi\microsoft you just copied from the win 8 installation disk.
Copy the \microsoft folder form the desktop to e:\efi\microsoft
Resume the guide from step 18.:
http://
hodgin.ca/2012/10/02/creating-a-uefibios-windows-7-usb-and-installing-to-gpt-partitions/
18. Insert the USB in the machine and turn it on and boot into the UEFI/BIOS loader and check for boot options. On the ASUS Zenbook it detected two boot options on the USB drive. One was UEFI and one was regular BIOS. I made the
UEFI option the first choice and restarted the machine.
My bios setup was:
Secure Boot = Disable
OS Mode Selection = CSM and UEFI OS
Boot Device Priority = I made the UEFI option the first choice and restarted the machine.
The installation should start normal.
E.g. See this guide:
www.sevenforums.com/tutorials/186875-uefi-unified-extensible-firmware-interface-install-windows-7-a.html
What I did was:
Select custom installation (Advanced).
Click Drive options (Advanced).
Delete all partitions (this might not be needed). When I did not delete all partitions I was asked every time after the install, during start up by the windows boot manager to select ether win 8 or win 7.
Click new (DO NOT make Changes in the size of the disk), apply, see NOTE!
Edit the Primary partition as you want it e.g. divide it to more partitions.
Select the one you will install windows on and do a normal install.
I do not make changes in the Bios after install. The Boot priority is automatic set to “Windows boot manager”. If I change the boot mode back to OS Mode Selection = UEFI OS, the computer will freeze at the “starting windows” screen again.
All this worked for me, good luck. There might be more to it, but this is a start.
By the way, the start up time for a MBT install was 37 s. And for the GPT it was 49 s.
Remember if we stand on each other’s shoulders we will reach higher
J.
NOTE: Here the installation program should create three partitions automatically!
Partition 1 - System - The EFI System partition that contains the NTLDR, HAL, Boot.txt, and other files that are needed to boot the system, such as drivers.
Partition 2 - MSR - The Microsoft Reserved (MSR) partition that reserves space on each disk drive for subsequent use by operating system software.
Partition 3 - Primary - Where Windows is to be installed to.
If this isn’t the cast you are not installing in UEIF mode. To check for this (thanks again Daniel):
If you need to find out if you have booted into BIOS mode or UEFI mode when the installer starts you can press SHIFT+F10 when the welcome installer shows up to open a cmd prompt. from here you will likely be at X:\Sources. Type cd .. to
go back a dir and move into \Windows\Panther\
Then type notepad setupact.log
Within this file do a ctrl+f and search for
Callback_BootEnvironmentDetect: Detected boot environment:
It should either say BIOS or UEFI.
To check if your disk is in the GPT format.
Open the command prompt.
Type: DISKPART
Type: List Disk
See for the star (*) in the GPT column -
BPM Process not getting started
Dear All,
I have created a BPM Process, and have attached a webservice with the start event.After deploying the Process DC I am getting my start webservice in my wsnavigator. When I am executing the start webservice I am getting the following error.
Web service returned error. Fault Code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Process start has been triggered."
But my process is inprogress but not getting proceeded to the next step , it is stuck in start itself.
how can i make my webservice work?
Regards,
ShamilaHi Shamila,
To me this looks like a configuration issue. You can trouble shoot it this way
First try to check if the web services is up and running
Second check your configuration, for this, in NWA Manage Processes application get all the 'failed processes'
-check if your in-progress process is listed here-
- if so then open the Error log tab for the process in the details section in Manage Process
- See the logs listed here; generally the last log will tell you if your configuration is correct or not
-if you figure out that the configuration isn't done or is improper then correct the same in provider systems and/or application communication configuration
- then once this is done, re-query the failed process and use the "Recover" option
Regards,
Harsha -
WebLogic Server: 10.3.5.0 - Managed stuck in STARTING
Hi all. I have a managed stuck in STARTING for like 2 hours, the logs are these:
####<Sep 25, 2013 1:40:42 PM CEST> <Info> <JMS> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109242585> <BEA-040321> <JMSServer "JMSServer-SPSS-1" is resuming.>
####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496786> <BEA-282003> <The messaging kernel JMSServer-SPSS-1 will use up to 536,870,912 bytes of memory before paging begins>
####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496795> <BEA-282001> <The messaging kernel JMSServer-SPSS-1 is beginning recovery of its persistent state>
It's creating a log ot .TMP files under the managed tmp. There is a way to speed up or elude this "recover"? Please note that I'm quite noob with Weblogic.
Thanks!Hi,
Add -Dweblogic.StdoutDebugEnabled flag while starting the managed server and then post the verbose error message in your next post
For setting the flag follow the below steps
If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
JAVA_OPTIONS="-Dweblogic.StdoutDebugEnabled=true ${JAVA_OPTIONS}"
echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
If your using Windows box and not using node manager to start the managed server,add the below line startManagedWebLogic.cmd file
set JAVA_OPTIONS=-Dweblogic.StdoutDebugEnabled=true %JAVA_OPTIONS%
echo JAVA_OPTIONS=%JAVA_OPTIONS%
If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>. MS1 >>>> server start >>>> Arguments :-Dweblogic.StdoutDebugEnabled=true
Regards,
Fabian -
I downloaded the iOS 7 but it would not install so i tethered it to my computer the connect to iTunes screen came on the iPhone. But after a few minutes, it crashed and iTunes told me it was in recovery mode and that it will be restored to factory setting. After that process, it is stuck on the activation part and will not activate. Please advise!
All of Apple's servers...including the activation servers are pretty much flooded with users like you doing the same thing. Be patient and keep at it...or wait till the traffic to them has decreased and then try again. Coming back to it tomorrow (if that's a viable option for you) will likely increase your chances of not having issues.
-
Received an authorized unlock code from apple/AT&T for my off-contract 3GS (8GB). Per the “Completing Authorized iPhone Unlock” instructions, I connected to iTunes to back up and restore so my iPhone can be unlocked! But after the restore my iPhone is stuck at the activation screen, it will not activate saying “Your iPhone cannot be activated because the activation server is temporarily unavailable”. I tried this again and again for countless times, no way! I have my old AT&T simcard and other carrier’s simcard. Both will not help. Please help me to activate and start using my phone.
Hello,
I got like the same problem, last days I get message to restore my iPhone, so I did it yesterday and it work very well. In the afternoon I saw that at top in the left corner show invaild sim card or so (only knew the german version). so I restore it again but now it won`t activate after I enter SIM-PIN and it accept it, it shows "No Service".
Anybody can help? My Carrier is o2 Germany.
Thanks! -
Service reads data but Bpel process does not start
i have a very simple project. I have db2(as400) adapter and it reads data, i will receive data, transfom and send to oracle database. I deployed the project successfuly but when instance start i see the service reads the data but bpel process does not start and and there is no error. At the flow chart there is only readAS400 partnerlink, there is no bpelprocess. In the partnerlink i am usin polling, i read the data's with 1 and update to 2. It reads but dont update to 2.
In deploy step and when instance starts there is no errors. But when i am deploying i get a warning but i dont know it's related with this situation.
(Warning: property "activationAgent.readAs400.className" may not be understood by BPEL component BPELProcessEqpType - it will likely be ignored.)
Do you have any suggestion ? Thanks in advance.check the recovery console, the bpel process possibly is going into manual recovery,
Another thing you might wanna try is using checkpoints in your process..
also, instead of getting the db adapter to instantiate the process, try a simpler process just to see if the db adapter is working or not..
A normal process, which you manually instantiate from em console, with the db adapter in it after the recevie activity
Edited by: AshishSharma on Jun 24, 2010 5:48 PM -
Node server0 stuck on starting framework exitcode = -11113
Hello experts, <br><br>
After installation, i'm able to start the SAP Server via mmc, the ABAP part is up and running, but my Java stack stucks on starting framework.<br><br>
Bellow, the "tail" of my developer trace<br><br>
612 com.microsoft.sqlserver.jdbc.Parameter$GetTypeDefinitionOp::setTypeDefinition (833 bytes)
613 com.microsoft.sqlserver.jdbc.DTV$SendByRPCOp::<init> (50 bytes)
614 java.lang.Math::min (12 bytes)
615 ! com.sap.engine.services.deploy.server.DeployServiceImpl::getApplicationInfo (2773 bytes)
616 com.microsoft.sqlserver.jdbc.SQLServerStatement::getNextResult (155 bytes)
617 com.sap.engine.lib.xml.parser.handlers.NamespaceEntry::levelDown (98 bytes)
618 s com.sap.engine.lib.util.cache.Cache::getByKey (145 bytes)<br><br>
Tue Apr 19 16:37:34 2011<br><br>
619 com.microsoft.sqlserver.jdbc.SQLServerResultSet::close (105 bytes)
620 java.io.ObjectInputStream$HandleTable::markDependency (171 bytes)
621 ! com.sap.engine.lib.xml.parser.XMLParser::scanEndTag (638 bytes)
622 java.lang.ref.ReferenceQueue::reallyPoll (58 bytes)
623 java.io.ObjectInputStream::checkResolve (48 bytes)
624 com.sap.sql.jdbc.basic.BasicResultSet::getString (11 bytes)
625 com.sap.engine.core.configuration.impl.cache.ConfigurationCache::releaseConfiguration (112 bytes)
626 com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement::buildServerCursorExecParams (202 bytes)
627 com.sap.tc.logging.LogController::<init> (206 bytes)
628 com.sap.engine.lib.xml.parser.handlers.NamespaceHandler::levelUp (44 bytes)
629 com.sap.engine.services.deploy.ReferenceObject::encode (294 bytes)
630 com.microsoft.sqlserver.jdbc.TDSReader::readLong (56 bytes)
631 com.microsoft.sqlserver.jdbc.SQLServerStatement$1NextResult::onRetStatus (28 bytes)
632 com.microsoft.sqlserver.jdbc.StreamDone::hasUpdateCount (1544 bytes)
633 com.microsoft.sqlserver.jdbc.SQLServerStatement$1NextResult::onDone (213 bytes)
634 java.lang.Math::max (11 bytes)
635 s com.sap.tc.logging.LogController::addLogNormalInt (139 bytes)
636 ! com.sap.engine.core.configuration.impl.cache.AccessController::getAccess (156 bytes)
637 com.sap.sql.jdbc.basic.BasicPreparedStatement::setInt (12 bytes)
Tue Apr 19 16:37:35 2011
638 com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer$FetchBufferTokenHandler::onDone (24 bytes)
639 com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader::scanByte (17 bytes)
640 com.sap.engine.lib.xml.dom.AttrImpl::<init> (66 bytes)
641 com.microsoft.sqlserver.jdbc.TDSWriter::writeLong (211 bytes)
642 com.sap.engine.core.configuration.impl.PersistentDataInputStream::read (29 bytes)
643 com.sap.engine.lib.xml.parser.XMLParser::scanComment (377 bytes)
644 com.sap.engine.lib.xml.dom.DOMDocHandler1::getChd (115 bytes)
645 com.sap.engine.services.deploy.server.DUtils::getApplicationID (82 bytes)
646 com.sap.engine.services.deploy.server.DUtils::replaceForbiddenSymbols (122 bytes)
647 com.sap.engine.services.deploy.server.DeployServiceImpl::listApplications (53 bytes)
648 com.sap.engine.services.deploy.server.ReferenceResolver::getApplicationForComponent (59 bytes)
14.575: [GC 14.575: [ParNew: 181723K->20372K(245760K), 0.0281875 secs] 181723K->20372K(2015232K), 0.0282645 secs]
649 ! java.lang.ref.Reference$ReferenceHandler::run (108 bytes)
650 com.sap.engine.services.deploy.server.DUtils::getWord (84 bytes)
651 com.sap.engine.services.deploy.server.DeployServiceImpl::addApplicationInfo (227 bytes)
652 com.sap.engine.services.deploy.server.DUtils::isAlreadyAdded (45 bytes)
653 java.util.StringTokenizer::nextToken (92 bytes)
654 com.sap.engine.services.deploy.ReferenceObject::setCompositeName (269 bytes)
Tue Apr 19 16:37:36 2011
655 ! sun.security.provider.PolicyFile::getPermissions (250 bytes)
656 com.sap.engine.core.classload.impl0.LoadContextImpl::dfsCycleDetection (74 bytes)
657 java.util.ArrayList::RangeCheck (48 bytes)
658 s com.sap.engine.core.classload.impl0.LoadContextImpl::getReferences (23 bytes)
37% com.sap.engine.core.classload.impl0.LoadContextImpl::dfsCycleDetection @ 38 (74 bytes)
659 java.util.ArrayList::get (12 bytes)
660 java.util.ArrayList::remove (70 bytes)
661 java.util.ArrayList::ensureCapacity (68 bytes)
662 com.sap.engine.core.service630.container.LoadContextWrapper::checkName (54 bytes)
663 ! com.sap.engine.services.deploy.server.DeployServiceImpl::initializeApplications (1194 bytes)
664 s! java.net.URLStreamHandler::getHostAddress (54 bytes)
665 com.sap.engine.services.deploy.server.DeploymentInfo::getApplicationLoaderFiles (212 bytes)
666 ! java.util.zip.Inflater::reset (52 bytes)
667 s java.util.Vector::remove (82 bytes)
668 s! com.sap.engine.services.log_configurator.admin.LogConfigurator::adjustConfiguration (4223 bytes)
669 ! sun.nio.cs.SingleByteEncoder::encodeArrayLoop (356 bytes)
670* java.lang.System::currentTimeMillis (0 bytes)
38% ! sun.security.provider.SeedGenerator$ThreadedSeedGenerator::run @ 114 (243 bytes)
671 com.sap.engine.lib.xml.dom.DocumentImpl::updateDTDForAllElements0 (67 bytes)
672 com.sap.engine.lib.xml.dom.ElementImpl::setAttributeNodeNS (187 bytes)
673 java.util.LinkedList$ListItr::hasNext (20 bytes)
Tue Apr 19 16:37:37 2011
16.325: [GC 16.325: [ParNew: 184212K->21281K(245760K), 0.0204138 secs] 184212K->21281K(2015232K), 0.0204826 secs]
674 ! java.util.zip.Inflater::inflate (74 bytes)
675 sun.misc.URLClassPath$JarLoader::getResource (48 bytes)
676 java.io.ObjectOutputStream$BlockDataOutputStream::getUTFLength (124 bytes)
677 java.io.ObjectOutputStream$BlockDataOutputStream::writeBytes (144 bytes)
678 sun.misc.SoftCache::processQueue (47 bytes)
679 java.io.ObjectStreamClass::writeNonProxy (148 bytes)
680* java.lang.System::identityHashCode (0 bytes)
681 java.io.ObjectOutputStream$HandleTable::lookup (56 bytes)
682 java.io.ObjectOutputStream::clear (15 bytes)
683 com.sap.engine.lib.util.HashMapObjectObject::contains (60 bytes)
684 java.io.ObjectOutputStream::writeSerialData (135 bytes)
685 ! java.io.ObjectOutputStream::writeObject0 (551 bytes)
686 javax.naming.NameImpl::stringifyComp (604 bytes)
687 java.io.ObjectOutputStream$HandleTable::insert (39 bytes)
688 javax.naming.NameImpl::equals (126 bytes)
689 s java.util.Vector::elementAt (49 bytes)
690* java.security.AccessController::doPrivileged (0 bytes)
691 java.io.ObjectOutputStream$BlockDataOutputStream::writeShort (47 bytes)
39% java.security.Security::getProviderProperty @ 15 (60 bytes)
692 java.lang.String::charAt (33 bytes)
693 java.io.ObjectOutputStream$BlockDataOutputStream::writeUTF (46 bytes)
694 java.util.Vector$1::hasMoreElements (20 bytes)
695 com.sap.engine.frame.core.load.res.JarsResource::getClassInfo (43 bytes)
696 com.sap.engine.boot.FrameClassLoader::loadClass (7 bytes)
40% com.sap.tc.logging.LogController$Regarders::put @ 54 (104 bytes)
697 s! java.security.Security::reloadProviders (144 bytes)
41% javax.crypto.SunJCE_b::a @ 17 (55 bytes)
698 com.sap.engine.lib.xml.parser.XMLParser::<init> (403 bytes)
42% iaik.utils.Base64InputStream::read @ 134 (360 bytes)
699 javax.crypto.SunJCE_b::a (55 bytes)
43% iaik.utils.Base64InputStream::read @ 18 (360 bytes)
700 iaik.security.cipher.j::a (643 bytes)
44% iaik.utils.Base64InputStream::read @ 55 (360 bytes)
701 iaik.utils.Base64InputStream::read (360 bytes)
702 ! com.sap.engine.lib.xml.parser.URLLoaderBase::pop (58 bytes)
703 com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader::getLastChar (6 bytes)
704 ! javax.crypto.SunJCE_b::c (271 bytes)
705 iaik.utils.CryptoUtils::squashBytesToInts (84 bytes)
706 com.sap.engine.services.dbpool.deploy.XMLUtils::processAliasesXML (377 bytes)
707 sun.reflect.AccessorGenerator::emitBoxingContantPoolEntries (1417 bytes)
708 java.security.Security::getEngineClassName (216 bytes)
45% java.util.Arrays::fill @ 10 (28 bytes)
709 java.io.ObjectOutputStream$HandleTable::<init> (45 bytes)
710 java.text.MessageFormat::applyPattern (360 bytes)
711 com.sap.engine.core.classload.impl0.LoaderInfo::getReferencesTo (83 bytes)
712 com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault::switchType (212 bytes)
713 com.sap.engine.core.configuration.impl.ValueEntry::<init> (40 bytes)
714 com.sap.engine.boot.ControlledCryptographyProvider::useProvider (50 bytes)
Tue Apr 19 16:37:38 2011
715 com.sap.tc.logging.LogController$Regarders::put (104 bytes)
46% com.sap.sql.sqlparser.SQLLexer::yy_unpack_cmap @ 32 (57 bytes)
716 sun.text.resources.DateFormatZoneData::handleGetObject (92 bytes)
717 s java.security.Security::insertProviderAt (92 bytes)
718 com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement::doExecutePreparedStatement (207 bytes)
719 com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer::<init> (42 bytes)
720 com.microsoft.sqlserver.jdbc.SQLServerConnection::setMaxFieldSize (49 bytes)
721 com.microsoft.sqlserver.jdbc.SQLServerConnection::setMaxRows (39 bytes)
722 com.sap.sql.jdbc.mss.MssInetJdbcObjectFactory::createResultSet (11 bytes)
723 com.sap.sql.jdbc.basic.BasicResultSet::close (10 bytes)
724 com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement::buildPreparedStrings (87 bytes)
725 com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd::doExecute (10 bytes)
726 ! com.sap.engine.core.configuration.impl.utilities.ConfigurationPath::getConfigurationPathInternal (154 bytes)
727 com.microsoft.sqlserver.jdbc.TDSTokenHandler::onRetStatus (13 bytes)
728 ! java.io.ObjectOutputStream::writeObject0 (551 bytes)
729 ! com.sap.engine.services.jndi.implclient.ClientContext::checkOperation (140 bytes)
730 s java.io.ByteArrayOutputStream::write (117 bytes)
731 com.sap.engine.lib.xml.parser.helpers.CharArray::trim (104 bytes)
732 javax.naming.NameImpl::extractComp (761 bytes)
733 java.io.ObjectOutputStream::writeOrdinaryObject (68 bytes)
734 java.lang.Long::appendTo (47 bytes)
Tue Apr 19 16:37:39 2011
735 java.io.ObjectInputStream::readHandle (110 bytes)
736 ! java.lang.StringCoding::encode (127 bytes)
737 java.lang.String::<init> (52 bytes)
738 com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl::existsValue (9 bytes)
739 com.sap.engine.frame.core.load.res.JarsResource::getClassInfo (43 bytes)
47% sun.misc.URLClassPath::getResource @ 3 (38 bytes)
740 com.sap.engine.lib.xml.parser.XMLParser::scanContent (197 bytes)
741 com.sap.engine.frame.core.load.NegativeCache::contains (69 bytes)
Tue Apr 19 16:37:40 2011
742 s! java.util.Hashtable::clone (99 bytes)
743 ! java.util.zip.ZipFile$ZipFileInputStream::close (63 bytes)
744 s java.util.Vector::size (5 bytes)
48% ! com.sap.engine.lib.xml.parser.readers.EncodedDataReader::readData @ 127 (175 bytes)
745 sun.misc.URLClassPath::getResource (38 bytes)
746 ! com.sap.engine.lib.xml.parser.readers.EncodedDataReader::readData (175 bytes)
747 ! com.sap.engine.lib.xml.parser.XMLParser::scanAttList (644 bytes)
748 com.sap.engine.lib.xml.dom.CharacterDataImpl::setParent (6 bytes)
749 com.sap.engine.lib.xml.dom.NodeImpl::ensureChildren (61 bytes)
750 com.sap.engine.lib.xml.dom.NodeImpl::checkChildNodeType (84 bytes)
751 com.sap.security.core.role.imp.xml.XMLServiceAction::addPermission (100 bytes)
752 ! com.sap.engine.lib.xml.dom.DOMDocHandler1::addAttribute (179 bytes)
753 com.sap.engine.lib.xml.dom.ElementImpl::init (99 bytes)
754 java.nio.ByteBuffer::<init> (45 bytes)
755 com.sap.engine.lib.xml.dom.Base::getChildNodes (4 bytes)
756 com.sap.engine.lib.xml.dom.NodeListImplEmpty::getLength (2 bytes)
757 java.util.HashMap::put (113 bytes)
758* java.util.zip.Inflater::inflateBytes (0 bytes)
759 ! java.util.zip.InflaterInputStream::read (127 bytes)
Tue Apr 19 16:37:49 2011
760 ! com.sap.engine.frame.core.load.ResourceLoader::loadClass (171 bytes)
761 sun.misc.URLClassPath$JarLoader::getResource (48 bytes)
762 ! java.io.ObjectStreamClass::lookup (236 bytes)
763 com.sap.engine.services.jndi.implclient.Schema::init (85 bytes)
764 java.io.ObjectOutputStream$HandleTable::assign (52 bytes)
765 ! com.sap.engine.lib.xml.parser.XMLParser::scanAttList (644 bytes)
766 com.sap.engine.lib.xml.dom.AttrImpl::getNodeType (2 bytes)
767 com.sap.engine.lib.xml.dom.Base::getParentNode (2 bytes)
768 com.sap.engine.lib.xml.dom.DOMDocHandler1::startElementStart (95 bytes)
769 com.sap.engine.lib.xml.parser.helpers.DefaultAttributesHandler::clearDefaultCheck (43 bytes)
Tue Apr 19 16:37:50 2011
770 com.sap.engine.lib.xml.parser.helpers.CharArray::set (47 bytes)
771 com.sap.sql.sqlparser.SQLKeywords::hash (169 bytes)
772 iaik.security.md.Md5::engineReset (59 bytes)
773 ! com.sap.sql.jdbc.direct.DirectPreparedStatement::setLong (196 bytes)
774* java.lang.reflect.Array::newArray (0 bytes)
775 iaik.security.md.SHA::engineReset (67 bytes)
49% com.sap.tc.logging.ListFormatter::escape @ 31 (153 bytes)
776 java.lang.StackTraceElement::toString (140 bytes)
777 com.sap.tc.logging.ListFormatter::escape (153 bytes)
778 ! com.sap.engine.core.classload.impl0.LoaderInfo::loadClassByReference (57 bytes)
779 ! java.net.URL::<init> (531 bytes)<br><br>
[Thr 6788] JLaunchIExitJava: exit hook is called (rc = -11113)<br>
[Thr 6788] **********************************************************************<br>
ERROR => The Java VM terminated with a non-zero exit code.<br>
Please see SAP Note 943602 , section 'J2EE Engine exit codes'<br>
for additional information and trouble shooting.<br>
**********************************************************************<br>
[Thr 6788] JLaunchCloseProgram: good bye (exitcode = -11113)<br>
<br><br>
Could anybody help? I have already checked the note mentioned above, but got no sucess.
Edited by: egamer on Apr 19, 2011 9:52 PMI have also found this at my std.server0.out:
Core service security failed. J2EE Engine cannot be started.
com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:194)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:80)
at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)
at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)
at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)
at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:147)
... 5 more
com.sap.engine.services.security.exceptions.SecurityServiceException: Unexpected exception:
at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:194)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)
Caused by: com.sap.engine.services.security.exceptions.BaseSecurityException: No active userstore is set.
at com.sap.engine.services.security.server.UserStoreFactoryImpl.getActiveUserStore(UserStoreFactoryImpl.java:80)
at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.update(LoginModuleHelperImpl.java:405)
at com.sap.engine.services.security.server.jaas.LoginModuleHelperImpl.<init>(LoginModuleHelperImpl.java:84)
at com.sap.engine.services.security.server.SecurityContextImpl.<init>(SecurityContextImpl.java:58)
at com.sap.engine.services.security.SecurityServerFrame.start(SecurityServerFrame.java:147)
... 5 more
[Framework -> criticalShutdown] Core service security failed. J2EE Engine cannot be started.
Apr 19, 2011 4:39:32 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_27] Fatal: Critical shutdown was invoked. Reason is: Core service security failed. J2EE Engine cannot be started.
781 ! java.util.zip.ZipFile$ZipFileInputStream::close (63 bytes) -
Managed server is stuck in STARTING
Hi All,
I have managed severs on weblogic consol.
These servers are linked to the windows services on my prodcution server.
to start and stop the managed servers we used to simply restart the respective services on the production server.
Now the situation is - two managed servers are stuck in STARTING state though i restarted my windiws services several tims?
Please advice ASAP as its a production enviroment issue.. Thanks
Mahendrasame thing in our case but little different.
i have a domain with four different clusters where two instances per cluster and those instances reside on two separate machines. All these instances are under NM control with -Xnohup switch on the serverstart tab.
the problem i have is, when we have a weekly reboot on the two windows servers, one particular cluster instances always in 'STARTING' state. As you can see below the .out log will have the following content and nothing else. EVen for a day or two the server sits on 'STARTING' state with no additional logging in .out file.
At this stage it gets ugly to bring the instances back to normal. We can't kill the instances so we had to use process explorer to kill it. As nodemanager restarts the instance immediately after killed the isntances we had to stop NM.
again start NM and start repeating the steps untill the instances back up to normal. This is not good.
not sure what else we can do. any kind of help is appreciated..thanks
<Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Starting WebLogic server with command line: D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\bin\java -Dweblogic.Name=System_Managed01 -Dbea.home=D:\bea -Djava.security.policy=D:\bea\weblogic92\server\lib\weblogic.policy -Dweblogic.management.server=http://rchz3105.mckesson.com:7510 -Djava.library.path=D:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\bea\WEBLOG~1\server\native\win\x64;D:\bea\WEBLOG~1\server\bin;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\jre\bin;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\bin;D:\bea\WEBLOG~1\server\native\win\x64\oci920_8;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\ZANTAZ\EAS Client\; -Djava.class.path=D:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\bea\weblogic92\domains\SupplyManager\lib\xercesImpl.jar;D:\bea\weblogic92\domains\SupplyManager\lib\yuicompressor-2.4.2.jar;D:\bea\jrockit-jdk1.5.0_24-R28.1.0-4.0.1\lib\tools.jar;D:\bea\weblogic92\domains\SupplyManager\lib\ojdbc14_10.2.0.4.jar;D:\bea\weblogic92\server\lib\weblogic.jar;D:\bea\weblogic92\domains\SupplyManager\lib\customlogger2.jar;D:\Program Files\wily\WebAppSupport.jar -Dweblogic.system.BootIdentityFile=D:\bea\weblogic92\domains\SupplyManager\servers\System_Managed01\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xgc:gencon -Xms1024m -Xmx1024m -XXcompressedRefs:enable=false -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,disk=true,repository=D:/bea/weblogic92/domains/SupplyManager/jfr,maxage=5m,maxchunksize=10m -XX:StartFlightRecording=filename=system.jfr -XlargePages -XX:+HeapDumpOnCtrlBreak -XX:+HeapDumpOnOutOfMemoryError -Xnohup -Xverbose:gc,gcpause,codegen,opt,codegc -XverboseLog:D:\wls_logs\servers\System\gc.txt -XverboseTimeStamp -Dweblogic.TracingEnabled=true -javaagent:"D:\Program Files\wily\Agent.jar" -Dcom.wily.introscope.agentProfile="D:\Program Files\wily\IntroscopeAgent.profile" -Dcom.wily.introscope.agent.agentName="system-managed01" -XX:+UnlockDiagnosticVMOptions -XX:MaxClassBlockMemory=100M weblogic.Server >
<Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Working directory is "D:\bea\weblogic92\domains\SupplyManager">
<Oct 19, 2012 11:01:41 AM> <Info> <NodeManager> <Server output log file is "D:\bea\weblogic92\domains\SupplyManager\servers\System_Managed01\logs\System_Managed01.out"> -
Hello,
I'm new to NetWeaver BMP and in SAP in general. I've downloaded and installed the following Trial Version:
[SAP NetWeaver Composition Environment 7.2 Trial Version|http://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/a0a6bd7b-3dfc-2c10-eb95-aae0f777d4ab]
I have already managed to get a workflow running with two human activities, that's no problem. But as soon as I include an automated Activity, the process get's stuck at that point, when the webservice should be called.
My BPM process looks like that:
[View my designed process|http://floriankalisch.de/pics/process.png]
The webservice I want to use:
[The external webservice|http://www.thomas-bayer.com/axis2/services/BLZService?wsdl]
I imported the web service from remote location and assigned the interface to the automated activity.
The mappings should be ok.
The 'Process Visualisation' (stuck at the automated activity):
[Stuck at automated Activity|http://floriankalisch.de/pics/stuck.png]
Could some one give me a hint? Any help is appreciated
Thanks in advance
Florian
Edited by: devandmore on Jan 26, 2011 8:39 PMHi Florian,
I see the following in the error stack trace
"Log entry 8
com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Configuration not found for application: demo.sap.com/bp_retrieve_bank,serviceRefId:bp_retrieve_bank_demo.sap.combp_retrieve_bankBPMcomponent_c3170c61-9da4-4da4-9209-4508677ac60f_WS. Please check the configuration details from the NWA. You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed.
com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:334)
... (22 more)
You need to configure the service groups /destinations in NWA(Netweaver Administrator) while using the automated activities.
logon to NWA ->SOA Management->Application and comminication scenario->Application communication.
Under this you can find your process DC and then goto consumed services tab and configure the WSDL
Regards, Anil
Maybe you are looking for
-
OBIEE 11g agents are failed to connect to Essbase
OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase. User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Ess
-
How can I sort photos on iPads, I have several models and the order is different on every one.
We use iPads as photo albums. I have several model iPads and the photo order is different on Avery one. How do I get them to sort in the order I want, preferably alphabetically.
-
When I go to my email account through Safari, I cannot see all of my messages. It says there are 34 but I can only see 26. However, at the bottom right the arrows to go to the next screen are not highlighted? I also cannot scroll any further dow
-
How do I turn off faces recognition in iphoto
how do I turn off faces recognition in iphoto? I mean forever!!
-
Trying to create the login sample portlet.
Hi; Ok, I did the following: 1. Created a portal domain on my system. (But it was not a choice in later parts so did not use it.) 2. Created a new portal application and added a portal web project to it - http://e-docs.bea.com/workshop/docs81/doc/en/