PI7.1 EHP1 Java suppor packages LM-CORE Deployment ERROR
Hi,
I have installed PI7.1 EHP1 on Linux X86_64 /oracle 11.
Successfully Updated the ABAP Stack support packages to 7.11 SPS07 thru
SPAM, but During Java stack thru JSPM i have encountered follwoing
error for LS-CORE
7.11.7.3.
Error: 1. Item is skipped because of failed deployment of the item
sap.com_tclmwebadminflexstateview and because the applied error
strategy is oneErrorstop 1. Contains Aborted Deployment Component
sap.com_tclmwebadminflexstateview .
LOG::
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[/usr/sap/JXD/DVEBMGS00/j2ee/JSPM/log/log_2011_09_22_20_20_06/deploy_2011-09-22_20-56-07.log]/>
<!PATTERN[deploy_2011-09-22_20-56-07.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Sep 22, 2011 8:56:07 PM [Info ]:DC API is trying to connect to 'SJXD0001:50004'
Sep 22, 2011 8:56:07 PM [Info ]:DC API has Connected to 'SJXD0001:50004'
Sep 22, 2011 8:56:07 PM [Info ]:+++++ Starting D E P L O Y action +++++ [ deployerId=5 ] [ timerId=177]
Sep 22, 2011 8:56:07 PM [Info ]:Selected archives for deployment. [ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA
Sep 22, 2011 8:56:07 PM [Info ]:DC API got Session id='161',time:[id:#177, elapsed: 23 ms.].[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:component version handling rule is UpdateLowerOrChangedVersionsOnly.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:deployment workflow strategy is safety deploy strategy.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=5 ]
Sep 22, 2011 8:56:07 PM [Info ]:Error strategies[ deployerId=5 ]:
Sep 22, 2011 8:56:07 PM [Info ]:error action 'DeploymentAction' is 'OnErrorStop'
Sep 22, 2011 8:56:07 PM [Info ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Sep 22, 2011 8:56:09 PM [Info ]:clusterRestartTriggered for transactionId:161, clusterEventAction:cluster restart triggered
Sep 22, 2011 8:56:09 PM [Info ]:Caught exception [P4ConnectionException]. Because cluster restart has been triggered beforehand, assuming a cluster restart.
Sep 22, 2011 8:56:09 PM [Info ]:+++ Server is being restarted +++. The currently set engine start timeout is: 7200 seconds.
Sep 22, 2011 8:56:09 PM [Info ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
Sep 22, 2011 8:56:25 PM [Info ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
Sep 22, 2011 8:56:41 PM [Info ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
Sep 22, 2011 8:56:57 PM [Info ]:+++ Wait for server response +++. Elapsed: 48 seconds. Remainig to timeout 7151 seconds.
Sep 22, 2011 8:57:13 PM [Info ]:+++ Wait for server response +++. Elapsed: 64 seconds. Remainig to timeout 7135 seconds.
Sep 22, 2011 8:57:26 PM [Info ]:Wait for the operation 'Deploying' to finish
Sep 22, 2011 8:57:28 PM [Info ]:Assuming a subsequent restart of the server due to exception: [P4ConnectionException], message: Error. Check your available working servers. Error message: the requested server is not available
Sep 22, 2011 8:57:28 PM [Error ]:[ Exception ]::Unexpected exception during the notification of cluster listeners
Sep 22, 2011 8:57:28 PM [Info ]:+++ Wait for server response +++. Elapsed: 0 seconds. Remainig to timeout 7200 seconds.
Sep 22, 2011 8:57:45 PM [Info ]:+++ Wait for server response +++. Elapsed: 16 seconds. Remainig to timeout 7183 seconds.
Sep 22, 2011 8:58:01 PM [Info ]:+++ Wait for server response +++. Elapsed: 32 seconds. Remainig to timeout 7167 seconds.
Sep 22, 2011 8:58:18 PM [Info ]:+++ Wait for server response +++. Elapsed: 49 seconds. Remainig to timeout 7150 seconds.
Sep 22, 2011 8:58:36 PM [Info ]:Obtaining the deployment result from the server ...
Sep 22, 2011 8:58:37 PM [Info ]:Deployment result
Sorted Items -
1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcsld~data.sda'
Deploy status is 'Skipped'
SDA : name 'tcslddata', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('FS', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
2. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
Deploy status is 'Skipped'
SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
3. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
Deploy status is 'Skipped'
SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
4. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
Deploy status is 'Skipped'
SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
5. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
Deploy status is 'Skipped'
SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
6. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
Deploy status is 'Skipped'
SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
7. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjebasicadminsapcontrolapp.sda'
Deploy status is 'Skipped'
SDA : name 'tcjebasicadminsapcontrolapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-ADM', dependencies :[( name 'tcjmx', vendor 'sap.com') , ( name 'adminadapter', vendor 'sap.com') , ( name 'tcjebasicadminsapcontrol~lib', vendor 'sap.com') ]
8. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~com.sap.engine.customizing.ccms.sda'
Deploy status is 'Skipped'
SDA : name 'com.sap.engine.customizing.ccms', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826155427.0000', software type ('J2EE', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'monitor', vendor 'sap.com') , ( name 'tcjmx', vendor 'sap.com') , ( name 'rfcengine', vendor 'sap.com') , ( name 'tcmonitoring~api', vendor 'sap.com') , ( name 'monitortree', vendor 'sap.com') ]
9. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexflexcommons.sda'
Deploy status is 'Skipped'
SDA : name 'tclmwebadminflexflex_commons', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
10. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
Deploy status is 'Aborted'
SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
11. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
Deploy status is 'Skipped'
SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
12. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
Deploy status is 'Skipped'
SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
13. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.dbcontent.sda'
Deploy status is 'Skipped'
SDA : name 'com.sap.sl.ut.jddi.content', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('DBSC', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.sl.ut.jddi.schema', vendor 'sap.com') ]
14. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
Deploy status is 'Aborted'
SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
Deployment Items -
1. Client path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA'
Deploy status is 'Aborted'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop
1. Contains Aborted deployment component:
sap.com_tclmwebadminflexstateview'.
SCA : name 'LM-CORE', vendor 'sap.com', location 'SAP AG', version '1000.7.11.7.3.20110829165900'
Composite Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
Contained DCs:
1.1 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_ear.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823093938.0000
2. Already deployed component has version:7.1107.20110823093938.0000'.
SDA : name 'tcsldcds~wsproxy_ear', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.2 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.namealloc.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110711084722.0000
2. Already deployed component has version:7.1107.20110711084722.0000'.
SDA : name 'com.sap.lcr.namealloc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.3 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctc~interface_lib.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823083938.0000
2. Already deployed component has version:7.1107.20110823083938.0000'.
SDA : name 'tclmctc~interface_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.4 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcslddpj2ee.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823093938.0000
2. Already deployed component has version:7.1107.20110823093938.0000'.
SDA : name 'tcslddp~j2ee', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.5 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.util.monitor.grmg.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110309073123.0000
2. Already deployed component has version:7.1107.20110309073123.0000'.
SDA : name 'com.sap.util.monitor.grmg', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.6 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> apptracing.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110826165427.0000
2. Already deployed component has version:7.1107.20110826165427.0000'.
SDA : name 'apptracing', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
versions : 31
3.Persist in storage : 11
1.22 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~cdsclient_lib.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823093938.0000
2. Already deployed component has version:7.1107.20110823093938.0000'.
SDA : name 'tcsldcds~cdsclient_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.23 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.com~sl.ut.infoprovider.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'sl.ut.infoprovider', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('library', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') ]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.24 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldcds~wsproxy_lib.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823093938.0000
2. Already deployed component has version:7.1107.20110823093938.0000'.
SDA : name 'tcsldcds~wsproxy_lib', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.25 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> monitortree.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110826155427.0000
2. Already deployed component has version:7.1107.20110826155427.0000'.
SDA : name 'monitortree', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.26 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.lcr.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110823093938.0000
2. Already deployed component has version:7.1107.20110823093938.0000'.
SDA : name 'com.sap.lcr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.27 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcrprof~rprof_tbl.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'tcrprofrprof_tbl', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('JDDSCHEMA', sub type ''), csn component 'BC-CCM-SLD', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.28 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtcmonitoring~sda.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110826155427.0000
2. Already deployed component has version:7.1107.20110826155427.0000'.
SDA : name 'tcmonitoringsda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.29 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmctcutilinfra_lib.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'tclmctcutilinfra_lib', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823083938.0000', software type ('library', sub type ''), csn component 'BC-INS-CTC', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.30 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexstateview.sda'
Deploy status is 'Aborted'
Description:'1. CFS Container reported an error. Check the causing exceptions for the reason for failure.
-> [ERROR CODE DPL.CFS.0301] Error while notifying bootstrap about component "sap.com/tclmwebadminflexstateview". Collected error messages are: Collected bootstrap error messages ( appName:sap.com/tclmwebadminflexstateview) :
/usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/AC_OETags.js (No such file or directory)
/usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.html (No such file or directory)
/usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/ComponentStateView.swf (No such file or directory)
/usr/sap/JXD/DVEBMGS00/exe/servicehttp/ctsv/playerProductInstall.swf (No such file or directory)
SDA : name 'tclmwebadminflexstateview', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.31 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcsldabapapi_ear.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'tcsldabapapi_ear', vendor 'sap.com', location 'SAP AG', version '7.1107.20110823093938.0000', software type ('J2EE', sub type ''), csn component 'BC-CCM-SLD', dependencies :[( name 'com.sap.mw.jco', vendor 'sap.com') , ( name 'tcsldsldclient_sda', vendor 'sap.com') ]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.32 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.sl.ut.info.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'com.sap.sl.ut.info', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826143016.0000', software type ('J2EE', sub type ''), csn component 'BC-INS-JCI', dependencies :[( name 'com.sap.exception', vendor 'sap.com') , ( name 'com.sap.tc.Logging', vendor 'sap.com') , ( name 'sl.ut.infoprovider', vendor 'sap.com') ]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.33 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> com.sap.engine.heartbeat.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110826155427.0000
2. Already deployed component has version:7.1107.20110826155427.0000'.
SDA : name 'com.sap.engine.heartbeat', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.34 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> dsr.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110826165427.0000
2. Already deployed component has version:7.1107.20110826165427.0000'.
SDA : name 'dsr', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.35 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> sap.comtclmctccul~service_sda.sda'
Deploy status is 'AlreadyDeployed'
Description:'1. Already deployed component has version:7.1107.20110815124828.0000
2. Already deployed component has version:7.1107.20110815124828.0000'.
SDA : name 'tclmctcculservice_sda', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), csn component '', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.36 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tcjecontextcollectorwsproxyapp.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'tcjecontextcollectorwsproxyapp', vendor 'sap.com', location 'SAP AG', version '7.1107.20110826165427.0000', software type ('J2EE', sub type ''), csn component 'BC-NWA-EMB', dependencies :[( name 'tcjeembeddedsupportlib', vendor 'sap.com') , ( name 'contextcollector', vendor 'sap.com') ]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
1.37 : Relative path '/usr/sap/trans/EPS/in/LMCORE07P_3-20002600.SCA --> tclmwebadminflexjavastatistics.sda'
Deploy status is 'Skipped'
Description:'1. Item is skipped because of failed deployment of item 'sap.com_tclmwebadminflexstateview' and because the applied error strategy is OnErrorStop'.
SDA : name 'tclmwebadminflexjavastatistics', vendor 'sap.com', location 'SAP AG', version '7.1107.20110309083123.0000', software type ('FS', sub type ''), csn component 'BC-JAS-ADM-MON', dependencies :[none]
Time statistics( ms ):
1.Check composite version : 24
1.1.Check version:sap.com_LM-CORE : 1
1.2.Check contained SDAs versions : 23
2.validate : 31
2.1.Check composite version : 31
2.1.1.Check contained SDAs versions : 31
3.Persist in storage : 11
Sep 22, 2011 8:58:37 PM [Info ]:+++ Deployment finished with status 'Error' +++.[ deployerId=5 ][#178: 149.398 sec]
Sep 22, 2011 8:58:37 PM [Info ]:+++++ End D E P L O Y action +++++[ deployerId=5 ]. Total time:[#177: 149.501 sec]
Similar Messages
-
What is the difference between SAP NW PI7.1 and PI7.1 EHP1
We have a customer using SAP PI7.1 EHP1. The application to be deployed
isdeveloped on SAP Netweaver PI 7.1 SP06.
We need to know if application developed and transported from PI7.1 is
compatible with EHP1?
Below are the Components used by the application .
1) SSL communication using SOAP adapter
2) Java mapping , Graphical mapping , XSLT mapping
3) Customised EJB modules
4) Adapter framework
5) ALE layer for IDoc communication from ERP to PI
6) RFC lookups to PI system and ERP system.
Questions
1)Will PI EHP1 be able to communicate with PI7.1 using SOAP adapter ?
2) What is the difference between SAP NW PI7.1 and PI7.1 EHP1 ?
Regards,
SnehaHi,
EHP Pi7.1 new
IPv6 Support in SAP Systems (new)
Async/Sync and Sync/Async Bridge in the JMS Adapter (New)
High Availability (New) Locate the document in its SAP Library structure
Use
A new concept is available for setting up a high availability environment for SAP NetWeaver Process Integration (PI). To do this, you need SAP Web Dispatcher for load balancing, and you must reconfigure your HTTP, RFC, and RMI connections so that they can be used for load balancing. You must also make various configuration steps in other components of your PI environment.
[Level 4: Document: XML to Text Conversion Module (New)] XML to Text Conversion Module (New)
Message Packaging (New)
Monitoring Milestones (New) Locate the document in its SAP Library structure
Use
You can use the new scenario variant Monitoring Milestones of the Business Process Management scenario to define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems.
check given Link
http://help.sap.com/saphelp_nwpi711/helpdata/en/61/8c3842bb58f83ae10000000a1550b0/frameset.htm
Regards,
Amit -
Java embedding code in BPEL 2.0 giving deployment errors
Hello,
I am using Jdeveloper and SOA 6 11.1.1.0.6 version. BPEL 2.0
When i use simple sysout in the java embedding it is deploying fine but when using XMLElement api in the java embedding it s giving deployment error.
Please suggest me how to make it work.
Please see the error message below:
Error deploying archive sca_FetchAttachments_rev1.1.jar to partition "default" on server soa_server1 [http://XXX.XXX.com:8001]
[01:04:09 PM] HTTP error code returned [500]
[01:04:09 PM] Error message from server:
There was an error deploying the composite on soa_server1: Error occurred during deployment of component: FetchAttachments to service engine: implementation.bpel, for composite: FetchAttachments: ORABPEL-05250Hello Rolando Carrasco,
Thank for responding my question. I figure out the issue. It is because we need to import the java API's what we are using in the java embedding.
Thank you,
Raj -
Class java.lang.NullPointerException thrown on deploying Support Packages
Hello Everybody,
My version of <b>Enterprise Portal is 6.0</b> .Earlier the <b>Support Pack Stack level was SP</b>S09 After deploying <b>Support
Pack Stack level SPS16</b> for <b>J2ee Engine</b>,<b>Portal Platform</b> and <b>KMC</b> and restarting the entire server,following error message is being displayed in Portal:
<b>System Error :
An exception occurred during the program execution. Below you will find technical information pertaining to this exception that you might want to forward to your system administrator.
Exception Class </b> <b>class java.lang.NullPointerException</b>
The Details of which are as follows:
<b>
java.lang.NullPointerException
at com.sapportals.wcm.repository.service.appproperties.PropertiesManager.getProperty(PropertiesManager.java:144)
at com.sapportals.wcm.repository.service.layout.cm.LayoutService$ApplicationPropertyProxy.getPropertyValue(LayoutService.java:249)
at com.sapportals.wcm.repository.service.layout.cm.LayoutService.readProfile(LayoutService.java:409)
at com.sapportals.wcm.repository.service.layout.cm.customizing.CustomizingController.readFolderSettings(CustomizingController.java:659)
at com.sapportals.wcm.repository.service.layout.cm.customizing.CustomizingController.initParamters(CustomizingController.java:298)
at com.sapportals.wcm.repository.service.layout.cm.customizing.CustomizingController.(CustomizingController.java:240)
at com.sapportals.wcm.repository.service.layout.cm.customizing.CustomizingController.getInstance(CustomizingController.java:122)
at sun.reflect.GeneratedMethodAccessor217.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.wcm.repository.service.layout.customizing.CustomizingControllerFactory.createCustomizingController(CustomizingControllerFactory.java:141)
at com.sapportals.wcm.repository.service.layout.customizing.CustomizingControllerFactory.getCustomizingController(CustomizingControllerFactory.java:30)
at com.sapportals.wcm.rendering.layout.LayoutControllerFactory.getLC(LayoutControllerFactory.java:198)
at com.sapportals.wcm.rendering.layout.LayoutControllerFactory.getLayoutController(LayoutControllerFactory.java:164)
at com.sapportals.wcm.rendering.control.cm.WdfProxy.createLayoutController(WdfProxy.java:1995)
at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1364)
at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1234)
at com.sapportals.wdf.stack.Control.create(Control.java:291)
at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1307)
at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)
at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)
at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)
at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)
at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)
at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)
at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)
at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)
at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:414)
at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
at com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:130)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:73)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
</b>
Due to this error the screen looks distorted and none of the link opens, Does that error mean that Support Packages have not been Properly Applied ,bcoz iam not able to do anything after that.None of the link opens and window looks distorted.
can Someody plz revert back to resolving this issue.Kindly plz revert back how to resolve this exception at earliest.
Thanks,
SaumyaHi somya
is ur j2ee server is running?
check with following
http://host:j2eeport
or login into j2ee visual administrator,
are u able to login into it?
is server is connected?
regards,
kaushal -
Update Java Support Package Stack in JSPM
Hi all,
When i update Java Support Package Stack in JSPM i can't start the dispatcher
[Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 920] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
When i goto the log-file of the dispatcher (server.0.log):
E:
usr
sap
P01
DVEBMGS01
j2ee
cluster
dispatcher
bin
services
log_configurator
log_configurator.jar
Loading model: {parent,local,references}
The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
#1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
#1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
Somebody know how to solve this problem?
Thanks in advance,
Cheungdefaulttrc.0.trc"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[0, 2, 10485760]/>
<!PREVIOUSFILE[defaultTrace.1.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
#1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 12 more#
#1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 13 more#
#1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
#1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
#1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
#1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
#1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
#1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
#1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
#1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
#1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
#1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
#1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
#1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
#1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
#1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
#1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 12 more#
#1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
#1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
#1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
#1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
#1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain### ... 13 more# -
Error while Installing NW701 EHP1 JAVA Only on AIX/DB2 UDB
Hi All,
While Installing NW701 EHP1 JAVA only on AIX/DB2 UDB platform I am getting below erron in Update Database Registry Step.
Previously system was installed with DB29.1 patch level 7 whiach was wrong. Then I have uninstalled SAP and cleaned all the mounted directories related to SID. After that I stsrted again and getting below error.
The step UpdateDB2Registry with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_UpdateDb2Registry|ind|ind|ind|ind|13|0|UpdateDB2Registry was executed with status ERROR .
Imediate response would highly appreciated and rewarded.
Best Regards
DevendraHi,
Check file system characteristics, it should be created with read and write only. Please make sure that file system should not be created with cio option.
Thanks
Sunny -
Need Info Regarding Implementaion of Interfaces in java.sql package
Hi All,
I am interested in knowing details abt how the Interfaces in the java.sql package are implemented. We all work with the database using the interfaces provided ,but how do they work at the backend ? How can a Interface provide details (work ) with out an implementation class.I Is this taken care by the JVM or some of the Call level interfaces? Please do provide details abt this..hi Sheshadri,
The implementation of the various interfaces in
java.sql package are provided by your jdbc driver,
which also manages the connection and communication of
your java program with the appropriate database.
cheers,
-Jer -
Hi,
I have an issue in editing the text and viewing the font properties of a text region on a PDF created using Java iText package.
I use Adobe Acrobat 9 Pro Extended and the option Tools -> Advanced Editing -> TouchUp Text Tool.
The strange behaviour is that, I have 2 PDFs created out of the same base PDF and text added via Java iText package with the same Text, Font and other properties.
One of the PDF has the text region editable on Acrobat but the other one has the text region which is not editable.
But both the PDFs are editable via Adobe Illustrator.
I have attached both the PDFs for your reference
PDF_Editable.pdf - Editable on Acrobat
PDF_Not Editable.pdf - Not Editable on Acrobat
Any help or insight to find out the difference/issue with the PDF which is not editable via Acrobat would be appreciated.
Thanks in advance.
Regards,
Madhusoodhan HenryramanYou don't have direct control of the leading of a multiline text field. A common approach is to control the background color of the field with JavaScript since the lines are not really needed when the field is used in Reader/Acrobat. They may be useful when using the form by hand. For more information, see the posts by Max in this topic: http://acrobatusers.com/forum/forms-acrobat/how-do-i-use-multi-lined-text-fields-over-prin ted-line-area-existing-form
-
RSPOR_SETUP = Different ABAP and Java support packages.
Hi all,
We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
Different ABAP and Java support packages. Combination of support packages invalid
And with some more clicking we find this:
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
ABAP Support Package: 13
Java Support Package: 0
On the Java stack we see (among others) these components:
sap.com BI-IBC 7.00 SP12 (1000.7.00.12.0.20070509050058)
sap.com BI_MMR 7.00 SP12 (1000.7.00.12.0.20070507084106)
sap.com BI_UDI 7.00 SP12 (1000.7.00.12.0.20070507084125)
sap.com BI-BASE-S 7.00 SP12 (1000.7.00.12.11.20080324092518)
sap.com BI-WDALV 7.00 SP12 (1000.7.00.12.1.20071105133039)
sap.com BI-REPPLAN 7.00 SP12 (1000.7.00.12.3.20080104101916)
So I believe all components are correctly installed.
What are we doing wrong?Hello.
Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
I hope I can be helpful.
Thanks,
Walter Oliveira. -
Error : java:6: package com.crystaldecisions.sdk.framework does not exist
Hi All,
I am using BO XI R2 version.
I am facing issues with BOE Java SDK web application.
In this application, I have just by-passed login page(jsp page) and logout from BO. But, it is throwing errors as mentioned below:
Generated servlet error:
E:\BusinessObjects\Tomcat\work\Catalina\localhost\_\org\apache\jsp\BO_005fHello_005fWorld\login_jsp.java:6: package com.crystaldecisions.sdk.framework does not exist
import com.crystaldecisions.sdk.framework.CrystalEnterprise;
Application gives errors for these two packages:
package com.crystaldecisions.sdk.framework
package com.crystaldecisions.sdk.exception
Can anyone please tell me the solution?
From where I can get the jar files to resolves these problems?
I tried to search these jar files in BO installation folder but was not able to get.
Can anyone tell the exact folder path for these jar files, if it is there.
Or any link to download jar files.
Thanks in advance.Hello ,
-In order to run your application, please copy the Business Objects JAR files from the installed location.
-For example : If you have installed Business Objects on C:
then , go to the path :
C:\Program Files\Business Objects\common\3.5\Java\Lib and copy all the Jar files from that location including JAR files that are present in the external folder.
-Paste these JAR files inside lib folder of your application.
-The class com.crystaldecisions.sdk.framework comes under cesession.jar
Thanks,
Chinmay -
JRE 1.6 missing/can't find java/util package
I installed Sun's JRE1.6 to mitigate the DST issue a couple
of months ago. In the past few days, my clients report when, trying
access web-services the Java Compiler throws an exception dealing
with the inability to access the java/util package.
One solution (in Japanese) purported to say that if one adds
the switch:
-Djmx.invoke.getters=true
This can help mitigate the issue (after a restart). I did for
a couple of hours but the services began failing again.
### Exception Code ###
coldfusion.jsp.CompilationFailedException: Errors reported by
Java compiler: Found 2 system errors: *** Error: Could not find
package "java/util" in:
/opt/coldfusionmx7/runtime/jre/bin/jre1.6.0/lib/ext/sunjce_provider.jar
[filepath]coldfusionmx7/runtime/jre/bin/jre1.6.0/lib/ext/sunpkcs11.jar
[filepath]coldfusionmx7/runtime/jre/bin/jre1.6.0/lib/ext/dnsns.jar
[filepath]coldfusionmx7/runtime/jre/bin/jre1.6.0/lib/ext/meta-index
[filepath]/coldfusionmx7/runtime/jre/bin/jre1.6.0/lib/ext/localedata.jar
/opt/coldfusionmx7/wwwroot/WEB-INF/classes
[filepath]/coldfusionmx7/wwwroot/WEB-INF/lib/cfmx_bootstrap.jar
/opt/coldfusionmx7/wwwroot/WEB-INF/lib/cfx.jar
[filepath]/coldfusionmx7/wwwroot/WEB-INF/lib/commons-beanutils.jar
[filepath]/coldfusionmx7/wwwroot/WEB-INF/lib/commons-collections.jar
/opt/coldfusionmx7/wwwroot/WEB-INF/lib/js.jar
[filepath]/coldfusionmx7/lib/updates/chf700003.jar
/opt/coldfusionmx7/lib/ant-launcher.jar ....
### EOF ###
SysInfo:
Solaris 2.8
CFMX Ent 7.0.0
Java Version 1.6.0b.105Thx Ian - you're correct. I've incepted 1.4.12 and
web-services are up and running *note to readers: watch your
permissons on the new files - ensure CFSvr "user" has access to new
files.
This technote details how to upgrade the JVM:
http://kb.adobe.com/selfservice/viewContent.do?externalId=2d547983&sliceId=2
Thank you both. DjlR -
How to deploy EAR on CE server using Java Support Package Manager
Hello,
I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
Does any one has idea?
Regards,
NKHi,
The Java Support Package Manager is not able to deploy a single .ear file.
If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
You have to create a .SCA from an .EAR file
SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
Gerd -
Flickering using Java Elements package
Im pretty new to Java and open to all suggestions for help.
Basically, Im creating a simple animation in a drawing window, and using the draw and clear commands to move the image. This is causing the image to flicker and I would like to know how to stop this.
I think it may have something to do with 'hold' and 'release' commands but like I say Im open to all suggestions
Im using the elements package to create the animation - all I could seem to find elsewhere was help for the AWT.
Cheers, LukeWhat is the 'Elements' package? Is this a standard java sdk package?
Look into 'double-buffering' to resolve your flickering. Swing components are double-buffered by default.
http://www.spacejack.org/games/dbufanim/
http://java.sun.com/docs/books/tutorial/extra/fullscreen/doublebuf.html
google 'java double-buffering' for more info.. -
Problem Installing Java Servlets Package
I downloaded a sample servlet program which imports classes from the Java Servlets Package. I have the JDK 1.2 which does not come with the servlet classes (javax.servlet and javax.servlet.http). So I then downloaded them from java.sun.com. They come as a set of class files in .zip format. I thought packages were supposed to be in .jar format? At any rate, my compiler still fails to see these classes even after I have extracted these files into the same directory as the original .zip file and added this directory to my classpath. Am I going about this the wrong way? Any ideas on how I can make my compiler see these classes? --Thanks
I down loaded j2sdk 1.4 . and also down loade servlet package. I installed in bin directory.
i took the sample program and compiled. there is error message " java servlet package not found.
please help. email me at [email protected]
Thanks
sri -
ATMTag.java:5: package javax.servlet does not exist
My j2ee jdk1.4.2 is not supporting javx package.
i already set all pathh and class path.
anybody can help me.
details are given below ::
C:\AVA\J2EE Programs\JSP\JSPCustomTag>javac ATMTag.java
ATMTag.java:5: package javax.servlet does not exist
import javax.servlet.*;
^<br>
ATMTag.java:6: package javax.servlet.http does not exist
<br>
import javax.servlet.http.*;
<br>
ATMTag.java:18: cannot resolve symbol
symbol : class TagSupport
location: class ATMTag
public class ATMTag extends TagSupport{
<br> ^
ATMTag.java:29: cannot resolve symbol
symbol : class JspTagException
location: class ATMTag
public int doStartTag() throws JspTagException{
<br> ^
ATMTag.java:31: cannot resolve symbol
symbol : class JspWriter
location: class ATMTag
<br> JspWriter out =pageContext.getOut();
^
ATMTag.java:31: cannot resolve symbol
symbol : variable pageContext
location: class ATMTag
<br> JspWriter out =pageContext.getOut();
^
ATMTag.java:56: cannot resolve symbol
symbol : variable pageContext
location: class ATMTag
pageContext.getOut().write(str);
<br> ^
ATMTag.java:60: cannot resolve symbol
symbol : variable EVAL_PAGE
location: class ATMTag
return EVAL_PAGE;
^
8 errorsWhen compiling servlets etc, you need to include in your classpath a jar file with all the javax.* classes defined in it.
For Tomcat this is called servlet.jar and is in (I think) [TOMCAT_HOME]/shared/lib or /common/lib
For J2EE 1.4 Server, the jar is [J2EE_HOME]/lib/j2ee.jar
Where the _HOME directory is the directory where you installed J2EE.
Include this jar file in your classpath when compiling.
Good luck,
evnafets
Maybe you are looking for
-
How to pass more characters in grid header
Hi, I Need to display header of length 50 characters in ALV grid display. Im using OO method and passing 50 in outlen parameter but it is not allowing me to display more than 40 chars. Please let me know if it is posible. Rgds
-
I want to create a tree structure by the node of a xml..with the help of xslt.. how i will generate the node tree stucture display in a html??? anyone pls help me
-
Dear sir, Please suggest that How to Mention the Method,Tolerance and Functional Area in the TASK LIST. eg. I has an Operation that; CHECK THE MOTOR MEGGER VALUE. CHECK THE
-
Accidently removed my phone number from my profile...
i accidently removed my phone number from my profile on my bt and now when i try and put in my phone number it tells me that the telephone number is the wrong number when i know it's the right number
-
Hello Illustrator experts out there! I'm stuck trying to apply a gradient to a zig-zag object that I've created on Illustrator. I want every peak to be black and the gradient should be kind of rounded (but not radial). The center of the shape should