[WLP 700] Hot Deploy fails

Hi all,
I hope qomeone will be able to help me with this: I'm trying to deploy a new portal,
but it fails.
This is the message I receive:
HotDeply failed with the following message: Unable to add module: foremPortalApp
to application descriptor for: portalApp
If i check the details, this is what I see:
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\portlets\Portlet1.portlet
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\portal.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\security.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\tools.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\user_account.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\webflow-extensions.wfx
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\ForemPortal.portal
to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.
If I check the log, this is what I can read:
[INFO] HotDeployer.runDeployer() called
[ERROR] Operation timed out: connect
[ERROR] No Message
com.bea.commerce.tools.util.XmlFileException: No Message
     at com.bea.commerce.tools.util.XmlFile.init(XmlFile.java:106)
     at com.bea.commerce.tools.util.XmlFile.<init>(XmlFile.java:79)
     at com.bea.commerce.tools.util.XmlFile.<init>(XmlFile.java:69)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployer.addModuleToApplicationDescriptor(HotDeployer.java:349)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployer.runDeployer(HotDeployer.java:117)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployThread.run(HotDeployThread.java:72)
And, finally, this is the error message I recieve in the 'dos' box from my running
server:
<02-dÚc.-02 13:56:48 CET> <Error> <PortalManager> <415454> <Attempt to created
a
duplicate Portal Definition within web App: foremPortalApp URI:/webapps/foremPo
rtalApp/ForemPortal.portal.>
<02-dÚc.-02 13:56:48 CET> <Error> <Data Synchronization> <000000> <Application:
portalApp; Persistence Failure executing DataItemMessage with Persistence Manage
r: com.bea.portal.manager.internal.PortalPersistenceManager [DR: Portal Applica
tion Data Repository, URI: /webapps/foremPortalApp/ForemPortal.portal, Action:
C
REATE]
Exception[com.bea.p13n.management.data.repository.PersistenceException: Attempt
to created a duplicate Portal Definition within web App: foremPortalApp URI: /we
bapps/foremPortalApp/ForemPortal.portal.]
at com.bea.portal.manager.internal.PortalPersistenceManager.updatePortal
Model(PortalPersistenceManager.java:239)
at com.bea.portal.manager.internal.PortalPersistenceManager.createDataIt
em(PortalPersistenceManager.java:201)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.handleDataItemMessage(AbstractDataRepository.java:814)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onDataSyncMessage(AbstractDataRepository.java:990)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:252)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:261)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onSyncRequestMessage(AbstractDataRepository.java:1086)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:257)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepository(AbstractDataRepository.java:706)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepositories(AbstractDataRepository.java:658)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepositories(AbstractDataRepository.java:606)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onDataSyncMessage(AbstractDataRepository.java:994)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:252)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispa
tchMessage(DataSyncServlet.java:351)
at com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPos
t(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:945)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:332)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:242)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5360)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:721)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3043)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Is this meaningfull to anyone???
Thank you for helping me out...
Philippe

Ok, it works now, thank you very much for your help
Bye,
Philippe
"tanya" <[email protected]> wrote:
>
there is also another workaround described here:
http://edocs.bea.com/wlp/docs70/relnotes/relnotes.htm#292355
look for "CR080390 Hot Deploy fails with "Unable to add module" message"
fyi, this will be fixed in 7.0sp2
-tanya
"Kunal Mittal" <[email protected]> wrote:
Phillippe -
I was having a similar problem. Mine was fixed by ensuring that theserver
had
an internet connection to go to the web to verify the DTD's. That might
be your
problem too, but u never know.
Thanks
Kunal Mittal
CTO, Microsec Technologies Ltd.
"Philippe Blockmans" <[email protected]> wrote:
Hi all,
I hope qomeone will be able to help me with this: I'm trying to deploy
a new portal,
but it fails.
This is the message I receive:
HotDeply failed with the following message: Unable to add module: foremPortalApp
to application descriptor for: portalApp
If i check the details, this is what I see:
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\portlets\Portlet1.portlet
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\portal.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\security.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\tools.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\user_account.wf
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\webflow-extensions.wfx
to sync list.
Adding file: D:\bea\user_projects\foremPortalDomain\beaApps\portalApp-project\application-sync\webapps\foremPortalApp\ForemPortal.portal
to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.
If I check the log, this is what I can read:
[INFO] HotDeployer.runDeployer() called
[ERROR] Operation timed out: connect
[ERROR] No Message
com.bea.commerce.tools.util.XmlFileException: No Message
     at com.bea.commerce.tools.util.XmlFile.init(XmlFile.java:106)
     at com.bea.commerce.tools.util.XmlFile.<init>(XmlFile.java:79)
     at com.bea.commerce.tools.util.XmlFile.<init>(XmlFile.java:69)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployer.addModuleToApplicationDescriptor(HotDeployer.java:349)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployer.runDeployer(HotDeployer.java:117)
     at com.bea.portal.tools.portal.wizard.hotdeploy.HotDeployThread.run(HotDeployThread.java:72)
And, finally, this is the error message I recieve in the 'dos' box
from
my running
server:
<02-dÚc.-02 13:56:48 CET> <Error> <PortalManager> <415454> <Attemptto
created
a
duplicate Portal Definition within web App: foremPortalApp URI:/webapps/foremPo
rtalApp/ForemPortal.portal.>
<02-dÚc.-02 13:56:48 CET> <Error> <Data Synchronization> <000000> <Application:
portalApp; Persistence Failure executing DataItemMessage with Persistence
Manage
r: com.bea.portal.manager.internal.PortalPersistenceManager [DR: Portal
Applica
tion Data Repository, URI: /webapps/foremPortalApp/ForemPortal.portal,
Action:
C
REATE]
Exception[com.bea.p13n.management.data.repository.PersistenceException:
Attempt
to created a duplicate Portal Definition within web App: foremPortalApp
URI: /we
bapps/foremPortalApp/ForemPortal.portal.]
at com.bea.portal.manager.internal.PortalPersistenceManager.updatePortal
Model(PortalPersistenceManager.java:239)
at com.bea.portal.manager.internal.PortalPersistenceManager.createDataIt
em(PortalPersistenceManager.java:201)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.handleDataItemMessage(AbstractDataRepository.java:814)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onDataSyncMessage(AbstractDataRepository.java:990)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:252)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:261)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onSyncRequestMessage(AbstractDataRepository.java:1086)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:257)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepository(AbstractDataRepository.java:706)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepositories(AbstractDataRepository.java:658)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.notifyDataRepositories(AbstractDataRepository.java:606)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.onDataSyncMessage(AbstractDataRepository.java:994)
at com.bea.p13n.management.data.repository.internal.AbstractDataReposito
ry.executeMessage(AbstractDataRepository.java:252)
at com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.se
ndMessage(JvmCommunicationPipe.java:116)
at com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispa
tchMessage(DataSyncServlet.java:351)
at com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPos
t(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:945)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:332)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:242)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5360)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:721)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3043)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
Is this meaningfull to anyone???
Thank you for helping me out...
Philippe

Similar Messages

Cannot hot deploy portal

hi
I have a problem with hot deploying portals.
When i hot deploy i get this message:
"Hot deploy failed with the following message:
Exception while attempting to sync EBCC portal files. Please make sure the portal
server is running and your connection settings are correct. "
The portal server is running fine.
Thanks

Do you have an internet connection?
If not, this is a bug that will be fixed in 7.0sp2 and in the mean time, you can
follow the procedures for CR080390 at:
http://e-docs.bea.com/wlp/docs70/relnotes/relnotes.htm#305089
-tanya
"rashed karim" <[email protected]> wrote:
>
hi
I have a problem with hot deploying portals.
When i hot deploy i get this message:
"Hot deploy failed with the following message:
Exception while attempting to sync EBCC portal files. Please make sure
the portal
server is running and your connection settings are correct. "
The portal server is running fine.
Thanks

Creation of InitialContext fails when i hot-deploy scheduler-service.xml

Creation of InitialContext fails when i hot-deploy scheduler-service.xml
I configured scheduler-service as follows in Jboss 3.2:
scheduler-service.xml
<mbean code="org.jboss.varia.scheduler.Scheduler"
     name=":service=Scheduler">
<attribute name="StartAtStartup">true</attribute>
<attribute name="SchedulableClass">com.beta.my.utils.FMScheduler</attribute>
<attribute name="SchedulableArguments">Schedulabe Test,12345</attribute>
<attribute name="SchedulableArgumentTypes">java.lang.String,int</attribute>
<attribute name="InitialStartDate">0</attribute>
<attribute name="SchedulePeriod">10000</attribute>
<attribute name="InitialRepetitions">-1</attribute>
</mbean>
Schedulable Class
package com.beta.my.utils;
import java.util.Date;
import org.jboss.varia.scheduler.Schedulable;
public static class FMScheduler
implements Schedulable
private String mName;
private int mValue;
public FMScheduler(String pName,int pValue)
mName = pName;
mValue = pValue;
public void perform(Date pTimeOfCall,long pRemainingRepetitions)
try {
          Context context = new InitialContext();//properties taken from jndi.properties file
          } catch (Exception e){
               e.printStackTrace();
I started my jboss..,FMScheduler created successfully, perform method in FMScheduler called succesfully after SchedulePeriod(1000)
The problem occurs(NullPointerException) while i changed SchedulePeriod time and hot-deployed(just saved scheduler-service.xml).
The following Exception occures due to InitialContext creation fails*(Context context = new InitialContext();)* in FMScheduler.
17:46:27,361 ERROR [STDERR] java.lang.NullPointerException
17:46:27,361 ERROR [STDERR] at org.jboss.mx.loading.UnifiedClassLoader.findR
esources(UnifiedClassLoader.java:374)
17:46:27,361 ERROR [STDERR] at java.lang.ClassLoader.getResources(ClassLoade
r.java:825)
17:46:27,361 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12$5.run
(VersionHelper12.java:145)
17:46:27,361 ERROR [STDERR] at java.security.AccessController.doPrivileged(N
ative Method)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12.getRe
sources(VersionHelper12.java:142)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getAp
plicationResources(ResourceManager.java:468)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getIn
itialEnvironment(ResourceManager.java:159)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.init(InitialConte
xt.java:215)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.<init>(InitialCon
text.java:195)
17:46:27,377 ERROR [STDERR] at com.beta.my.utils.FMScheduler.perform
(FMScheduler.java:42)
17:46:27,392 ERROR [STDERR] at org.jboss.varia.scheduler.Scheduler$Listener.
handleNotification(Scheduler.java:1263)
17:46:27,392 ERROR [STDERR] at org.jboss.mx.server.NotificationListenerProxy
.handleNotification(NotificationListenerProxy.java:69)
17:46:27,392 ERROR [STDERR] at javax.management.NotificationBroadcasterSuppo
rt.sendNotification(NotificationBroadcasterSupport.java:95)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.sendNotification
s(Timer.java:441)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.access$000(Timer
.java:31)
17:46:27,408 ERROR [STDERR] at javax.management.timer.Timer$RegisteredNotifi
cation.doRun(Timer.java:612)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.SchedulableRunnable.run(Sch
edulableRunnable.java:164)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.ThreadPool$Worker.run(Threa
dPool.java:225)
please help me if u have any idea,thanks

Hi Hamsa,
Did you also create and configure an "Execution Destination"?
You can test the Metadata destination configuration on Web Service Navigator.
On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
Best regards,
Yasar

Hot deployment using the REDEPLOY feature

Hi
I am rather confused regarding the usage of the HOT DEPLOYMENT in WLS 6.1 sp2
- Win2000.
According to the documentation - "deployment.pdf" p. 31 you should be able to
simply touch the REDEPLOY file and the entire application should then be redeployed
by WLS. However according to the following link:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.management&item=2095
the usage of the REDEPLOY feature is only for WebApp's not EJB's.
So my question in short terms: What am I supposed to belive ? the BEA documentation
or the BEA support team ?
I have tried using the REDEPLOY feature as suggested by the documentation however
the WLS fails to do the redeployment with an execption.
Kind regards
Jorgen Fastrup

From my experience REDEPLOY does work for EJBs as well. You need to meet two conditions: REDEPLOY file should be in META-INF and your application should be deployed under the domain/application. I was not able to get it to work when the application is deployed elsewhere. If somebody knows how to it, please let me know.
Alexander.

SAP SDM Deployment failed

Hello everybody i have a problem with my SAP ERP Installation the Error is :
An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
Jan 19, 2010 7:34:14 AM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: Ending deployment prerequisites. All items are correct.
Jan 19, 2010 7:35:49 AM Info: Saved current Engine state.
Jan 19, 2010 7:35:49 AM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
Jan 19, 2010 7:35:49 AM Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
Jan 19, 2010 7:35:49 AM Info: Software type of SDA: J2EE
Jan 19, 2010 7:35:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Info: Begin of log messages of the target system:
10/01/19 07:35:50 - ***********************************************************
10/01/19 07:35:51 - Start updating EAR file...
10/01/19 07:35:51 - start-up mode is lazy
10/01/19 07:35:51 - EAR file updated successfully for 47ms.
10/01/19 07:35:51 - Start deploying ...
10/01/19 07:35:51 - EAR file uploaded to server for 32ms.
10/01/19 07:35:56 - ERROR: NOT deployed. The Deploy Service returned the following error:
                     For detailed information see the log file of the Deploy Service.
                     Exception is:
                     com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
                          at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
                          at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
                          at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
                          at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
                          at java.lang.Thread.run(Thread.java:534)
10/01/19 07:35:56 - ***********************************************************
Jan 19, 2010 7:35:56 AM Info: End of log messages of the target system.
Jan 19, 2010 7:35:56 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
     at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
     at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jan 19, 2010 7:35:56 AM Info: Starting to save the repository
Jan 19, 2010 7:35:57 AM Info: Finished saving the repository

Hi,
Check below thread:
/message/441671#441671 [original link is broken]
Thanks
Sunny

Hot Deploy Servlet in JAR file problem

I've been playing with hot deploying servlets in WLS 5.1. I have SP2
          installed. I have things working fine with individual servlet class files. I
          decided to try hot deploying with jar files.
          I created a servlet, added it to a jar file, and then added the jar file to
          the 'weblogic.http.servlet.classpath'. I then restarted the server. I
          started the console and was able to hot deploy the servlet. So far so good.
          My next test is what failed. I modified the servlet, and rebuilt the jar
          file. I went back to the console, selected the servlet and hit the redeploy
          button. I went back to the browser and hit refresh - nothing, still the old
          servlet.
          It appears that WLS isn't reloading the jar file and the updated servlet.
          Everything works with individual class files.
          Does anyone know how I can cause the reload of updated servlets embedded
          within a jar file?
          Weblogic group - If there is no way now, will support be added soon?
          Thanks,
          Rick


Hi,
          If I use weblogic.servlet.ServletServlet to try just the servlet , It
          works correctly.But When I develop it in a web application , there is a lot
          of hypelink to this servlet,thus I can't use the relative path reference to
          that servlet.I try to set the name of weblogic.servlet.ServletServlet same
          as the webapp,It doesn't work,how do I solve this problem?
          Thank you
          Pan
          Subject: Re: Hot deploy Servlet in webapp
          > http://www.weblogic.com/docs51/classdocs/API_servlet.html#134798
          >
          > It even explains why you shouldn't use it in production environment.
          >
          > Dimitri

Assertion Error during hot deployment in WLS6.1

Hi,
I am using WLS6.1SP2. The hot deployment feature is enabled. But when I try to
redeploy the bean, it gives the following
assertion error. Somehow the hot deployment doesn't seem to work.
Following is the stack trace:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize be
fore invoke ]]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
throwable exception in BaseServlet weblogic.rmi.extensions.RemoteRuntimeExcepti
on - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize be
fore invoke ]]
throwable exception message null

Are you deployed in an EAR? If so, this is probably a hot redeploy bug.
Report to [email protected].
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Atul Sapkal" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
I am using WLS6.1SP2. The hot deployment feature is enabled. But when Itry to
redeploy the bean, it gives the following
assertion error. Somehow the hot deployment doesn't seem to work.
Following is the stack trace:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ mustinitialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ mustinitialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must
initialize be> fore invoke ]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
throwable exception in BaseServletweblogic.rmi.extensions.RemoteRuntimeExcepti
on - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must
initialize be> fore invoke ]
throwable exception message null

Hot Deploy

When going through the "Creating a New Portal in a New Domain" whitepaper, everything works great until I get to the Hot Deploy. It begins Hot Deploying asks me for my username/password (weblogic/weblogic) continues along for a bit then constantly asks for my username/password. Any ideas?

Hi Karen,
This problem occurs when you don't have Internet access when you attempt hot-deploy (or your firewall blocks the ebcc).
The DOCTYPE tag in the descriptor file specifies the dtd on Sun's website. When the ebcc fails to download the dtd, it
(incorrectly) also fails to make the necessary changes to the application descriptor xml. Manually editing the application
descriptor as you described should do the trick. In general, however, here is the workaround:
1. Save the attached file to your hard drive (just save it to c:\).
2. Edit the application.xml file as follows:
a. First copy the entire DOCTYPE declaration and save it somewhere in a separate text file (in case want to revert back to it later).
b. Edit the DOCTYPE declaration so that it looks like this:
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'file:///application_1_3.dtd'>
(Notice that the java.sun.com web address is replaced with a URI to the file on your hard drive.)
3. Save your changes and hotdeploy will work with or without Internet access.
Best Regards,
Scott Ellis
BEA Systems
Karen Hensel wrote:
I have had the same problem after following the directions multiple times. I could
not get the portal to hot deploy or manually deploy from the console. It appears
xml files are not being updated with the new portal information.
I was finally able to get the portal deployed by adding (when the server was down,
of course) a <module> to application.xml and a <WebAppComponent> to the config.xml.
I'm still not sure things are fully correct.
"Robert Costa" <[email protected]> wrote:
I have tried 5 times now. The domain is created successfully but during
the hot
deploy of the portal, this is shown in the status window of the hot deploy:
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\portlets\Portlet1.portlet
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\tools.wf
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\webflow-extensions.wfx
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\user_account.wf
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\portal.wf
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\security.wf
to sync list.
Adding file: C:\bea\user_projects\testDomain\beaApps\portalApp-project\application-sync\webapps\testPortalWebApp\testPortal.portal
to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
At which time it begins prompting me for my username/password. The dialog
box
says:
Logon (in titlebar)
Connection:
Server:
Username:weblogic
Password:
Should connection and server have values? If so, why don't they? I
followed
the document completely.
Thanks!
"Daniel Selman" <[email protected]> wrote:
Robert,
Strange. Are there any clues in the EBCC or server logs you could post?
Did
you double check your password is correct by logging in to the console?
Thanks,
Daniel Selman
"Robert Costa" <[email protected]> wrote in message
news:[email protected]...
When going through the "Creating a New Portal in a New Domain" whitepaper,everything works great until I get to the Hot Deploy. It begins Hot
Deploying asks me for my username/password (weblogic/weblogic) continues
along for a bit then constantly asks for my username/password. Anyideas?
>




<!ELEMENT application (icon?, display-name, description?, module+,
          security-role*)>

<!ELEMENT alt-dd (#PCDATA)>

<!ELEMENT connector (#PCDATA)>

<!ELEMENT context-root (#PCDATA)>

<!ELEMENT description (#PCDATA)>

<!ELEMENT display-name (#PCDATA)>

<!ELEMENT ejb (#PCDATA)>

<!ELEMENT icon (small-icon?, large-icon?)>

<!ELEMENT java (#PCDATA)>

<!ELEMENT large-icon (#PCDATA)>

<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>

<!ELEMENT role-name (#PCDATA)>

<!ELEMENT security-role (description?, role-name)>

<!ELEMENT small-icon (#PCDATA)>

<!ELEMENT web (web-uri, context-root)>

<!ELEMENT web-uri (#PCDATA)>

<!ATTLIST alt-dd id ID #IMPLIED>
<!ATTLIST application id ID #IMPLIED>
<!ATTLIST connector id ID #IMPLIED>
<!ATTLIST context-root id ID #IMPLIED>
<!ATTLIST description id ID #IMPLIED>
<!ATTLIST display-name id ID #IMPLIED>
<!ATTLIST ejb id ID #IMPLIED>
<!ATTLIST icon id ID #IMPLIED>
<!ATTLIST java id ID #IMPLIED>
<!ATTLIST large-icon id ID #IMPLIED>
<!ATTLIST module id ID #IMPLIED>
<!ATTLIST role-name id ID #IMPLIED>
<!ATTLIST security-role id ID #IMPLIED>
<!ATTLIST small-icon id ID #IMPLIED>
<!ATTLIST web id ID #IMPLIED>
<!ATTLIST web-uri id ID #IMPLIED>

Error while deploying BPEL Process(Error during deployment: Deployment Fail

Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM

Hi,
when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] HTTP error code returned [500]
[04:53:50 PM] Error message from server:
Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
[04:53:50 PM] Check server log for more details.
[04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
[04:53:50 PM] #### Deployment incomplete. ####
[04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Please, any one can tell solution for this.
Thanks In advance
Amar.
Edited by: 897448 on Dec 13, 2011 8:48 PM

Error deploying the composite on soa_server1: Deployment Failed ..

Hi,
I am trying to access external webservice from my BPEL Process; imported the external system's wsdl with xsd into my local & change all the reference of the xsd in my wsdl ,which now pointing to local xsd etc.
I am getting the following error while deploying to EM console from my J Developer; but in Make/Rebuild from jdevloper is working fine, no error. In the deployment from JDeveloper 11.1.1.5.0 I got this below error.
[01:36:45 PM] Error deploying archive sca_TG7_rev1.0.0.jar to partition "default" on server soa_server1
[01:36:45 PM] HTTP error code returned [500]
[01:36:45 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Unable to register service..
[01:36:45 PM] Check server log for more details.
[01:36:45 PM] Error deploying archive sca_TG7_rev1.0.0.jar to partition "default" on server soa_server1 [01:36:45 PM] #### Deployment incomplete. ####
[01:36:45 PM] Error deploying archive file:/C:/JDeveloper/mywork/TG7/deploy/sca_TG7_rev1.0.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
========Log ==
<[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <2db1df1f7258da77:342b4c64:1361c317b43:-8000-0000000000007504> <1331930173734> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: Unable to register service.
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:62)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:378)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:226)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:160)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:109)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:96)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:78)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:221)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:124)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.fabric.common.FabricDeploymentException: Unable to register service. {rootCauses=[]}
     at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(WebServiceEntryBindingComponent.java:226)
     at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(WebServiceEntryBindingComponent.java:97)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployServices(CompositeDeploymentConnection.java:160)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:91)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:62)
     at sun.reflect.GeneratedMethodAccessor1622.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:68)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy306.load(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:57)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:378)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:226)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:160)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:109)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:96)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:78)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:221)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:124)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
An help will be much .

Hi There...
Oracle explains:
The cause of the problem:
While defining an Exposed Service for your composite you used the option Generate WSDL from schemas and selected elements or types from one of more XML schema (.xsd) files to define the various message parts for input or outputs to the service. One of these message parts was defined by selecting from a schema an element or type that is not associated with an XML namespace.
Therefore at deployment time, if the WSDL file for the exposed service defines a default namespace, all elements must belong to either the default namespace or any namespace explicitly defined for each element or type. Since there is no XML namespace associated with the "no namespace" XML element or type in question there is no namespace prefix that can be used to identify the relevant XML namespace.
Solution:
1. Ensure all elements and types use an XML namespace.
Adjust the original XSD so that the offending "no namespace" elements/types are associated with a namespace.
2. Modify the WSDL for the service to allow No Namespace elements/types to be used
Whilst is is not possible to give a fixed sequence of steps to achieve this, essentially:
ensure the definitions element in the WSDL document does not use an xmlns="xxxx" attribute to set a default namespace
without a default namespace, ensure all other elements in the document that are expected to be associated with the previous default namespace have an explicit
namespace declaration
Riko

Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0

Hi,
I need your help to sort out the following issue.
I have installed MDT 2012 +ADK 8.0 and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
Image from the machine,even the sysprep failed. This is the error
Your PC needs to restart.
Please hold down the power button.
Error Code:0x0000005D
Parameters:
0x030F0209
0x746E6547
0X49656E69
0X6C65746E
So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
D530 is the maximum available HW model in client environment so your help will be much appreciated.
Thanks in Advance!!

I have never seen that error before (see identical post). I did a quick internet search and found the following:
http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
Either:
1) Upgrade your machines with modern processors that support the ADK.
or
2) Downgrade to the WAIK
http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
Keith Garner - keithga.wordpress.com

Merchandising Deployment Fails w/ Table does not exist error

Very intermittently, our Merchandising Deployments fail.
After successfully inserting records into a target table (e.g. dcs_sku), it suddenly fails and the logs show an Oracle error about said table missing.
The table exists. It's there. We realize this is very strange.
Has anybody else encountered this? The stacktrace is below:
09:29:24,077 ERROR [ProductCatalog_staging] SQL Statement Failed: [++SQLInsert++]
INSERT INTO dcs_sku(sku_id,version,creation_date,start_date,end_date,display_name,description,sku_type,fulfiller,nonreturnable)
VALUES(?,?,?,?,?,?,?,?,?,?)
-- Parameters --
p[1] = {pd} sku12345 (java.lang.String)
p[2] = {pd: version} 1 (java.lang.Integer)
p[3] = {pd: creationDate} 2011-08-08 11:54:59.0 (java.sql.Timestamp)
p[4] = {pd: startDate} null
p[5] = {pd: endDate} null
p[6] = {pd: displayName} Sku Description (java.lang.String)p[7] = {pd: description} null
p[8] = {pd: type} 0 (java.lang.Integer)
p[9] = {pd: fulfiller} 0 (java.lang.Integer)
p[10] = {pd: nonreturnable} false (java.lang.Boolean)
[--SQLInsert--]
09:29:24,197 ERROR [DeploymentManager] item = repositoryMarker:mark2455397 cause = CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException
: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:245)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:521)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:300)
message = Deployment Failed time = Fri Aug 12 09:29:24 PDT 2011 atg.deployment.DeploymentFailure@3d938aa9
CAUGHT AT:
CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:245)
at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:521)
at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:300)
Caused by: CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6416)
at atg.adapter.gsa.GSARepository.addItem(GSARepository.java:1010)
at atg.deployment.repository.RepositoryWorkerThread.deployItem(RepositoryWorkerThread.java:1071)
at atg.deployment.repository.RepositoryWorkerThread.processMarkerForAddUpdatePhase(RepositoryWorkerThread.java:233)
... 2 more
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3468)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1062)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
at atg.adapter.gsa.SQLStatement.executeUpdate(SQLStatement.java:725)
at atg.adapter.gsa.Table.insert(Table.java:1378)
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6339)
... 5 more
thanks!
Joe

We ran into a similar ORA-00942 issue when statements hitting the same table with the same SQL worked fine before and after. This was happening to us in production, and flushing the shared pool made them go away immediately.
Research led to this link that has a patch that you can try to apply: http://www.freelists.org/post/oracle-l/Not-as-straightforward-as-it-would-appear-exec-java-javasqlSQLException-ORA00942-table-or-view-does-not-exist,3

Sun java studio enterprise 8 - Deployment FAILED error

could anyone please help?
When I try to Deploy a EJB module and webservice I get Deployment failed:
run-deploy:
Starting server Sun Java System Application Server 8.1
/app/sun/jstudio_ent8/AppServ8.1UR2/bin/asadmin start-domain --domaindir /app/sun/jstudio_ent8/AppServ8.1UR2/domains/ domain1
Distributing /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jar to [localhost:4848_server]
Start registering the project's server resources
Finished registering server resources
No archivist is able to handle the archive /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jar
Deployment FAILED: No archivist is able to handle the archive /vfat/Roe/DevProject/Implementation/EJBModuleOnlineRegistration/dist/EJBModuleOnlineRegistration.jar

Your porblem has been developed by another user:
Does the MSQL database have a primary key, the CMP wizard determines the primary key based on the primary key setup on the database. The primary key which is selected can be detemined using the database browser Runtime->Database, this displays meta data information from the specified databases.
John
http://websearch.money.cnn.com/websearch/search?magazine=websearch&query=media-press-release.com
http://websearch.money.cnn.com/websearch/search?magazine=websearch&query=hostcube.co.uk

SDM Deployment fails - Dependency caf/core/ear missing

crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
deploying a DC from NWDS into SDM the following Exception is thrown:
07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
002Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
<!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
<!PATTERNhttp://sdmcl20080107151422.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGUTF8/>
<!LOGHEADEREND/>
Jan 7, 2008 4:14:22 PM Info:
Starting deployment
Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
dependency:
name: 'caf/core/ear'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
system:
sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
I checked http://<srv>/sap/monitoring/ComponentInfo
the missing 'caf/core/ear' is not listed, however several other CAFs are:
sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
etc....
Is it possible to deploy this missing caf-ear component supplementary?
I have the strange feelings caf/core/ear is something 7.1 CE only related....
thanks for any hint!
kai

Kai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
Regards,
\-- Vladimir

Hot deployment of class files (non-EJB)

Also posting to the servlet newsgroup.
"Craig Ambrose" <[email protected]> wrote in message
news:[email protected]..
>
I am using WebLogic 6.1 and am interested in using auto-deployment indevelopment
mode of JSPs and class files that those JSPs rely on. I have a simpleWebLogic
application that gets deployed using the exploded directory format andwhen I
modify the JSPs or the class files that they use everything reloadsproperly and
a newly modified class file will be reloaded the next time the pageutilizing
the Java class is requested.
I have a much more complicated application (the one I am really doing workon)
and I can't get the hot deploy of the class files to take effect. The JSPswill
reload but I can't seem to cause the class loader to reload any changedclass
files. If I use the WebLogic Console and un-deploy and then re-deploy theapplication
then the class files will be reloaded, but I thought that wasn't necessaryfor
hot deployment. This complex application stores many things in the HTTPsession
context. I am wondering if that has an effect on the class loader fordependant
class files.
I'm pretty sure it is not a configuration issue as I have it working forthe simple
application. I have the application deployed under the.\config\<domainname>\applications
directory and am using the exploded directory format with the class filesalso
exploded in the WEB-INF\classes directory.
Any insights on dependancies of the hot depployment would be helpful.

[WLP 700] Hot Deploy fails

Similar Messages

Maybe you are looking for