SDM Deploy Error
Hello! I'm deploying a J2EE project and the J2EE Server gives me the following error :
18-may-2005 14:02:06 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[005]Deployment aborted
Settings
SDM host : linux2
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
Aborted: development component 'Isicres_J2EE'/'sap.com'/'localhost'/'2005.05.18.13.59.43':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application sap.com/Isicres_J2EE.. Reason: null; nested exception is: java.lang.NullPointerException (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I haven't idea to solve this problem!! any help, please?
Thank you
Hi Carlos,
You can find the root exception in the defaultTrace.trc file under /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/log.
Hope it helps,
Vladimir
Similar Messages
-
SDM deployment error during XI 3.0 installation
(nobody in the PI forum replied, so I'm reposting here)
I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
errors:
service sld ================= ERROR =================
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
and around 20 more services which have a dependency on sld
sld does not start because:
/Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
OR:
SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
further suspicious warnings:
Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
and this for around 20 more components from comp.sap.aii*
What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
Any help is appreciated, Thanks.
SanjayCan you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
Please check this note it will solve your issue.
Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
you can manually start th services.
Thanks Rishi Abrol -
Hi all,
When I tried deploying a simple webdynpro application in the server I get the error like this
Jul 25, 2007 1:09:01 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
1. I tried to connect to sdm via remote_gui and entered password and it connected correctly there without any error.
2. In NWDS I selected the sap j2ee engine as
sap j2ee engine is installed on local host
system name : F06
J2EE Instance : 30
SCS Instance : 31
3. I went through all the post about this issue and none helped me out.
Thanks in advance,
Pls help
Best Regards,
Suresh.In Window=>Preferences>SAP j2ee Engine.
I selected
SAP J2ee Engine installed in local host. Clicked the Browse button and then selected F06. This populated
System Name: F06
J2ee instance:30
SCS Instance:31
So what could be the problem. -
Hi ,
During installation of NW2004S I am facing the below error
WARNING
SDM call of deploySdaList ends with returncode 16. See output of logfile Z:\usr\sap\SAPinst\NW04S\SYSTEM\DB4\CENTRAL\AS\callSdmViaSapinst.log.
callSdmviaSapinstlog:
ERROR: Cannot connect to Host: [hostname] with user name: [J2EE_ADMIN]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at java.lang.Throwable.<init>(Throwable.java:180)
at java.lang.Exception.<init>(Exception.java:29)
at javax.naming.NamingException.<init>(NamingException.java:109)
at com.sap.engine.services.jndi.persistent.exceptions.NamingException.<init>(NamingException.java:119)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:233)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at java.lang.Throwable.<init>(Throwable.java:195)
at java.lang.Exception.<init>(Exception.java:41)
at java.security.GeneralSecurityException.<init>(GeneralSecurityException.java:43)
at javax.security.auth.login.LoginException.<init>(LoginException.java:53)
at com.sap.engine.services.security.exceptions.BaseLoginException.<init>(BaseLoginException.java:113)
at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
... 35 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/172.16.10.5,port=50004,localport=24156]
at java.lang.Throwable.<init>(Throwable.java:195)
at java.lang.Exception.<init>(Exception.java:41)
at java.io.IOException.<init>(IOException.java:40)
at java.io.EOFException.<init>(EOFException.java:44)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
Apr 24, 2008 7:48:48 PM Info: Starting to save the repository
Apr 24, 2008 7:48:52 PM Info: Finished saving the repository
Apr 24, 2008 7:48:52 PM Info: Starting: Initial deployment: Selected software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060827113300''/'0' will be deployed.
Apr 24, 2008 7:48:52 PM Error: Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060827113300''/'0':
Failed deployment of SDAs:
development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0009.20060825141640.0000'/'0' : aborted
Please, look at error logs above for more information!
Apr 24, 2008 7:48:52 PM Info: Starting to save the repository
Apr 24, 2008 7:48:56 PM Info: Finished saving the repository
Apr 24, 2008 7:48:56 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Apr 24, 2008 7:48:56 PM Error: -
At least one of the Deployments failed -
Apr 24, 2008 7:49:03 PM Info: Summarizing the deployment results:
Apr 24, 2008 7:49:03 PM Error: Aborted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIIBC09_0.SCA
Apr 24, 2008 7:49:03 PM Info: OK: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIWEBAPP09_0.SCA
Apr 24, 2008 7:49:03 PM Info: OK: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIBASES09_0.SCA
Apr 24, 2008 7:49:03 PM Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIREPPLAN09_0.SCA
Apr 24, 2008 7:49:03 PM Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIWDALV09_0.SCA
Apr 24, 2008 7:49:03 PM Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/VCKITBI09_0.SCA
Apr 24, 2008 7:49:04 PM Error: Processing error. Return code: 4
thanks in advancehi prasanna ,
please go through the logs of std_server & std_dispatcher and let me know the reason
stdout/stderr redirect
node name : dispatcher
pid : 694
system name :SID
system nr. : 00
started at : Thu May 1 18:59:21 2008
[Thr 1] Thu May 1 18:59:26 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier C8C2406445003900; heap identifier C8C2406445003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 18:59:33
GC 1: live objects 2615; collected objects 1646; collected(KB) 144.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 6508; current threshold(KB) 65536.
GC 1: collect (milliseconds) 67.
GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 18:59:33
Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/dispatcher/bin/boot/boot.jar.
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 12302 ms.
Loading: PoolManager ... 93 ms.
Loading: ThreadManager ... 1687 ms.
Loading: IpVerificationManager ... 667 ms.
Loading: ConnectionsManipulator ... 1166 ms.
Loading: ClassLoaderManager ... 44 ms.
Loading: ClusterManager ... 4756 ms.
Loading: PortsManager ... 669 ms.
Loading: LockingManager ... 3256 ms.
Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 19:00:24
GC 2: live objects 59229; collected objects 284349; collected(KB) 50255.
GC 2: queued for finalization 0; total soft references 60; cleared soft references 0.
GC 2: current heap(KB) 83164; current threshold(KB) 65536.
GC 2: collect (milliseconds) 552.
GC 2: current cycle allocation(KB) 5455; previous cycle allocation(KB) 66441.
GC 2: total weak references 35; cleared weak references 0.
GC 2: total final references 216; cleared final references 62.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 19:00:24
36868 ms.
Loading: LicensingManager ... 642 ms.
Loading: CacheManager ... 4029 ms.
Loading: ServiceManager ...
Loading services.:
Service security started. (1561 ms).
Service licensing started. (1387 ms).
Service sld started. (2637 ms).
Service httptunneling started. (2648 ms).
Service timeout started. (2472 ms).
Service memory started. (2449 ms).
Service r3startup started. (2340 ms).
Service webservices started. (2981 ms).
Service jmx_notification started. (1773 ms).
Service keystore started. (2061 ms).
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 19:00:56
Service iiop started. (2812 ms).
Service shell started. (3721 ms).
GC 3: live objects 103453; collected objects 372425; collected(KB) 56714.
GC 3: queued for finalization 0; total soft references 162; cleared soft references 0.
GC 3: current heap(KB) 109196; current threshold(KB) 65536.
GC 3: collect (milliseconds) 1198.
GC 3: current cycle allocation(KB) 5183; previous cycle allocation(KB) 65548.
GC 3: total weak references 198; cleared weak references 0.
GC 3: total final references 643; cleared final references 367.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 19:00:57
Service telnet started. (298 ms).
Service ssl started. (9290 ms).
May 1, 2008 7:01:05 PM com.sap.engine.services.ssl [SAPEngine_System_Thread[impl:6]_20] Fatal: Source: com.sap.engine.services.keystore.exceptions.BaseRemoteException: Remote call errored; Description: SSL server identity keystore view not found; Consequences: SSL transport protocol not available; Countermeasures:create keystore view "service_ssl" with at least one private key entry, restart the SSL service
Service p4 started. (13628 ms).
Service classload started. (0 ms).
Service log_configurator started. (15935 ms).
Service configuration started. (23 ms).
Service http started. (4921 ms).
Service jmx started. (14325 ms).
Service basicadmin started. (3789 ms).
Service adminadapter started. (52 ms).
Service jms_provider started. (17803 ms).
GC 4: starting collection, threshold allocation reached.
GC 4: collection starting 05/01/08 19:01:41
Service tc.monitoring.logviewer started. (20999 ms).
GC 4: live objects 155285; collected objects 260747; collected(KB) 57227.
GC 4: queued for finalization 0; total soft references 492; cleared soft references 0.
GC 4: current heap(KB) 132084; current threshold(KB) 65536.
GC 4: collect (milliseconds) 3227.
GC 4: current cycle allocation(KB) 12710; previous cycle allocation(KB) 65591.
GC 4: total weak references 429; cleared weak references 0.
GC 4: total final references 1238; cleared final references 771.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 05/01/08 19:01:45
Service monitor started. (26655 ms).
ServiceManager started for 72516 ms.
Framework started for 139690 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 5: starting collection, threshold allocation reached.
GC 5: collection starting 05/01/08 19:56:01
GC 5: live objects 186102; collected objects 462345; collected(KB) 60574.
GC 5: queued for finalization 0; total soft references 1320; cleared soft references 0.
GC 5: current heap(KB) 144312; current threshold(KB) 65536.
GC 5: collect (milliseconds) 18649.
GC 5: current cycle allocation(KB) 0; previous cycle allocation(KB) 65543.
GC 5: total weak references 654; cleared weak references 10.
GC 5: total final references 1171; cleared final references 741.
GC 5: total phantom references 0; cleared phantom references 0.
GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
GC 5: collection ending 05/01/08 19:56:20
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
Stopping services.
Service tc.monitoring.logviewer stopped. (654 ms)
Service classload stopped. (210 ms)
Service p4 stopped. (450 ms)
Service ssl stopped. (1040 ms)
Service keystore stopped. (469 ms)
Service iiop stopped. (2129 ms)
Service adminadapter stopped. (164 ms)
Service monitor stopped. (1193 ms)
Service security stopped. (6 ms)
Service basicadmin stopped. (52 ms)
Service jms_provider stopped. (1201 ms)
Service jmx stopped. (69 ms)
Service webservices stopped. (25 ms)
Service sld stopped. (4 ms)
Service telnet stopped. (1105 ms)
Service http stopped. (1089 ms)
Service timeout stopped. (7 ms)
Service configuration stopped. (93 ms)
Service log_configurator stopped. (66 ms)
Service memory stopped. (15 ms)
Service r3startup stopped. (38 ms)
Service licensing stopped. (39 ms)
Service httptunneling stopped. (35 ms)
Service shell stopped. (168 ms)
Service jmx_notification stopped. (5 ms)
stdout/stderr redirect
node name : dispatcher
pid : 694
system name : SID
system nr. : 00
started at : Thu May 1 20:02:03 2008
[Thr 1] Thu May 1 20:02:06 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier F83A6D6E7B003900; heap identifier F83A6D6E7B003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 20:02:14
GC 1: live objects 2817; collected objects 1704; collected(KB) 149.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 6544; current threshold(KB) 65536.
GC 1: collect (milliseconds) 54.
GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 20:02:14
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 3104 ms.
Loading: PoolManager ... 40 ms.
Loading: ThreadManager ... 539 ms.
Loading: IpVerificationManager ... 107 ms.
Loading: ConnectionsManipulator ... 266 ms.
Loading: ClassLoaderManager ... 93 ms.
Loading: ClusterManager ... 1040 ms.
Loading: PortsManager ... 57 ms.
Loading: LockingManager ... 511 ms.
Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 20:02:29
GC 2: live objects 107477; collected objects 418716; collected(KB) 64931.
GC 2: queued for finalization 0; total soft references 59; cleared soft references 0.
GC 2: current heap(KB) 103592; current threshold(KB) 65536.
GC 2: collect (milliseconds) 1114.
GC 2: current cycle allocation(KB) 22125; previous cycle allocation(KB) 65803.
GC 2: total weak references 30; cleared weak references 0.
GC 2: total final references 218; cleared final references 65.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 20:02:30
13732 ms.
Loading: LicensingManager ... 294 ms.
Loading: CacheManager ... 2235 ms.
Loading: ServiceManager ...
Loading services.:
Service security started. (262 ms).
Service sld started. (371 ms).
Service httptunneling started. (452 ms).
Service licensing started. (234 ms).
Service r3startup started. (419 ms).
Service webservices started. (416 ms).
Service memory started. (600 ms).
Service timeout started. (619 ms).
Service jmx_notification started. (451 ms).
Service iiop started. (631 ms).
Service keystore started. (725 ms).
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 20:02:46
GC 3: live objects 98384; collected objects 238422; collected(KB) 42389.
GC 3: queued for finalization 0; total soft references 142; cleared soft references 0.
GC 3: current heap(KB) 112560; current threshold(KB) 65536.
GC 3: collect (milliseconds) 452.
GC 3: current cycle allocation(KB) 4333; previous cycle allocation(KB) 65537.
GC 3: total weak references 193; cleared weak references 0.
GC 3: total final references 652; cleared final references 367.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 20:02:46
Service ssl started. (794 ms).
Service shell started. (2602 ms).
Service jmx started. (1587 ms).
Service telnet started. (138 ms).
Service p4 started. (6246 ms).
Service classload started. (1 ms).
Service log_configurator started. (7255 ms).
Service configuration started. (24 ms).
Service http started. (1365 ms).
Service jms_provider started. (1628 ms).
Service basicadmin started. (1209 ms).
Service adminadapter started. (35 ms).
GC 4: starting collection, threshold allocation reached.
GC 4: collection starting 05/01/08 20:02:56
Service tc.monitoring.logviewer started. (2642 ms).
GC 4: live objects 160497; collected objects 282434; collected(KB) 57082.
GC 4: queued for finalization 0; total soft references 491; cleared soft references 0.
GC 4: current heap(KB) 139048; current threshold(KB) 65536.
GC 4: collect (milliseconds) 386.
GC 4: current cycle allocation(KB) 14679; previous cycle allocation(KB) 65740.
GC 4: total weak references 419; cleared weak references 0.
GC 4: total final references 1406; cleared final references 896.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 05/01/08 20:02:56
Service monitor started. (4371 ms).
ServiceManager started for 19752 ms.
Framework started for 42188 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 5: starting collection, threshold allocation reached.
GC 5: collection starting 05/01/08 20:38:07
GC 5: live objects 185219; collected objects 409132; collected(KB) 57626.
GC 5: queued for finalization 0; total soft references 778; cleared soft references 0.
GC 5: current heap(KB) 142692; current threshold(KB) 65536.
GC 5: collect (milliseconds) 15208.
GC 5: current cycle allocation(KB) 423; previous cycle allocation(KB) 65588.
GC 5: total weak references 624; cleared weak references 11.
GC 5: total final references 1173; cleared final references 717.
GC 5: total phantom references 0; cleared phantom references 0.
GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
GC 5: collection ending 05/01/08 20:38:22
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
Stopping services.
Service tc.monitoring.logviewer stopped. (1054 ms)
Service classload stopped. (174 ms)
Service p4 stopped. (555 ms)
Service ssl stopped. (403 ms)
Service keystore stopped. (69 ms)
Service iiop stopped. (3292 ms)
Service adminadapter stopped. (417 ms)
Service monitor stopped. (3190 ms)
Service security stopped. (24 ms)
Service basicadmin stopped. (431 ms)
Service jms_provider stopped. (1217 ms)
Service jmx stopped. (126 ms)
Service webservices stopped. (50 ms)
Service sld stopped. (17 ms)
Service telnet stopped. (1357 ms)
Service http stopped. (1204 ms)
Service timeout stopped. (38 ms)
Service configuration stopped. (390 ms)
Service log_configurator stopped. (232 ms)
Service memory stopped. (97 ms)
Service r3startup stopped. (126 ms)
Service licensing stopped. (126 ms)
Service httptunneling stopped. (61 ms)
Service shell stopped. (200 ms)
Service jmx_notification stopped. (21 ms)
stdout/stderr redirect
node name : dispatcher
pid : 694
system name : GBV
system nr. : 00
started at : Thu May 1 21:06:38 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier C6F3A9F0B8003900; heap identifier C6F3A9F0B8003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 21:06:47
GC 1: live objects 2649; collected objects 1704; collected(KB) 149.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 6544; current threshold(KB) 65536.
GC 1: collect (milliseconds) 54.
GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 21:06:47
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 3558 ms.
Loading: PoolManager ... 51 ms.
Loading: ThreadManager ... 394 ms.
Loading: IpVerificationManager ... 119 ms.
Loading: ConnectionsManipulator ... 120 ms.
Loading: ClassLoaderManager ... 68 ms.
Loading: ClusterManager ... 1019 ms.
Loading: PortsManager ... 80 ms.
Loading: LockingManager ... 695 ms.
Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 21:07:04
GC 2: live objects 58479; collected objects 282635; collected(KB) 50395.
GC 2: queued for finalization 0; total soft references 58; cleared soft references 0.
GC 2: current heap(KB) 82336; current threshold(KB) 65536.
GC 2: collect (milliseconds) 332.
GC 2: current cycle allocation(KB) 3761; previous cycle allocation(KB) 65896.
GC 2: total weak references 30; cleared weak references 0.
GC 2: total final references 213; cleared final references 62.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 21:07:05
12764 ms.
Loading: LicensingManager ... 192 ms.
Loading: CacheManager ... 956 ms.
Loading: ServiceManager ...
Loading services.:
Service security started. (247 ms).
Service sld started. (380 ms).
Service httptunneling started. (462 ms).
Service webservices started. (501 ms).
Service r3startup started. (447 ms).
Service licensing started. (307 ms).
Service memory started. (472 ms).
Service timeout started. (569 ms).
Service jmx_notification started. (546 ms).
Service iiop started. (684 ms).
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 21:07:15
Service keystore started. (646 ms).
Service shell started. (786 ms).
Service telnet started. (64 ms).
Service ssl started. (687 ms).
Service jmx started. (1865 ms).
GC 3: live objects 128135; collected objects 368341; collected(KB) 55808.
GC 3: queued for finalization 0; total soft references 137; cleared soft references 0.
GC 3: current heap(KB) 117676; current threshold(KB) 65536.
GC 3: collect (milliseconds) 4067.
GC 3: current cycle allocation(KB) 14745; previous cycle allocation(KB) 65575.
GC 3: total weak references 187; cleared weak references 0.
GC 3: total final references 635; cleared final references 368.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 21:07:19
Service p4 started. (5623 ms).
Service classload started. (0 ms).
Service log_configurator started. (7555 ms).
Service configuration started. (7 ms).
Service basicadmin started. (746 ms).
Service adminadapter started. (28 ms).
GC 4: starting collection, threshold allocation reached.
GC 4: collection starting 05/01/08 21:07:25
Service tc.monitoring.logviewer started. (2513 ms).
GC 4: live objects 169322; collected objects 304225; collected(KB) 58510.
GC 4: queued for finalization 0; total soft references 478; cleared soft references 0.
GC 4: current heap(KB) 144236; current threshold(KB) 65536.
GC 4: collect (milliseconds) 1835.
GC 4: current cycle allocation(KB) 21225; previous cycle allocation(KB) 65597.
GC 4: total weak references 411; cleared weak references 0.
GC 4: total final references 1345; cleared final references 861.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 05/01/08 21:07:27
Service jms_provider started. (4492 ms).
Service http started. (4399 ms).
Service monitor started. (29724 ms).
ServiceManager started for 43503 ms.
Framework started for 64037 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 5: starting collection, threshold allocation reached.
GC 5: collection starting 05/01/08 21:31:12
GC 5: live objects 184326; collected objects 378511; collected(KB) 56530.
GC 5: queued for finalization 0; total soft references 801; cleared soft references 0.
GC 5: current heap(KB) 144508; current threshold(KB) 65536.
GC 5: collect (milliseconds) 74315.
GC 5: current cycle allocation(KB) 49; previous cycle allocation(KB) 65589.
GC 5: total weak references 706; cleared weak references 10.
GC 5: total final references 1138; cleared final references 684.
GC 5: total phantom references 0; cleared phantom references 0.
GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
GC 5: collection ending 05/01/08 21:32:26
GC 6: starting collection, threshold allocation reached.
GC 6: collection starting 05/02/08 03:03:17
GC 6: live objects 199214; collected objects 762329; collected(KB) 61062.
GC 6: queued for finalization 0; total soft references 779; cleared soft references 0.
GC 6: current heap(KB) 168484; current threshold(KB) 65536.
GC 6: collect (milliseconds) 12090.
GC 6: current cycle allocation(KB) 341; previous cycle allocation(KB) 65553.
GC 6: total weak references 589; cleared weak references 0.
GC 6: total final references 1688; cleared final references 1235.
GC 6: total phantom references 0; cleared phantom references 0.
GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
GC 6: collection ending 05/02/08 03:03:29
stdout/stderr redirect
node name : server0
pid : 694
system name : GBV
system nr. : 00
started at : Thu May 1 18:59:21 2008
[Thr 1] Thu May 1 18:59:26 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier F9A676BFAF003900; heap identifier F9A676BFAF003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 18:59:33
GC 1: live objects 2518; collected objects 1665; collected(KB) 146.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 6544; current threshold(KB) 1048576.
GC 1: collect (milliseconds) 53.
GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 18:59:33
Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/server0/bin/boot/boot.jar.
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/server0/bin/system/bytecode.jar.
12427 ms.
Loading: PoolManager ... 7 ms.
Loading: ApplicationThreadManager ... 1200 ms.
Loading: ThreadManager ... 639 ms.
Loading: IpVerificationManager ... 10 ms.
Loading: ClassLoaderManager ... 757 ms.
Loading: ClusterManager ... 5440 ms.
Loading: LockingManager ... 3369 ms.
Loading: ConfigurationManager ... 36874 ms.
Loading: LicensingManager ... 642 ms.
Loading: CacheManager ... 4042 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (975 ms).
Service timeout started. (2182 ms).
Service memory started. (1863 ms).
Service userstore started. (1000 ms).
Service jmx_notification started. (867 ms).
Service cross started. (3029 ms).
Service file started. (3829 ms).
Service trex.service started. (12103 ms).
Service p4 started. (11079 ms).
Service classpath_resolver started. (858 ms).
Service log_configurator started. (19432 ms).
Service locking started. (4 ms).
Service http started. (15405 ms).
Service naming started. (17125 ms).
Service failover started. (840 ms).
Service appclient started. (1785 ms).
Service javamail started. (2268 ms).
Service ts started. (2197 ms).
Service licensing started. (6 ms).
Service jmsconnector started. (2781 ms).
Service iiop started. (5166 ms).
Service connector started. (3628 ms).
Service deploy started. (35090 ms).
Service MigrationService started. (634 ms).
Service bimmrdeployer started. (171 ms).
Service configuration started. (1237 ms).
Service webservices started. (25127 ms).
Service dbpool started. (24840 ms).
Service com.sap.security.core.ume.service started. (60071 ms).
Service security started. (11292 ms).
Service shell started. (379 ms).
Service tceCATTPingservice started. (701 ms).
Service telnet started. (1087 ms).
Service applocking started. (3204 ms).
Service webdynpro started. (2064 ms).
Service classload started. (7995 ms).
Service cafummetadata~imp started. (1979 ms).
Service jmx started. (1446 ms).
Service tc.monitoring.logviewer started. (17911 ms).
Service keystore started. (36345 ms).
Service ssl started. (829 ms).
Service basicadmin started. (29864 ms).
Service cafumrelgroups~imp started. (41597 ms).
Service dsr started. (35451 ms).
Service com.adobe~LicenseService started. (2324 ms).
Service servlet_jsp started. (52833 ms).
Service tcsecsecurestorage~service started. (7895 ms).
Service com.adobe~DataManagerService started. (53112 ms).
Service adminadapter started. (23450 ms).
Service monitor started. (22187 ms).
Service com.adobe~DocumentServicesBinaries2 started. (499 ms).
Service com.adobe~DocumentServicesConfiguration started. (12876 ms).
Service com.adobe~FontManagerService started. (4482 ms).
Service ejb started. (87561 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (3687 ms).
Service com.adobe~PDFManipulation started. (2417 ms).
Service com.adobe~TrustManagerService started. (1811 ms).
Service tcsecdestinations~service started. (26759 ms).
Service tcsecwssec~service started. (16232 ms).
Service apptracing started. (29230 ms).
Service com.adobe~DocumentServicesDestProtoService started. (2891 ms).
Service CUL started. (84303 ms).
Service rfcengine started. (12183 ms).
Service pmi started. (2564 ms).
Service com.adobe~XMLFormService started. (14499 ms).
Service cafruntimeconnectivity~impl started. (269831 ms).
Service sld started. (38976 ms).
Service tcsecvsi~service started. (8136 ms).
Service jms_provider started. (119482 ms).
ServiceManager started for 300168 ms.
Framework started for 367378 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 19:07:44
GC 2: live objects 657606; collected objects 5135128; collected(KB) 936066.
GC 2: queued for finalization 0; total soft references 6782; cleared soft references 0.
GC 2: current heap(KB) 1196680; current threshold(KB) 1048576.
GC 2: collect (milliseconds) 76581.
GC 2: current cycle allocation(KB) 54165; previous cycle allocation(KB) 1048613.
GC 2: total weak references 2318; cleared weak references 33.
GC 2: total final references 23528; cleared final references 21721.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 19:09:01
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 19:15:13
GC 3: collected class sun/reflect/GeneratedMethodAccessor3630385287.
GC 4: starting collection, reason stop the world collection.
GC 3: live objects 1309097; collected objects 5717926; collected(KB) 1021549.
GC 3: queued for finalization 0; total soft references 9700; cleared soft references 0.
GC 3: current heap(KB) 1603768; current threshold(KB) 1048576.
GC 3: collect (milliseconds) 148590.
GC 3: current cycle allocation(KB) 49; previous cycle allocation(KB) 1350524.
GC 3: total weak references 3025; cleared weak references 5.
GC 3: total final references 18457; cleared final references 16313.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 19:17:41
GC 4: collection starting 05/01/08 19:17:41
GC 4: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
GC 4: live objects 1040398; collected objects 2212819; collected(KB) 296348.
GC 4: queued for finalization 0; total soft references 10054; cleared soft references 0.
GC 4: current heap(KB) 1585208; current threshold(KB) 1048576.
GC 4: collect (milliseconds) 2101.
GC 4: current cycle allocation(KB) 49; previous cycle allocation(KB) 0.
GC 4: total weak references 3191; cleared weak references 50.
GC 4: total final references 3574; cleared final references 1377.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 05/01/08 19:17:44
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
Stopping services.
Service rfcengine stopped. (518 ms)
Service ejb stopped. (20000 ms) - Timeout expired.
Service failover stopped. (75 ms)
Service classload stopped. (178 ms)
Service cafumrelgroups~imp stopped. (275 ms)
Service telnet stopped. (13 ms)
Service webdynpro stopped. (57 ms)
Service tceCATTPingservice stopped. (6 ms)
Service shell stopped. (705 ms)
Service jms_provider stopped. (416 ms)
Service com.adobe~TrustManagerService stopped. (341 ms)
Service sld stopped. (62 ms)
Service ssl stopped. (19 ms)
Service tcsecvsi~service stopped. (202 ms)
Service pmi stopped. (743 ms)
Service com.adobe~DocumentServicesDestProtoService stopped. (161 ms)
Service tcsecdestinations~service stopped. (14 ms)
Service com.adobe~DocumentServicesConfiguration stopped. (50 ms)
Service tcsecwssec~service stopped. (66 ms)
Service tcsecsecurestorage~service stopped. (0 ms)
Service keystore stopped. (85 ms)
Service servlet_jsp stopped. (20000 ms) - Timeout expired.
Service dsr stopped. (464 ms)
Service cafummetadata~imp stopped. (68 ms)
Service applocking stopped. (56 ms)
stdout/stderr redirect
node name : server0
pid : 694
system name : GBV
system nr. : 00
started at : Thu May 1 20:02:28 2008
[Thr 1] Thu May 1 20:02:31 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier D45A23E848003900; heap identifier D45A23E848003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 20:02:36
GC 1: live objects 2329; collected objects 1650; collected(KB) 145.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 5484; current threshold(KB) 1048576.
GC 1: collect (milliseconds) 57.
GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 20:02:36
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 1580 ms.
Loading: PoolManager ... 47 ms.
Loading: ApplicationThreadManager ... 348 ms.
Loading: ThreadManager ... 139 ms.
Loading: IpVerificationManager ... 34 ms.
Loading: ClassLoaderManager ... 108 ms.
Loading: ClusterManager ... 1194 ms.
Loading: LockingManager ... 482 ms.
Loading: ConfigurationManager ... 9102 ms.
Loading: LicensingManager ... 62 ms.
Loading: CacheManager ... 761 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (164 ms).
Service cross started. (288 ms).
Service memory started. (332 ms).
Service timeout started. (555 ms).
Service userstore started. (5 ms).
Service file started. (1915 ms).
Service trex.service started. (1695 ms).
Service jmx_notification started. (202 ms).
Service p4 started. (1638 ms).
Service classpath_resolver started. (210 ms).
Service log_configurator started. (41195 ms).
Service locking started. (3 ms).
Service deploy started. (41554 ms).
Service http started. (2008 ms).
Service MigrationService started. (398 ms).
Service bimmrdeployer started. (134 ms).
Service naming started. (2915 ms).
Service failover started. (289 ms).
Service jmsconnector started. (848 ms).
Service javamail started. (836 ms).
Service appclient started. (678 ms).
Service ts started. (981 ms).
Service licensing started. (27 ms).
Service connector started. (2930 ms).
Service configuration started. (983 ms).
Service iiop started. (4286 ms).
Service webservices started. (13478 ms).
Service dbpool started. (24229 ms).
Service com.sap.security.core.ume.service started. (22463 ms).
Service security started. (5515 ms).
Service shell started. (270 ms).
Service tceCATTPingservice started. (60 ms).
Service applocking started. (690 ms).
Service telnet started. (228 ms).
Service classload started. (1409 ms).
Service webdynpro started. (1192 ms).
Service keystore started. (1750 ms).
Service ssl started. (166 ms).
Service jmx started. (2980 ms).
Service dsr started. (2423 ms).
Service tcsecsecurestorage~service started. (1903 ms).
Service tcsecwssec~service started. (1804 ms).
Service ejb started. (9909 ms).
Service cafummetadata~imp started. (9484 ms).
Service basicadmin started. (5061 ms).
Service servlet_jsp started. (12051 ms).
Service com.adobe~DataManagerService started. (5543 ms).
Service com.adobe~LicenseService started. (1450 ms).
Service tcsecdestinations~service started. (9840 ms).
Service com.adobe~DocumentServicesConfiguration started. (4484 ms).
Service rfcengine started. (6033 ms).
Service com.adobe~DocumentServicesBinaries2 started. (2353 ms).
Service tc.monitoring.logviewer started. (14836 ms).
Service pmi started. (998 ms).
Service com.adobe~FontManagerService started. (3991 ms).
Service com.adobe~DocumentServicesDestProtoService started. (2826 ms).
Service com.adobe~PDFManipulation started. (1639 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (2373 ms).
Service com.adobe~TrustManagerService started. (1498 ms).
Service sld started. (18028 ms).
Service CUL started. (17248 ms).
Service apptracing started. (8930 ms).
Service cafumrelgroups~imp started. (15606 ms).
Service adminadapter started. (10318 ms).
Service tcsecvsi~service started. (8219 ms).
Service com.adobe~XMLFormService started. (5849 ms).
Service cafruntimeconnectivity~impl started. (139211 ms).
Service monitor started. (15138 ms).
Service jms_provider started. (52820 ms).
Service com.sap.portal.prt.sapj2ee started. (5383 ms).
Service prtbridge started. (39544 ms).
ServiceManager started for 207093 ms.
Framework started for 221438 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 20:08:08
GC 2: live objects 755454; collected objects 5496751; collected(KB) 930552.
GC 2: queued for finalization 0; total soft references 6634; cleared soft references 0.
GC 2: current heap(KB) 1153380; current threshold(KB) 1048576.
GC 2: collect (milliseconds) 47233.
GC 2: current cycle allocation(KB) 62234; previous cycle allocation(KB) 1048576.
GC 2: total weak references 2795; cleared weak references 28.
GC 2: total final references 17170; cleared final references 15377.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 20:08:56
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 20:11:21
GC 3: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
GC 3: live objects 1246857; collected objects 6993092; collected(KB) 1017416.
GC 3: queued for finalization 0; total soft references 9636; cleared soft references 0.
GC 3: current heap(KB) 1399752; current threshold(KB) 1048576.
GC 3: collect (milliseconds) 10774.
GC 3: current cycle allocation(KB) 42367; previous cycle allocation(KB) 1048625.
GC 3: total weak references 3387; cleared weak references 10.
GC 3: total final references 11622; cleared final references 9210.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 20:11:32
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.iviewservice
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.netweaver.bc.util
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.api_portalpcm
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcd.glservice
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcm.admin.apiservice
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.config
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.usermanagement
May 1, 2008 8:11:42 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.api_landscape
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcd.glservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.contentmigration.contentmigrationservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.httpconnectivity.urlfetcherservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.connectorservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.application.jcoclient
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.systemlandscapeservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.iviewservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.themes.designservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.themes.lafservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.productivity.resolverservice
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.config
May 1, 2008 8:11:56 PM com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/irj
SAP J2EE Engine Version 7.00 PatchLevel is shutting down! PatchLevel September 11, 2006 16:35 GMT
Stopping services.
Service com.sap.portal.prt.sapj2ee stopped. (176 ms)
Service com.adobe~DocumentServicesLicenseSupportService stopped. (818 ms)
Service sld stopped. (118 ms)
Service com.adobe~DocumentServicesBinaries2 stopped. (259 ms)
Service rfcengine stopped. (92 ms)
Service cafumrelgroups~imp stopped. (50 ms)
Service cafummetadata~imp stopped. (71 ms)
GC 4: starting collection, threshold allocation reached.
GC 4: collection starting 05/01/08 20:59:48
Service applocking stopped. (410 ms)
Service com.adobe~LicenseService stopped. (29 ms)
Service tc.monitoring.logviewer stopped. (5966 ms)
Service com.adobe~TrustManagerService stopped. (205 ms)
Service com.adobe~XMLFormService stopped. (312 ms)
Service com.adobe~FontManagerService stopped. (193 ms)
Service com.adobe~PDFManipulation stopped. (335 ms)
Service com.adobe~DocumentServicesDestProtoService stopped. (330 ms)
Service com.adobe~DataManagerService stopped. (337 ms)
Service com.adobe~DocumentServicesConfiguration stopped. (20 ms)
Service monitor stopped. (11508 ms)
Service adminadapter stopped. (10 ms)
Service basicadmin stopped. (435 ms)
Service CUL stopped. (29 ms)
Service apptracing stopped. (316 ms)
Service jms_provider stopped. (441 ms)
Service prtbridge stopped. (43 ms)
Service jmx stopped. (11 ms)
stdout/stderr redirect
node name : server0
pid : 694
system name : sid
system nr. : 00
started at : Thu May 1 21:07:00 2008
[Thr 1] MtxInit: -2 0 0
GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier EBD4A45A98003900; heap identifier EBD4A45A98003900.
GC 1: starting collection, reason external thread attached.
GC 1: collection starting 05/01/08 21:07:06
GC 1: live objects 2311; collected objects 1655; collected(KB) 146.
GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
GC 1: current heap(KB) 5484; current threshold(KB) 1048576.
GC 1: collect (milliseconds) 60.
GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4155.
GC 1: total weak references 0; cleared weak references 0.
GC 1: total final references 6; cleared final references 0.
GC 1: total phantom references 0; cleared phantom references 0.
GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
GC 1: collection ending 05/01/08 21:07:06
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 1458 ms.
Loading: PoolManager ... 43 ms.
Loading: ApplicationThreadManager ... 393 ms.
Loading: ThreadManager ... 92 ms.
Loading: IpVerificationManager ... 42 ms.
Loading: ClassLoaderManager ... 135 ms.
Loading: ClusterManager ... 698 ms.
Loading: LockingManager ... 257 ms.
Loading: ConfigurationManager ... 6882 ms.
Loading: LicensingManager ... 39 ms.
Loading: CacheManager ... 992 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (106 ms).
Service runtimeinfo started. (814 ms).
Service memory started. (1000 ms).
Service cross started. (986 ms).
Service timeout started. (1112 ms).
Service userstore started. (237 ms).
Service jmx_notification started. (282 ms).
Service file started. (2739 ms).
Service trex.service started. (2105 ms).
Service p4 started. (6490 ms).
Service classpath_resolver started. (614 ms).
Service log_configurator started. (41399 ms).
Service locking started. (14 ms).
Service http started. (3587 ms).
Service naming started. (4369 ms).
Service failover started. (278 ms).
Service appclient started. (976 ms).
Service javamail started. (1537 ms).
Service jmsconnector started. (1752 ms).
Service ts started. (2010 ms).
Service licensing started. (69 ms).
Service deploy started. (44892 ms).
Service connector started. (4269 ms).
Service MigrationService started. (657 ms).
Service bimmrdeployer started. (119 ms).
Service iiop started. (5427 ms).
Service configuration started. (1895 ms).
Service webservices started. (18814 ms).
Service dbpool started. (21073 ms).
Service com.sap.security.core.ume.service started. (41934 ms).
Service security started. (9841 ms).
Service applocking started. (991 ms).
Service shell started. (1442 ms).
Service classload started. (1888 ms).
Service tceCATTPingservice started. (250 ms).
Service telnet started. (763 ms).
Service webdynpro started. (1402 ms).
Service keystore started. (4630 ms).
Service ssl started. (240 ms).
Service tcsecsecurestorage~service started. (1102 ms).
Service dsr started. (3796 ms).
Service ejb started. (8102 ms).
Service servlet_jsp started. (6737 ms).
Service jmx started. (5763 ms).
Service tcsecwssec~service started. (2560 ms).
Service basicadmin started. (2749 ms).
Service cafummetadata~imp started. (12205 ms).
Service com.adobe~LicenseService started. (845 ms).
Service adminadapter started. (1835 ms).
Service prtbridge started. (7226 ms).
Service cafumrelgroups~imp started. (3700 ms).
Service com.sap.portal.pcd.gl started. (52 ms).
Service CUL started. (13400 ms).
Service monitor started. (10580 ms).
Service tc.monitoring.logviewer started. (16568 ms).
Service com.sap.portal.prt.sapj2ee started. (642 ms).
Service rfcengine started. (23940 ms).
Service com.adobe~DataManagerService started. (23670 ms).
Service com.adobe~DocumentServicesBinaries2 started. (760 ms).
Service com.adobe~DocumentServicesConfiguration started. (22272 ms).
Service apptracing started. (20484 ms).
Service com.adobe~PDFManipulation started. (776 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (1062 ms).
Service com.adobe~FontManagerService started. (1476 ms).
Service tcsecdestinations~service started. (30901 ms).
Service sld started. (32153 ms).
Service cafruntimeconnectivity~impl started. (172286 ms).
Service pmi started. (310 ms).
Service com.adobe~TrustManagerService started. (358 ms).
Service com.adobe~DocumentServicesDestProtoService started. (583 ms).
Service com.adobe~XMLFormService started. (3334 ms).
Service tcsecvsi~service started. (2789 ms).
Service jms_provider started. (41330 ms).
ServiceManager started for 202642 ms.
Framework started for 214111 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel September 11, 2006 16:35 GMT
>
Login :GC 2: starting collection, threshold allocation reached.
GC 2: collection starting 05/01/08 21:12:43
GC 2: live objects 821653; collected objects 5507929; collected(KB) 930171.
GC 2: queued for finalization 0; total soft references 6661; cleared soft references 0.
GC 2: current heap(KB) 1411040; current threshold(KB) 1048576.
GC 2: collect (milliseconds) 70928.
GC 2: current cycle allocation(KB) 342021; previous cycle allocation(KB) 1048597.
GC 2: total weak references 2851; cleared weak references 22.
GC 2: total final references 17577; cleared final references 15585.
GC 2: total phantom references 0; cleared phantom references 0.
GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
GC 2: collection ending 05/01/08 21:13:54
GC 3: starting collection, threshold allocation reached.
GC 3: collection starting 05/01/08 21:15:55
GC 3: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
GC 3: live objects 1141518; collected objects 7001492; collected(KB) 1015923.
GC 3: queued for finalization 0; total soft references 9542; cleared soft references 0.
GC 3: current heap(KB) 1478764; current threshold(KB) 1048576.
GC 3: collect (milliseconds) 4943.
GC 3: current cycle allocation(KB) 18409; previous cycle allocation(KB) 1048578.
GC 3: total weak references 3416; cleared weak references 10.
GC 3: total final references 11311; cleared final references 8870.
GC 3: total phantom references 0; cleared phantom references 0.
GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
GC 3: collection ending 05/01/08 21:16:00
GC 4: starting collection, threshold allocation reached.
GC 4: collection starting 05/01/08 21:19:12
GC 4: live objects 1712827; collected objects 9309307; collected(KB) 995205.
GC 4: queued for finalization 0; total soft references 10433; cleared soft references 0.
GC 4: current heap(KB) 1791312; current threshold(KB) 1048576.
GC 4: collect (milliseconds) 12627.
GC 4: current cycle allocation(KB) 83189; previous cycle allocation(KB) 1048615.
GC 4: total weak references 4320; cleared weak references 42.
GC 4: total final references 15130; cleared final references 12235.
GC 4: total phantom references 0; cleared phantom references 0.
GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
GC 4: collection ending 05/01/08 21:19:25
GC 5: starting collection, threshold allocation reached.
GC 5: collection starting 05/01/08 21:20:48
GC 5: live objects 1995994; collected objects 11111932; collected(KB) 1029776.
GC 5: queued for finalization 0; total soft references 10641; cleared soft references 0.
GC 5: current heap(KB) 1980804; current threshold(KB) 1048576.
GC 5: collect (milliseconds) 8913.
GC 5: current cycle allocation(KB) 66502; previous cycle allocation(KB) 1049216.
GC 5: total weak references 4535; cleared weak references 4.
GC 5: total final references 14318; cleared final references 11227.
GC 5: total phantom references 0; cleared phantom references 0.
GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
GC 5: collection ending 05/01/08 21:20:57
GC 6: starting collection, threshold allocation reached.
GC 6: collection starting 05/01/08 21:22:45
GC 6: live objects 1953332; collected objects 6193794; collected(KB) 1035355.
GC 6: queued for finalization 0; total soft references 11241; cleared soft references 0.
GC 6: current heap(KB) 2028284; current threshold(KB) 1048576.
GC 6: collect (milliseconds) 4005.
GC 6: current cycle allocation(KB) 53049; previous cycle allocation(KB) 1049147.
GC 6: total weak references 5352; cleared weak references 1.
GC 6: total final references 8606; cleared final references 5381.
GC 6: total phantom references 0; cleared phantom references 0.
GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
GC 6: collection ending 05/01/08 21:22:49
GC 7: starting collection, threshold allocation reached.
GC 7: collection starting 05/01/08 21:23:36
GC 7: live objects 1990485; collected objects 5358483; collected(KB) 1045077.
GC 7: queued for finalization 0; total soft references 12197; cleared soft references 0.
GC 7: current heap(KB) 2081188; current threshold(KB) 1048576.
GC 7: collect (milliseconds) 2336.
GC 7: current cycle allocation(KB) 51278; previous cycle allocation(KB) 1048587.
GC 7: total weak references 6594; cleared weak references 0.
GC 7: total final references 5444; cleared final references 2179.
GC 7: total phantom references 0; cleared phantom references 0.
GC 7: total JNI global weak references 0; cleared JNI global weak references 0.
GC 7: collection ending 05/01/08 21:23:38
GC 8: starting collection, threshold allocation reached.
GC 8: collection starting 05/01/08 21:24:01
GC 8: live objects 2324130; collected objects 5128151; collected(KB) 1046573.
GC 8: queued for finalization 0; total soft references 12474; cleared soft references 0.
GC 8: current heap(KB) 2047444; current threshold(KB) 1048576.
GC 8: collect (milliseconds) 5092.
GC 8: current cycle allocation(KB) 133699; previous cycle allocation(KB) 1048650.
GC 8: total weak references 6957; cleared weak references 0.
GC 8: total final references 4232; cleared final references 831.
GC 8: total phantom references 0; cleared phantom references 0.
GC 8: total JNI global weak references 0; cleared JNI global weak references 0.
GC 8: collection ending 05/01/08 21:24:06
GC 9: starting collection, threshold allocation reached.
GC 9: collection starting 05/01/08 21:24:27
GC 9: live objects 2268890; collected objects 5671964; collected(KB) 1057910.
GC 9: queued for finalization 0; total soft references 13224; cleared soft references 0.
GC 9: current heap(KB) 2073064; current threshold(KB) 1048576.
GC 9: collect (milliseconds) 4319.
GC 9: current cy -
Hello Folks,
I have been facing this error for some time now, I've tried repeating and restarting SDM deployment but just doesn't wok.
Its the BP for ESS that I'm trying to deploy for PCD.
Can some one suggest how to fix this please.
Best regards
Sandeep.
===========================================================================
Deployment started Thu Jun 05 19:20:57 PDT 2008
===========================================================================
Starting Deployment of com.sap.pct.employee
Aborted: development component 'com.sap.pct.employee'/'sap.com'/'SAP AG'/'60.2.20050321200422.0000'/'1', grouped by software component 'BP_ERP4ESS'/'sap.com'/'SAP AG'/'1000.60.2.0.0.20050419020715''/'1':
Caught exception during module deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: Unable to lookup the Deploy Service. java.lang.ClassCastException
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment of com.sap.pct.employee finished with Error (Duration 3079 ms)
Starting Deployment of BP_ERP4ESS
Aborted: software component 'BP_ERP4ESS'/'sap.com'/'SAP AG'/'1000.60.2.0.0.20050419020715''/'1':
Failed deployment of SDAs:
development component 'com.sap.pct.employee'/'sap.com'/'SAP AG'/'60.2.20050321200422.0000'/'1' : aborted
Please, look at error logs above for more information!
Deployment of BP_ERP4ESS finished with Error (Duration 3093 ms)Hello Sandeep,
Tell me what is your portal version ( NW2004 or 2004s) and SP level ?
upgrade you SP (mainly J2ee engine and JSPM) level and try again.
- Pratap -
<h5>Good Morning Gentleman,</h5>
<h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
<h5>20120228122646 Info :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
20120228122646 Info :start deployment of archives:http://sapsps.sonaesierra.com:50004
20120228122646 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy225.performDirectDeployment(Unknown Source)
at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20120228122646 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
<h5>I'm new to NWDI and related subjects. I've already checked:</h5>
<h5>1. Port 50004 is available in the productive system</h5>
<h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
<h5>3. j2ee_admin isn't locked in productive system</h5>
<h5>What more should i check? What could be the reason behind this error?</h5>
<h5>Thank you.</h5>
<h5>Best Regards,</h5>
<h5>Pedro Gaspar</h5>Good Morning Kumar,
If i tell you what happened you're going to laugh... But i'll tell you anyway.
After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
The difference a message and the browser version can do in your life
Thanks for your reply, which helped me solve the problem.
Best Regards,
Pedro Gaspar -
Hi all
I have a setup of SAP ECC 6.0 with both ABAP stack and JAVA stack installed.
I can see the JAVA Stack running as well as I can see the SDM also running fine.
inside my NWDS when i insert the server details I can see the server showing me GREEN icons
when I try to deploy my webdynpro application it tells me for SDM password.
When I put the password it shows
Deployment error occurs when deploying from IDE, the following message is displayed:
Server XXX did not accept login request as admin on port 50018
Details: ERROR: Could not establish connection to server XXX at port
50018: XXX
I have changed the SDM password and then also it giving me the same error.
Can someone help me on this issue as I am unable to find a solution of this.
Regards
JMi feel i have a unique problem where no one can still cant solve this problem.
i am trying everything you all tell me but still i am stuck up there only
still i am getting the same error
Deployment exception : Server xx.xx.xx.xx did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server xx.xx.xx.xx at port 50018: Connection timed out: connect
Inner exception was :
Server xx.xx.xx.xx did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server xx.xx.xx.xx at port 50018: Connection timed out: connect
can one tell me is there any way to solve this.......
Regards
Janak Mehta -
J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0
Hi,
We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
The BEX WAD had the error " Java communication error"
" An Error occured during communication with the BI Components of the J2ee engine"
We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
Kindly help asap.
Trace:
SDM:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
J2ee Engine:
Error while connecting
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)Hi Anup,
The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
However, after restart, when we try to deploy again, the deploy fails saying the same msg
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
Any clues ?
Regards
Venkat. -
Deployment error using CMS (Component is not a SCA but a SDA)
I haven't seen this message before on the forum so I thought I'd see if anyone else has run into this. My landscape is as follows:
Runtime System: NW04 SP14
JDI System: NW04 SP19
SAP SCA plugins: NW04 SP14
Application: Standard web dynpro with 2 DC's (one for model and one for application)
Landscape: Dev (no runtime), Cons (no runtime), Test (runtime), Production (runtime)
I have migrated my local development of these DC's into the JDI following the standard help documentation for migrating web dynpros. Everything went smoothly (no errors during build in Dev and Cons, Assembly went fine).
I am at the point of attempting to import my new SCA into the Test runtime environment using standard CMS. I first imported the SAP_BUILDT, SAP_JEE, and SAP_TECHS into test. This imported fine and from my understanding nothing will deploy for these so all is good. When I import my SCA, the SDM-deploy step issues the following fatal error:
<b>Info:Starting Step SDM-deploy at 2007-04-06 11:44:20.0344 -7:00
Info:start deployment of archives to SDM:http://myserver:50018
Info:The following archives will be deployed (on http://myserver:50018)
Info:E:\usr\sap\JTrans\CMS\archives\pcbp.comVMRSJDV_VMRS_C~20070406171501.sca
Fatal:Unexpected exception 'Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.' occurred. Stopping processing.
Fatal Exception:java.lang.IllegalArgumentException: Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.:Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.
java.lang.IllegalArgumentException: Component [Name: vmrs , Vendor: pcbp.com] is not a SCA, but a SDA.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
.....</b>
Has anyone seen this message before or have any thoughts as to what may be the issue? I have searched the forums and OSS for the "Component is not a SCA but a SDA" message and have been unsucessful. I have validated that the archive is in fact packaged as an SCA file. I attempted to rename it from the file system to a .sda to see what would happen but that was not successful. One more bit of info that may be helpful is that there may have been a previous application deployed on the runtime environment with the same name. Prior to attempting to deploy the JDI version, I had removed the app (the non JDI one) from the server using the Deploy service of Visual Administrator so there shouldn't be a conflict there right?
Message was edited by:
Eric Vota
I think I figured this out. When I remove the application via the Visual Admin deploy service it does not synchronize with the SDM. For that reason, the old application (which was a deployed SDA) was still in the SDM repository. I am in process of using the SDM deploy tool to remove the offending application. After that I will attempt to reimport the SCA via the CMS. Hopefully this works. I'll update the post with the result in case anyone else has this problem.This was fixed by undeploying from the SDM instead of from Visual Admin. Good to go now
-
SDM Deployment fails - Dependency caf/core/ear missing
crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
deploying a DC from NWDS into SDM the following Exception is thrown:
07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
002Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
<!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
<!PATTERNhttp://sdmcl20080107151422.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGUTF8/>
<!LOGHEADEREND/>
Jan 7, 2008 4:14:22 PM Info:
Starting deployment
Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
dependency:
name: 'caf/core/ear'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
system:
sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
I checked http://<srv>/sap/monitoring/ComponentInfo
the missing 'caf/core/ear' is not listed, however several other CAFs are:
sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
etc....
Is it possible to deploy this missing caf-ear component supplementary?
I have the strange feelings caf/core/ear is something 7.1 CE only related....
thanks for any hint!
kaiKai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
Regards,
\-- Vladimir -
Java Server Proxy---Deployment error?
I am trying the scenario from this blog
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
I am getting deployment error
May 30, 2006 1:39:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp57679JPS_EAR.ear
Deployment exception : Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
Inner exception was :
Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
Help me
ThanksHi Saru,
It seems u dont have the correct sdm password or someone has changed the sdm password.It has not accepted the credentials u have given during deployment.
Check with all Sap enterprise portal settings in the prefernces/NWDS
The host name,alias,port
If not done with
Try to change the sdm password using this Password trouble in SDM
restart server again after changes
even try
- Stop nd restart the sdm from yor NWDS and deploy once again
Thanks,
Swathi
Do offer pts:-) -
Deployment Error when transporting to TEST server
Hi experts,
I'm having a deployment error when transporting my dc from development server to test server using the Change Management Service - Transport Studio.
In the error message, there is the mention of the following sentence:
=============================================
Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine ?
=============================================
But the dc is using only the standard default dcs like:
com.sap.aii.proxy.framework (default)
com.sap.aii.util.misc (default)
com.sap.exception (default)
com.sap.mw.jco (default)
tc/cmi (default)
tc/ddic/ddicruntime (default)
td/ddic/metamodel/content (default)
tc/logging (default)
tc/wd/webdynpro (default)
tc/wdp/metamodel/content (default)
So could these dcs not have been deployed on the test server ?
How do we confirm this ?
Thanks in advance.
Rgds,
DanielA dump of the exception i m getting.
Anyone has a clue or advice of how to overcome this problem ?
20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: Starting: Update: Selected development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' updates currently deployed development component 'appl/main'/'com.diagonal'/'LOKAL'/'0.2006.01.12.14.18.23'/'0'.
20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: SDA to be deployed: /usr/sap/WS5/JC00/SDM/root/origin/com.diagonal/appl/main/dev_devcias_C/0/823/appl~main.sda
20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: Software type of SDA: J2EE
20081107165952 Info :Nov 7, 2008 4:46:03 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Begin of log messages of the target system:
20081107165952 Info :08/11/07 16:46:03 - ***********************************************************
20081107165952 Info :08/11/07 16:46:04 - Start updating EAR file...
20081107165952 Info :08/11/07 16:46:04 - start-up mode is lazy
20081107165952 Info :08/11/07 16:46:04 - EAR file updated successfully for 70ms.
20081107165952 Info :08/11/07 16:46:04 - Start updating...
20081107165952 Info :08/11/07 16:46:06 - EAR file uploaded to server for 861ms.
20081107165952 Info :08/11/07 16:46:07 - ERROR: Not updated. Deploy Service returned ERROR:
20081107165952 Info : java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
20081107165952 Info : Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
20081107165952 Info : com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
20081107165952 Info : at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
20081107165952 Info : at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
20081107165952 Info : at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
20081107165952 Info : at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
20081107165952 Info : at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
20081107165952 Info : at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
20081107165952 Info : at java.security.AccessController.doPrivileged(AccessController.java:215)
20081107165952 Info : at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
20081107165952 Info : at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
20081107165952 Info : Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info : at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1050)
20081107165952 Info : at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1281)
20081107165952 Info : at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
20081107165952 Info : at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
20081107165952 Info : at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
20081107165952 Info : at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
20081107165952 Info : at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
20081107165952 Info : at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
20081107165952 Info : ... 10 more
20081107165952 Info : For detailed information see the log file of the Deploy Service.
20081107165952 Info :08/11/07 16:46:07 - ***********************************************************
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: End of log messages of the target system.
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
20081107165952 Info :Nov 7, 2008 4:46:07 PM Error: Aborted: development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0', grouped by :
20081107165952 Info :Caught exception during application deployment from SAP J2EE Engine's deploy service:
20081107165952 Info :java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
20081107165952 Info :Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
20081107165952 Info : com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info : (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting to save the repository
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Finished saving the repository
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting: Update: Selected software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0' updates currently deployed software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.0.0.20061122075934''/'1'.
20081107165952 Info :Nov 7, 2008 4:46:07 PM Error: Aborted: software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0':
20081107165952 Info :Failed deployment of SDAs:
20081107165952 Info :development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' : aborted
20081107165952 Info :Please, look at error logs above for more information!
20081107165952 Info :Nov 7, 2008 4:46:07 PM Info: Starting to save the repository
20081107165952 Info :Nov 7, 2008 4:46:08 PM Info: Finished saving the repository
20081107165952 Info :Nov 7, 2008 4:46:08 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
20081107165952 Info :Nov 7, 2008 4:46:08 PM Error: -
At least one of the Deployments failed -
20081107165952 Info :end of log
20081107165952 Info :RC of deployment: 12
20081107165952 Info :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2008-11-07 16:59:52.0155 +9:00 -
Deployment Error on sap-j2ee engine
Hi
I build an EJB project,Web project and added these to EAR project and built an '.ear' file. When i tried to deploy on sapj2ee engine. I got the following deployment error.
My j2ee engine is up and running. What went wrong?
Help me,
Thanks
==========
May 24, 2006 5:39:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.24.15.58.19':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear: JCP_EJB.jar,Please check the ear content.
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item abortedHi Amol!
The password is admin for SDM, i redployed by building '.ear' file again.
You suggested to deploy the ear file on SDM remote gui, how to do that?
help me
Thanks
==========
I got the error as:
May 25, 2006 11:22:11 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.25.11.17.51':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear: JCP_EJB.jar,Please check the ear content.
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item aborted -
Hello everybody i have a problem with my SAP ERP Installation the Error is :
An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
Jan 19, 2010 7:34:14 AM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: Ending deployment prerequisites. All items are correct.
Jan 19, 2010 7:35:49 AM Info: Saved current Engine state.
Jan 19, 2010 7:35:49 AM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
Jan 19, 2010 7:35:49 AM Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
Jan 19, 2010 7:35:49 AM Info: Software type of SDA: J2EE
Jan 19, 2010 7:35:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Info: Begin of log messages of the target system:
10/01/19 07:35:50 - ***********************************************************
10/01/19 07:35:51 - Start updating EAR file...
10/01/19 07:35:51 - start-up mode is lazy
10/01/19 07:35:51 - EAR file updated successfully for 47ms.
10/01/19 07:35:51 - Start deploying ...
10/01/19 07:35:51 - EAR file uploaded to server for 32ms.
10/01/19 07:35:56 - ERROR: NOT deployed. The Deploy Service returned the following error:
For detailed information see the log file of the Deploy Service.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
at java.lang.Thread.run(Thread.java:534)
10/01/19 07:35:56 - ***********************************************************
Jan 19, 2010 7:35:56 AM Info: End of log messages of the target system.
Jan 19, 2010 7:35:56 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jan 19, 2010 7:35:56 AM Info: Starting to save the repository
Jan 19, 2010 7:35:57 AM Info: Finished saving the repositoryHi,
Check below thread:
/message/441671#441671 [original link is broken]
Thanks
Sunny -
WD app Deployment Error - Where can we find J2ee log file for linux install
Hi,
I have a problem with deploying a web dynpro application. There are no errors before deployment but when I deploy the application, I get a deployment error with the following description.
I tried to view the trace or log file but we have SAP installed on a linux OS and I do not know where can we see the log or trace file. Please help.
Version:
SAP NW 2004s SP15
NWDS 7.0
xRPM 4.5
Error Description:
May 14, 2008 12:49:50 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager)
[Thread[Deploy Thread,5,main]] ERROR:
[008]Deployment aborted
Settings
SDM host : BS307
SDM port : 50718
URL to deploy : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Result
=> deployment aborted : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Aborted: development component 'SempraDemo4.5'/'local'/'LOKAL'/'0.2008.05.14.00.49.36'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application local/SempraDemo4.5.. Reason: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Edited by: Subramanya Srinivas Mullapudi on May 14, 2008 8:34 AMHi Reza,
Hope you are doing good.
You can set the trace level in the SAP/Java Gui dynamically :
Call transaction SMICM
Choose the menu Goto → Trace Level → Set
In the pop-up window, set the desired level (0,1,2,3)
To switch on an /nSMICM or ICM HTTP trace via command line you should go to
usr\sap\<SID>\<instance_number>\exe directory and run the icmon program with the following command:
icmon◦◦pf=\usr\sap\<SID>\SYS\profile\<SID>_<instance_name>_<HOST>
where you fill in the SID, instance name and host corresponding to your system.
The icmon program is interactive and to increase trace level you must write
"+" and pres enter.To quit you must write "q" and press enter.
The trace will be written◦to the following file: usr\sap\<SID>\<instance_number>\work\dev_icm
Thank you!
Kind Regards,
Hemanth
SAP AGS
Maybe you are looking for
-
It keeps saying my username or password is wrong no matter how many times I reset my password.
Hi there, please help. I am an existing Spotify user who was on PC. Then I moved to Macbook and just install spotify on my both iPad and macbook. I logged in the first time it said wrong username or password. Thereafter I have reset my password few t
-
CS6 Photoshop asked do I want to load previous settings from CS5.5
How do I get all the features in CS6 back as when I installed it it asked did I want to load previous settings. As I didn't know what this ment I said yes, now I don't have things like the new perspective tool. How do I reload these features?
-
I upgraded to io7 on my iphone 4s. I recieve text messages with pictures. I forward the pictures to my email address it sends but I never get them. I always was able to do this before the upgrade. Can anyone help me? Thanks
-
Explain with this example abt cenvat details?
can u plz explain with this example Purchase Order (P.O) (We give Vendor No, Rate, Material, Tax Code) ***Basic Amount 100.00*** ***Excise Duty @ 16% 16.00*** o + 116.00*** ***VAT@ 4% 5.00*** ***(On Basic + Excise) 121.00***
-
IPhone videos showing up sideways.
Videos taken in portrait mode with iPhone and imported to iTunes are now showing up in landscape (sideways) on the iPhone and do not rotate. They used to show up the way they were taken. Any ideas why? and how to fix this? I don't have quicktime pro