J2EE Server Component
Hello,
I found that in developer studio, one can create a project of type: J2EE Server Component. It is a kind of library. Once you create, you have to edit "server/provide.xml" and "sda-dd.xml" files.
Could anyone tell me exactly what it is and is there any development documentation for this kind of project. What is the difference between this kind of project with J2EE Enterprise Application Project
OK, I found the related document:
http://help.sap.com/saphelp_nw04/helpdata/en/9f/2ade3fc6c6ec06e10000000a1550b0/frameset.htm
Similar Messages
-
How to add a Jar file to J2EE Server Component Library ?
Hello,
My objective:
=====================================================
To add a 3rd party jar file to be a runtime jar file to J2EE Server Component
Library project.
I have created a J2EE Server Component Library project.
I have built the J2EE Server Component Library project to get the provider.xml file and place the provider.xml under the J2EE Server Component Library project's server folder.
Here is my problem:
=====================================================
I can't open the provider.xml with SAP's special editor for the provider.xml.
The special SAP editor doesn't exist for me.
Here is my question:
=====================================================
Q1) Do I copy/paste my JAR_X file where <jar_0> is located? (Below is the
J2EE Server Component Library SDA structure.)
Q2) If you were to update the provider.xml with notepad, what would you
type in provider.xml for JAR_X?
Q3) Is there anything else that I need to do?
Thanks,
Steve
J2EE Server Component Library SDA structure.
======================================
|-META-INF_
| |-manifest.mf
| |-sap_manifest.mf
| |-SearchRules.xml
| |-<SDA>.xml
| |...
|-<jar_0>
|- ...
|-<jar_N>
|-dispatcher_
| |-provider.xml
| |-properties
| |-runtime.properties
| |-persistent__
| | |-<persistent_files(2)>
| |-descriptors_
| |-<descriptor_files(3)>
|-server_____
| |-provider.xml
| |-properties
| |-runtime.properties
| |-persistent__
| | |-<persistent_files>
| |-descriptors_
| |-<descriptor_files>
|-os_libs____
|-<char set>__
|-<platform>__
|-<jvm bitlength>__
|-<native lib files>Thank you for all your solution...
my provider.xml was missing the <!DOCTYPE> tag for me to use the SAP LibraryDD Editor
Thanks again,
Steve
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE provider-descriptor SYSTEM "library.provider.dtd">
<provider-descriptor>
<display-name>
Your_Lib_Name
</display-name>
<component-name>
Your_Lib_Name
</component-name>
<major-version>6</major-version>
<minor-version>40</minor-version>
<micro-version>0</micro-version>
<provider-name>
sap.com
</provider-name>
<references>
<reference
provider-name="sap.com"
strength="weak"
type="library">Your_Lib_Name</reference>
</references>
<jars>
<jar-name>my_jar.jar</jar-name>
</jars>
</provider-descriptor> -
External library DC vs J2EE Server Component - Library DC
Hi all,
I have been developing where I used jars through the public part of an external library DC and it worked fine, but I'm wondering:
What is actually the difference between a external library DC and a J2EE Server Component - Library DC ?
When do i use the external library DC and when do i use the J2EE library DC?
Kind regards,
J.Hello Mark,
I tried what you said in the following scenario:
I created Proxy classes for Enterprise Connector for a BAPI from a backend system.
Those classes where put in a jar. That jar is put in a external library DC with an assembly public part and a compilation public part.
From that i tried two method:
Method 1: i referenced the public parts (assembly and compilation) from external library DC in my web dynpro DC and it worked fine.
Method 2: I referenced the public parts (assembly and compilation) in a J2EE library DC ( for compilation: build time ; for assembly: build time and runtime with strong). In my Web Dynpro DC i referenced the compilation public part from my external library. And in the properties of my web dynpro project i added the reference to my j2ee library (that was also deployed; i can see it in my visual administrator). When running my application, i get the following error:
<i>java.lang.NoClassDefFoundError: com/sap/aii/proxy/framework/core/AbstractProxy -
Loader Info -
ClassLoader name: [gtsc.jnj.com/testapptestwdp] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/tcwddispwda sap.com/cafeugpapiwd sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:tcwdwslib library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:cafeugpapi library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:gtsc.jnj.comjcrauweltestr3proxieslibrary library:com.sap.aii.util.misc library:tccmi Resources: C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\src.zip C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\commons-collections-2.1.1.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\cglib-2.1.3.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\asm-attrs.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\gtsc.jnj.comtestapptestwdp.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\dom4j-1.6.1.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\hibernate3.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\commons-logging-1.0.4.jar C:\usr\sap\NDW\JC01\j2ee\cluster\server0\apps\gtsc.jnj.com\testapptestwdp\webdynpro\public\lib\asm.jar Loading model: {parent,references,local} -
The error occurred while trying to load "com.jnj.gtsc.im.jcrauwel.proxies.MyR3Proxies_PortType".</i>
Any idea what i'm doing wrong?
Kind regards,
J. -
Is there a J2EE Server Component Library DC in 7.1?
I'm creating an External Library DC to be accessed by an EAR Project using reference. I understand you need to place this DC into a J2EE Server Component Library DC to be able to be deployed. There is a choice for this DC on 7.0. Why there is none in 7.1? Am I missing something or there is a new way to accomplish this?
No more J2EE Server Component Library DC in 7.1. Use EAR and reference using application not library.
http://help.sap.com/saphelp_nwce10/helpdata/en/45/c93bc6a24a4ebce10000000a11466f/frameset.htm -
Problem: J2EE Server Component Library's provider.xml error message
Hello,
I open the provider.xml fle. Then I click on the Jars tab and I get an error message:
The source page has errrors. Other pages cannot be used until these errors are
corrected.
How can I correct the error(s) so that when I click on the Jars tab it will allow me add jar files?
provider.xml content:
======================
<?xml version="1.0" encoding="utf-8"?>
<provider-descriptor>
<display-name>Store jar files that need to be used at runtime</display-name>
<component-name>global/lmco/runtime/j2ee/libs</component-name>
<description/>
<major-version>6</major-version>
<minor-version>40</minor-version>
<micro-version>0</micro-version>
<provider-name>lmco.com</provider-name>
<jars>
<jar-name>
commons-dbutils-1.0.jar
</jar-name>
</jars>
</provider-descriptor>I have one provider.xml which has the dtd in it
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE provider-descriptor SYSTEM "library.provider.dtd">
<provider-descriptor>
<display-name>abclib</display-name>
<component-name>abcLib</component-name>
<description>
</description>
<major-version>6</major-version>
<minor-version>1</minor-version>
<micro-version>0</micro-version>
<provider-name>com.company</provider-name>
<group-name>
</group-name>
<references>
<reference reference-type="hard">
<reference-target provider-name="com.company" target- type="library">xyzLib</reference-target>
</reference>
</references>
<jars>
<jar-name>aspectjrt.jar</jar-name>
<jar-name>axiom-api-1.2.5.jar</jar-name>
<jar-name>axiom-impl-1.2.5.jar</jar-name>
<jar-name>nux.jar</jar-name>
<jar-name>stax.jar</jar-name>
<jar-name>xom.jar</jar-name>
</jars>
</provider-descriptor>
check for the DOCTYPE declaration
Regards
Fariha -
J2ee-Server-Component library and Buildpath
Hi,
I have a J2ee-Servercomponent - Project in the NW Dev. Studio to build and deploy a library for the J2EE WEBAs 6.4.
During buildtime this Library requires certain external JAR's to be build. But every time when I change something in the provider.xml for example the buildpath gets reset and I have to add all the external JAR's again if I want to build the library component again.
I'm NOT using a DC and I'm not using the DTR or NWDI.
Any ideas how to fix this ?
Thanks in advance,
FrankHi
What is the version of NWDS ?
One issue could be the jar files which u have used has been publish as file , if u r using CE version so make it publish as archive
For further assistance please refer this [thread|Problem with JavaBean-Model on Web DynPro for Java;
Best Regards
Satish Kumar -
How to refer to J2EE library server component from a web service?
Hi,
I need help! I created a web service and it worked fine. However, I started having problems when I tried to use java classes from my deployable J2EE library server component. I got the NoClassDefFound error.
I tried to include the library DC in the Used DC list and put the reference of it in the web service deployment descriptor xml (application.xml and application-j2ee-engine.xml), but it did not work.
How do I refer and use java classes from my deployable J2EE library at run time from my web service application? What should I do?
Thanks,
Giavinh PhamI would like to clarify more about the web service project. I created a Java DC project and converted it into a web service as the SAP manual instructions. It worked fine by itself, but I now want to use some of my classes that I deployed as a J2EE library server component.
It was compiled and built when I refer to my J2EE library server component DC in the UsedDC. It was deployed fine as well. However, it broke when I tested the web service calls. The class declarations and usage from the J2EE server component could not be found (NoClassDefFound error.)
I thought it was because I did not have an application-j2ee-engine.xml in my META-INF folder so I created one and referred to the library in xml as type library and reference 'strong'. I built and deployed again. It still did not work.
I examined the EAR and noticed that there were two parts of the EAR. One is the WSAR archive file that contains the META-INF folder from my project and other web service assemblies. The other part is the META-INF folder generated by the SAP NetWeaver IDE.
The strange thing was that SAP NetWeaver IDE generated an application-j2ee-engine.xml without any reference to my J2EE library server component. However, the nested application-j2ee-engine.xml in the WSAR archive file did contain the info.
Since I cannot control the application-j2ee-engine.xml generated by SAP NetWeaver IDE, what should I do? Is it the cause for my problem?
Please advice, anyone?
Giavinh -
Java DC wrapped in J2EE Server Comp Library DC
Hi Experts
I have jxl.jar file, I imported this jar file in a Java DC and declared jxl.jar as public part. I created a Webdynpro DC and used the public part in it. I have created an application, component and a view in it using some classes of jxl.jar. I created a new J2EE Server Component Library DC and used the public part of jxl.jar in it again. Built the J2EE Server Component Library DC. Once done I got a .sda file. I deployed it in server. Once this is done, I have added the J2EE Server Component Library DC in my Webdynpro DC's Library Reference. Once I added this, i built it and deployed it. I got deployment finished with Warnings. Please see the exception below and Please advice.
Exception from NWDS Deployment Screen
"java.rmi.RemoteException: Error occurred while starting application wrigley.com/signauth/ui and wait. Reason: Clusterwide exception: server ID 6840450:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application wrigley.com/signauthui for startup. Reason=Clusterwide exception: Failed to start dependent library ''signauth/libraryimpl'' of application ''wrigley.com/signauthui''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?"
Names of the DCs used
Webdynpro DC - signauth/ui
J2EE Server Component DC - signauth/libraryimpl
Java External Library DC - signauth/library
FYI. I have created J2EE Server Component DC's name with more number of characters. Hope this shouldn't create issue. If this is also an issue, please let me know. I will reduce it and try.
Thank you
Best Regards
Ramamoorthy DHi Experts
Kindly help me out in getting a solution for this problem.
Thank you.
Best Regards
Ramamoorthy D -
Error while starting NW server and j2ee server is getting stopped.
Hi,
I am working in NW04s. It contains ABAP sp5 and java sp9 versions. The server was working find till ten days back. After the gap of ten days, when i started to work on this SAP system, i was not able to start the j2ee server. During the startup of the server itself, j2ee server is getting stopped and dispatcher also. Following is the error bunch I got in trace. If any one has any idea about this, please reply this soon.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=garden SYSNR=00 GWHOST=garden GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR connection to partner '15.70.176.191:sapgw00' broken
TIME Mon Nov 13 12:45:30 2006
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -6
MODULE nixxi.cpp
LINE 4207
DETAIL NiIRead
SYSTEM CALL recv
ERRNO 10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER 4
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#1.5#000E7FFD8B5D001D00000011000008540004221BAAB8047C#1163402130490#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_54##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#> ceException: Connect to SAP gateway failed
> Connect_PM TYPE=A ASHOST=garden SYSNR=00
> GWHOST=garden GWSERV=sapgw00 PCS=1
>
> LOCATION CPIC (TCP/IP) on local host with Unicode
> ERROR connection to partner
> '15.70.176.191:sapgw00' broken
You can ping this machine from your portal-nodes and you can connect to the port "sapgw00" (should be 3300) ?
> ##0#0#Fatal#1#/System/Server#Plain###Critical
> shutdown was invoked. Reason is: Core service
> com.sap.security.core.ume.service failed. J2EE Engine
> cannot be started.#
This is the reason why your j2ee-server stops - the portal can't connect to the ume. What did you configured as the ume - the portal database, a ldap-server or a r3-system ?
Regards
Norman -
Pros and cons of installing a local J2EE server
Hi,
We are about to start developing portal applications with Web Dynpro and will use NWDI (DTR/CBS/CMS). I would like to know what SAP recommends for team development, each developer installs a local J2EE server or they all deploy and test on a central server?
From my past experiences, using only one central server can cause problems with debugging, deployment and collisions of a DC tested simultanously by two developers. Running a local server can solve these problems but this could be costly; first because PCs often don't have enough CPU/RAM to run it, and second to support all these complex installations.
I have read Benny's two blogs and some SAP documentation but it is still not clear to me which option is best. If you have lived good or bad experiences with one or the other please let me know!
Thanks,
MartinI would strongly suggest you avoid having a single runtime environment for multiple developers. The nature of Java development makes working in a runtime environment such as this very difficult. It's far too easy to have multiple developers working on the same component making changes that result in different versions of the same component getting deployed to the same runtime environment. Unless communication is very good, you're developers will end up clobbering each others changes. Obviously not good, since the developers will spend time trying to debug problems which really don't exist!
At the other end of the spectrum, each developer can have their own Java stack running locally on their desktop PC. This was the solution that we first tested out, but due to the amount of virus scanning and the overall 'weight' of the other software tools on our desktop PC's, this didn't work too well - performance wasn't all that good. It was also too easy for the developer to clobber their own environment by accidentally removing files, or by making changes to the configuration that would render their engine unusable.
What we opted for was something in the middle: a dedicated multi-cpu system with lots of RAM that runs multiple J2EE instances, each of which is assigned to a single developer. What you get from this sort of configuration is this: only a single operating system to patch when you are required to do upgrades; a controlled environment where the developer doesn't have file system access to the system (which they don't need anyways); if you're lucky, basis support to perform installation and patching duties.
We've been using this environment for about a year now, and it works well. I have full access to the J2EE container via the Visual Admin, and since the dev instances are configured as single server debuggable instances, I can restart the server via the Dev Studio with just two clicks.
Hope that gives you an idea of another possible config. -
J2ee server has suddenly stopped running with exit code -11113
Hi,
Have installed WAS 6.40 portal and TREX on same machine.
j2ee server has suddenly stopped with exit code -1331.sdm and dispatcher are working fine.
Please help..!
here is the default trace file
#1.5#000C29352CBB001400000149000008C400042E8904DE861B#1177065933781#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00E600000000000008C400042E89108312C3#1177066129093#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#sap.com/tcdtrenterpriseapp#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#Guest#192####b885af50ef2c11dbcb71000c29352cbb#Thread[Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176_workerThread\#0,1,Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176]##0#0#Warning#1#/dtr/nameres#Java###error while retrieving data from secure-store
[EXCEPTION]
#1#com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID sapcomtcdtrenterpriseapp
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
at com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig.loadConfiguration(SecureStoreNameServerConfig.java:54)
at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.loadNameServerConfiguration(NameReservationManager.java:162)
at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.processQueue(NameReservationManager.java:231)
at com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask._run(ProcessNameReservationsTask.java:35)
at com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask.run(AbstractSessionBoundTask.java:37)
at com.tssap.dtr.pvc.util.scheduler.Invocation$Worker.run(Invocation.java:130)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00140000014A000008C400042E8916B567FD#1177066233031#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00140000014B000008C400042E8916B570EB#1177066233031#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB000D0000001F000008C400042E8919E67A90#1177066286578#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
#1.5#000C29352CBB000D00000020000008C400042E8919E696EC#1177066286578#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:06:51_20/04/07_0132_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB00180000000F000008C400042E891F950BA4#1177066381890#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
#1.5#000C29352CBB001800000010000008C400042E891F951BEF#1177066381890#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java###Exception ID:06:53_20/04/07_0133_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB001100000198000008C400042E892504640C#1177066473062#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB001100000199000008C400042E892504642F#1177066473062#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00110000019A000008C400042E89289DD7BB#1177066533437#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00110000019B000008C400042E89289DDB04#1177066533437#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB003000000028000008C400042E892CEAA96A#1177066605437#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
#1.5#000C29352CBB003000000029000008C400042E892CEAC648#1177066605562#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Error#1#/System/Server#Java###Exception ID:06:56_20/04/07_0134_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB001A00000028000008C400042E8934452A55#1177066728921#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
#1.5#000C29352CBB001A00000029000008C400042E8934453D75#1177066728921#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server#Java###Exception ID:06:58_20/04/07_0135_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
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:522)
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)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
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.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
Thanks
RockyHi Rocky,
1)Goto configtool directory and run confgitool.sh
<drive:\>\usr\sap\sid\JC<InstanceNumber>\J2EE\configtool\configtool.sh
2)Under Clustre Data -> Global Server Configuration -> Services -> com.sap.security.cor.ume.services
3)Now find the parameter - ume.persistence.data_source_configuration
And change to default value (The default - dataSourceConfiguration_database_only.xml)
4)Click on set and then apply the setting. Then restart the server.
Hope it will be helpful.
Thanks & regards
Arun Singh -
Hello everybody,
today as i tryed to logon to the J2EE-Engine Start Page i got the following error (Port: 8000!)
WAS 6.40 on Stack 9 (ABAP+JAVA)
Internal Server Error(-1)
Error: -1
Version: 6040
Component: J2EE Server
Date/Time: Fri Oct 07 11:55:23 2005
Module: http_j2ee.c
Line: 789
Server: xxx_00
Detail: Cannot reach external Application Server on xxx:50000
When i check the MMC at the server all nodes are green.
Also the ABAP Stack is just working fine!
Any idea what could be the problem?
regards,
MarkusOk i just checked the Instance Profile:
The Parameter icm/HTTP/j2ee_0 looks like this:
PREFIX=/,HOST=localhost,CONN=0-500,PORT=50000
So its already the way it should look like as mentioned in the SAP Note.
Markus -
Error start SOA Suite(J2EE Server)
Usually J2EE Server successfully start and works. But sometimes server cannot start, and shows a following error:
==================================================
ias-component: default_group
process-type: home
process-set: default_group
Error Message:time out while waiting for a managed process to start
==================================================
And generates such log-file:
Configuration information
Running in C:\product\10.1.3.1\OracleAS_1
Operation mode:Startup, App Server, No Enterprise Manager, Single Instance
Oracle home:C:\product\10.1.3.1\OracleAS_1
Oracle home name:Unnamed
Instance name:orcl.localhost
Instance type:core
Version:10.1.3.1.0
Uses infrastructure:false
Not an infrastructure instance, no infrastructure information available
Components:[j2ee, Wsil]
2007-02-16 01:22:44.361--Begin log output for Mid-tier services (orcl.localhost)
2007-02-16 01:22:44.361--Processing Step: starting OPMN
2007-02-16 01:22:45.613--Processing Step: starting OPMN managed processes
2007-02-16 01:51:54.17--End log output for Mid-tier services (orcl.localhost)
An unknown OPMN error has occured
oracle.appserver.startupconsole.model.ConsoleException: An unknown OPMN error has occured
at oracle.appserver.startupconsole.control.OPMNController.doStart(OPMNController.java:140)
at oracle.appserver.startupconsole.control.Controller.start(Controller.java:69)
at oracle.appserver.startupconsole.control.GroupController.doStart(GroupController.java:47)
at oracle.appserver.startupconsole.control.Controller.start(Controller.java:69)
at oracle.appserver.startupconsole.view.controller.ControllerAdapter.start(ControllerAdapter.java:30)
at oracle.appserver.startupconsole.view.controller.MasterControlAdapter.run(MasterControlAdapter.java:94)
at oracle.appserver.startupconsole.view.Runner.main(Runner.java:39)
Caused by: oracle.appserver.startupconsole.model.ConsoleException: There are some errors while stopping the following components. Refer to the generated error report for more details.
==================================================
ias-component: default_group
process-type: home
process-set: default_group
Error Message:time out while waiting for a managed process to start
==================================================
at oracle.appserver.startupconsole.control.OPMNController.doStart(OPMNController.java:139)
... 6 more
Caused by: oracle.ias.opmn.optic.OpticControlException: Error from opmn during process control operation
at oracle.ias.opmn.optic.AbstractOpmnEntity.runCommand(AbstractOpmnEntity.java:174)
at oracle.ias.opmn.optic.AbstractOpmnEntity.start(AbstractOpmnEntity.java:110)
at oracle.appserver.startupconsole.control.OPMNController.doStart(OPMNController.java:97)
... 6 more
Exception caused by
There are some errors while stopping the following components. Refer to the generated error report for more details.
==================================================
ias-component: default_group
process-type: home
process-set: default_group
Error Message:time out while waiting for a managed process to start
==================================================
oracle.appserver.startupconsole.model.ConsoleException: There are some errors while stopping the following components. Refer to the generated error report for more details.
==================================================
ias-component: default_group
process-type: home
process-set: default_group
Error Message:time out while waiting for a managed process to start
==================================================
at oracle.appserver.startupconsole.control.OPMNController.doStart(OPMNController.java:139)
at oracle.appserver.startupconsole.control.Controller.start(Controller.java:69)
at oracle.appserver.startupconsole.control.GroupController.doStart(GroupController.java:47)
at oracle.appserver.startupconsole.control.Controller.start(Controller.java:69)
at oracle.appserver.startupconsole.view.controller.ControllerAdapter.start(ControllerAdapter.java:30)
at oracle.appserver.startupconsole.view.controller.MasterControlAdapter.run(MasterControlAdapter.java:94)
at oracle.appserver.startupconsole.view.Runner.main(Runner.java:39)
Caused by: oracle.ias.opmn.optic.OpticControlException: Error from opmn during process control operation
at oracle.ias.opmn.optic.AbstractOpmnEntity.runCommand(AbstractOpmnEntity.java:174)
at oracle.ias.opmn.optic.AbstractOpmnEntity.start(AbstractOpmnEntity.java:110)
at oracle.appserver.startupconsole.control.OPMNController.doStart(OPMNController.java:97)
... 6 more
<?xml version='1.0' encoding='WINDOWS-1251'?>
<response>
<msg code="-82" text="Remote request with weak authentication.">
</msg>
<opmn id="r-0c2b16d9f3e64:6200" http-status="408" http-response="0 of 1 processes started.">
<ias-instance id="orcl.localhost">
<ias-component id="default_group">
<process-type id="home">
<process-set id="default_group">
<process id="896076993" pid="808" status="Stop" index="1" log="C:\product\10.1.3.1\OracleAS_1\opmn\logs\\default_group~home~default_group~1.log" operation="request" result="failure">
<msg code="-22" text="time out while waiting for a managed process to start">
</msg>
</process>
</process-set>
</process-type>
</ias-component>
</ias-instance>
</opmn>
</response>
Configuration:
WinXP Pro SP2
SOA Suite 10.1.3.1 (installation type: J2EE Server)
Thanks,
stan1slav.You say:
Usually J2EE Server successfully start and works. But sometimes server cannot start, and shows a following error.
Are you using the SOA Suite on the same machine? I mean does it use the same IP-adress, hostname? Are you using proxy-settings? -
Hello.
I want to delete files in a certain folder in a web component in the J2EE server using JSP.
When I try to call File.delete(), it is rejected because file access denied.
How can I control the file permission in J2EE?
I tried to add to JDK java.policy file the permission, but it seems that J2EE controls the file access using other mechanism.
Please help me.This may help you:
http://java.sun.com/products/jdk/1.2/docs/guide/security/index.html
Especially the Chapter about Security Permissions.
The policytool included in the jdk makes the editing of such policy-files much easier.
hope this helps -
Hi all,
I'm trying to consume a web service that i did with a ABAP function module. This means that my Web Service is in R/3 not in the Web AS.
I created a Deployable Client Proxy with the WSDL in the NWDS.
Now the EAR is deployed in the WebAS.
In my web-j2ee-engine.xml i have:
Application Local JNDI name: sc
Server component type: interface
Server component JNDI name: /wsclients/proxies/sap.com/sc/sap.com.sc
My question is where is the Server component JNDI name of my Web Service in the Web AS?
How can i find the JNDI names of all my apps in the Web AS?
In the help is says:
/wsclients/proxies/<ProviderName>/<ApplicationName>/<ProxyName>
But every time that i do
DefaultService obj = (DefaultService) ctx.lookup("java:comp/env/sc");
The error is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name webContainer/applications/sap.com/testear/test/java:comp/env/sc, cannot resolve object reference. [Root exception is com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at sc, the whole lookup name is wsclients/proxies/sap.com/sc/sap.com.sc.
Please help,
Regards,
César FelceHi César,
You can access JNDI Registry with Visual Administrator tool.
Under "Services->JNDI Registry".
Best Regards,
Jorge Linares
Maybe you are looking for
-
Re-Using XML file from decode barcode + extract xml process
I was hoping someone could put me in the right direction here. I am decodeing the information stored in a 2D Bar code and sending this information to an XML file, then I am trying to combine that xml file with a blank PDF template but the process is
-
I own a WRT160n V3 router, and it's set up to be the host of a wired LAN setup. To detail the layout, one computer is directly connected to the router. A cable then feed from the router and into an ethernet port which leads to the back of the house.
-
Upgradation steps for XI 3.0 to PI 7.0..?
Hi Folks, Can anyone give me the steps to upgrade the xi 3.0 with some suport pack to pi 7.0 with some support pack. What i need is what are the consideration should be taken and poceedure to do it. What about the interfaces in xi.? Thanks in ad
-
Does Bridge use Less Ram than Elements?
I have been running PSE 11, and recently moved on to PSCC. I still use PSE for sorting and accessing my images, but find that PSCC is very slow when PSE is open. Presumably this is because PSE is employing a lot of RAM. Do you think that changing
-
Taking much time when trying to Drill a characterstic in the BW Report.
Hi All, When we are executing the BW report, it is taking nearly 1 to 2 mins then when we are trying to drill down a characterstic it is taking much time nearly 30 mins to 1 hour and througing an error message that, "An error has occared during loadi