Gettng Started on AII
hi everyone,
i know the bascis of RFID, how it works, its adv n all.
i also know a bit about SAP ABAP & NetWeaver Devel Studio.
I hav the documentation on SAP AII(Auto Id Infrastructure) from: http://help.sap.com/content/documentation/sbs/docu_sbs_autoid.htm
But i am still all lost. i got R/3, NetWeaver installed on my terminal. wat more do i need? how do i launch AII???
I CANT ACCESS THE service.sap SITES, SO PLEASE DONT SEND ME THOSE LINKS.
IF ANYONE HAS ANY OTHER DOCUMENTATION WHICH IS EASY TO UNDERSTAND AND WHICH GIVES A STEP BY STEP GUIDE TO USING AND UNDERSTANDING SAP AII, please put it up here or mail it to me at:
[email protected] or
[email protected]
i will be extrememly grateful to all of you.
I got the username and passwd 2 access the service.sap sites
Similar Messages
-
Need a FM for gettng starting & ending date based on the settlement period
Hi,
I have to filter a database table based on the settlement period( IDENT3 ) and the field available is of date field. Can anyone give me a function module by which can calculate the starting date and ending date by providing the settlement period ( eg. AM- Monthly, AQ- Quarterly, AJ- Annually, etc ) and date.
Thanx in advance.
Regards,
Sumanth.Hi Sumanth,
Please use the function module 'DATE_CONVERT_TO_FACTORYDATE' to get the start date and end date for the particular factory calender.
For end date:
CORRECT_OPTION +
DATE sy-datum
FACTORY_CALENDAR_ID Aq(quaterly)
For start date:
CORRECT_OPTION -
DATE sy-datum
FACTORY_CALENDAR_ID Aq(quaterly)
According to sy-datum, it will calculate the Extreme interval .
Thanx,
Zenthil. -
hi everyone,
i know the bascis of RFID, how it works, its adv n all.
i also know a bit about SAP ABAP & NetWeaver Devel Studio.
I hav the documentation on SAP AII(Auto Id Infrastructure) from: http://help.sap.com/content/documentation/sbs/docu_sbs_autoid.htm
But i am still all lost. i got R/3, NetWeaver installed on my terminal. wat more do i need? how do i launch AII???
I CANT ACCESS THE service.sap SITES, SO PLEASE DONT SEND ME THOSE LINKS.
IF ANYONE HAS ANY OTHER DOCUMENTATION WHICH IS EASY TO UNDERSTAND AND WHICH GIVES A STEP BY STEP GUIDE TO USING AND UNDERSTANDING SAP AII, please put it up here or mail it to me at:
[email protected] or
[email protected]
i will be extrememly grateful to all of you.Hi Hanoz,
I have the same situation that you had before. I do not have account to get service place. Can you help me to get in there. Please send info in the following address
[email protected]
I will be appriciate your help.
Thanks,
Reed -
Hi all,
I am XI developer, and new in the field of AII
Can any one give me the list of T-code and link for useful document to learn AII(SAP Auto ID Infrastructure)
Thanks & Regards
Diwakar ChaubeHello,
Im new here and i dont know how to post a new question. I really need to know the price of SAP Auto-ID Infrastructure license.
Thank you,
Silvia -
Error in SQLJ..Please guide :(
Hello All,
Am new to SQLJ and am implementing the first practise project from pdf called "<i><b>Gettng Started with Relational Persistence</b></i>".
Am at the step wherein The <i>Data Access Interface has been implemented using SQLJ</i> but am getting these 2 errors at this step:
1. <b>SQLJ: The connecttion "ctx" does not have a Java type</b>.
2. <b>SQLJ: The context type must e defined explicitly</b>.
Please help me resolve these errors.
Awaiting Reply.
Thanks & Warm Regards,
RituHello,
I have implemented the first sample program on Persistence from help.sap.com
As per that, u dont have to add the Dict. project to the enterprise project.
If you are referring to thr same project then:
1. Creation of dictionary project
2. Created a Web Project (with servlet & JSP) & addition of Dic project.
3. Creation of Enterprise Project and addition of the above Web project.
You may also refer to the steps given here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/b8/092492099b7c44b266c3128624076e/frameset.htm -
Converting old 35mm photos to digital
I am looking to purchase a digital photo converter to convert my old 35mm photos onto my Mac. Looking for advice on a good converter or way to go about this task.
usmc
You were probably looking at the
VuPoint Solutions Digital Photo Converter - PS-C500-VP
http://www.vupointsolutions.com/index.asp
I don't know of any converter that is Mac friendly. I can inderstand the appeal of a simple to operate dedicated appliance. Scanning old shoes boxes full of pictures is tedious at best. I've managed to avoid gettng started on this for years with little guilt.
That said, I don't see any real advantage with the converter. Online reviews are not very good anyway. This unit may already be discontinued.
The new line of both Epson and HP photo scanners have come a long way in making archiving a lot easier. The scanning is fast, the Mac software is very good for correctng the scanned image, and I think both companies have an option to scan to iPhoto.
I use an HP scanner which has that option but don't use it. I prefer to scan directly to desktop folders I create. I can organize easier that way, check the scans in Preview and see which ones I want to send to Photoshop first before importing folders into iPhoto. -
Hello,
In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
com.sap.aii.adapter.lib_api.jar
com.ibm.ws.ejb.thinclient_7.0.0.jar
com.ibm.ws.orb_7.0.0.jar
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
com.ibm.ws.runtime.jar
javax.j2ee.jms.jar
The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
Checking dev_server0 file I found the following error.
==============================================================================================
Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure that any
bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than
an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
on.
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
port=2809 vmcid: 0x4942f000 minor code: 3586 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
... 6 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809 vmcid: 0x4942f0
00 minor code: 3586 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 16 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:522)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:180)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 28 more
Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure t
hat any bootstrap address information in the URL is correct and that the target name server is running. Possible causes othe
r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
iguration.
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor co
de: 775 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
... 7 more
Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor code: 775 completed: No
at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 17 more
==============================================================================================
Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
Thank you in advance.
Roger Allué i VallHi Roger,
we also experience the same issue and would be very keen to understand how you resolved this problem.
Many thanks.
Dieter -
Unable to start service 'com.sap.aii.adapter.jms.svc'
Hi people,
After I have successfully deployed the external drivers jdbc/jms drivers on a PI 7.1 system trough JSPM using the com.sap.aii.adapter.lib.sda file but now the com.sap.aii.adapter.jms.svc and the com.sap.aii.adapter.jdbc.svc do not want to start up. When checking the log DefaulTrace log file I found the following error Reported reason: Service com.sap.aii.adapter.jms.svc is not loaded Any ideas on what the problem could be?Hi people,
Thanks for all the ideas. I have followed all the notes and guides to prepare the SDA file ie editing the XML file and adding the JAR files.
The problem was that somewhere along the line the provider.xml file of the old aii_af_jmsproviderlib.sda and the new com.sap.aii.adapter.lib.sda file seeming ot "merged" during my struggles.
The provider.xml file of the SDA which I tried to uploaded had the two reference entries which actually belong to the old aii_af_jmsproviderlib.sda in as well as the correct reference entry. Once I removed these incorrect reference entries the services started up correctly.
I found the error mention above by firstly renaming the DefaultTrace_X.trc file and restarting the JAVA stack. I then stepped through each line of the newly created DefaultTrace_X.trc file from the top down and found the following entries:
1) Cannot resolve component library:sap.com/com.sap.aii.adapter.lib because referenced component Reference strong to library com.sap.aii.messaging.runtime not found#
2) Cannot resolve component service:sap.com/com.sap.aii.adapter.jdbc.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
3) Cannot resolve component service:sap.com/com.sap.aii.adapter.jms.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
In line line 1 I saw that it was referencing the com.sap.aii.messaging.runtime which seemed suspect. Luckily I still had the original SDA file and when comparing it to the uploaded SDA file I found the incorrect entry.
Thanks again for all the help -
Fresh to aii, where can i find technical help on aii ,some starting documen
hi all ,
am new to aii, where can i get some technical document that helps me in aii.
i basically have to read epc data. so given a product i want to read how many units of that product are present at a given location assuming data is already loaded.
please give me some pointersThanks & Regards.,
V.Rangarajan
Edited by: Rangarajan on Oct 7, 2008 7:15 AM -
Hi there,
I'm trying to generate Java Proxies for SAPJCO using the SAP Java Connectivity Builder (JCB). I got it from the NetWeaver 6.20 Release. The tool installs and runs properly but after putting in the connection properties and klicking "next", the application hangs. When activating System output, I get the error shown below.
I already tried to put all jar files contained in the C:\JBuilder5\lib\ext directiry into the classpath (but none of them contains the class mentioned).
Which is the right (standalone) tool for generating Java Proxies for a standalone Java application?
If it is JCB, is there a bug on the version I use (NetWeaver Release 6.20)?
Any help would be apreciated.
C:\JBuilder5>java -Dlog.handler.FileLog=FileHandler,log.txt -Dlog.logger.com=ALL,FileLog -cp lib/ext/aii_basis.jar;lib/e
xt/aii_ifr_core.jar;lib/ext/aii_ifr_jbtool.jar;lib/ext/aii_lcraccess.jar;lib/ext/aii_msg_runtime.jar;lib/ext/aii_proxy_g
en.jar;lib/ext/aii_proxy_rt.jar;lib/ext/aii_util.jar;lib/ext/aii_util_log.jar;lib/ext/lcrclient.jar;lib/ext/logging.jar;
lib/ext/SapIdeHelp.jar;lib/ext/SapIdeJBUtil.jar;lib/ext/SapIdeJspInsight.jar;lib/ext/SapIdeTaglibReflection11.jar;lib/ex
t/SapIdeTracing.jar;lib/ext/SapIdeUtil.jar;lib/ext/SAPJ2EEEngineJBuilderPlugin.jar;lib/ext/sapjco.jar;lib/ext/SAPmdi.jar
;lib/ext/servlet.jar;lib/ext/tc_sec_core.jar com.sap.aii.ifr.tool.jbuilder.JBuilderTool
#0 12:35:37 [main] DEBUG com.sap.aii.util.misc.api.AIIProperties: Initial AIIProperties
com.sap.aii.client = true
#1 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.standalone" from "null" t
o "true"
#2 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.xml.parserFactory" from "
null" to "com.inqmy.lib.jaxp.SAXParserFactoryImpl"
#3 12:35:37 [main] FINE com.sap.aii.util.misc.api.AIIProperties: changed Property "com.sap.aii.xml.transformerFactory" f
rom "null" to "com.inqmy.lib.jaxp.TransformerFactoryImpl"
#4 12:35:46 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.client.SAPNavigationPane: New file is C:\Documents and Setti
ngs\kalkoo1\Desktop\t.jar
#5 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Client : 010
#6 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Logon Name : kalkoo1
#7 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Password : #########
#8 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Language : EN
#9 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for Host name: bgstsapedai01.s
t.behr.de
#10 12:36:08 [AWT-EventQueue-0] FINER com.sap.aii.ifr.upload.client.R3LogonScreen: setting for System number : 20
#11 12:36:08 [AWT-EventQueue-0] INFO com.sap.aii.ifr.upload.client.R3LogonScreen: trying to establish connection
#12 12:36:08 [AWT-EventQueue-0] FINEST com.sap.aii.ifr.util.IdentityCheck: Looking up identity
#13 12:36:08 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.util.IdentityCheck: Results of identity check: isIFRServer: false;
isIFRRMIClient: false; isStandaloneIFR: true
#14 12:36:08 [AWT-EventQueue-0] FINEST com.sap.aii.ifr.util.IdentityCheck: Checking IdentityCheck.isIFRServer. Result: f
alse
#15 12:36:08 [AWT-EventQueue-0] INFO com.sap.aii.ifr.upload.sap.SAPConnection: connecting to system 20 on bgstsapedai01.
st.behr.de via JCo
#16 12:36:09 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.sap.SAPUploadSource: init MDI to System bgstsapedai01.st.be
hr.de (system=20, client=010) (BasisRelease: 620)
#17 12:36:09 [AWT-EventQueue-0] DEBUG com.sap.aii.ifr.upload.UploadBuffer: new UploadBuffer
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: com/sap/aii/ifr/client/editor/Reference
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethod(Unknown Source)
at java.awt.Component.isCoalesceEventsOverriden(Unknown Source)
at java.awt.Component.access$100(Unknown Source)
at java.awt.Component$2.run(Unknown Source)
at java.awt.Component$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Component.checkCoalescing(Unknown Source)
at java.awt.Component.<init>(Unknown Source)
at java.awt.Container.<init>(Unknown Source)
at javax.swing.JComponent.<init>(Unknown Source)
at javax.swing.JTree.<init>(Unknown Source)
at javax.swing.JTree.<init>(Unknown Source)
at com.sap.aii.ifr.navigation.IFRJTree.<init>(IFRJTree.java:84)
at com.sap.aii.ifr.navigation.IFRTreePane.buildPane(IFRTreePane.java:123)
at com.sap.aii.ifr.navigation.IFRTreePane.<init>(IFRTreePane.java:33)
at com.sap.aii.ifr.upload.client.SAPNavigationPane.<init>(SAPNavigationPane.java:43)
at com.sap.aii.ifr.upload.client.SAPBrowser.setIsConnected(SAPBrowser.java:252)
at com.sap.aii.ifr.upload.client.SAPBrowser$ConnectAction.actionPerformed(SAPBrowser.java:594)
at com.sap.aii.ifr.upload.client.SAPBrowser$NextAction.actionPerformed(SAPBrowser.java:536)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)Hi,
>> Error :- java.lang.NoClassDefFoundError: com/sap/aii/security/proxy/KeystoreHelp
1) Can you check the class path you have mentioned is correctly
2) Setting of the Java in your system ( Desk top /Lap top ) check the Proxy settings
3) Re start the J2EE engine in the server
Regards
Agasthuri Doss -
Unable to launch Integeration Builder - Java Web Start - Unexpected Error
Hi there,
I am not able to launch the Integeration builder. The ESR has no problem and is working fine though.
Here is the exception :- com.sap.aii.ibdir.gui.appl.ApplicationImpl
I have tried below options already :
1. Cleared the java cache under - javaws -logviewer
2. Go into administration and inside Directory --> Java Web Start Administration clicked "Restore archives and generate new sign."
Strange part is some of my colleagues here doesnt have any issue while opening the Integeration Builder. In fact I dont have any such issue in QA and PROD environment. The issue is only in DEV environment. Please advice.
AnshulHello,
Usually restoring the archives will help resolve the issue.
If the issue is occurring for just yourself maybe you could check that you are using the correct java version. e.g. for for 7. 1 java version 5
Also please refresh the Java Web Start:
If it's a Windows terminal, select Start - Run - javaws to launch Java Web Start and then clear the cache. File -> preferences ->
advanced -> clear folder button
If you have later versions of Java and doing the
Start -> Run doesn't give you anything, then select Start - Run and type Control and hit Enter. Double-click Java in the list
that displays to view the more up-to-date Java Control Panel. In the General tab, select Settings from the Temporary Internet Files section. Click Delete Files to clear the cache and then log into the Integration Builder again (download will be longer as jars will be cached locally again).
If the problem still remains I would advise to check that the latest patches have been applied for XI_TOOL, and also the other components MESSAGING SAP-XIAFC SAP_XIAF SAP_XIESR SAP_XIGUI
Regards,
Sarah -
hello
I am running an interface RFC2WS sync and recieve this message in the RFC. the message does not get out of the XI and rich the target (WS).
the XI been upgraded lately, and I think this might be the cuase to the problem, becuase the interface been worked before, and still working in PROD environment as is.
what could be the problem and how can I start investigate it to find the problem?
this is what the SAP recieves
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
Thanks
KfirHi Kfir,
just check in RWB, in component monitoring, the status of integration server and adapter engine.......if it is red, then ask your basis guys to remove that error................just check your comm channels, i think your comm channels are in error, if they are just edit them, save and activate them again..........i think then your this issue will be resolved.'
Regards,
Rajeev Gupta -
Exit Code -11114 J2EE Engine doesn't start completely. DESPERATE
XI system - Windows - Oracle - ABAP + Java Stack
We would like to upgrade our J2EE Engine Version however, during the upgrade, there is a phase wherein the J2EE Engine is being started. But, as it is being started, it returns an error and it provides the message Exit Code -11114 and it starts restarts the J2EE Instance automatically over and over again. I've read a forum here that resolved this error. However, the scenario wherein the data source is database_only is not applicable to our case since our data source is already dataSourceConfiguration_r3_roles_db.xml. Furthermore, I've read in one of the logs that indicates that: Critical shutdown was invoked. Reason is: 5 core services have timed out http://adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin. Hope you could help us out! Please help us! This is affecting the business operation since the server 0 doesn't startup completely, thus the java sites are all inaccessible.
Here is one part of the trace.
#1.5#0015C588AED40047000001690000141800044578CA30039C#1202284997468#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/com.sap.aii.af.sdk.rnif.message.listener] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/com.sap.aii.af.sdk.rnif.message.listener.
Exception id: [0015C588AED40047000001670000141800044578CA300130]#
#1.5#0015C588AED400470000016E0000141800044578CA30A0A8#1202284997515#com.sap.engine.services.servlets_jsp.Deploy##com.sap.engine.services.servlets_jsp.Deploy#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application. The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.unBindApp(StopAction.java:92)
at com.sap.engine.services.servlets_jsp.server.container.StopAction.commitStop(StopAction.java:56)
at com.sap.engine.services.servlets_jsp.server.container.WebContainer.commitStop(WebContainer.java:419)
at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:262)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:305)
at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:296)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235)
at com.sap.engine.services.deploy.server.FinishListener.run(FinishListener.java:77)
at com.sap.engine.services.deploy.server.FinishListener.makeOperation(FinishListener.java:57)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startTransactionsLocal(DeployServiceImpl.java:4183)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopMyApplications(DeployCommunicatorImpl.java:214)
at com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame.stop(ServletsAndJspServerFrame.java:235)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
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#0015C588AED40047000001700000141800044578CA30A304#1202284997515#com.sap.engine.services.servlets_jsp.server.container.WebContainer##com.sap.engine.services.servlets_jsp.server.container.WebContainer#######SAPEngine_System_Thread[impl:5]_51##0#0#Error#1#/System/Server#Plain###Cannot lookup and destroy an application context of [sap.com/tclmwebadminclusteradminapp] application.
The error is: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at applications, the whole lookup name is webContainer/applications/sap.com/tclmwebadminclusteradminapp.
Exception id: [0015C588AED400470000016E0000141800044578CA30A0A8]#
#1.5#0015C588AED4005D0000004A0000141800044578CA38DF9E#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_5]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: java.lang.Thread | toString: Thread[SAPEngine_EnquReader,5,main]] with classloader [com.sap.engine.boot.CoreClassLoader@a981ca]#
#1.5#0015C588AED4005D0000004B0000141800044578CA38F484#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_51]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.core.service630.container.ServiceStopper | toString: com.sap.engine.core.service630.container.ServiceStopper@122c960] with classloader [null]#
#1.5#0015C588AED4005D0000004C0000141800044578CA38F5B3#1202284998062#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:5]_71]
Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]d2e636] with classloader [[email protected]5b6@service:log_configurator]#
#1.5#0015C588AED40047000001780000141800044578CA38F6DB#1202284998062#com.sap.engine.core.service630.container.ServiceStopper##com.sap.engine.core.service630.container.ServiceStopper#######SAPEngine_System_Thread[impl:5]_51##0#0#Error##Plain###Service servlet_jsp error java.lang.ThreadDeath during shutdown.#
#1.5#0015C588AED4005D0000004D0000141800044578CA3DA356#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_2]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.jms.WorkerHandlerImpl | toString: com.sap.aii.af.service.jms.WorkerHandlerImpl@81f25] with classloader [[email protected]b87f@service:com.sap.aii.adapter.jms.svc]#
#1.5#0015C588AED4005D0000004E0000141800044578CA3DA528#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_25]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory | toString: [email protected]2222] with classloader [[email protected]74b@common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore]#
#1.5#0015C588AED4005D0000004F0000141800044578CA3DA681#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_29]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.af.service.scheduler.JobBroker$Broker | toString: com.sap.aii.af.service.scheduler.JobBroker$Broker@134d801] with classloader [[email protected]619e@service:com.sap.aii.af.svc]#
#1.5#0015C588AED4005D000000500000141800044578CA3DA79A#1202284998375#com.sap.engine.core.thread.impl3.ThreadManagerImpl##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#4#####Thread[Thread-47,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_Application_Thread[impl:3]_ThreadManager:
Thread[SAPEngine_Application_Thread[impl:3]_32]
Task: com.sap.engine.core.thread.impl3.ActionObject - Processing Task [classname: com.sap.aii.adapter.xi.ms.SLDReader | toString: com.sap.aii.adapter.xi.ms.SLDReader@513bb5] with classloader [[email protected]4ab4@service:com.sap.aii.adapter.xi.svc]#
#1.5#0015C588AED4001900000000000034D800044578FAB55C7D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<super()>#
#1.5#0015C588AED4001900000001000034D800044578FAB58D2D#1202285811437#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
#1.5#0015C588AED4001900000002000034D800044578FAB597E9#1202285811453#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
#1.5#0015C588AED4001900000003000034D800044578FAC784C7#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
#1.5#0015C588AED4001900000004000034D800044578FAC78D1C#1202285812625#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_79##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
#1.5#0015C588AED4000000000016000034D8000445790BF2E967#1202286100703#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Wed Feb 06 16:21:40 CST 2008 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
Service com.sap.aii.af.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.marketplace.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service ejb > hard reference to interface security.
Service com.sap.aii.af.security.service > hard reference to service keystore.
Service ssl > hard reference to service keystore.
Service com.sap.aii.adapter.jms.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service adminadapter > hard reference to service jmx.
Service tcsecsecurestorage~service > hard reference to service keystore.
Service pmi > hard reference to service tcsecdestinations~service.
Service security > hard reference to service com.sap.security.core.ume.service.
Service jms_provider > hard reference to service security.
Service sld > hard reference to service tcsecsecurestorage~service.
Service jmx > hard reference to interface security.
Service rfcengine > hard reference to service ejb.
Service tcsecsaml~service > hard reference to service adminadapter.
Service telnet > hard reference to service shell.
Service com.sap.aii.adapter.jdbc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tclmctcculculservice_sda > hard reference to service jmx.
Service webdynpro > hard reference to interface shell.
Service tcsecvsiservice > hard reference to service tcsecdestinationsservice.
Service tceCATTPingservice > hard reference to interface shell.
Service com.sap.aii.af.ispeak.svc > hard reference to service applocking.
Service tcsecdestinationsservice > hard reference to service tcsecsecurestorageservice.
Service dsr > hard reference to service security.
Service keystore > hard reference to service security.
Service applocking > hard reference to service security.
Service tclmctcculservice_sda > hard reference to service jmx.
Service monitor > hard reference to service jmx.
Service com.sap.security.core.ume.service > service com.sap.security.core.ume.service start method invoked.
Service com.sap.aii.adapter.bc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service com.sap.aii.adapter.rfc.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service tc.monitoring.logviewer > hard reference to service jmx.
Service apptracing > hard reference to service jmx.
Service com.sap.aii.af.ms.svc > hard reference to service com.sap.aii.af.svc.
Service com.sap.aii.af.cpa.svc > hard reference to service sld.
Service shell > hard reference to interface security.
Service tcsecwssecservice > hard reference to service tcsecsecurestorageservice.
Service com.sap.aii.adapter.mail.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service servlet_jsp > hard reference to interface security.
Service com.sap.aii.adapter.file.svc > hard reference to service com.sap.aii.af.cpa.svc.
Service classload > hard reference to service security.
Service basicadmin > hard reference to service jmx.
Service com.sap.aii.adapter.xi.svc > hard reference to service com.sap.aii.af.cpa.svc.
#1.5#0015C588AED4000000000018000034D8000445790BF36AF2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###43 services have timed out.#
#1.5#0015C588AED400000000001A000034D8000445790BF36CBF#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001C000034D8000445790BF36E70#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.marketplace.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000001E000034D8000445790BF3702D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ejb has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000020000034D8000445790BF371D8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.security.service has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000022000034D8000445790BF3737F#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ssl has timed out > hard reference to service keystore.#
#1.5#0015C588AED4000000000024000034D8000445790BF3752A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000026000034D8000445790BF376D2#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service adminadapter has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000028000034D8000445790BF3787A#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsecurestorage~service has timed out > hard reference to service keystore.#
#1.5#0015C588AED400000000002A000034D8000445790BF37ACC#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service pmi has timed out > hard reference to service tcsecdestinations~service.#
#1.5#0015C588AED400000000002C000034D8000445790BF37D4C#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service security has timed out > hard reference to service com.sap.security.core.ume.service.#
#1.5#0015C588AED400000000002E000034D8000445790BF37EF7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jms_provider has timed out > hard reference to service security.#
#1.5#0015C588AED4000000000030000034D8000445790BF380A1#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service sld has timed out > hard reference to service tcsecsecurestorage~service.#
#1.5#0015C588AED4000000000032000034D8000445790BF3824E#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service jmx has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000034000034D8000445790BF383F8#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service rfcengine has timed out > hard reference to service ejb.#
#1.5#0015C588AED4000000000036000034D8000445790BF385A7#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecsaml~service has timed out > hard reference to service adminadapter.#
#1.5#0015C588AED4000000000038000034D8000445790BF38754#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service telnet has timed out > hard reference to service shell.#
#1.5#0015C588AED400000000003A000034D8000445790BF38903#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jdbc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000003C000034D8000445790BF38AB4#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000003E000034D8000445790BF38C5D#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service webdynpro has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000040000034D8000445790BF38E07#1202286100734#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecvsiservice has timed out > hard reference to service tcsecdestinationsservice.#
#1.5#0015C588AED4000000000042000034D8000445790BF38FD6#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tceCATTPingservice has timed out > hard reference to interface shell.#
#1.5#0015C588AED4000000000044000034D8000445790BF3918B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ispeak.svc has timed out > hard reference to service applocking.#
#1.5#0015C588AED4000000000046000034D8000445790BF3938A#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecdestinationsservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000048000034D8000445790BF3953F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service dsr has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004A000034D8000445790BF396EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service keystore has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004C000034D8000445790BF398A2#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service applocking has timed out > hard reference to service security.#
#1.5#0015C588AED400000000004E000034D8000445790BF39B53#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculservice_sda has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000050000034D8000445790BF39CFE#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service monitor has timed out > hard reference to service jmx.#
#1.5#0015C588AED4000000000052000034D8000445790BF39EAB#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.security.core.ume.service has timed out > service com.sap.security.core.ume.service start method invoked.#
#1.5#0015C588AED4000000000054000034D8000445790BF3A068#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.bc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000056000034D8000445790BF3A217#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.rfc.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000058000034D8000445790BF3A3CD#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tc.monitoring.logviewer has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005A000034D8000445790BF3A5EC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service apptracing has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000005C000034D8000445790BF3A7B3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.ms.svc has timed out > hard reference to service com.sap.aii.af.svc.#
#1.5#0015C588AED400000000005E000034D8000445790BF3A967#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.af.cpa.svc has timed out > hard reference to service sld.#
#1.5#0015C588AED4000000000060000034D8000445790BF3AB0C#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service shell has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000062000034D8000445790BF3ACBC#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tcsecwssecservice has timed out > hard reference to service tcsecsecurestorageservice.#
#1.5#0015C588AED4000000000064000034D8000445790BF3AE81#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.mail.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000066000034D8000445790BF3B03B#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service servlet_jsp has timed out > hard reference to interface security.#
#1.5#0015C588AED4000000000068000034D8000445790BF3B2D1#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.file.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED400000000006A000034D8000445790BF3B47F#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service classload has timed out > hard reference to service security.#
#1.5#0015C588AED400000000006C000034D8000445790BF3B628#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service basicadmin has timed out > hard reference to service jmx.#
#1.5#0015C588AED400000000006E000034D8000445790BF3B7D3#1202286100750#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.xi.svc has timed out > hard reference to service com.sap.aii.af.cpa.svc.#
#1.5#0015C588AED4000000000070000034D8000445790BF3BA67#1202286100750#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######Thread[Thread-1,5,main]##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: 5 core services have timed out [adminadapter; security; jmx; com.sap.security.core.ume.service; basicadmin].#Hello Sir,
I am also having the similar prblem after upgrading the AIX 5.3 TL 5 to TL6.
I would really like to know what you did to solve you problem, even though our scenario is a little different. -
J2EE ENGINE Takes a lot of time to start
Hi
Whenever we restart the J2EE ENGINE it takes it about and hour and half to start
We upgraded our R/3 to Unicode , but XI Is still non-unicode ( I dont know its connected )
The defaultrace log when it tries to start is :
#1.5#001125A56002001800000000001080B200041C10571A98A0#1156756413257#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<super()>#
#1.5#001125A56002001800000001001080B200041C10571AAF4B#1156756413263#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupConfigurationService().after<applicationServiceContext = ctx;>#
#1.5#001125A56002001800000002001080B200041C10571AB8C9#1156756413266#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###mobile_setupGenerationdoes exist.#
#1.5#001125A56002001800000003001080B200041C10571C8F33#1156756413386#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<7>#
#1.5#001125A56002001800000004001080B200041C10571C937D#1156756413387#tcmobileadmincoresetup##tcmobileadmincoresetup#######SAPEngine_System_Thread[impl:5]_75##0#0#Error##Plain###SetupApplicationServiceFrame.after<8>#
#1.5#001125A56002002F00000000001080B200041C1057CBF48D#1156756424881#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Starting Configuration util service...#
#1.5#001125A56002003000000000001080B200041C1057CC1A7C#1156756424890#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###entering CulServiceFrame.start#
#1.5#001125A56002003000000001001080B200041C1057CCC060#1156756424933#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###deploymentListener registered#
#1.5#001125A56002002F00000002001080B200041C1057EC01D6#1156756426981#com.sap.tc.lm.ctc.confs.service.ServiceFrame##com.sap.tc.lm.ctc.confs.service.ServiceFrame#######SAPEngine_System_Thread[impl:5]_65##0#0#Info#1#/System/Server/CTC#Plain###Configuration util service started successfully.#
#1.5#001125A56002003000000002001080B200041C10580B287A#1156756429023#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Enum = com.sap.engine.frame.core.load.res.CompoundEnumeration@21b85f86#
#1.5#001125A56002003000000003001080B200041C10580DB59B#1156756429190#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Inputstream CTC start file java.io.ByteArrayInputStream@b3d5e4e#
#1.5#001125A56002003000000004001080B200041C105811AAC8#1156756429449#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info##Plain###Object = com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup@3105de41#
#1.5#001125A56002003000000005001080B200041C10581C597B#1156756430149#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...ConfigManagerProvider registered#
#1.5#001125A56002003000000007001080B200041C10581C6353#1156756430152#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...TextSourceProvider registered#
#1.5#001125A56002003000000009001080B200041C10581C7EC4#1156756430159#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...JavaServiceProvider registered#
#1.5#001125A5600200300000000B001080B200041C10581D03F2#1156756430193#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...AbapConfigurationProvider registered#
#1.5#001125A5600200300000000D001080B200041C10581F48CA#1156756430342#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###registerApplication2MBeanServer(sc)...#
#1.5#001125A5600200300000000F001080B200041C105820069C#1156756430390#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULExportService registered#
#1.5#001125A56002003000000011001080B200041C105820358F#1156756430402#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULImportService registered#
#1.5#001125A56002003000000013001080B200041C10582078A5#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###...CULAdminService registered#
#1.5#001125A56002003000000015001080B200041C10582079B2#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup##com.sap.tc.lm.ctc.cul.j2eeengine.CULStartup#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CTC System started...#
#1.5#001125A56002003000000017001080B200041C1058207ACA#1156756430420#com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame##com.sap.tc.lm.ctc.cul.j2eeengine.CULServiceFrame#######SAPEngine_System_Thread[impl:5]_59##0#0#Info#1#/System/Server/CTC#Plain###CUL Service started...#
#1.5#001125A56002003B00000000001080B200041C10587E30E2#1156756436562#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]_70##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://terudbxid1:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xid.terudbxid1), due to: HTTP 503: Service Unavailable#
#1.5#001125A56002003B00000001001080B200041C10587F353A#1156756436628#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]_70##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: Service Unavailable#
#1.5#001125A56002003D00000000001080B200041C105899F3CB#1156756438381#com.sap.aii.af.service.alerting.Alert##com.sap.aii.af.service.alerting.Alert.getMDTUrl()#######SAPEngine_System_Thread[impl:5]_12##0#0#Error##Plain###HTTP response code: 503 Service Unavailable#
#1.5#001125A56002004600000000001080B200041C1058C7442C#1156756441351#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.invoke()#J2EE_GUEST#1#####File2XI[:MQ_Service:File_Gad_Sender_CONV]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel File_Gad_Sender_CONV: No suitable sender agreement found#
#1.5#001125A56002004800000000001080B200041C105A99226B#1156756471882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000001001080B200041C105C62E7E3#1156756501882#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000002001080B200041C105E2CC5CB#1156756531889#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000003001080B200041C105FF68EAB#1156756561890#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000004001080B200041C1061C06873#1156756591896#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 1 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000005001080B200041C10638A7936#1156756621916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000006001080B200041C1065543E74#1156756651916#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000007001080B200041C10671E0481#1156756681917#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)#######SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002000000000015001080B200041C106814AC14#1156756698082#com.sap.engine.frame.Environment##com.sap.engine.frame.Environment#######Thread[Thread-1,5,main]##0#0#Error#1#/System#Plain###Mon Aug 28 11:18:18 GMT+02:00 2006 Thread[Thread-1] initiated a full thread dump due to: Timed out services:
Service com.sap.aii.adapter.jms.svc > service com.sap.aii.adapter.jms.svc start method invoked.
#1.5#001125A56002000000000017001080B200041C106814B974#1156756698085#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###1 services have timed out.#
#1.5#001125A56002000000000019001080B200041C106814BB1F#1156756698086#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service com.sap.aii.adapter.jms.svc has timed out > service com.sap.aii.adapter.jms.svc start method invoked.#
#1.5#001125A56002004800000008001080B200041C1068E7CA65#1156756711918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
#1.5#001125A56002004800000009001080B200041C106AB18FB6#1156756741918#com.sap.aii.af.service.jms.WorkerHandlerImpl##com.sap.aii.af.service.jms.WorkerHandlerImpl.setAction(int)######2c8f20e0367611db8f53001125a56002#SAPEngine_System_Thread[impl:5]_21##0#0#Error##Plain###Setting action 2 failed for module com.sap.aii.af.service.jms.WorkerJMSReceiver with actionTimeout = 30 secs#
any Ideas ?
Thx,Shaihi shai,
"but XI Is still non-unicode"
as far as i know XI can be installed only on a unicode Web AS.
plz check that once again
cheers
satish -
Hi Team,
Created a simple file2file scenarion successfully. Unable to pick the file from Sender directory to Receiver Directory.
Checked from monitoring the Communication Channel.
Error message shown for sender communication channel as below:
Communication Channel Status Short Log Control Data Party Service Adapter Type Direction
sen_cc Red ball Processing Errors In the Last 30 Seconds Manually kanchuf2f_sen_bs File Sender
Line 1 / 1
By selecting the sender communication channel "sen_cc", below is the node details given.
Processing Details for Cluster Node Server 0 1_54295
Type
Time Stamp Message ID Explanation
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Retry interval started. Length: 60.0 seconds
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
By clicking on the first Message ID, The message says successful upto some point and give error says JCO COMMUNICATION FAILURE and RFC issue.
Below is the information provided in detail.
Audit Log for Message: 45f841be-a421-43bd-235a-c7ad19b0aec8
Time Stamp Status Description
03.12.2008 08:20:00 Success Channel sen_cc: Send binary file "f:\xi_file\sender\f2fmap.xml". Size 210 with QoS BE
03.12.2008 08:20:00 Success Application attempting to send an XI message synchronously using connection AFW.
03.12.2008 08:20:00 Success Trying to put the message into the call queue.
03.12.2008 08:20:00 Success Message successfully put into the queue.
03.12.2008 08:20:00 Success The message was successfully retrieved from the call queue.
03.12.2008 08:20:00 Success The message status set to DLNG.
03.12.2008 08:20:01 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error Transmitting the message using connection http://sitaserv33:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error The message status set to FAIL.
03.12.2008 08:20:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
Page 1 / 2
I think this could be the problem with some basis related settings, I am not sure what exactly the issue with.
Any idea what exactly the error is talking about please do help me in finding the solution to thresolve this error message.
Regards,
Venkat Ramana KHi Carlos,
Thank you for the quick information.
Followed all the steps and also basis person from onsite restarted the XI server.
Now, I am able to log onto XI with the login Id but, when I give Tr Code: SXMB_IFR, unable to open the browser that shows Integration Builder.
Getting the error message.
*500 Internal Server Error*
*SAP J2EE Engine/7.00*
**Exception**
*An internal error occurred. Contact you XI administrator*
*Unable to read configuration data (ExchangeProfile/aii.properties)*
Error Details, Error History, Build Info, Generic Application Info
Regards,
Venkat Ramana K
Maybe you are looking for
-
DEtailed scheduling planning board - scalling of objects in the charts
Hi, I am wandering if there is a possibility of changing the scale in the graphical planning board in APO PPDS, eg. in the resource chart. in the way that I could change the scale just for a certain period of time or one object. for example: the plan
-
MacBook Pro (13") Trackpad
Hi. When I bought my MacBoo Pro 3 weeks ago, the trackpad was working fine. But, it doesn't let me do a double-click if i use the bottom left corner. It does eventually work if I keep on clicking it, but it feels as if its sticking? Does anyone know
-
Displaying Row and Column Numbers
I see through other research on Oracle SQL Developer that I should be able to display the row and column numbers on version 1.5.4, but I don't see where to go to turn this on. Suggestions?
-
I can not open 9.0 Distiller on my G5 running OSX 10.4.11. It unexpectedly quits everytime. Adobe support is taking a very long time to figure out. Any suggestions?
-
Where can I find a download for the latest version of Firefox 4. I'll upgrade when Norton has an updated version for Ff5.