Disable portal,km startup in multi-application dual stack

Hello,
We have a dual stack ECC installation with ESS,MSS,Portal and XECO on the java stack. We are currenty trying to run debug against the XECO components on the java stack. It appears that the debugger is getting very slow due to the multiple java applications. We would like to disble portal(km,cm), ess and mss for a few weeks while we complete our debugging with XECO.
Is there anyway to disable the startup of portal,ess and mss?
thanks in advance
Vipin

Hello Vipin,
You can turn off any Java application easily from Visual Admin.
Just login into Visual Admin and goto Cluster -> Server -> Services -> Deploy then in Runtime tab select Radio button Application. You will see all your Java application here. If you see check mark in front of your application, the app is running but if you see "x" sign then it's stopped.
Select your application and click on "Stop Application" button on right side.
Hope this will help you.
Bijay

Similar Messages

"UDDIClerkServlet" failed to preload on startup in Web application: "uddiportlets". java.lang.NullPointerException

Hi,
I was trying to implement jUDDI on weblogic. I have set up all the prerequisites, i have set up the db also. I am trying to deploy the application as an ear file which contains jUDDI war file, pluto portal war file, UDDI portlet war file. Everything is working without this UDDI portlet war file now when i added this UDDI its showing the following error in logs::
Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "UDDIClerkServlet" failed to preload on startup in Web application: "uddiportlets".
java.lang.NullPointerException
    at org.apache.juddi.v3.client.config.UDDIClerkServlet.init(UDDIClerkServlet.java:49)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
any help will be so helpful for me... Thanks in advance, have a nice day
Thanks
Sharath.

Let's say your Weblogic domain for Contract Management is located in
C:\Oracle\Middleware\user_projects\domains\cm, please first check if the com folder exists in the domain folder. If the folder not exists, you have to reinstall Contract Management using an administrative account.

SSO from portal to Java based web application not happening

Hi,
We are trying to configure SSO from SAP Enterprise portal with Java based
web application(Solaris on SPARC 64 bit).
Then we downloaded library files for "Solaris on SPARC 64 bit" from
service market place from the path "Support Packages and Patches"
Additional Components" SAPSSOEXT".
We are successful in sending the portal side cookie to the application.
But while loading the library files we get the following error
INFO | jvm 1 | 2009/04/13 04:47:00 | java.lang.UnsatisfiedLinkError:
/usr/local/blackboard/apps/tomcat/lib/libsapssoext.so: ld.so.1: java:
fatal: /usr/local/blackboard/apps/tomcat/lib/libsapssoext.so: wrong ELF
class: ELFCLASS64 (Possible cause: endianness mismatch)
Can you please suggest us what went wrong in this whole process.
But when i tried with the 32 bit library files i was able to load libsapssoext.so file but when I
tried to initialize libsapsecu.so i got the below message
java.lang.Exception: MySapInitialize failed: rc= 14
Also do we require to take"SAPSECULIB" from Support Packages and Patches" ...>Additional Components" ...>SAPSECULIB" ...>SAPSECULIB 5.4 for this SSO activity.
Please get back on this ASAP as we are nearing the golive date.
regards
Bharath

hi,
am facing similar issue... i.e.
java.lang.Exception: MySapInitialize failed: rc= 14
        at com.mysap.sso.SSO2Ticket.init(Native Method)
        at com.mysap.sso.SSO2Ticket.<clinit>(SSO2Ticket.java:27)
        at org.apache.jsp.index_jsp._jspService(index_jsp.java:92)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
static beendet.
java.lang.Exception: MySapEvalLogonTicketEx failed: standard error= 9, ssf error= 0
CustomeSSO: Object is null.
pls. help me in resolving it.
rgds,
santosh malavade

How do I disable the automatic startup on HP Photosmart Premier when I turn my computer on?

Someone else posted ths question a month ago, but still no answers. Anyone?
How do I disable the automatic startup on HP Photosmart Premier when I turn my computer on?
Windows XP, SP3 operating system recently re-installed so I also reinstalled my printer software. Now, for some reason, each time I turn my computer on, my HP Photosmart C4100 all-in-one photosmart premier software opens. It is not in my startup. This slows down my computer terribly, which is why I never used the program before my re-install. How can I disable this feature? I only print, I don't use it for photos.
Any help here is appreciated.

Run msconfig.exe from the start button (type in msconfig). When it comes up go to the Startup tab and find and deselect the HP product you do not want to start. Save and reboot computer. Now try.
Say thanks by clicking the Kudos Thumbs Up to the right in the post.
If my post resolved your problem, please mark it as an Accepted Solution ...
I worked for HP but now I'm retired!

I cannot install Creative Suite 5.5 on my Windows 7 Professional. I keep getting error message: "Exit Code: 15 - Media DB sync failed". I have disabled UAC and Startup items and Services with no luck. Can you please help?

I cannot install Creative Suite 5.5 on my Windows 7 Professional. I keep getting error message: "Exit Code: 15 - Media DB sync failed". I have disabled UAC and Startup items and Services with no luck. Can you please help?

I am sorry Erickkasner but there is no longer direct support provided for Creative Suite 5.5 installation issues.
You are welcome to post any specific errors you are able to discover within your installation log to this discussion. Since you are using Windows then Exit Code 15 could mean one of the following:
Installer database is corrupted
Update pending to your operating system
Improper permissions set for the Media.db
The installation log file should provide additional insight into the exact error you are experiencing. Please make sure to use the find command to look for the words 'ERROR' and 'FATAL' to locate the relevant error messages.

"No enought room on startup disk for Application Memory" when using the Accelerate Framework

Dear colleagues,
I am running what I know is a large problem for a scientific application (tochnog) a finite element solver that runs from the Terminal. The application tries to solve 1,320,000 simultaneous linear equations. The problem starts when I use the Accelerate Framework as the Virtual Memory size jumps from 142 G to about 576 G after the library (LAPACK) is called to solve the system.It does not do it if I use a solver that does not calls LAPACK inside Accelerate.
The machine is a mac pro desktop with 8 GB of ram, the 2.66 GHz Quad-core Intel and the standard 640 GB hard drive. The system tells me that I have 487 GB available on hard drive.
The top instruction in Terminal reads VM 129G vsize when starting. When I run the finite element application once the LAPACK library in the Accelerate framework gets called, the Virtual Memory (VM) jumps to 563 G vsize.
After a short while, I get the "No enought room on startup disk for Application Memory error"
This is a screen capture of the application attempting to solve the problem using the LAPACK library inside the Accelerate framework: Here are the numbers as reported by the activity Monitor.
Tochnog Real Memory 6.68 GB
System Memory Free: 33.8 MB, Wired 378.8 MB, Active 5.06 GB, Inactive 2.53 GB, Used 7.96 GB.
VM size 567.52 GB, Page ins 270.8 MB, Page outs 108.2 MB, Swap used 505 MB
This is a screen copy of the same application solving the same problemwithout using the Accelerate framework.
Tochnog Real Memory 1.96 GB,
System Memory Free: 4.52 MB, Wired 382.1 MB, Active 2.69 GB, Inactive 416.2 GB, Used 3.47 GB.
VM size 148.60 GB, Page ins 288.8 MB, Page outs 108.2 MB, Swap used 2.5 MB
I can not understand the disparity in the behavior for the same case. As I said before, the only difference is the use of Accelerate in the first case. Also, as you can see, I thought that 8 GB of ram memory was a lot.
Your help will be greatly appreciated
Best regards,
F Lorenzo

The OP had posted this question in the iMac Intel forum.
I replied along similar lines, but suggested he repost this in the SL forum where I know there are usually several people who have a far better grasp of these issues than I.
I would be interested in getting their take on this.
Although, I think you are coming to the correct conclusion that there are not enough resources available for this process, I'm not certain that what you are saying on the way to that conclusion is correct. My understanding of VM is that it is the total theoretical demand on memory a process might make. It is not necessarily the actual or real world demand being made.
As such, this process is not actually demanding 568GB (rounded.) As evidence of that, you can see there is still memory available, albeit quite small, in the form of free memory of 33.8MB and inactive of 2.53GB (the GB for that figure, above, seems like it might be a typo, since for the process when not using Accelerate the reported figure for inactive was 416.2 GB -- surely impossible) and 7.96GB used. The process, itself, is using 6.68GB real memory.
In addition, I question whether the OP has misstated the 487GB free drive space. I think that might be the total drive capacity, not the free space.
My guess is that it is the combination of low available memory and low free drive space prompting this error.
From Dr. Smoke on VM:
it is possible that swap files could grow to the point where all free space on your disk is consumed by them. This can happen if you are very low on both RAM and free disk space.
https://discussions.apple.com/message/2232469?messageID=2232469&#2232469
This gets more to the actual intent of your question...
EDIT: Looks like some kind of glitch right now getting to the Dr. Smoke post.
Message was edited by: WZZZ
<Hyperlink Edited by Host>

Everytime I start up my MacBook Pro, I get this message. 'Insecure Startup Disabled.' "/Library/Startup items/HP Trap Monitor" has not been started because it does not have the proper security settings.

Everytime I start up my MacBook Pro, I get this message. 'Insecure Startup Disabled.' "/Library/Startup items/HP Trap Monitor" has not been started because it does not have the proper security settings.

Update your HP Printer drivers/software at their website or uninstall using the developers method.

Servlet: "MessageBrokerServlet" failed to preload on startup in Web application:

We are migrating from the community edition to ES edition. The application server is Oracle Weblogic running on Solaris SPARC. I have deployed all the jars from the samples lib directory i.e tomcat/webapps/lcds-samples/WEB-INF/lib/. The appication is getting built successfully.But while I am trying to login to our application it is failing.The MessageBroker is not getting initialised. It is showing the following error in the application logs
<Aug 8, 2010 6:47:05 PM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "MessageBrokerServlet" failed to preload on startup in Web application: "bdcui.war".
javax.servlet.UnavailableException: flex.messaging.util.concurrent.DefaultThreadPoolExecutor.<init>(IIJLjava/util/concurrent/ TimeUnit;Ljava/util/concurrent/BlockingQueue;Ljava/util/concurrent/ThreadFactory;)V
at flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:170)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.jav a:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
Truncated. see log file for complete stacktrace
Please suggest on this. I need some immediate advice on the above issue since I am not able to proceed further. I have tried by adding flex.write.path in the MessageBroker servlet's init params in the web.xml file. But may be I am not giving the correct value to the param.
Any comment would be appreciated.
Thanks & regards,
Chandra.

specify /WEB-INF/flex/services-config.xml in your
messagebroker servlet ..
weblogic probebly doesnt accept the relative path or your
weblogic thinks your webapp is in the wrong dir.. I had the same
problem with resin because i started my webapp from the path
/developement/servers/resin/ etc... the problem was fixed when i
used something like c:/development/servers/resin ..
i dont have any experience with weblogic

LDAP configuration for HR Portal in dual stack EHP4 - Best Practice

Hi Experts,
Hello Experts,
We are trying to use the JAVA Stack of ECC server for HR Portal i.e Dual Stack and have applied EHP4 package for ESS/MSS Appraisal. When we are trying to configure the LDAP ADS datasource through portal , we are not able to do it since ABAP datasorce file is available by default.This we are doing for HR(ESS/MSS) Portal.This is for access to the object data stored in the Active Directory.
We have already checked note 718383.
Also, for the scenatrio ,LDAP <-> ABAP <-> J2EE
We have already checked sap help doc.here:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/e6/0bfa3823e5d841e10000000a11402f/frameset.htm
What should now be the best practice to follow for configuration ? Should we go for separate Portal server or is it possible to use Java Stack of ECC server for configuration ?
Also, LDAP <-> ABAP <-> J2EE scenario please suggest if it a best practice and we can follow the same .What are the limitations , risks and issues ? Please suggest if this has been implemented and running well in any live project .
Are the suggestions applicable for load balanced production servers as well?
Thanks,
Rakesh

Hi,
the UME datasource must remain ABAP but you can sync the users between ABAP and LDAP using the LDAP connector:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/48/74040175bb501ae10000000a42189b/frameset.htm
Regards,
Jozsef

Rebuild our XI application server from Single stack to dual stack

Hello,
We currently have an XI landscape with two application servers, the CI is of course a dual stack system, however the two app servers are single stacked, however we would like to make the two app servers into DUAL STACKs, my first guess was to rebuild the two apps from scratch and reinstall them as a dual stack apps. My Q is:
First: Do we need to rebuild both app servers, or can we make a change to the app servers to modify them to become dual stacked
Second: If we do need to rebuild both these apps, is there a specific document available to do this on Market place for installing a Dual stack app servers with PI?
Thanks in advance.
Sam
<Moved from SAP PI Forum>
Edited by: Prateek Raj Srivastava on May 13, 2010 12:27 PM

Hello,
Thank you all for your feedback,
Denny Liao, it is very interesting question you implied, we do have a J2EE directory created under the /usr/sap/SID/D30 directory:
/usr/sap/XQ9/D30
mqaapz28:xq9adm 13% ls -ltr
total 36
drwxr-xr-x   7 xq9adm   sapsys        96 Aug 24 2009 igs
drwxr-xr-x   9 xq9adm   sapsys      1024 Aug 24 2009 j2ee
drwxr-xr-x   2 xq9adm   sapsys      1024 Nov 11 2009 sec
drwxr-xr-x   3 xq9adm   sapsys      1024 Nov 24 10:48 log
obviously this app server does not have any (jlaunch/jcontrol process running) therefore it is not running as dual stacked. but interestingly enough I do see logs in the
/usr/sap/XQ9/D30/j2ee/cluster/server0/log directory created at the time of the initial install. and under:
/usr/sap/XQ9/D30/j2ee/cluster
mqaapz28:xq9adm 29% ls -ltr
total 30
drwxr-xr-x   2 xq9adm   sapsys      1024 Aug 24 2009 bootstrap
-rw-rr   1 xq9adm   sapsys        39 Aug 24 2009 version.bin
-rw-rr   1 xq9adm   sapsys      6339 Aug 24 2009 instance.properties.vmprop
-rw-rr   1 xq9adm   sapsys      3676 Aug 26 2009 instance.properties
drwxr-xr-x   7 xq9adm   sapsys      1024 Aug 26 2009 dispatcher
drwxr-xr-x 11 xq9adm   sapsys      1024 Aug 26 2009 server0
as per the note you mentioned above (741289 ) this explains how to recover a lost J2EE parameter setup, I am guessing this can be simply followed and re-enable the app server to run as a dual stack.
also my system information for the J2EE on the CI is:
System XQ9
Find other systems in SLD... Message Server
Host: mcsapxq9j
Port: 3924
Enqueue Server
Host: mcsapxq9j
Port: 3224
Database
Name: XQ9
Host: mcsapxq9dbx
Type: Oracle (Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production With the Partitioning and Data Mining options)
Software Components all components...
Name Version Applied
sap.com/SAP-JEECOR 7.00 SP21 (1000.7.00.21.0.20091214121410) 20100506125119
sap.com/SAP-JEE 7.00 SP21 (1000.7.00.21.0.20091214121301) 20100506124943
Licenses
Installation Number *** not yet assigned ***
System Number *** not yet assigned ***
Software Product Days Until Expiry
Download system configuration
Instance mqacsz27_XQ9_30 All processes running
Host: mqacsz27
OS: SunOS (sparcv9) 5.10
dispatcher Running
VM system properties...
PID: 21384
Name: Java HotSpot(TM) 64-Bit Server VM
Vendor: Sun Microsystems Inc.
Version: 1.4.2_21-b03
VM Parameters
Cluster
Node ID: 301932700
Kernel Version: 7.00 PatchLevel 76340.450
HTTP Port: 53000
HTTPS Port: 53001
P4 Port: 53004
Telnet Port: 53008
Info for crashes of this node
server0 Running
VM system properties...
PID: 21394
Name: Java HotSpot(TM) 64-Bit Server VM
Vendor: Sun Microsystems Inc.
Version: 1.4.2_21-b03
VM Parameters
Cluster
Node ID: 301932750
Kernel Version: 7.00 PatchLevel 76340.450
Info for crashes of this node
SDM Running
VM
PID: 21400
SDM Port: 53018
So: besides setting up the parameters in the above Note and consider the Load balancing, as there any other major setups required to start this app server as a dual stacked instance?
Thanks in advance.
SAM
Edited by: SAM_ONE on May 14, 2010 3:45 AM
Edited by: SAM_ONE on May 14, 2010 3:55 AM

Use of multi applications and interface comp controller in Leave(any WDP)

Hi Frndz,
AM new to ESS/MSS, now am modifying standard ESS leave proj while doing this i want make clear myself about somethings ..those r
1) What is the use(purpose) creating multi applications(LeaveRequest,LeaveRequestAdmin,LeaveRequestApprover,TeamView) in a WDP (for ex:ESS leave) proj.
2) And i came to know that interface controller is playing big role in this , i need a exact use of interface controller, if posible with any basic example, i gone through SDN blogs but i did't get clear picture about interface controller.
Regards
Rajesh

Refer help.sap.com for exact defination
In brief
LeaveRequest > For requesting Leaves by the Employee ie enduser
LeaveRequestAdmin > to solve error in Leave request application, not available, Need to use PTARQ
LeaveRequestApprover> to approve Leave requests like a manager
TeamView : to see other employees absences in ones org unit

Get portal session id in WD application

Hi Experts,
We have a Z WD application which is displayed using portal. In this WD application we have a disclaimer pop up that should be displayed to the user only once per user-portal session.
This mean once the user loggs in and clicks on the WD application link for the first time, pop up should be displayed but not for the consecutive clicks of the WD application link in the same portal session.
I tried using the FM TH_GET_SESSION_ID but it gives different session IDs for every click of WD link in the same portal session.
I have read several threads and found out that it is not possible to get this info in WD framework.
So can some one suggest an alternative way to do this based on my requierment?
Let me know if more details are required.
Thanks,
Anubhav
Edited by: Anubhav Jain on Apr 4, 2011 9:21 PM

Hi Abhimanyu / Bhaskaran,
Thanks a lot for the replies, but I can not do anything from portal side.....this has to be from WD side only.
Any more ideas?
Regards,
Anubhav

[HTTP:101216]Servlet: "jersey" failed to preload on startup in Web application:"

Hi,
i'm trying to deplay a restful webservice on a WL 10.3 with jdeveloper. As soon as i try to deploy my webservice i'm getting the follwing error :
weblogic.application.ModuleException: [HTTP:101216]Servlet: "jersey" failed to preload on startup in Web application: "name.war".
com.sun.jersey.spi.inject.Errors$ErrorMessagesException
    at com.sun.jersey.spi.inject.Errors.processErrorMessages(Errors.java:170)
    at com.sun.jersey.spi.inject.Errors.postProcess(Errors.java:137)
    at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:203)
    at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:702)
    at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:691)
    at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:438)
    at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:288)
    at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:587)
    at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:213)
    at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:343)
    at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:542)
    at javax.servlet.GenericServlet.init(GenericServlet.java:242)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:54)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
:com.sun.jersey.spi.inject.Errors.ErrorMessagesException:null
What do i have to do to make it work?
Best regards.

Did you deploy and target the jersey libraries to your server (these can (usually) be found in the ${WL_HOME}/common/deployable-libraries). Deploy these as shared libraries and then reference it by using the following in the weblogic.xml file:
<library-ref>
    <library-name>jersey-bundle</library-name>
    <specification-version>1.1.1</specification-version>
    <implementation-version>1.1.5.1</implementation-version>
</library-ref>
<library-ref>
    <library-name>jsr311-api</library-name>
    <specification-version>1.1.1</specification-version>
    <implementation-version>1.1.1</implementation-version>
</library-ref>
Version can differ in your case (you have to check this when the libraries are deployed).

Jdev 11g "WSEE_SERVLET" failed to preload on startup in Web application

Hi,
if I create a new EJB project, add an Entity and session bean, annotate that bean as @WebService and try to run it, I get the following error:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/WsBean".
java.lang.NullPointerException
     at weblogic.wsee.wsdl.WsdlTypes.collectNamespaces(WsdlTypes.java:213)
     at weblogic.wsee.wsdl.WsdlTypes.collectNamespaces(WsdlTypes.java:229)
     at weblogic.wsee.wsdl.WsdlTypes.collectNamespaces(WsdlTypes.java:229)
     at weblogic.wsee.wsdl.WsdlTypes.parse(WsdlTypes.java:151)
     at weblogic.wsee.wsdl.WsdlDefinitions.parseChild(WsdlDefinitions.java:520)
     at weblogic.wsee.wsdl.WsdlExtensible.parse(WsdlExtensible.java:98)
     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:468)
     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:403)
     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:389)
     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)
     at weblogic.wsee.jaxws.framework.jaxrpc.server.ServerEnvironmentFactory.getWsdlDef(ServerEnvironmentFactory.java:216)
     at weblogic.wsee.jaxws.framework.jaxrpc.EnvironmentFactory.getService(EnvironmentFactory.java:393)
     at weblogic.wsee.jaxws.framework.jaxrpc.EnvironmentFactory.buildDeploymentContext(EnvironmentFactory.java:581)
     at weblogic.wsee.jaxws.framework.jaxrpc.EnvironmentFactory.getDeploymentContext(EnvironmentFactory.java:570)
     at weblogic.wsee.jaxws.framework.jaxrpc.TubelineDeploymentListener.createServer(TubelineDeploymentListener.java:74)
     at weblogic.wsee.jaxws.WLSTubelineAssemblerFactory$TubelineAssemblerImpl.createServer(WLSTubelineAssemblerFactory.java:74)
     at com.sun.xml.ws.server.WSEndpointImpl.<init>(WSEndpointImpl.java:152)
     at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:217)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:510)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:182)
     at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:164)
     at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:51)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:53)
     at javax.servlet.GenericServlet.init(GenericServlet.java:241)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:146)
     at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
     at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1329)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:476)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any ideas why?

hi
This could be confusing without a more specific reference. Looks like it is about this:
"Oracle XDK specified in weblogic-application.xml will cause JAX-WS to fail to deploy (7424247, 7436727)"
http://www.oracle.com/technology/products/jdev/htdocs/11/knownissues.html#wsd11
"+If you create any ADF components ... any code deployed in that application will use the oracle xml parser rather than the default weblogic one ...+"
regards
Jan Vervecken

[HTTP:101216]Servlet: "OnlineReserveren" failed to preload on startup in Web application: "Ruislip_Webservices". java.lang.IllegalStateException

I try to migrate a Oracle iAS webservice to WebLogic 11g by just deploying the ear on WLS.
This results into the following exception: Who can help fixing this error?
[HTTP:101216]Servlet: "OnlineReserveren" failed to preload on startup in Web application: "Ruislip_Webservices". java.lang.IllegalStateException: could not find schema type named {{urn}OnlineReserveren/service/types}TSublocatieBase at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalTypeNode.getSchemaType(AnonymousTypeFinder.java:182) at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getTypeNamed(AnonymousTypeFinder.java:87) at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createBindingTypeFrom(Deploytime109MappingHelper.java:1111) at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:526) at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:273) at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:171) at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86) at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:705) at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201) at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54) at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:91) at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:372) at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:83) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Did you deploy and target the jersey libraries to your server (these can (usually) be found in the ${WL_HOME}/common/deployable-libraries). Deploy these as shared libraries and then reference it by using the following in the weblogic.xml file:
<library-ref>
    <library-name>jersey-bundle</library-name>
    <specification-version>1.1.1</specification-version>
    <implementation-version>1.1.5.1</implementation-version>
</library-ref>
<library-ref>
    <library-name>jsr311-api</library-name>
    <specification-version>1.1.1</specification-version>
    <implementation-version>1.1.1</implementation-version>
</library-ref>
Version can differ in your case (you have to check this when the libraries are deployed).

Disable portal,km startup in multi-application dual stack

Similar Messages

Maybe you are looking for