Deployment problem : WD application in status "stopping"

Hello again,
here is one problem I often meet when I try to deploy my application :
I get a message saying that the deployment started successfully, but nothing follows. When I look in the Visual Administrator (Services -> Deploy), I can see the application i try to deploy with a "Stop" sign. When I try to restart, redeploy, undeploy or stop it through the Visual Admin, nothing happens and I lose control on the Visual Admin.
I applied note 710966 to unlock it, but it's not enough. Restarting the SDM has no effects. The only way we found to get out of this situation was to restart the J2EE server (and the server admin is becoming quite upset with this...).
This problems occurs about 2 times a day, on local and JDI projects. I tried to deploy using the SDM RemoteGUI instead of NWDS, and the problem is still here.
Anyone ever encountered this nasty problem and found a solution quicker than restarting the J2EE server ?
Best Regards,
Julien

Hi
What is the Support Pack version. We have not faced this kind of problem. Does it happen to any application that is deployed. Well in the configtool check what is the value of HeapSize.
Open ConfigTool and select Server Instance and see what are the heap size values. Change it from 128 to atleast 512. Let the dispatcher be 512 and server be 1024.Ensure that you save your values and restart your J2EE. Maybe your memory is low. Just check that and see. I dont see any reason for your problem.
regards
Ravi

Similar Messages

Problem with packageing and deploying a sample application

HI,
I have tried to download and install the server in my system. I am able to deploy a sample application using autodeploy utility.
But when i tried to package a new sample application and deploy i am getting 404 error. For application server i have used 7070 port and not the default 8080 port will this a problem to package & deploy sample application provided with this software.
The error is as below:
HTTP Status 404 - /hello1
type Status report
message /hello1
description The requested resource (/hello1) is not available.
Sun-Java-System/Application-Server

Btw, verify that the url you are trying to access is correct. For instance, assuming you deploy app. without --contextroot option. By default, the url is http://<host>:<port>/<web module name>/<value of url-pattern in web.xml> if your app contains servlet. If your app has jsp then it's http://<host>:<port>/<web module name>/<value of url-pattern in web.xml>/<name of jsp>

Deployment Problems of Enterprise Application in NWDS 7.1

Hello Everyone, 
 
I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer. SUMMARY 
~~~~~~~~~~~~~~~~~~~ 
Successfully deployed: 0 
Deployed with warnings: 0 
Failed deployments: 1 
~~~~~~~~~~~~~~~~~~~ 
ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it. 
 
1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear 
 Name:test~sgj_ent_app_test_three 
 Vendor:sap.com 
 Location:PDI_J2EETST1_D 
 Version:20100716152020 
 Deploy status:Aborted 
 Version:HIGHER 
 
 Description: 
 1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container. 
 
Exception: 
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
 at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
version status: [HIGHER]
deployment status: [Admitted]
description: []
]. Cannot update it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 ... 12 more
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
 at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
 at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
 at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
 at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
 at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
 at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
 at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Edited by: Savin on Aug 5, 2010 10:25 PM
Edited by: Savin on Aug 5, 2010 10:26 PM
Edited by: Savin on Aug 5, 2010 10:31 PM
Edited by: Savin on Aug 5, 2010 5:27 PM
Edited by: Savin on Aug 5, 2010 5:38 PM
Edited by: Savin on Aug 5, 2010 5:44 PM

Hi Veera/Abhi
I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
On my NWDS PDA Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
2009-02-11 13:02:40 ... (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
Madhu--
Please find my ans to the following points mentioned by you
1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
It is assigned
2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
Rule is activated
3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
Rule is activated
4) Make sure that you have installed the following components in the following sequence in the PDA
- Creme
- MinDB/DB2e
- PDA_eswt_container
- PDA Runtime.
Client is installed in this sequence only. I referrred to help.sap.com while installing
the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking up the data. giving the above mentioned error.
Regards
Priya

J2ee server status stopped in one of application server

Short Text
J2ee server status stopped in one of application server
Long Text
Dear supprot,
We have 3 application servers to our production server.
App1 and App3 are working fine. when i am trying to start App2
J2ee server0 for the same server is getting stopped.
at that time "r3trans -d" is also taking lots of time on all the servers but giving RC 000.
when i will stop the app2 application server again "r3trans -d" status is
coming fast with 0000 for remaining servers and at that time everything is working fine.
please kindly help me to resolve this problem.
Regards
Nirgun

Hello,
Refer to the log files in the instance work directory for a clue why the server node does not start. Usually the files you are interested in are:
dev_serverX
std_serverX.out
dev_disp
If you share these files I could help you identify and fix the problem.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA)

Problems about deploying Oracle web application (Forms, Reports)

I am going to deploy Oracle web applications (Forms and Reports) and plan to use the same server machine for both Application web server and Database server.
1. How can I enable SSL (for data encryption) on Application web server for Oracle Forms ?
2. Since both Application web server and Database server will use the same machine, do I still need Oracle Advanced Security for data transmission between Application web server and Database server if data encryption for transmission is required ?
3. Can I user Oracle Forms to call Oracle Report on web as I did in Client/Server in the past ?
Experts like you may have come across such problems. Would you please give me some opinions/ideas ?
Regards,
Richard

1. check the paper about the Forms servlet architecture on otn forms section for SSL tips.
3. Check the reports and forms integration paper on otn too.

Web-application deployment problem (404 - File not found)

Hello
Does anyone have had the same problems like me on deploying java web-applications on iPlanet WS 6.0?
I started with the HelloWorld.war example that came with the server and went through the manual but no luck so far. Heres what I did:
0. Checked that webapps are enabled in the servler.xml file
1. Created a directory /opt/webapps and /opt/webapps/hello with sufficient permissions
2. Copied the HelloWorld.war example to /opt/webapps
3. Deployed the excample on my test-server using the webinterface.
Heres the content of the web-apps.xml file of my testserver after step 3:
[DTD here]
<vs>
<jsp-servlet enable="true">
<init-param>
<param-name>use-precompiled</param-name>
<param-value>true</param-value>
</init-param>
</jsp-servlet>
<web-app uri="/hello" dir="/opt/webapps/hello" enable="true"/>
</vs>
All files have been extracted to /opt/webapps/hello properly. The server has been restarted.
When I finally point my browser to http://server/hello or hello/index.jsp I get only a 404 - File not found message by the server. The context path seems to be totaly ignored.
Heres the error log of the server
[17/Feb/2003:16:17:38] info (12040): successful server startup
[17/Feb/2003:16:17:38] info (12040): iPlanet-WebServer-Enterprise/6.0SP2 B11/13/2001 00:49
[17/Feb/2003:16:17:39] info (12041): Installing a new configuration
[17/Feb/2003:16:17:39] info (12041): [LS ls1] http://XXX.XXX.XXX.XX, port 1080 ready to accept requests
[17/Feb/2003:16:17:39] info (12041): A new configuration was successfully installed
[17/Feb/2003:16:17:40] info (12041): Using the Solaris VM v1.2.2 from Sun Microsystems Inc.
[17/Feb/2003:16:17:40] info (12041): Java VM classpath: /www/ns-home6sp2/plugins/servlets/examples/legacy/beans.10/SDKBeans10.jar:/opt/jdk1.2.2/lib/tools.jar:/www/ns-home6sp2/bin/https/jar/NSServletLayer.jar:/www/ns-home6sp2/bin/https/jar/NSJavaUtil.jar:/www/ns-home6sp2/bin/https/jar/NSJavaMiscUtil.jar:/www/ns-home6sp2/bin/https/jar/servlet.jar:/www/ns-home6sp2/bin/https/jar/servlet-2.3-filters-api.jar:/www/ns-home6sp2/bin/https/jar/jsp092.jar:/www/ns-home6sp2/bin/https/jar/jaxp.jar:/www/ns-home6sp2/bin/https/jar/crimson.jar:/www/ns-home6sp2/bin/https/jar/xalan.jar:/www/ns-home6sp2/bin/https/jar/jspengine.jar:
[17/Feb/2003:16:17:40] info (12041): Loading IWSSessionManager by default.
[17/Feb/2003:16:17:40] info (12041): IWSSessionManager: Maximum number of sessions is 1000
[17/Feb/2003:16:17:40] info (12041): Adding web application (/hello) at (/opt/webapps/hello)
[17/Feb/2003:16:17:40] info (12041): Loading IWSSessionManager by default.
[17/Feb/2003:16:17:40] info (12041): IWSSessionManager: Maximum number of sessions is 1000
[17/Feb/2003:16:17:40] info (12041): vs(https-duke)servlet 'snoop' class = 'SnoopServlet' loaded in context = '/hello'
[17/Feb/2003:16:17:40] info (12041): snoop: init
[17/Feb/2003:16:17:40] info (12041): Successfully initialized web application environment (web-apps.xml) for virtual server (https-duke)

i had similar problem due to the incorrect jdk path...
try http://..../hello/snoop, if this works, it seems that the jsp file cannot be compiled automatically and jdk path needs to be checked...

Problem while deploying the ADF application in weblogic 10.3

Hi,
We did the application using ADF and EJB3.0 in JDeveloper11g relese and this application is working fine when i run in the JDeveloper release. When i try to deploy the same application in weblogic 10.3(Which I downloded and installed) i am getting following error.
shared library "adf.oracle.domain" could not be found.
Can any one tell me, what the problem is?
Thanking you,
NIRANJAN REDDY.

person with many names,
You need to configure the WLS domain for ADF.
http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/toc.htm#wls_adf
John

Problem deploying a web application (war)

Hello,
I am having a problem deploying a web application in Tomcat.
Here is what happens:
-I copied the war file into the webapps directory.
-I started Tomcat.
-Tomcat automatically expanded the war file into a directory of the same name.
The problem is that I get the following error: "The requested resource (/jadmin) is not available." when I try to access my web application
Can anyone please help?
Thanks in advance,
Balteo.

Hi,
check the Tomcat log file <tomcat_dir>/logs/localhost_log.yyyy-mm-dd.txt and see if there is an error corresponding to the deployement of the (/jadmin) context.

Deploying problem of web dynpro java application

Hi,
I have a web dynpro java application with no problem about deploying.
I copied this application with another name.
I tryed new application to deploy but sdm aborted with error.
Error
19.Tem.2011 10:22:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : vserver0202
SDM port : 52018
URL to deploy : file:/C:/Users/CEMIL~1.BOZ/AppData/Local/Temp/temp27456HF_PERS_RAPOR_BUTCE.ear
Result
=> deployment aborted : file:/C:/Users/CEMIL~1.BOZ/AppData/Local/Temp/temp27456HF_PERS_RAPOR_BUTCE.ear
Aborted: development component 'HF_PERS_RAPOR_BUTCE'/'local'/'LOKAL'/'0.2011.07.19.10.22.15'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/HF_PERS_RAPOR_BUTCE.. Reason: Clusterwide exception: Failed to deploy application local/HF_PERS_RAPOR_BUTCE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/HF_PERS_RAPOR_BUTCE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted

Hi,
Since the exception says "Are all referenced components deployed and available on the engine?"
Check wether any DC is used as a used DC in the webdynpro component which you are deploying.
If any used DC is available try to deploy that DC in the server and then deploy ur webdynpro application.
If all reference DC's are avialable in server, still if you get this error try to rename the component and reload+rebuild the project and deploy it.
Hope this helps you...
Regards,
Saleem Mohammad.

Terracotta: application deploy problem (WLP 9.2)

hi,
when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
regards,
erik
log snippet:
####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
Unable to deploy EJB: netuix.jar from netuix.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
public final class ProducerPersistenceManager_7vyoe8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
public final class BookDefinitionManager_1xzrxc_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
public final class PortletCategoryManager_uhkdka_Impl
[MORE CLASSES HERE]
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
public final class PortalDefinitionManager_d875a8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
public final class PageDefinitionManager_c4el9c_Impl
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
25 errors
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
 at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
 at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: firefox.exe Application Version: 1.9.2.3855 Application Timestamp: 4c48d5ce Hang Signature: 9962

I am having this problem, in the first window when I try to do anything.
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: firefox.exe
Application Version: 1.9.2.3855
Application Timestamp: 4c48d5ce
Hang Signature: 9962
Hang Type: 0
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Hang Signature 1: 5df72ce88195c0212c542e9c8c172716
Additional Hang Signature 2: 2b94
Additional Hang Signature 3: 9acafbb8ad01bf9d2eb258d8fddad3ca
Additional Hang Signature 4: 9962
Additional Hang Signature 5: 5df72ce88195c0212c542e9c8c172716
Additional Hang Signature 6: 2b94
Additional Hang Signature 7: 9acafbb8ad01bf9d2eb258d8fddad3ca
== This happened ==
Every time Firefox opened
== User Agent ==
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4

I suspect a RAM or hardware problem.

[deployment] problems with a big application

Hi, I try to deploy a big application using EJB and web modules. All seem to be fine but I get that error when initializing something after d?ployment of my modules:
28050 catalog INFO [[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel
.Default (self-tuning)'] openjpa.MetaData - Parsing class "be.star.design.model.
catalog.entity.UserRole".
28070 catalog INFO [[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel
.Default (self-tuning)'] openjpa.MetaData - Parsing sequence "genUserRole".
<25-avr.-2007 10 h 22 min 44 s CEST> <Error> <ServletContext-/config> <BEA-00000
0> <action: null
javax.ejb.EJBException: nested exception is: <4|true|0.9.7> org.apache.openjpa.p
ersistence.ArgumentException: You have supplied columns for "be.star.design.mode
l.catalog.entity.User.userRestrictions", but this mapping cannot have columns in
this context.
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(Remote
BusinessIntfProxy.java:57)
at $Proxy102.getUser(Unknown Source)
at be.star.webconfig.plugin.InitCatalogDBPlugIn.createUser(InitCatalogDB
PlugIn.java:361)
at be.star.webconfig.plugin.InitCatalogDBPlugIn.createBasicParameters(In
itCatalogDBPlugIn.java:339)
at be.star.webconfig.plugin.InitCatalogDBPlugIn.init(InitCatalogDBPlugIn
.java:412)
Truncated. see log file for complete stacktrace
>
<25-avr.-2007 10 h 22 min 44 s CEST> <Error> <HTTP> <BEA-101216> <Servlet: "acti
on" failed to preload on startup in Web application: "config".
javax.servlet.UnavailableException
at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServle
t.java:880)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:336)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
ubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
Truncated. see log file for complete stacktrace
>
Any ideas ?
Is it a struts problems ?
Incompatibility ?
Thanks

There is something wrong with your PC
I am using the same config while I work on TV Animations with
fla files > 150 MB in size and more than 3000 frames in 30
scenes, 128 KBPS sound etc. - Cakewalk - No Hour Glass.
I am using original Intel Motherboard - 945 HT

Problem with Hot deployment of Struts application

I used the exploded archive format to deploy a web application ( no EJB Jars etc involved). But after modifying a custom Action class and placing it in the WEB-inf\classes, I get the following exception: java.lang.ClassCastException: org.apache.struts.action.RequestProcessor at org.apache.struts.action.ActionServlet.getProcessorForModule Clearly weblogic managed to load the new Action class, and if I understand correctly it would have destroyed the old web class loader and create a new one and loaded all the classes visible to the web app class loader. But somehow it still seems to cache the RequestProcessor class.. Can some one please throw some light on this.
PS I dont have anything in the server classpath, and there is no chance of duplicate copies anywhere in the classpath or under web-inf

Yes, I added the line getServletContext().removeAttribute(Globals.REQUEST_PROCESSOR_KEY) in ActionServlet's destroy(). It works now.
It was previously getting back the old class reference while doing a getAttribute(REQ....) , so was giving the classcast.
Not sure if this is a bug in the ActionServlet, or if I am missing something.

Webdynpro application deployment problem

Hi, I am tring to deploy webdynpro application using netweaver studio 2004 version, and using ep6.
when I deploy and run application , I get following error:-
URL to deploy : file:/C:/DOCUME1/PROCES1/LOCALS~1/Temp/temp32470a.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PROCES1/LOCALS~1/Temp/temp32470a.ear
Aborted: development component 'a'/'local'/'LOKAL'/'0.2006.09.28.23.40.19':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Only Administrators have the right to perform this operation.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
1.
why does it say only administrator can deploy? I am uing login which has admin rights.
2. is there any other way to deploy ear file? using some SDM or other way? How?

I tried using SDM, same error message: only adminsitrators have rights to perform this action.
I think, I am not able to access J2EE engine.
How to get J2EE engine access?
Message was edited by: Ankit

Portal Application deployment problem to Managed Web Server

I'm trying to deploy an ADF application using JSR168 portlets to a Managed Web Server on WebCenter 11g and I'm getting the following error in the log file after running the portal.jsp (I get 'Portlet unavailable' on the browser page):
oracle.adf.model.portlet.binding.PortletBindingException: The metadata for portlet binding TasksPortlet1_1 was not found in MDS.
When I deploy the application from JDeveloper to the Managed Web Server I get the following error (The application does deploy successfully):
Error during portlet export. Portlets will not be available in the target application. Context: input mds repository file path = C:\JDeveloper\mywork\Mindflow\mds. output mds repository file path = C:\JDeveloper\mywork\Mindflow\.mdsExport. input connections file path and name = /C:/JDeveloper/mywork/Mindflow/.adf/META-INF/connections.xml. export ID = /oracle/adf/portlet/export. producer/portlet IDs to export: [oracle/adf/portlet/MindFlowWsrpPortletProducer].
However if I right-click on the portal.jsp page and select Run from JDeveloper and run it within the Integrated WLS it does run fine there.
Is there something special that needs to be set for the Deployment on either the application or project? Or is there something that needs to be setup via the web-based Adminstrative Console (I have verified that the MindFlowWsrpPortletProducer is registered on the Admin console)?
Thanks,
Randy Skold

Thanks for the reply ... here is the answer to your questions along with an update to some more information after trying something different
Did you deploy the WebCenter Managed server from Jdeveloper
I am deploying the application to the WebCenter Managed server from JDeveloper.
What managed server did you deploy it to - a custom server that you created?
Yes this is a custom Managed Server (called MindFlow). At the time of your response the only two servers up and running on WebCenter was the AdminServer and MindFlow.
Did the deployment go through?
Yes
Are there any errors in the managed server log when you access the page?
Yes these where the errors showing that it could not connect with the metadata via the repositories.
Now for the update:
I went ahead and started up the WLS_Portlet managed server that comes with WebCenter. When I did this I got the following error:
WSM-04509: cannot initialize the connection to the data store
I then deployed the Portlet Producer Application to the WLS_Portlet from JDeveloper. I then grabbed the url for the newly created portlet producer and updated the connection on the Portal application. After doing this and updating the portal.jspx file, I then deployed the Portal application to the MindFlow managed web server. I then brought up the portal.jspx page via a browser and was able to bring back results. The only issue now is that while doing this I got multiple MDS errors (including the initialize error above) and not sure if I can ignore these or not. One of the errors received was as follows:
oracle.mds.exception.MDSException: MDS-01258: The value @MDS_CLASS for property class-name is invalid.

Deployment problem : WD application in status "stopping"

Similar Messages

Maybe you are looking for