AS java Components/Services in CE 7.2
Dear All
I have CE 7.2 quality on windows up and running fine.what my concern is when I see in SAP MMC ->AS Java Components ,600+ components/services are stopped,I can start them manually but they are not coming up automatically when I reboot the server.
To name a few :::
sap.com/VisualComposerRuntimeServiceEar
sap.com/bi~bikit
sap.com/bialvtestapps
Whereas on CE 7.2 Develpment server I see 100+ services stopped,Why there's difference between CE dev and CE QA..We are going to implement SOA so i assume services not starting auto could create a problem in the future.
Please let me know if anybody has any idea on this.
Thanks
I think it is normal, some service is started on demand.
Similar Messages
-
My task - my company has several legacy PowerBuilder applications that access a variety of Sybase and MS SQL databases. Rather than re-inventing the wheel by re-writing these applications in Java, we would like to enable these applications to call java components (EJBs) that will provide new functionality. I would need a piece of software called CSXtend (from www.cynergysystems.com) to allow PowerBuilder to call a web service. However, I am not sure how to expose my business functions (EJBs) as web services on the iPlanet 6.0 App server. Thanks for all previous responses! Any additional info would be greatly appreciated! Mike
I have used Glue (http://www.themindelectric.com/products/glue/glue.html) to expose some of our stuff as Web Services. I recently found this on serverside. It's pretty good.
http://www.theserverside.com/resources/article.jsp?l=Systinet-web-services-part-1
I believe that the middleware they use can be plugged into IPlanet. There is also an article in the knowledge base on the IPlanet site.
Jon -
Stack file that is generated does not contain any java components
We are in process of upgrading our ecc6.0 system with ehp4. The enhancement is stuck up in configuration phase for JAVA. Though we have configured Java in solution manager the stack file that is generated does not contain any java components and so the installation is stuck up. Kindly request you to advice us on this issue .
Attached is the 'Trouble Ticket Report', PREPARE_JSPM_QUEUE_CSZ_01.LOG, and SMSDXML_EA4_20100623144541.375.txt
++++
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: EA4
Hostname...........: wipro
Install directory..: e:/usr/sap/EA4
Upgrade directory..: F:\EHPI\java
Database...........: Oracle
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
More information can be found in the log file F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
++++++
PREPARE_JSPM_QUEUE_CSZ_01.LOG>>
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter inputFile=EHPComponents.xml
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml has finished.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/28 09:21:23.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/28 09:21:24.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.781.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
++++++++++++++++++++++
[stack xml data: version=1.0]
[SPAM_CVERS]
ST-PI 2005_1_7000006
LSOFE 600 0015
SAP_AP 700 0015
SAP_BASIS 701 0003
SAP_ABA 701 0003
SAP_BW 701 0003
PI_BASIS 701 0003
PLMWUI 700 0002
SAP_APPL 604 0002
EA-APPL 604 0002
SAP_BS_FND 701 0002
EA-IPPE 404 0002
WEBCUIF 700 0002
INSURANCE 604 0002
FI-CA 604 0002
ERECRUIT 604 0002
ECC-DIMP 604 0002
EA-DFPS 604 0002
IS-UT 604 0002
IS-H 604 0003
EA-RETAIL 604 0002
EA-FINSERV 604 0002
IS-OIL 604 0002
IS-PRA 604 0002
IS-M 604 0002
SEM-BW 604 0002
FINBASIS 604 0002
FI-CAX 604 0002
EA-GLTRADE 604 0002
IS-CWM 604 0002
EA-PS 604 0002
IS-PS-CA 604 0002
EA-HR 604 0005
SAP_HR 604 0005
ECC-SE 604 0002
[PRDVERS]
01200314690900000432SAP ERP ENHANCE PACKAGE EHP2 FOR SAP ERP 6.0 sap.com EHP2 FOR SAP ERP 6.0 -00000000000000
01200314690900000463SAP ERP ENHANCE PACKAGE EHP4 FOR SAP ERP 6.0 sap.com EHP4 FOR SAP ERP 6.0 -00000000000000
01200615320900001296 sap.com +00000000000000
01200615320900001469SAP ERP ENHANCE PACKAGE EHP3 FOR SAP ERP 6.0 sap.com EHP3 FOR SAP ERP 6.0 -00000000000000
01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01 +00000000000000
[SWFEATURE]
1 01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0: SAP ECC Server
19 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Discrete Ind. & Mill Products
20 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Media
21 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Utilities/Waste&Recycl./Telco
23 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Leasing/Contract A/R & A/P
24 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Retail
25 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Global Trade
26 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Supply Chain Mgmt
30 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Central Applications
31 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Strategic Enterprise Mgmt
33 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Human Capital Management
37 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas
38 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Catch Weight Management
42 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Public Sector Accounting
43 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Insurance
44 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Hospital
45 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ECC Server VPack successor
46 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: ERecruiting
47 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense & Public Security
48 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Services
55 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas with Utilities
56 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense
59 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: PLM Core
69 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: EAM config control
9 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ESA ECC-SE
++++++++++++++++Though we have configured Java in solution manager the stack file that is generated does not contain any java components
You will probably need to update Solution Manager first with a number of corrections so you can get a correctly generated stack file. Depending on your ST400 version in Solution Manager apply collective corrections from "Note 1461849 - MOpz: Collective corrections 24" or "Note 1452118 - MOpz: Collective Corrections 23". They generally deal with these kind of stack file issues.
Nelis -
Deploy java components error in NW7.4 installation
Hi Experts,
I am installing NW 7.4, i have done all the pre-installation steps but i am getting error at deploy java components.
please find the log. please help me in this it is very urgent. I need your experience.
An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MaxDB > SAP Systems > Optional Standalone Units > Process Orchestration > Standard System > Process Integration and Orchestration Package( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jce.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jsse.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_smime.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_ssl.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host PO --port 50004' aborts with return code 104. Error message is 'Component:BI_UDI ( sap.com) Status:Aborted Description:. SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP.
Regards,
Patan Thavaheer.Hi manu,
Please find the error log.
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [31] seconds. Will timeout in [14,368] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [48] seconds. Will timeout in [14,351] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Deployment of session ID [21] finished with status [Error] +++. [[ deployerId=1 ]] [[#3: 340.111 sec]] [
===== Summary - Deploy Result - Start =====
Type | Status : Count
> SCA(s)
- [Aborted] : [80]
> SDA(s)
- [Success] : [80]
- [Admitted] : [1189]
Type | Status : Id
> SCA(s)
- [Aborted] : name: 'BI_UDI', vendor: 'sap.com', name: 'COMP_BUILDT', vendor: 'sap.com', name: 'CU-BASE-JAVA', vendor: 'sap.com', name: 'CU-BASE-WD', vendor: 'sap.com', name: 'DATA-MAPPING', vendor: 'sap.com', name: 'ECM-CORE', vendor: 'sap.com', name: 'ESCONF_BUILDT', vendor: 'sap.com', name: 'ESMP_BUILDT', vendor: 'sap.com', name: 'LM-TOOLS', vendor: 'sap.com', name: 'MMR_SERVER', vendor: 'sap.com', name: 'MOIN_BUILDT', vendor: 'sap.com', name: 'NWTEC', vendor: 'sap.com', name: 'EP-BASIS', vendor: 'sap.com', name: 'SERVICE-COMP', vendor: 'sap.com', name: 'SWLIFECYCL', vendor: 'sap.com', name: 'UKMS_JAVA', vendor: 'sap.com', name: 'KM-KW_JIKS', vendor: 'sap.com', name: 'INTG_VIS', vendor: 'sap.com', name: 'SAP_XIADMIN', vendor: 'sap.com', name: 'SAP_XITOOL', vendor: 'sap.com', name: 'PI-SCP-EXT', vendor: 'sap.com', name: 'PI-SCP-BUILDT', vendor: 'sap.com', name: 'BPEM-CORE', vendor: 'sap.com', name: 'BPEM-FACADE', vendor: 'sap.com', name: 'BPEM-COLLAB', vendor: 'sap.com', name: 'BPEM-BASE', vendor: 'sap.com', name: 'BPEM-BUILDT', vendor: 'sap.com', name: 'BPEM-CONTENT', vendor: 'sap.com', name: 'BPEM-HIM', vendor: 'sap.com', name: 'BPEM-MM', vendor: 'sap.com', name: 'BPEM-MON', vendor: 'sap.com', name: 'BPEM-PP', vendor: 'sap.com', name: 'BPEM-WDUI', vendor: 'sap.com', name: 'BPEM-CUUI', vendor: 'sap.com', name: 'BRMS-BASE', vendor: 'sap.com', name: 'BRMS-BUILDT', vendor: 'sap.com', name: 'BRMS-CORE', vendor: 'sap.com', name: 'BRMS-FACADE', vendor: 'sap.com', name: 'BRMS-WDUI', vendor: 'sap.com', name: 'BRMS-MON', vendor: 'sap.com', name: 'FP-INFRA', vendor: 'sap.com', name: 'CU-BASE-WD-EXT', vendor: 'sap.com', name: 'TM-WLUI', vendor: 'sap.com', name: 'BPEM-ACC', vendor: 'sap.com', name: 'CAF-MF', vendor: 'sap.com', name: 'CAF-UI', vendor: 'sap.com', name: 'COLLAB-ADP', vendor: 'sap.com', name: 'CAF', vendor: 'sap.com', name: 'BI-BASE-S', vendor: 'sap.com', name: 'BI-BASE-B', vendor: 'sap.com', name: 'BI-BASE-E', vendor: 'sap.com', name: 'SEA-CORE', vendor: 'sap.com', name: 'SEA-FACADE', vendor: 'sap.com', name: 'SEA-UI', vendor: 'sap.com', name: 'BI-WDEXT', vendor: 'sap.com', name: 'CU-WD4VC-ADPT', vendor: 'sap.com', name: 'ECM-APPS', vendor: 'sap.com', name: 'ECM-STORE', vendor: 'sap.com', name: 'EP-ADMIN', vendor: 'sap.com', name: 'EP_BUILDT', vendor: 'sap.com', name: 'EP-CONNECTIVITY', vendor: 'sap.com', name: 'EP-MODELING', vendor: 'sap.com', name: 'EP-RUNTIME', vendor: 'sap.com', name: 'UWLJWF', vendor: 'sap.com', name: 'VCFREESTYLEKIT', vendor: 'sap.com', name: 'VCCORERT', vendor: 'sap.com', name: 'VCBASE', vendor: 'sap.com', name: 'VCKITBI', vendor: 'sap.com', name: 'VCFRAMEWORK', vendor: 'sap.com', name: 'VTP_BUILDT', vendor: 'sap.com', name: 'WDEXTENSIONS', vendor: 'sap.com', name: 'WD-FLEX', vendor: 'sap.com', name: 'ECM-ADMIN', vendor: 'sap.com', name: 'ECM-JEE-COMP', vendor: 'sap.com', name: 'SAP_XIESR', vendor: 'sap.com', name: 'SAP_XIGUILIB', vendor: 'sap.com', name: 'XI_CNT_SAP_BASIS', vendor: 'sap.com', name: 'INTG_VIS_DCJ', vendor: 'sap.com', name: 'SAP_XIAF', vendor: 'sap.com', name: 'SOAMON', vendor: 'sap.com',
> SDA(s)
- [Success] : name: 'com.sap.ip.bi.sdk.dac.connector.odbodll', vendor: 'sap.com', name: 'com.sap.glx.mapping.lib', vendor: 'sap.com', name: 'com.sap.glx.common.rt.lib', vendor: 'sap.com', name: 'tc~lm~ctc~confs~service_sda', vendor: 'sap.com', name: 'bi~mmr~dictionary', vendor: 'sap.com', name: 'bi~mmr~deployer', vendor: 'sap.com', name: 'com.sap.portal.pcm.indexingservice', vendor: 'sap.com', name: 'com.sap.netweaver.rtmf.server', vendor: 'sap.com', name: 'tc~rtmf~service', vendor: 'sap.com', name: 'com.sap.aii.sca.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.sca.maas.svc', vendor: 'sap.com', name: 'tc~bpem~eventlog~ddic', vendor: 'sap.com', name: 'com.sap.glx.base.lib', vendor: 'sap.com', name: 'com.sap.glx.container.dbschema', vendor: 'sap.com', name: 'com.sap.glx.rrhandlermanager.svc', vendor: 'sap.com', name: 'com.sap.glx.repository.handler.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc', vendor: 'sap.com', name: 'com.sap.glx.contextcontainer.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc.facade', vendor: 'sap.com', name: 'tc~bpem~index~ddic', vendor: 'sap.com', name: 'tc~bpem~base~svc', vendor: 'sap.com', name: 'com.sap.glx.repository.dbschema', vendor: 'sap.com', name: 'tc~bpem~bl~lib', vendor: 'sap.com', name: 'tc~bpem~base~type~plib', vendor: 'sap.com', name: 'com.sap.glx.repository.ifc', vendor: 'sap.com', name: 'com.sap.glx.repository.svc', vendor: 'sap.com', name: 'tc~bpem~base~lib', vendor: 'sap.com', name: 'tc~bpem~tm~ddic', vendor: 'sap.com', name: 'tc~bpem~shared~lib', vendor: 'sap.com', name: 'tc~brms~engine~lib', vendor: 'sap.com', name: 'tc~brms~ws~svc', vendor: 'sap.com', name: 'tc~brms~repository~svc', vendor: 'sap.com', name: 'tc~brms~io~plib', vendor: 'sap.com', name: 'tc~brms~acl~plib', vendor: 'sap.com', name: 'tc~brms~ddic', vendor: 'sap.com', name: 'tc~brms~wdui~plib', vendor: 'sap.com', name: 'caf~um~relgroups~ddic', vendor: 'sap.com', name: 'tc~esi~sea~schema~ddic', vendor: 'sap.com', name: 'tc~esi~sea~service', vendor: 'sap.com', name: 'tc~esi~sea~api~lib', vendor: 'sap.com', name: 'com.sap.portal.healthChecks', vendor: 'sap.com', name: 'com.sap.portal.fpn.migration.fpnmigrationlib', vendor: 'sap.com', name: 'com.sap.portal.landscape.config', vendor: 'sap.com', name: 'tc~pp~gpal~deploylistener', vendor: 'sap.com', name: 'com.sap.portal.fpn.service', vendor: 'sap.com', name: 'com.sap.portal.smart.smartsrv', vendor: 'sap.com', name: 'com.sap.obn.migration.obnmigrationlib', vendor: 'sap.com', name: 'tc~kmc~bc.uwl~api', vendor: 'sap.com', name: 'devserver_lib', vendor: 'sap.com', name: 'vc_ds_service', vendor: 'sap.com', name: 'vc_generation', vendor: 'sap.com', name: 'ds_repository', vendor: 'sap.com', name: 'ds_environment', vendor: 'sap.com', name: 'visualcomposer_server_api', vendor: 'sap.com', name: 'SAPMetamodelFW', vendor: 'sap.com', name: 'SAPBuildPluginHandler', vendor: 'sap.com', name: 'tc~ecm~svc~deploy', vendor: 'sap.com', name: 'com.sap.aii.adapter.rfc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.svc', vendor: 'sap.com', name: 'com.sap.aii.af.maas.lib', vendor: 'sap.com', name: 'com.sap.aii.af.ifc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.lib', vendor: 'sap.com', name: 'com.sap.aii.adapter.jdbc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.bc.svc', vendor: 'sap.com', name: 'com.sap.aii.af.int.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.af.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.mapping.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.file.svc', vendor: 'sap.com', name: 'com.sap.aii.af.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.dbs', vendor: 'sap.com', name: 'com.sap.aii.adapter.mail.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ws.cxf.lib', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.http.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.jms.svc', vendor: 'sap.com', name: 'com.sap.aii.af.axis.lib', vendor: 'sap.com',
- [Admitted] : name: 'com.sap.ip.bi.sdk.monitoring', vendor: 'sap.com', name: 'bi~sdk~resultset', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checks', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checko', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla.x', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.jdbc', vendor: 'sap.com', name: 'tc~bi~sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.ds', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.fields', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.java', vendor: 'sap.com', name: 'bi~sdk~core', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sys', vendor: 'sap.com', name: 'bi~sdk~query', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sync', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkx', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.odbo', vendor: 'sap.com', name: 'sc~bi_udi', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.sapq', vendor: 'sap.com', name: 'sc~comp_buildt', vendor: 'sap.com', name: 'sc~cu-base-java', vendor: 'sap.com', name: 'tc~cu~base~java~ear', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd~ps', vendor: 'sap.com', name: 'tc~cu~base~wd~core', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd', vendor: 'sap.com', name: 'sc~cu-base-wd', vendor: 'sap.com', name: 'tc~cu~base~wd~intapi', vendor: 'sap.com', name: 'tc~cu~base~wd~utils', vendor: 'sap.com', name: 'tc~cu~base~wd~contract~ps', vendor: 'sap.com', name: 'sc~data-mapping', vendor: 'sap.com', name: 'tc~ecm~core', vendor: 'sap.com', name: 'sc~ecm-core', vendor: 'sap.com', name: 'tc~ecm', vendor: 'sap.com', name: 'sc~esconf_buildt', vendor: 'sap.com', name: 'sc~esmp_buildt', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~taskplnr', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~processviewer', vendor: 'sap.com', name: 'tc~lm~itsam~lmr~app', vendor: 'sap.com', name: 'tc~bcf~prov~ddic', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~initialsetuptables', vendor: 'sap.com', name: 'tc~lm~itsam~ui~ctc~wd', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~master', vendor: 'sap.com', name: 'tc~lm~aci~engine~sapctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~engine~ddic', vendor: 'sap.com', name: 'tc~slm~ui_maintain', vendor: 'sap.com', name: 'tc~archtech~browser_ume', vendor: 'sap.com', name: 'tc~slm~ui_jnet', vendor: 'sap.com', name: 'tc~lm~ctc~itsam~kpi', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~defaultui', vendor: 'sap.com', name: 'tc~bcf~ws~ddic', vendor: 'sap.com', name: 'tc~lm~aci~vpm~wsproxy~sap', vendor: 'sap.com', name: 'tc~bcf~prov~wd', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~compif', vendor: 'sap.com', name: 'tc~bcf~lib~ear', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sys~overview~xi~wd', vendor: 'sap.com', name: 'tc~lm~aci~virtual~vmware~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~resource', vendor: 'sap.com', name: 'tc~bcf_xi~ear', vendor: 'sap.com', name: 'tc~archtech~sbook_wd', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~other_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~aclog', vendor: 'sap.com', name: 'tc~bcf~prov~ear', vendor: 'sap.com', name: 'tc~sec~sanity~jmx~sda', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~locator', vendor: 'sap.com', name: 'tc~slm~ui_review', vendor: 'sap.com', name: 'tc~lm~aci~engine~csm~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~utils', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~xmlui', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~sldregisterapp', vendor: 'sap.com', name: 'sc~lm-tools', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~services', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~vpm', vendor: 'sap.com', name: 'tc~lm~ctc~confs~startup_app', vendor: 'sap.com', name: 'tc~lm~itsam~ui~overview~panel~interface', vendor: 'sap.com', name: 'tc~lm~itsam~ui~avail~panel', vendor: 'sap.com', name: 'tc~bcf~ws~ear', vendor: 'sap.com', name: 'tc~slm~ui_slm', vendor: 'sap.com', name: 'tc~lm~itsam~ui~thresholds~wd', vendor: 'sap.com', name: 'tc~lm~ctc~ccl~rep~hist~ddic', vendor: 'sap.com', name: 'tc~lm~aci~engine~archconfig', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sysinfo', vendor: 'sap.com', name: 'tc~lm~aci~engine~hstctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~spc~config_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~types', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~overview', vendor: 'sap.com', name: 'tc~slm~ui_navigation', vendor: 'sap.com', name: 'tc~archtech~sbook_init_j2ee', vendor: 'sap.com', name: 'tc~bcf~prov~ddic~content', vendor: 'sap.com', name: 'tc~sld~destsvc_dic', vendor: 'sap.com', name: 'tc~bizc~ws~ear', vendor: 'sap.com', name: 'tc~archtech~browser', vendor: 'sap.com', name: 'tc~archtech~sbook_j2ee', vendor: 'sap.com', name: 'tc~sec~sanity~wd', vendor: 'sap.com', name: 'tc~lm~itsam~ui~nwso~cfg~db', vendor: 'sap.com', name: 'tc~lm~itsam~ui~perf~panel', vendor: 'sap.com', name: 'tc~archtech~browser~dbschema', vendor: 'sap.com', name: 'tc~bcf~transport~ddic', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~acenable', vendor: 'sap.com', name: 'tc~lm~nzdm~crr~ui', vendor: 'sap.com', name: 'bi~mmr~mini_md_library', vendor: 'sap.com', name: 'bi~mmr~mini_mm_library', vendor: 'sap.com', name: 'bi~mmr~api', vendor: 'sap.com', name: 'bi~mmr~webToolsEAP', vendor: 'sap.com', name: 'bi~mmr~bi_library', vendor: 'sap.com', name: 'bi~mmr~bi_ear', vendor: 'sap.com', name: 'bi~mmr~mmrlib', vendor: 'sap.com', name: 'bi~mmr~reportmodel_library', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_library', vendor: 'sap.com', name: 'bi~mmr~reportmodel_ear', vendor: 'sap.com', name: 'bi~mmr~jnet', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_ear', vendor: 'sap.com', name: 'sc~mmr_server', vendor: 'sap.com', name: 'bi~mmr~mmrapplib', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_library', vendor: 'sap.com', name: 'bi~mmr~amlib', vendor: 'sap.com', name: 'bi~mmr~mini_mm_ear', vendor: 'sap.com', name: 'bi~mmr~mini_md_ear', vendor: 'sap.com', name: 'bi~mmr~bi_repository', vendor: 'sap.com', name: 'bi~mmr~metamodel_library', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_ear', vendor: 'sap.com', name: 'bi~mmr~ejb', vendor: 'sap.com', name: 'bi~mmr~metamodel_ear', vendor: 'sap.com', name: 'sc~moin_buildt', vendor: 'sap.com', name: 'sc~nwtec', vendor: 'sap.com', name: 'tc~di~sdic~support~wd', vendor: 'sap.com', name: 'com.sap.portal.supportability.isolde.api', vendor: 'sap.com', name: 'com.sap.portal.pcd.textrepository', vendor: 'sap.com', name: 'com.sap.portal.prt.cache', vendor: 'sap.com', name: 'com.sap.portal.htmlb', vendor: 'sap.com', name: 'tc~jpe~dbschema', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndataless', vendor: 'sap.com', name: 'com.sap.portal.pcm.admin.pcdimplservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.notification', vendor: 'sap.com', name: 'sc~ep-basis', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.clusterinformation', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.contentconverter', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~srvgl', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.ucdadmin', vendor: 'sap.com', name: 'com.sap.portal.pcd.aclservice', vendor: 'sap.com', name: 'com.sap.portal.design.ui5designdataless', vendor: 'sap.com', name: 'com.sap.security.ume.consistencycheck', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.configuration', vendor: 'sap.com', name: 'com.sap.portal.pcd.umwrapperservice', vendor: 'sap.com', name: 'tc~epbc~prt~apps~restricted', vendor: 'sap.com', name: 'rtmfcommunicator', vendor: 'sap.com', name: 'com.sap.portal.themes.lafservice', vendor: 'sap.com', name: 'tc~epbc~resourcerepository~api', vendor: 'sap.com', name: 'com.sap.portal.usermapping', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.hooks', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.authentication', vendor: 'sap.com', name: 'com.sap.portal.pcd.softcacheservice', vendor: 'sap.com', name: 'com.sap.portal.pcm.metadata.service', vendor: 'sap.com', name: 'tc~epbc~pcm~pcmadminimplsrv', vendor: 'sap.com', name: 'com.sap.portal.design.vc5designdataless', vendor: 'sap.com', name: 'com.sap.portal.pcd.basicrolefactory', vendor: 'sap.com', name: 'tc~supportplatform~wd', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndata', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.prtconnection', vendor: 'sap.com', name: 'com.sap.portal.runtime.prtws', vendor: 'sap.com', name: 'com.sap.portal.resourcerepository', vendor: 'sap.com', name: 'com.sap.portal.pcd.lockservice', vendor: 'sap.com', name: 'irj', vendor: 'sap.com', name: 'tc~epbc~prt~apps', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.xsltransform', vendor: 'sap.com', name: 'com.sap.portal.pcd.traceservice', vendor: 'sap.com', name: 'tc~epbc~pcm~ext', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndataless', vendor: 'sap.com', name: 'tc~rtmf~wdtestapp', vendor: 'sap.com', name: 'com.sap.portal.pcd.basictransport', vendor: 'sap.com', name: 'com.sap.portal.pcd.glservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.idcounters', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndata', vendor: 'sap.com', name: 'com.sap.portal.usermanagement.admin', vendor: 'sap.com', name: 'tc~epbc~ume~ep5~deprecated', vendor: 'sap.com', name: 'tc~jpe~engine', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~restricted', vendor: 'sap.com', name: 'tc~ep~useragent~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.gwtintegration', vendor: 'sap.com', name: 'tc~bc~jpe~engine~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.connection', vendor: 'sap.com', name: 'com.sap.portal.usermanagement', vendor: 'sap.com', name: 'com.sap.portal.pcd.configservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.soap', vendor: 'sap.com', name: 'pcm_ext_libSDA', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.document', vendor: 'sap.com', -
Error in Deploying java components - SAP NW CE 7.2 installation on Windows
Hi,
I am installing NW CE 7.2 on a windows machine. I opted for custom installation. I get the below error at "Deploy java components step. Any clue on why is this happening and how to resolve ?
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html>
Regards,
RukmaniThe below msg is from sapinst_dev.log
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html> -
Can I Include an xml-stylesheet Link in a Java Web-Service?
The ability to easily create a SOAP-based web-service from a Java class using JDev's built in "Java Web Service" wizard is great.
From an "Ajax enablement" perspective, I see tremendous value in having the ability to specify an XSL url in the call to that web-service, so that the server will insert an <?xml-stylesheet .../> link to the specified URL prior to the SOAP message that it returns. That way, different callers to the web-service could render the same SOAP response differently (via an XSL transformation performed on the client-side via the XSL they've specified).
Is there already an undocumented way to do this with an Oracle "Java Web Service" that I am not aware of? If not, adding that capability would be trivial for Oracle, and it would add tremendous value to developers using Oracle's "Java Web Service" capability.Hi Chris,
I take it you are using the RESTful API method to GET the data. In that case you shoul be able to perform a http POST from your js code in order to update the controls.
This could be done as form components are updated, or after a submit button is pressed (I'm sure you are familiar with this part).
Please see here for more information: http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/build_web_service/
I hope this helps. -
Java Web Services Developer Pack 1.3 now available
All,
The Java Web Services Developer Pack 1.3 is now available for
download from http://java.sun.com/webservices. This release of JWSDP includes the fcs release of JAXRPC 1.1 and SAAJ 1.2 based on the WS-I basic profile 1.0 in addition to bug fixes /maintenance relases of the other components that have been in there in the previous releases. Feel free to download and send us comments at [email protected]
- Rajiv
:wqI was pumped when I saw this post, then deflated when I read what was new...
No new JSF. I'm sooo ready for an update :-)
TTFN,
-bd-
http://bill.dudney.net/roller/page/bill -
JavaFX trying to run java components off the applet host? (on mac only)
Does anyone know why my javafx applet is trying to access the likes of com/sun/java/util etc off the host that is hosting the applet.
The webserver just denies these requests and the applet crashes with something like java.util prohibited. Why is the applet doing this? It shoudl be getting the components from the client side?I keep getting a message about UNC paths not being supported. I could swear this that was working last week!!
I would simplify matters by running this command from a Console (cmd.exe):
\\ComputerName\c$\Java\bin\service\StopServerService.bat
Does it work?
What does StopServerService.bat contain?
What operating system do the two machines run?
Is UAC active on the remote machine?
After solving the problem at the console level you should get further advice from a VBA forum. -
How to undeploy java-components?
Hello! I have problem with undeployment java-components. My process server0 is grey. In my previous post I've got recommendations to redeploy java-components. But "how?" I don't know. I try to use SDM GUI and it suggests for me many services. Maybe somebody hint me which services I must kill and what component of SCA include this services. Especially I want to know which SCA (component/service) is responsible for server0 process.
Regards, Artem Ivashkinif i understood right
you want to undeploy some xyz.sca from the the AS JAVA.
1. go to system info page
http://host>:<port>/sap/monitoring/ComponentInfo
2. note down the DC name which you want to undeploy by searching xyz.sca
ex:
sap.com com.sap.portal.activityreport.db null (61919.20061025163630.0000) SAP AG SAP AG 20070207113306 sap.com/EP-PSERV
sap.com com.sap.portal.connectors.ws null (6.19019.20061005124622.0000) SAP AG SAP AG 20070207112511 sap.com/EP-PSERV
now you know the DC which you want to undeploy from xyz.sca
3. use sdm, go to undeploy tab, undeploy it one by one or you can select them all....Ctrl key...
Regards
Shridhar Gowda -
BW 352 install Java Components
During the install of Java components I get the following error when attempting to start J2EE...SAPINST attempts to start but cannopt because server is not running...here is error log:
BW has been successfully installed and Oracle up and running.....
AP J2EE Engine Version 6.30 PatchLevel 66061.37 is starting...
Loading: LogManager ... 2177 ms.
Loading: PoolManager ... 64 ms.
Loading: ThreadManager ... 129 ms.
Loading: IpVerificationManager ... 19 ms.
Loading: ConnectionsManipulator ... 128 ms.
Loading: ClassLoaderManager ... 37 ms.
Loading: ClusterManager ... My Library Path is: /usr/j2se/jre/lib/sparcv9/server
:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/usr
/sap/BX1/DVEBMGS00/j2ee/os_libs:/tmp/sapinst_exe.8532.1098309844:/sapmnt/BX1/exe
:/usr/lib:/usr/sap/BX1/DVEBMGS00/j2ee/os_libs:/usr/sap/BX1/D
VEBMGS00/j2ee/os_libs:/usr/sap/BX1/SYS/exe/run:/usr/sap/BX1/SYS/exe/runU
1095 ms.
Loading: PortsManager ... 26 ms.
Loading: LockingManager ... My Library Path is: /usr/j2se/jre/lib/sparcv9/server
:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/usr
/sap/BX1/DVEBMGS00/j2ee/os_libs:/tmp/sapinst_exe.8532.1098309844:/sapmnt/BX1/exe
:/usr/lib:/usr/sap/BX1/DVEBMGS00/j2ee/os_libs:/usr/sap/BX1/D
VEBMGS00/j2ee/os_libs:/usr/sap/BX1/SYS/exe/run:/usr/sap/BX1/SYS/exe/runU
239 ms.
Loading: ConfigurationManager ... 5708 ms.
Loading: LicensingManager ... 158 ms.
Loading: ServiceManager ...
Loading services:
service security started. (52 ms)
service httptunneling started. (7 ms)
service licensing started. (22 ms)
service webservices started. (131 ms)
service keystore started. (241 ms)
service timeout started. (150 ms)
service memory started. (164 ms)
service sld started. (166 ms)
service jmx_notification started. (113 ms)
service r3startup started. (245 ms)
service shell started. (305 ms)
service telnet started. (76 ms)
service jmx started. (928 ms)
service basicadmin started. (461 ms)
service adminadapter started. (70 ms)
service monitor started. (281 ms)
service p4 started. (3069 ms)
service classload started. (5 ms)
service log_configurator started. (3536 ms)
service configuration started. (13 ms)
service jms_provider started. (397 ms)
service http started. (441 ms)
service tc.monitoring.logviewer started. (1141 ms)
ServiceManager started for 6169 ms.
Framework started for 15978 ms.
SAP J2EE Engine Version 6.30 PatchLevel 66061.37 is running!
PatchLevel 66061.37 January 11, 2004 21:06 GMT
>Decrease threads to 90
Decrease threads to 80
Decrease threads to 70
Decrease threads to 60
Stoping services
service tc.monitoring.logviewer stopped. (0 ms)
service classload stopped. (3 ms)
service p4 stopped. (103 ms)
service keystore stopped. (1 ms)
service adminadapter stopped. (1 ms)
service monitor stopped. (104 ms)
service security stopped. (0 ms)
service basicadmin stopped. (20 ms)
service jmx stopped. (0 ms)
service webservices stopped. (46 ms)
service sld stopped. (48 ms)
service telnet stopped. (1062 ms)
service http stopped. (1057 ms)
service timeout stopped. (1 ms)
service configuration stopped. (1 ms)
service jms_provider stopped. (1104 ms)
service log_configurator stopped. (1 ms)
service memory stopped. (1 ms)
service r3startup stopped. (50 ms)
service licensing stopped. (1 ms)
service httptunneling stopped. (1 ms)
service shell stopped. (55 ms)
service jmx_notification stopped. (49 ms)
Thank JohnHi John,
this log just shows the server going up and then going down again. Everything fine with it. There are no errors in here.
Can youn tell me where you have found that log?
Did you check other logs?
Regards,
Benny -
Recieved error during Solution Manager EHP1 Java Components installation.
I successfully installed EHP1 ABAP components but I'm have a problem with the Java components. I recieved the following error. Import aborted during ADSSAP02_0-20002778.SCA
Feb 20, 2009 3:17:59 PM Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 3:17:59 PM Info: Starting to save the repository
Feb 20, 2009 3:18:01 PM Info: Finished saving the repository
Feb 20, 2009 3:18:01 PM Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 3:18:01 PM Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Please, look at error logs above for more information!
Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.200712
13024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Cannot load one of the bean interfaces or the bean class of bean LicenseEJBBean.; nested exception is:
com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot load one of the bean interfaces or the bean cla
ss of bean LicenseEJBBean.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 11:25:59... Info: Starting to save the repository
Feb 20, 2009 11:26:01... Info: Finished saving the repository
Feb 20, 2009 11:26:01... Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634'
'/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 11:26:01... Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Edited by: Darrell Kirklen on Feb 23, 2009 5:03 PMJust resolved problem. While reviewing the sdmlog20090310.log I found
error "java.lang.UnsupportedClassVersionError?" when I goggled this
error "How do I resolve a java.lang.UnsupportedClassVersionError? I
found the following solution:
http://support.codegear.com/article/35846 : This exception can occur
when the source is built targeting a JDK that is not supported by the
JDK attempting to run it. In the above example, if the servlet was
built targeting only JDK 1.5, but the web server runs JDK 1.4, the
above exception will occur. Check, Project Properties | Build | Java |
Target VM, and verify that the Target VM indicates a JDK compatibility
that is appropriate for the JDK that is running it. It is recommended
to set this field to 'All Java SDKs' for the most compatibility. The
only reason you would want to specify a particular version is if your
code uses language features that only appear in a particular version of
the JDK, and you want to ensure that users use only a compatible JDK.
Also check, Project Properties | Build | Java | Language Features, and
verify that the Language Features are applicable with JDK that is
running it
A this point I checked the java -version at the os level and it showed
1.5.0_17 we are aware the supported version of java should be 1.4.2_16
our Unix team (Solaris) recently installed new patches and didnu2019t
remember to leave the java version at 1.4.2_16 after their were done.
Once the java version was set back to 1.4.2_16 I was able to complete
the java portion of EHP1 using the JSPM successfully.
Edited by: Darrell Kirklen on Mar 13, 2009 4:37 PM -
Need a list NW BI 7.11 Java components
Hi,
Could you please list down the NW BI 7.11 Java components.
Thanks & Regards,
BalaHi,
You should find all the information on packages and components in SP stack in service marketplace.
https://websmp106.sap-ag.de/swdc
go to link: SAP support package Stacks.
Here you should be able to find all the related information,
Regards,
Sujit. -
Serialization error while invoking a Java web service
Hi,
I've a requirement where I need to create a Java web service, which returns a collection (a set of records).
The way I've created a web service is by having a Java Class, which internally calls a Pl/sql package returning Ref cursors and a bean Class, which wraps the method of the Java Class, to return the collection. I could create the web service successfully and could invoke the end point. The end point looks like this: http://localhost:8988/MyJavaWebService-New_JWS-context-root/MyWebService_finalSoapHttpPort
The method exposed for the web service in my Java class is of type ArrayList, to fetch the collection element.
After giving the input at the end point, while I say invoke, for the web service, I get the following error:
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://mypkg/types/"
xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (serialization error: no serializer is registered for (class mypkg.EmpBean, null))</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
I've tried making my exposed method of type Vector as well and re-generated the web service. But still I face the same issue at invocation.
Can anybody help me out and hint me on how I should proceed? I'm not sure if my approach is correct and so please correct me if I'm wrong.
Thanks in Advance,
GayathriHi,
do you use 10.1.2 or 10.1.3?
Take a look at:
Re: How to create a web service with ArrayList or Collection -
Error starting Oracle BI Java Host service
Hi,
We are facing some issue while starting the Oracle BI Java Host service. It throws the following error.
This application was working properly till some 2 days back and suddenly it has started giving this error. We have not updated any software. The host machine is Win XP.
Sep 27, 2011 12:08:15 PM Main main
INFO: Javahost config file(s): C:\OracleBI\web\javahost\config\config.xml. Xpath:.
Sep 27, 2011 12:08:16 PM ApplicationImpl createEnvironment
INFO: Config environment properties:
presentation.coreconfigdir=C:\OracleBI\web\config
javahostdir=C:\OracleBI\web\javahost
rootdir=C:\OracleBI
presentation.dataconfigdir=C:\OracleBIData\web\config
presentation.rootdir=C:\OracleBI\web
tempdir=C:\OracleBIData\tmp
presentation.cordaroot=C:\OracleBI\Corda50
Sep 27, 2011 12:08:16 PM ApplicationImpl init
SEVERE: java.io.IOException: Unable to establish loopback connection
at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:106)
at java.security.AccessController.doPrivileged(Native Method)
at sun.nio.ch.PipeImpl.<init>(PipeImpl.java:122)
at sun.nio.ch.SelectorProviderImpl.openPipe(SelectorProviderImpl.java:27)
at java.nio.channels.Pipe.open(Pipe.java:133)
at sun.nio.ch.WindowsSelectorImpl.<init>(WindowsSelectorImpl.java:104)
at sun.nio.ch.WindowsSelectorProvider.openSelector(WindowsSelectorProvider.java:26)
at com.siebel.analytics.javahost.Listener.<init>(Listener.java:53)
at com.siebel.analytics.javahost.ApplicationImpl.init(ApplicationImpl.java:121)
at com.siebel.analytics.javahost.standalone.Main.init(Main.java:127)
Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): bind
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:72)
... 9 more
Request some input to resolve this error.
Thanks in advance.@Deepak,
Following are the log contents
Sep 27, 2011 12:08:15 PM Main main
INFO: Javahost config file(s): C:\OracleBI\web\javahost\config\config.xml. Xpath:.
Sep 27, 2011 12:08:16 PM ApplicationImpl createEnvironment
INFO: Config environment properties:
presentation.coreconfigdir=C:\OracleBI\web\config
javahostdir=C:\OracleBI\web\javahost
rootdir=C:\OracleBI
presentation.dataconfigdir=C:\OracleBIData\web\config
presentation.rootdir=C:\OracleBI\web
tempdir=C:\OracleBIData\tmp
presentation.cordaroot=C:\OracleBI\Corda50
Sep 27, 2011 12:08:16 PM ApplicationImpl init
SEVERE: java.io.IOException: Unable to establish loopback connection
at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:106)
at java.security.AccessController.doPrivileged(Native Method)
at sun.nio.ch.PipeImpl.<init>(PipeImpl.java:122)
at sun.nio.ch.SelectorProviderImpl.openPipe(SelectorProviderImpl.java:27)
at java.nio.channels.Pipe.open(Pipe.java:133)
at sun.nio.ch.WindowsSelectorImpl.<init>(WindowsSelectorImpl.java:104)
at sun.nio.ch.WindowsSelectorProvider.openSelector(WindowsSelectorProvider.java:26)
at com.siebel.analytics.javahost.Listener.<init>(Listener.java:53)
at com.siebel.analytics.javahost.ApplicationImpl.init(ApplicationImpl.java:121)
at com.siebel.analytics.javahost.standalone.Main.init(Main.java:127)
Caused by: java.net.SocketException: No buffer space available (maximum connections reached?): bind
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:72)
It also mentions about the buffer space....could that be a reason for this.
By the way, I forgot to mention, this deployment is in a VMWare (with XP as OS) which is hosted on Windows Server. -
How to test a Java Web Service locally?
I developed simple java web services.
Now I want to test them locally.
I want to expose my web service through my Web Server(Tomcat).
How can I expose that webservice?
After that I want to access my web service through a Internet Browser.
Is it possible to test that web service locally (localhost)?
My computer is not connected to a network or internet.
My OS is Windows XP Professional.I just set up TCPMON. Considering it is free and the fact that it has more than just a basic UI, I am quite impressed. I also use SOAPscope, which is another great tool, but I am looking for a free option.
My issue: I set up TCPMON to sniff messages sent over HTTPS through port 8080. But I am getting encrypted messages upon sending the SOAP request as follows:
�b�b�b�bvC�Ym�)f��OvC�Ym�)f��W�O�k�v�W��dQ�$�{� �4�����F�������vO���XEC
)��~9gl^�OvC�Ym�)f��W�O�k�v�W��dQ�$�{� �4�����F�������vO���XEC
)��~9gl^�OvC�Ym�)f��W�O�k�v�W��dQ�$�{� �4�����F�������vO���XEC
)��~9gl^�
Any clue why?
Your help is greatly appreciated.
Aish
Maybe you are looking for
-
Hi , Earlier , We were connecting our application as partner applications in portal for SSO authentication. We used SSO sdk for diverting requests to SSO. I was reading some literature and it seems oracle is supporting connecting to SSO from JAAS pro
-
Send mail to spool list recipient from dynamically generated job
Hi Friends, We are running the SAP payment run daily in background mode using the transaction F110S (program SAPF110S). We have scheduled the program SAPF110S to run in SM36 and have specified an email address there as Spool List Recipient. The probl
-
Can I create a dynamic link proxy to place in my PP Sequence?
So, I'm editing a sequence in Premiere Pro CC with a number of After Effects comps as dynamic links. I need to render out lo-rez version for the director but the render is taking forever when it hits the dynamic links. Is there a workflow to work
-
I NEED THE TABLE NAME FOR THE FIELD DESCRIPTION GIVEN!
I NEED THE TABLE NAME FOR THE FIELD DESCRIPTION GIVEN! Partner Type Partner Type Desc Partner no Partner Name Partner Address 1 Partner Address 2 Partner Address 3 Partner Address 4
-
Setting fast_start_mttr_target on 10.2.0.4
Hi there, Can anyone please tell me how to set fast_start_mttr_target on 10.2.0.4. In 10g, by setting this parameter we override log_checkpoint_timeout. By doing so, we will have only incremental checkpoints. Does a higher value of fast_start_mttr_ta