Problem deploying webservice application to cluster

My web service is packaged inside an ear file generated by WLS workshop. The ear deploys and runs fine on standalone WLS 9.2.2 when deployed through console. When same ear file is deployed to cluster, the webservice does node show up on the managed nodes. Under test endpoints, WLS console shows links only to wsdl locations. WSDL is available on clicking the link. The console does not show links to webservice test client as it does on standalone installation. If I type in the expected test client location I get an HTTP 404 error. I do not see any obvious error messages during application deployment or runtime in the log file of admin server or managed nodes.
Any help on troubleshooting this issue is appreciated. Thanks.

The cluster address has a typo in it. The interesting part is weblogic does not report any errors / warning if the IP address in cluster address are invalid (not incorrect). So, if you give an IP address as 111.111.1111 you will get nothing in logs and app will not work but status of servers and app will be shown as active as if everything is fine.

Similar Messages

Serious problems deploying web application with enterprise manager

Hi all,
First I have to say that this thing that has happened to me today is freaking bizarre... I was trying to make a new deployment of a web application on OAS 10.1.2, using the Enterprise Manager. The application is using Spring and DWR, therefore it has some XML files included. The application worked perfect in JDeveloper 9.0.4, our development tool, and I've previously developed very similar applications in the past, and deployed them on the same server without any problem.
Today, when I was trying to deploy my .ear file, I got this error message:
The file specified, "FindAnExpert.ear" is not a valid ear file.
I tried with the .war file, and this happened:
Base Exception:
java.util.zip.ZipException
invalid END header (bad central directory offset). invalid END header (bad central directory offset)
I checked that all the included .jar files were fine, I even replaced them with new ones. I started to remove files from the .war file and discovered that without the XML files I was able to deploy the application. Then I copied over those XML files through FTP and the application is working correctly, but I was not able to use the Enterprise Manager to deploy it!!! The XML files are well formed, on of them contains the details of a data source that I also reviewed to be sure that it was correctly configured... This is nuts... any ideas over there???
Thanks in advance,
Luis

Luis,
If all of the files uploaded piecemeal worked fine, then I believe your problem to be with your deployment descriptor(s). Also, note that the .war file lives in a different directory:
C:\oc4j\j2ee\home\applications\Application-Name
Perhaps if you have time you could post all of the associated deployment descriptor files. Log files from the C:\oc4j\j2ee\home\log\oc4j directory would also help to troubleshoot your deployment issues. You can turn up the logging level to "FINEST" for maximum output to your log file.
-Michael

Problem deploying an application with more task flow

Hi all,
I am using Jdeveloper 11.1.1.0 and weblogic 10.3.1
I am trying to deploy an application that has more task flows.
I am in the home page and I click on a button and I go to a new task flow.
If I run the application from Jdeveloper it works, but if I deploy the application and try to do it I have this error on the page .jspx:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and this error on the server log:
servlet failed with Exception oracle.adf.controller.security.AuthorizationException:ADFC-0619: Can't check authorization at:
'/myFolder/calledTaskFlow.xml#myViewActivityoracle.adf.controller.internal.security.AuthorizationEnforcer.handleFailure<AuthorizationEnforcer.java:147>
oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPermission
oracle.adf.controller.internal.security.AuthorizationEnforcer.checkRead
oracle.adf.controller.internal.security.AuthorizationEnforcer.getTaskFlowDefinition
oracle.adfinternal.controller.activity.TaskFlowCallActivityLogic.findTaskFlowDefinition
What's the problem?
Thanks
Edited by: user10799119 on 2-set-2009 6.27

I have not understood well what you mean: "Its better you create an EAR profile, have proper ADF Security set up in Jdev with users and roles, and also proper roles and permissions assigned to taskflows, and then deploy the profile directly from JDev."
I have proper ADF Security set up in Jdev with users and roles, and also proper roles and permissions assigned to taskflows, and then deploy the profile directly from JDev. After that I have deployed my application to EAR file. I am using the EAR file create by default by Jdeveloper. Is this correct? Or have I to create another profile?
"If you still wanna deploy the EAR, check the Users and Roles section under security in the Weblogic console. Users and Roles need to be configured in Weblogic as well. In 11g they get deployed automatically but with any previous version of Jdev you might have to check this in the WLS console."
In the weblogic console, clicking on Security realms --> myRealm --> providers, I have defined myAuthenticator
I am using Jdeveloper 11.1.1.0 and web logic server 10.3.1, so it seems to me that users and roles get deployed automatically
what have I to do?
thanks

Problem deploying webservice client app

I have a JAX-RPC webservice client application which works flawlessly from within JDeveloper 10.1.3 EA1. However, after deploying the application and running it, I get the following error which I have been unable to trace to a missing library:
Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: javax/xml /rpc/ServiceFactory
at com.brunata.ptd.proxy.TempmonSoapHttpPortClient.<init>(TempmonSoapHtt pPortClient.java:17)
at com.brunata.ptd.proxy.PTDProxy.<init>(PTDProxy.java:24)
at com.brunata.ptd.proxy.PTDProxy.sharedInstance(PTDProxy.java:35)
at com.brunata.ptd.views.PTDAppView.<init>(PTDAppView.java:71)
at com.brunata.ptd.PTDApp.createGUI(PTDApp.java:93)
I made sure to include all libraries I can see JDeveloper is referencing, yet obviously I must be missing something. I include the following:
\j2ee\home\lib
\webservices\lib
\jlib
\lib\xmlparserv2.jar
\xdk\lib\xml.jar
\j2ee\home
\rdbms\jlib\xdb.jar
\diagnostics\lib\ojdl2.jar
\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar
\jakarta-taglibs\commons-logging-1.0.3\commons-logging-api.jar
I must admit, I am a bit shocked that/if I will have to deploy all these files into a some 40MB jar, not exactly fitting for the Java Web Start appliation I am working on.
Any help greaty appreciated,
Casper Bang

Hi Eric,
Thanks for the single-jar solution tip. Unfortunately I still get the same error (javax.xml.rpc.ServiceFactory) even with the use of that file. If I try to run manually from a commandline and include jaxrpc-api.jar, I get a little further though:
java -classpath J:\jdevstudiobase1013\jdev\mywork\PTD\PTD\classes;J:\jdevj2eebase1013\webservices\lib\jaxrpc-ap
i.jar;J:\jdevstudiobase1013\jdev\mywork\PTD\PTD\deploy\jcommon-1.0.0-rc1.jar com
.brunata.ptd.PTDApp
javax.xml.rpc.ServiceException: Provider oracle.j2ee.ws.client.ServiceFactoryImp
l not found
at javax.xml.rpc.FactoryFinder.newInstance(FactoryFinder.java:44)
at javax.xml.rpc.FactoryFinder.find(FactoryFinder.java:137)
at javax.xml.rpc.ServiceFactory.newInstance(ServiceFactory.java:69)
at com.brunata.ptd.proxy.TempmonSoapHttpPortClient.<init>(TempmonSoapHtt
pPortClient.java:17)
at com.brunata.ptd.proxy.PTDProxy.<init>(PTDProxy.java:24)
Which lib is this? (Any documentation somewhere for where packages are stored?)
Thanks a lot,
Casper

Problem deploying an Application

Hello everybody,
when i try to deploy an application (e.g. a WebDynpro) i get an error:
20.03.2005 14:18:55 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : host
SDM port : 50018
URL to deploy : file:/C:/DOKUME1/host/LOKALE1/Temp/temp35261Welcome.ear
Deployment exception : Server host did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server host at port 50018: host
Inner exception was :
Server host did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server host at port 50018: host
Anyone has any idea whats the problem? The J2EE-Server is running. The Management Console has everything on green. I can also log in on the server http://myhost:50000/index.html
http://myhost:50000/sap/monitoring/SystemInfo says that the SDM is running.
regards, Markus.
Message was edited by: Markus Klein

Hello,
im using the pwd i provided during the setup procedure. And yes im sure im using the correct one. When im deploying my application a popup screen appears for providing the sdn password, no username at all is required at this point. I didnt even had to provide a username for the SDM at all during the installation. Anyway, as soon as i provided the pwd at the popup, i get the error i posted above.
regards,
Markus

Problem deploying web application on WLS 8.1

Hi,
When I try to deploy a web application on weblogic 8.1 it comes back with success.But
trying to access it or testing it through admin console gives me the following
erors -
403 - Forbidden or
404 - Not found
Here is what I am doing
My web application is in a war file called paypluscls.war that I've saved inD:\bea\user_projects\domains\mydomain\applications
folder. My weblogic.xml reads like this:
<weblogic-web-app>
<virtual-directory-mapping>
<local-path>d:/bea/user_projects/domains/m
<url-pattern>/paypluscls/*</url-pattern>
</virtual-directory-mapping>
On deploying the application I get success message, but when I try running it
using the following in my browser : http://127.0.0.1:7001/paypluscls i get 403
forbidden error
and if I try http://127.0.0.1:7001/paypluscls/index.htm , i get 404 file not found
error. Please note that index.htm is present in my paypluscls.war.
What am I doing wrong? A quick response will be highly appreciated.

Define a context-root element in weblogic.xml
<weblogic-web-app>
<context-root>paypluscls</context-root>
</weblogic-web-app>
Get index.htm with url:
http://127.0.0.1:7001/paypluscls/index.htm
"vikas" <[email protected]> wrote:
>
Hi,
When I try to deploy a web application on weblogic 8.1 it comes back
with success.But
trying to access it or testing it through admin console gives me the
following
erors -
403 - Forbidden or
404 - Not found
Here is what I am doing
My web application is in a war file called paypluscls.war that I've saved
inD:\bea\user_projects\domains\mydomain\applications
folder. My weblogic.xml reads like this:
<weblogic-web-app>
<virtual-directory-mapping>
<local-path>d:/bea/user_projects/domains/m
<url-pattern>/paypluscls/*</url-pattern>
</virtual-directory-mapping>
On deploying the application I get success message, but when I try running
it
using the following in my browser : http://127.0.0.1:7001/paypluscls
i get 403
forbidden error
and if I try http://127.0.0.1:7001/paypluscls/index.htm , i get 404 file
not found
error. Please note that index.htm is present in my paypluscls.war.
What am I doing wrong? A quick response will be highly appreciated.

I've problem deploying JSF applications

Hi guys;
I've created simple JSF Web Application. Its only blank page contains button that brings u to other page. When I run it from NetBeans IDE it runs perfect. But when I take the application folder to deploy it to tomcat manually it won't run even with the server used by the IDE itself. I noticed that when the IDE starts the server it initializes also sun JSF implementation which I think the key to make JSF run on tomcat server.
Any body knows how to deploy JSF Applications, or how to generate distributable package..
Thanks alot to all
Edited by: Shampion on Oct 12, 2008 2:02 AM
Edited by: Shampion on Oct 12, 2008 2:05 AM

You'll probably get better answers if you post in the correct forum. JSF questions should be asked in the JSF forum:
[http://forums.sun.com/forum.jspa?forumID=427]
Kaj

Problem deploying war file in cluster wls 10 mp1

Hi,
Weblogic throws the following exception while i am deploying a war file in clusters with 6 servers distributed in 2 physical machines.
<Mar 6, 2008 12:22:52 PM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'siiaf'.>
<Mar 6, 2008 12:22:52 PM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
java.util.zip.ZipException: Error opening file - /usr/local/bea/user_projects/domains/sctDomain10/stage/siiaf/siiaf.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:81)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:70)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
<Mar 6, 2008 12:22:52 PM CST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: java.util.zip.ZipException: Error opening file - /usr/local/bea/user_projects/domains/sctDomain10/stage/siiaf/siiaf.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:81)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:70)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
The staging mode of all servers is "stage".
I think the problem is the file size because my war file size is 45 mb aprox.
When i delete some files within the file and the size is minor (2 mb) , the deploy process ends successfully.
I appreciate your help
GPA

Can you verify the integrity of your staged war file? This problem could be due to a bug in the container.You may want to open a support case with BEA

Problems deploying an application

Hi,
I have deployed my aplication in a local machine but when I execute these I have some problemes in the console
Error: CONN-003: socket receive error (RecvBuffer 1)
Error: Exception: SERVLET-execution_failed: Error in excuting servlet StaticServlet: java.lang.NullPointerException
Exception Stack Trace:
java.lang.NullPointerException at com.netscape.server.deployment.AppCompGDSUtil.getDescriptorFromGDSByKey(Unknown Source)
at com.netscape.server.deployment.WebAppCompGDSUtil.getDescriptorFromGDSByKey(Unknown Source)
at com.netscape.server.deployment.AppComponentDescriptorUtil.createWebAppComponentDescriptorCore(Unknown Source)
at com.netscape.server.deployment.DescriptorManager.getWebAppDescriptorFromCache(Unknown Source)
at com.netscape.server.servlet.servletrunner.StaticServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.serviceHttpServlet.java:865)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(UnknownSource)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
What's happened?? thanks ind advance

Hi Oriol -
The error being reported is that a class can't be found:
>
[com.icesoft.faces.context.View] - Problem encountered during View.servePage
java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
>
Looking around, it seems this is caused by having JSF 2.x in the classpath, which is not compatible with ICEFaces 1.8.x.:
http://jira.icesoft.org/browse/ICE-4704:
>
ICEfaces 1.8.x is not certified to run on JSF 2.0 runtimes. When this combination is attempted with ICEfaces 1.8.1, it fails with an exception such as
java.lang.ClassNotFoundException: org.icefaces.x.context.BridgeFacesContext2
>
Since WLS 12c provides a JSF 2.1.x environment by default, you will need to employ the JSF 1.2 alternative. From a previous discussion here on an OTN forum, I believe there was an additional step required to make it work, see here for details:
Re: jsf 1.2 on weblogic 12c
-steve-

Problem deploying an application to SunOne 8.1 instance

Hi I am trying to deploy one ear file to one of the SunOne instance locally. I am using SunOne8.1.
But I am getting the following error:
[#|2006-07-24T16:21:17.706+0530|SEVERE|sun-appserver-ee8.1|javax.enterprise.system.tools.deployment|_ThreadID=14;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: java.util.zip.ZipException: invalid entry size (expected 7080 but got 6991 bytes)
at com.sun.enterprise.deployment.backend.J2EEModuleExploder.explode(J2EEModuleExploder.java:145)
at com.sun.enterprise.deployment.backend.EarExploder.explodeWars(EarExploder.java:92)
at com.sun.enterprise.deployment.backend.EarExploder.explode(EarExploder.java:64)
at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:258)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:160)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:107)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:188)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:520)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:171)
|#]
Has anyone faced this kind of problem before? I have deployed the same ear file into SunOne 7, it worked fine.

Hi,
most of the time , if it works on 7 it can work on 8.1.
Can you check if you have enough temp space in hard disk.
if possible check the latest one from sun site Appserver 8.2
or if u r using platform edition download glassfish.
and then try.
iwhich platform u r using
run this command
<AS_INSTALL>/bin/asadmin version --verbose
thanks
Gajanan.

Error while deploying adf application using ant script or jdevloper IDE

Hi All,
While deploying adf application into cluster weblogic server I am getting strange error though my weblogic server is working fine as I checked it from weblogic console. Seems that there is some heap memory issue but don’t know the exact cause as it work perfectly if I restart the server.
Same error i get when i try to deploy application from Jdeveloper IDE though it created the server connection successfully.
Please help me by provided valuable tips to overcome this problem or any special tips to optimize weblogic server for ADF.
Thanks in advance
Error Reference:
Buildfile: builddeploy.xml
deploy:
[wldeploy] weblogic.Deployer -debug -stage -verbose -upload -noexit -name admin -source W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war -targets ADR_Cluster_1 -adminurl t3://WebServercom:7001 -user weblogic -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -debug -stage -verbose -upload -noexit -name admin -source W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war -targets ADR_Cluster_1 -adminurl t3://WebServercom:7001 -user weblogic -deploy
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at WebServercom:7001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://WebServercom:7001
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://WebServercom:7001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://WebServercom:7001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1d27069
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1d27069
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@200db9
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@200db9
[wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: ADR_domain
[wldeploy] [ServerConnectionImpl.setRemote():480] : Running in remote mode
[wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]21b
[wldeploy] [BasicOperation.dumpTmids():706] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():708] : {Target=ADR_Cluster_1, WebLogicTargetType=cluster, Name=admin}, targeted=true
[wldeploy] [BasicOperation.deriveAppName():140] : appname established as: admin
[wldeploy] <23-Sep-2011 11:05:14 o'clock BST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, admin [archive: W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war], to ADR_Cluster_1 .>
[wldeploy] [ServerConnectionImpl.upload():849] : Uploaded app to /data/app/Oracle/Middleware/user_projects/domains/ADR_domain/servers/AdminServer/upload/admin
[wldeploy] [BasicOperation.dumpTmids():706] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():708] : {Target=ADR_Cluster_1, WebLogicTargetType=cluster, Name=admin}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():623] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] ADR_Cluster_1
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: \data\app\Oracle\Middleware\user_projects\domains\ADR_domain\servers\AdminServer\upload\admin
[wldeploy] App config: \data\app\Oracle\Middleware\user_projects\domains\ADR_domain\servers\AdminServer\upload\admin\plan
[wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=admin,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
[wldeploy]
[wldeploy] [BasicOperation.execute():440] : Initiating deploy operation for app, admin, on targets:
[wldeploy] [BasicOperation.execute():442] : ADR_Cluster_1
[wldeploy] Task 5 initiated: [Deployer:149026]deploy application admin on ADR_Cluster_1.
[wldeploy] dumping Exception stack
[wldeploy] Task 5 failed: [Deployer:149026]deploy application admin on ADR_Cluster_1.
[wldeploy] Target state: deploy failed on Cluster ADR_Cluster_1
[wldeploy] java.lang.Exception: [DeploymentService:290036]Deployment for request id '1316772356780' is deferred since target 'ADR_ManagedServer_2' is disconnected.
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.commitFailedDueToServerDisconnect(AdminRequestStatus.java:1870)
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.access$600(AdminRequestStatus.java:51)
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus$CommitDisconnectListenerImpl.onDisconnect(AdminRequestStatus.java:2042)
[wldeploy] at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerDisconnectListenerImpl.onDisconnect(ServerDisconnectManager.java:124)
[wldeploy] at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerConnectDisconnectListenerImpl$2.run(ServerDisconnectManager.java:219)
[wldeploy] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
[wldeploy] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[wldeploy] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[wldeploy]
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + admin ADR_Cluster_1
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 5 failed: [Deployer:149026]deploy application admin on ADR_Cluster_1.
[wldeploy] Target state: deploy failed on Cluster ADR_Cluster_1
[wldeploy] java.lang.Exception: [DeploymentService:290036]Deployment for request id '1316772356780' is deferred since target 'ADR_ManagedServer_2' is disconnected.
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.commitFailedDueToServerDisconnect(AdminRequestStatus.java:1870)
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.access$600(AdminRequestStatus.java:51)
[wldeploy] at weblogic.deploy.service.internal.adminserver.AdminRequestStatus$CommitDisconnectListenerImpl.onDisconnect(AdminRequestStatus.java:2042)
[wldeploy] at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerDisconnectListenerImpl.onDisconnect(ServerDisconnectManager.java:124)
[wldeploy] at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerConnectDisconnectListenerImpl$2.run(ServerDisconnectManager.java:219)
[wldeploy] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
[wldeploy] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[wldeploy] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[wldeploy]
[wldeploy]
[wldeploy]
[wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy] at weblogic.Deployer.run(Deployer.java:70)
[wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:348)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:357)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:758)
[wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:217)
[wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection

Well, I guess you have a problem here. Check http://multikoop.blogspot.de/2012/12/deploying-adf-applications-into-oracle.html and from this
>
Note: In its current stage Oracle Java Cloud Service runs WebLogic Server 10.3.6 with the appropriate Runtime ADF 11.1.1.6. Deployment of ADF 11gR2 Applications is currently not supported. Beside this limitation some ADF Features are not supported on the Oracle Cloud. According to the Oracle Cloud Documentation it is not supported to use the following ADF features
ADF Desktop Integration
ADF mBean
ADF MDS (Seeded customizations or cross-session personalization)
ADF Mobile
ADF Active Data Services (=> No real-time ADF Web Apps in Oracles Cloud)
ADF Business Components services interfaces (web services) or events
ADF Data Controls for BI, Essbase, BAM, and JMX
Further there are some restrictions which are good to know I think
No Java Mail API (=>Sending Mails is prohibited)
No File system access by deployed applications (=>Writing files is prohibited)
No Direct use of Oracle JDBC Driver APIs
No Java Message Service (JMS)
Max Size for deployment archive 95MB
>
I hope for you that the information from the blog has changes in the meantime (blog is from end of last year). Check the current doc for the cloud ...
Timo

Error deploying several applications

Hello,
I have a problem deploying several applications. They are 3 wars that are continuously deployed. The error obtained is the following
deploy_:
+[java]+
+[java] Initializing WebLogic Scripting Tool (WLST) ...+
+[java]+
+[java] WARNING - Unable to create log file </bea/bea1035/modules/../logs/wlst_20110901091225.log>: java.io.IOException: No space left on device+
+[java] Welcome to WebLogic Server Administration Scripting Shell+
+[java]+
+[java] Type help() for help on available commands+
+[java]+
+[java] Could not find the properties file to load properties from /config/wl11_extra_ava/w63/w63Resources.properties.+
+[java] ==> Fichero de configuracion: /config/wl11_extra_ava/w63/w63Config.properties+
+[java] ==> Fichero de recursos: /config/wl11_extra_ava/w63/w63Resources.properties+
+[java] unlocking ...+
+[java] Connecting to t3://wl11admin27.ejiepru.net:8124 with userid weblogic11 ...+
+[java] Successfully connected to Admin Server 'admin' that belongs to domain 'wl11_extra_ava'.+
+[java]+
+[java] Warning: An insecure protocol was used to connect to the+
+[java] server. To ensure on-the-wire security, the SSL port or+
+[java] Admin port should be used instead.+
+[java]+
+[java] Location changed to edit tree. This is a writable tree with+
+[java] DomainMBean as the root. To make changes you will need to start+
+[java] an edit session via startEdit().+
+[java]+
+[java] For more help, use help(edit)+
+[java]+
+[java] Starting an edit session ...+
+[java] Started edit session, please be sure to save and activate your+
+[java] changes once you are done.+
+[java] Saving all your changes ...+
+[java] Saved all your changes successfully.+
+[java] Activating all your changes, this may take a while ...+
+[java] The edit lock associated with this edit session is released+
+[java] once the activation is completed.+
+[java] Activation completed+
+[java] weblogic.Deployer invoked with options: -adminurl t3://wl11admin27.ejiepru.net:8124 -userconfigfile /j2se/apache-ant-1.7.1/ejie_wls11/user.secure -userkeyfile /j2se/apache-ant-1.7.1/ejie_wls11/password.secure -name ispacmgr -targets gestExp1 -deploy /aplic/w63/dist/ispacmgr.war -stage -timeout 3600 -debug -verbose+
+[java] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments+
+[java] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at wl11admin27.ejiepru.net:8124, as user weblogic11+
+[java] [ServerConnectionImpl.getEnvironment():286] : setting environment+
+[java] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://wl11admin27.ejiepru.net:8124+
+[java] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://wl11admin27.ejiepru.net:8124/jndi/weblogic.management.mbeanservers.domainruntime+
+[java] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://wl11admin27.ejiepru.net:8124/jndi/weblogic.management.mbeanservers.runtime+
+[java] [DomainManager.resetDomain():36] : Getting new domain+
+[java] [DomainManager.resetDomain():39] : Using pending domain: false+
+[java] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83fbeb1+
+[java] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@83fbeb1+
+[java] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8313beb+
+[java] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8313beb+
+[java] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: wl11_extra_ava+
+[java] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]cc7+
+[java] [BasicOperation.dumpTmids():713] : Incoming tmids:+
+[java] [BasicOperation.dumpTmids():715] : {Target=gestExp1, WebLogicTargetType=cluster, Name=ispacmgr}, targeted=true+
+[java] [BasicOperation.deriveAppName():141] : appname established as: ispacmgr+
+[java] <Sep 1, 2011 9:12:59 AM CEST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, ispacmgr [archive: /aplic/w63/dist/ispacmgr.war], to gestExp1 .>+
+[java] [BasicOperation.dumpTmids():713] : Incoming tmids:+
+[java] [BasicOperation.dumpTmids():715] : {Target=gestExp1, WebLogicTargetType=cluster, Name=ispacmgr}, targeted=true+
+[java] [BasicOperation.loadGeneralOptions():628] : Delete Files:false+
+[java] Timeout :3600000+
+[java] Targets:+
+[java] gestExp1+
+[java] ModuleTargets={}+
+[java] SubModuleTargets={}+
+[java] }+
+[java] Files:+
+[java] null+
+[java] Deployment Plan: null+
+[java] App root: /tmp/webl11/./config/deployments/ispacmgr+
+[java] App config: /tmp/webl11/./config/deployments/ispacmgr/plan+
+[java] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=ispacmgr,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=3600,defaultSubmoduleTargets=true,timeout=3600000,deploymentPrincipalName=null,useExpiredLock=false}+
+[java]+
+[java] [BasicOperation.execute():445] : Initiating deploy operation for app, ispacmgr, on targets:+
+[java] [BasicOperation.execute():447] : gestExp1+
+[java] Task 164 initiated: [Deployer:149026]deploy application ispacmgr on gestExp1.+
+[java] dumping Exception stack+
+[java] Task 164 failed: [Deployer:149026]deploy application ispacmgr on gestExp1.+
+[java] Target state: deploy failed on Cluster gestExp1+
+[java] weblogic.management.DeploymentException: [Deployer:149189]An attempt was made to execute the 'deploy' operation on an application named 'ispacmgr' that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation can not be performed until server is restarted so that the application will be available.+
+[java] at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1319)+
+[java] at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1360)+
+[java] at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1050)+
+[java] at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1406)+
+[java] at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:162)+
+[java] at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:156)+
+[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147)+
+[java] at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29)+
+[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)+
+[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114)+
+[java] at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)+
+[java] at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)+
+[java] at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)+
+[java] at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)+
+[java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)+
+[java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)+
+[java]+
+[java]+
+[java] Target Assignments:+
+[java] + ispacmgr gestExp1+
+[java] [ServerConnectionImpl.close():332] : Closing DM connection+
+[java] [ServerConnectionImpl.close():352] : Unregistered all listeners+
+[java] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection+
+[java] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection+
+[java] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection+
+[java] Java Result: 1+
BUILD SUCCESSFUL
This error doesn`t appear always in the same war file. In admin log I can see this:
+79740> <BEA-149038> <Initiating Task for ispacmgr : [Deployer:149026]deploy application ispacmgr on gestExp1.>+
+####<Sep 1, 2011 9:13:19 AM CEST> <Warning> <Deployer> <ejlf031> <admin> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <131+
+4861199984> <BEA-149004> <Failures were detected while initiating deploy task for application 'ispacmgr'.>+
+####<Sep 1, 2011 9:13:19 AM CEST> <Warning> <Deployer> <ejlf031> <admin> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <131+
+4861199985> <BEA-149078> <Stack trace for message 149004+
+weblogic.management.DeploymentException: [Deployer:149189]An attempt was made to execute the 'deploy' operation on an application named 'ispacmgr' that is not currently available.+
The application may have been created after non-dynamic configuration changes were activated. If so, the operation can not be performed until server is restarted so that the appl
ication will be available.
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1319)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1360)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1050)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1406)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:162)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:156)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)
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)
+>+
So, is the same error. There isn`t any more. After this error, If I try to deploy the war (only the one with the error), it works!!!!
Restarting the server is not the solution.
Thanks in advance
Endika

Hi, I think you should delete all apps using WebLogic console instead of editing config.xml, is more safe. Then shutdown your instance and eliminate all that is inside in stage and .wlnotdelete directories. Start again your instance and deploy your apps.

Deploying JSF application on Tomcat 5.0.28

Hi,
I am having problems deploying JSF application (developed using Studio Creator) on Tomcat. Any suggessions ....
HTTP Status 404 - Servlet Faces Servlet is not available....
Thanks in advance

I ran into this same problem moving from Tomcat 4.1.31 to Tomcat 5.0.28. This one was definitely a headscratcher, but the solution turned out to be simple as I had an older servlet api jar (2.3) in my J2SE's jre/lib/ext directory. I replaced the existing servlet.api with servlet-api.jar and jsp-api.jar from the Tomcat 5.0.28 common/lib directory, restarted Tomcat, and the problem disappeared.

SaxParser error when deploying J2EE application on 10gAS for IBM AIX 5.2

Hello,
We have problems deploying J2EE application on 10gAS 9.0.4.0.0, on IBM AIX 5.2. We deployed it on 10gAS for Windows 9.4.0.0 and 9.0.4.0.1, and on 10gAS 9.0.4.0.0 for Linux, without any trouble (installed ADF runtime, etc.).
Application architecture is JSP/Struts/ADF BC4J. We used JHeadstart 10g framework.
As soon as we start the application, we get the message described bellow. We saw that J2SE version, shipped with the AS is 1.4.1? On all the other AS versions, and in embedded JDeveloper OC4J is 1.4.2.
We also use the Xerces library xercesImpl.jar, which is located in .../WEB-INF/lib directory (which contains SaxParser implementation), if that is important. But the application fails right on the beginning.
The complete error message follows:
javax.xml.parsers.FactoryConfigurationError: Provider null could not be
instantiated: java.lang.NullPointerException at
javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:30) at
org.apache.commons.digester.Digester.getFactory(Digester.java:512) at
org.apache.commons.digester.Digester.getParser(Digester.java:686) at
org.apache.commons.digester.Digester.getXMLReader(Digester.java:902) at
org.apache.commons.digester.Digester.parse(Digester.java:1567) at
org.apache.struts.action.ActionServlet.initServlet(ActionServlet.java:1433) at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:466) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at
oracle.jheadstart.controller.struts.JhsActionServlet.init(JhsActionServlet.java:219) at
com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.HttpApplication.loadServlet(HttpApplication.java:2094)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.HttpApplication.findServlet(HttpApplication.java:4523)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2561)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:640)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
at com.evermind[Oracle Application Server Containers for J2EE 10g
(9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:568)
Any information would be helpful,
Vladimir,
MAOP d.o.o., Slovenia

Figures, I've been fighting with this for the past day and a half and I figure it out shortly after I post the question.
It turns out the tiles.jar that was in our WEB-INF/lib directory was an old one. It looks like the newer struts.jar (from jdeveloper) we're using includes the tiles information. Once I removed tiles.jar, commons-dbcp, pool, resources, and services, it works now.
It looks like jdeveloper overwrites most of those files with it's built in struts integration, and we've just been lucky before that struts.jar was being loaded before tiles.jar and something with oas 10.1.3 is loading the jars in a different order--but I'm just guessing here.

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

Problem deploying webservice application to cluster

Similar Messages

Maybe you are looking for