Deployment Pending problem

Hi every one,
i'm running Sun Java System Web Server 7.0 REV=2006.12.04.11.12, i did some manual changes to the configuration and even if everything works fine, i still have the message "Deployment Pending" from the administration console.
I tried many things such as discard changes, pull-config i tried "wadm deploy-config --force" from the CLI without success.
I have already removed the "generated" directory from the config-store, but nothing has changed.
What i can check ???
Thank's in advance for your replies.
Caius

import com.sun.web.admin.AdminEnvironment;
import com.sun.web.admin.configlib.ConfigTOC;
class PrintTimes {
    public static void main(String[] args) throws Exception {
        ConfigTOC toc = new ConfigTOC("<config-name>",  AdminEnvironment.SERVER_ENVIRONMENT);
        toc.loadTOC();
        System.out.println(toc.getConfigChanges());
}If your instance directory is "https-test", then replace "<config-name>" in this code with "test".
Execute the above program as follows:
$ javac -cp <install_dir>/lib/webserv-rt.jar:<install_dir>/lib/webserv-admin-shared.jar:<install_dir>/lib/webserv-admin.jar PrintTimes.java
$ java -Dcom.sun.web.installRoot=<install_dir>  -Djava.library.path=<install_dir>/lib -cp .:<install_dir>/lib/webserv-rt.jar:<install_dir>/lib/webserv-admin-shared.jar:<install_dir>/lib/webserv-admin.jar PrintTimesPlease give the full path of Web Server installation directory in place of <install_dir> in the commands above.
Please provide the output of the above program.

Similar Messages

  • Bytes Pending Problem still Prevails;

              Sorry to say that my byte pending problem is still around.
              There are
              no applications exceptions.
              no runtime exceptions.
              I also made sure that the deployment discriptor declares the TX boundry as NEVER
              The problem that I see at the moment is that once NotificationMDB goes out of commision
              (meaning bytes pending starts increasing) even if I reddeploy the jar file. Message
              on reaching the notification topic do not fire the MDB's
              Could somebody explain possible reasons for this behavior.
              Also I have another process that subscibes to the same topic. but that only takes
              effect when i am communicating with my system sysnchronously.
              Here is the deployment discriptor for
              NotificationMDB-ejb-jar.xml
              <ejb-jar>
              <enterprise-beans>
              <message-driven>
              <ejb-name>NotificationMDB</ejb-name>
              <ejb-class>mypackage.NotificationMDB</ejb-class>
              <transaction-type>Container</transaction-type>
              <message-driven-destination>
              <destination-type>javax.jms.Topic</destination-type>
              </message-driven-destination>
              </message-driven>
              </enterprise-beans>
              <assembly-descriptor>
                   <container-transaction>
                        <method>
                             <ejb-name>NotificationMDB</ejb-name>
                             <method-name>*</method-name>
                        </method>
                   <trans-attribute>Never</trans-attribute>
                   </container-transaction>
              </assembly-descriptor>
              </ejb-jar>
              and
              NotificationMDB-weblogic-ejb-jar.xml
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>NotificationMDB</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>200</max-beans-in-free-pool>
              <initial-beans-in-free-pool>200</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>mysystem.jms.notificationTopic</destination-jndi-name>
              <connection-factory-jndi-name>mysystem.jms.notificationFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <jndi-name>mysystem.jms.NotificationMDB</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              

              Hi christian.
              you were right switching to sp2 solved the bytes pending problem on my topic
              thanks for your help
              Christian Buchegger <[email protected]> wrote:
              >Hi,
              >
              >
              >what version of WLS are you using ? Please check if this could be issue
              >061783 as documented at:
              >http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html#1143510
              >and which is fixed with WLS6.1SP2. Otherwise consider to open as case with
              >BEA Support.
              >
              >
              >Regards,
              >Christian Buchegger
              >Developer Relations Engineer
              >BEA Support
              >
              >
              >Mekaiel Hussain schrieb:
              >
              >> Sorry to say that my byte pending problem is still around.
              >>
              >> There are
              >> no applications exceptions.
              >> no runtime exceptions.
              >> I also made sure that the deployment discriptor declares the TX boundry
              >as NEVER
              >>
              >> The problem that I see at the moment is that once NotificationMDB goes
              >out of commision
              >> (meaning bytes pending starts increasing) even if I reddeploy the jar
              >file. Message
              >> on reaching the notification topic do not fire the MDB's
              >>
              >> Could somebody explain possible reasons for this behavior.
              >>
              >> Also I have another process that subscibes to the same topic. but that
              >only takes
              >> effect when i am communicating with my system sysnchronously.
              >>
              >> Here is the deployment discriptor for
              >>
              >> NotificationMDB-ejb-jar.xml
              >>
              >> <ejb-jar>
              >> <enterprise-beans>
              >> <message-driven>
              >> <ejb-name>NotificationMDB</ejb-name>
              >> <ejb-class>mypackage.NotificationMDB</ejb-class>
              >> <transaction-type>Container</transaction-type>
              >> <message-driven-destination>
              >> <destination-type>javax.jms.Topic</destination-type>
              >> </message-driven-destination>
              >> </message-driven>
              >> </enterprise-beans>
              >>
              >> <assembly-descriptor>
              >> <container-transaction>
              >> <method>
              >> <ejb-name>NotificationMDB</ejb-name>
              >> <method-name>*</method-name>
              >> </method>
              >> <trans-attribute>Never</trans-attribute>
              >> </container-transaction>
              >> </assembly-descriptor>
              >>
              >>
              >> </ejb-jar>
              >>
              >> and
              >>
              >> NotificationMDB-weblogic-ejb-jar.xml
              >>
              >> <weblogic-ejb-jar>
              >> <weblogic-enterprise-bean>
              >> <ejb-name>NotificationMDB</ejb-name>
              >> <message-driven-descriptor>
              >> <pool>
              >> <max-beans-in-free-pool>200</max-beans-in-free-pool>
              >> <initial-beans-in-free-pool>200</initial-beans-in-free-pool>
              >> </pool>
              >> <destination-jndi-name>mysystem.jms.notificationTopic</destination-jndi-name>
              >> <connection-factory-jndi-name>mysystem.jms.notificationFactory</connection-factory-jndi-name>
              >> </message-driven-descriptor>
              >> <jndi-name>mysystem.jms.NotificationMDB</jndi-name>
              >> </weblogic-enterprise-bean>
              >> </weblogic-ejb-jar>
              >
              

  • EPMA 11 - Deployment Pending

    Hi,
    I have an application in EPMA with the status Deployment pending, which I cannot release. When I first tried to deploy this app, I got the "Waiting Status Update.." message and the processing % was at 9%. I then updated the timeout in the awbconfig file, restarted both the EPMA and Planning services and after 10 minutes the app status went back to Undeployed. I then tried to deploy it again and now the status is stuck on Deployment pending. I have rebooted all servers, restarted the services but this status doesn't change. Does anyone have any suggestions as to where I can go from here?
    Thanks,
    Charlie

    This can be resolved by changing the status tag in the EPMA database. In my case this was SQL. I stopped all EPMA services then...
    First find the application ID in the DS_Application table. Then in the OR_Object table, find that ID, then change the status to 1 and in the X_OBJECT_DATA column make the following changes:
    Change the value of status to 2
    Remove the <PendingDeployment>….</PendingDeployment> tag
    (CLOB) <object id="1_5" name="EPMAPP1" folderId="root" type="8" owner="admin" created="1220361085652" status="2" modified="1220361085652"><description>EPMAPP1</description><applicationView><dimensionServerLibraryID>1</dimensionServerLibraryID><dimensionServerApplicationID>2</dimensionServerApplicationID><rulesDeployStatus>1</rulesDeployStatus><deployment><deploymentHistory><deploymentTimeStamp user="admin" seq="-1" transId="2620"><dateTime>1220361141027</dateTime></deploymentTimeStamp><deploymentTimeStamp user="admin" seq="-1" transId="11681"><dateTime>1226661134875</dateTime></deploymentTimeStamp><deploymentTimeStamp user="admin" seq="-1" transId="12473"><dateTime>1226874667563</dateTime></deploymentTimeStamp><deploymentTimeStamp user="admin" seq="-1" transId="13249"><dateTime>1250599505266</dateTime></deploymentTimeStamp></deploymentHistory><instance name="Default"><webServer>BACHVMDB10052</webServer><cluster>Default</cluster><datasource>EPMAPP1</datasource></instance><pendingDeployment transId="13257"><dateTime>1250599737547</dateTime></pendingDeployment></deployment><viewCreationDate transId="-1"><dateTime>1220361078745</dateTime></viewCreationDate></applicationView></object>
    Restarted all services and my app was undeployed again

  • A pending problem of x200 LCD

    There is a pending problem of my thinkpad x200 .
    I found that the x200 LCD is  LTD121EWVB made by toshiba.
    When i looking through a camera to the LCD of the notebook, Parallel stripes appers and flashing,and the eyes feel sotired after a short time.this problem does not exist in many othe notebook's LCD such as sony,samsung etc.
    Anyone can help??

    The refresh rates of the camera and of the LCD don't match. Nothing you can do about it, I suppose.

  • After "wadm pull-config" the Admin gui still shows deployment pending

    After doing a manual edit of my webserver 7.0u3 instance config files I run wadm with the pull-config subcommand. After the command successfully completes I go into the admin gui and it shows that I have a deployment pending. Why is this? Doesn't this command sync the instance config with the config-store?

    pull-config command pulls the configuration from the node to the config-store and then the user is supposed to deploy the configuration using deploy-config command to propagate those changes to the other instances if any.
    pull-config information from Web Server CLI reference:
    http://docs.sun.com/app/docs/doc/820-4842/pull-config-1?a=view

  • Weblogic Portal: Error While Deploying: VALIDATION PROBLEMS WERE FOUND

    Hello friends
    I am getting following error while deploying EAR on server.
    “Module named 'MyEAR' failed to deploy. See Error Log view for more detail.”
    Steps I followed:
    1: Created one portal domain successfully and was able to start the serve after thatr.
    2: Created one Portal EAR Project and added it on server.
    Now when I am restarting the server, getting following error/log
    **“weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND**
    **problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>”**
    Exception stack Trace:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
    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:81)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    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:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:178)
    as it is ‘brand new ‘ – IDE generated application, weblogic-application.xml is untouched.
    Thanks & Regards

    I have seen this problem also. To be clear, this occurs straight out of the box. In other words - launch eclipse, create a new workspace, create a new portal EAR project with the wizard, and then try to deploy it without touching anything. In fact, try changing the portal's facets to anything, plain EAR, 11g default, Portal EAR - it doesn't matter. It will not deploy. Either you get this error or you get deployment errors complaining about missing library references in the weblogic-application.xml. Then - you have to do surgery just to get an 'out of the box' portal to run. Very frustrating.

  • SCVMM 2012 R2 deploy network problem

    Hi,
    I'm trying to set up the network on SCVMM 2012 R2 according to the several documentation and I'm finding a problema trying to deploy my simple design.
    Basically I need to create two network environments completelly isolated from each other. The servers have one NIC connected to these networks, and what I have configured is two logical networks with some networks sites, the uplinks and logical switch, there
    is a Virtual network per logical network to connect the VMs... all seems to be ok, I add this two logical networks to the hosts but when I want to configure the networking in the virtual machine, I only see one logical network, I can't choose the environment
    I want... I don't know what I'm doing wrong...
    Thanks in advanced...

    "How should I configure networking in SCVMM to allow one virtual machine to connect to the same subnet using two network interfaces?"
    You can achieve this by simply adding multiple vNICs to a VM - connected to the same VM Network. 
    -kn
    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

  • Java stored procedure deployment : resolution problem

    Hi,
    I am trying to upload a Java class (to be able to send mail with attached files).
    At deployment, I have many errors of this type :
    errors : class javax/xml/transform/sax/SAXTransformerFactory
    ORA-29521: referenced name org/xml/sax/XMLFilter could not be found
    This is due to the "upload" of J2EE in the database but I do not find the options to bypass this in the "Deployment Profile Settings".
    I tried to uncheck "-resolve", to check "-noverify", to check "-force" options.
    I tried many combinations of those options but there is nothing to do !
    I even tried to "exclude package tree" in the "Dependency Analyzer Filters" but nothing is working.
    Does anyone has any idea ??
    Thanks,
    Ju.

    Hi everybody.
    I found the solution myself.
    I am posting it because I am sure I am not the onlyone that got that problem...
    The trick is to upload jar files manually by successive calls like
    "loadjava -user [user]/[passwd]@[tnsentry] mail.jar -resolve".
    The result of the commmand could list some errors but we do not care, the upload is done anyway...
    Then, you can upload your classes through JDeveloper.
    I did not managed to upload source files (it produces errors), I only uploaded class files (choose deploy "As Compiled Output Only").
    Also take care to uncheck everything in the "Dependency Analyzer" (you have already uploaded dependencies manually).
    In the "loadjava options", do NOT use "-force" param but use "-resolve" param.
    The only thing you still need to do is to click on "Deploy"...
    That's all folks !

  • Deployment Package problems DMS 5.2.1

    All just an FYI for anyone else having issues with a deployment package.
    This is on DMS 5.2.1
    If your presentation references a video file from the Media library that has a space in the Title the deployment does not complete.
    No error - just does not complete.
    It does create the LOCAL --  presentation name  GOTO URL.
    But if you check the deployment/content directory you will see that you are missing assets.
    To fix the problem you need to remove the asset from the presentation.
    Delete from the Media Asset library
    Re-add it withOUT a space.
    Add back to the presentation.
    Re-do the deployment package.
    Then all is good.
    Will try to test later on 5.2.3 but thought I would share this with others!

    [somewhat delayed response]
    The ACNS software will not be corrupted by a power outage, except in the usual situation where you were doing a software upgrade and the power outage occurred right in the middle of the flash write. If this happens, the software will tell you about it, and you can fix it by using the flash-based rescue image or recovery CD. Almost certainly this is not what happened in this case, however.
    What may have happened is that the data in the CFS volume(s) got corrupted due to some bug. ACNS 5.2.1 is pretty old. I would suggest upgrading to the latest 5.3.x build.
    gid

  • Deployment profiles problems in 9.0.3.3

    create a deployment profile as "Business Components EJB Session Bean" and click OK. a xxx.bcdeploy file was created successfully. Later on go back to this file, right click and choose "Settings" to edit the deployment profile but found ALL the application module are "Grayed out" (disabled and cannot be changed).
    This happens after I installed Jdeveloper 9.0.3.3 (clean installation). I had no problems in 9.0.3.2.
    Please help! Thanks a lot!

    Note: Haven't observed this problem with non-jsp projects.

  • Deploy Java problem

    Dear All
    Please help me,I deployed Java but It is problem,I executed with "SAP Note Number: 1006640 Not active container webdynpro during deployment" but still problem
    Start updating EAR file...
    08/07/19 11:21:00 -  start-up mode is lazy
    08/07/19 11:21:00 -  EAR file updated successfully for 125ms.
    08/07/19 11:21:00 -  Start deploying ...
    08/07/19 11:21:00 -  EAR file uploaded to server for 94ms.
    08/07/19 11:21:01 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_alv_common.ear.
                         Reason: None of the available containers recognized the components of application sap.com/bialvcommon; it is not possible to make deploy.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:572)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
                         For detailed information see the log file of the Deploy Service.
    08/07/19 11:21:01 -  ***********************************************************
    Jul 19, 2008 11:21:01... Info: End of log messages of the target system.
    Jul 19, 2008 11:21:01... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 19, 2008 11:21:01... Error: Aborted: development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'1077259'/'0', grouped by software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_alv_common.ear.
    Reason: None of the available containers recognized the components of application sap.com/bialvcommon; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 19, 2008 11:21:01... Info: Starting to save the repository
    Jul 19, 2008 11:21:02... Info: Finished saving the repository
    Jul 19, 2008 11:21:02... Info: Starting: Initial deployment: Selected software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0' will be deployed.
    Jul 19, 2008 11:21:02... Error: Aborted: software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0':
    Failed deployment of SDAs:
    development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'1077259'/'0' : aborted
    Please, look at error logs above for more information!
    Jul 19, 2008 11:21:02... Info: Starting to save the repository
    Jul 19, 2008 11:21:03... Info: Finished saving the repository
    Jul 19, 2008 11:21:03... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 19, 2008 11:21:03... Error: -
    At least one of the Deployments failed -
    Thanks

    what is your current support pack level?
    target level?
    if your curredt level is 6, 7 or 8 and target level is 11, 12, or 13
    read this note "978042"
    regards,

  • Getting error -1950679035, despite lvlib deployed without problems

    When reading shared variables I get the error 1950679035, despite all variables being configures correctly and the lvlib having no problem being deployed correctly. Attached pls find a screenshoot of the GUI and the shared var. monitor. The variable manager will correctly list the process under which the SV are deployed, but its not possible to read/write the values of the SV's. When trying to write to a tag, this error occours "Error 1184 occurred at DataSocket Write in VarMan Write to Variable NATIONAL_INSTRUMENTS.vi->Variable Manager NATIONAL_INSTRUMENTS.vi"
    On the GUI, you will see two tags with green leds, these are configures to direct access in via max to an I/O point.
    Any help is greatly appriciated,
    søren jensen
    screenshooot files are attached as bmp's, please rename.
    Attachments:
    1950679035_2.gif ‏2209 KB
    1950679035.gif ‏752 KB
    1950679035_1.gif ‏927 KB

    Hi Søren,
    The error you are seing may be because of an incorrect path under your Bind to Source section for the shared variable.
    You may also find this page useful regarding the 1184 error: http://digital.ni.com/public.nsf/websearch/29895C80B1015A15862571DC0078747F?OpenDocument.
    Best regards,
    Peter Porsman | Applications Engineer | National Instruments

  • Sun App Server 9.0_01 (build b14) Deployment (undeploy) problems

    Hi all,
    I apologize for this long post but I want to provide as much info as possible. Also, I am not sure this is the right place for this posting. I will appreciate it if anyone could direct me to a better place.
    I have this ongoing problem deploying my application. The app server is unable to completely delete the previously deployed files. It goes into a series of timeout loops saying it is running the gc to try and free up resources. The files that can't be deleted are all in the web application's lib folder. I tried deleting them manually while waiting for the app server timeout loop and indeed each one is busy and can't be deleted. None of the files here are my code. The files are all in the folder:
    domain1\applications\j2ee-apps\TS5529\U04A1_war\WEB-INF\lib
    and the files are: appbase.jar, commons-fileupload.jar, dataprovider.jar, errorhandler.jar, jsfcl.jar, json2.jar, rowset.jar, sqlx.jar, webui-jsf.jar, webui-jsf-suntheme.jar
    I have made sure destroy() method in my SessionBean nulls out any resources used, even variables containing injected EJBs but the problem remains.
    The application is a NetBeans Enterprise application with a couple of Session Beans, Entity classes and Entity Facades. The presentation is JSF with Visual Web Pack and consists of two simple pages. The SessionBean holds a reference to a Stateful Bean and 4 variables each containing a custom ListDataProvider for JSF tables data binding. The SessionBean destroy method sets all of these variables to null.
    The first page backing bean does most of the work. It accesses the SFSB and DataProviders through the SessionBean. This page includes four EJB injections like this:
    @EJB AuthorFacadeLocal af;
    @EJB PublisherFacadeLocal pf;
    @EJB SearchDBLocal sDB;
    @EJB TitleFacadeLocal tf;
    and a variable holding an empty, unmanaged Entity object. I tried setting all of these to null in the page's destroy() method, which I don;t think I need to do.
    Is there a problem with these injections in the page's backing bean?? I've been at this for about a week, trying various ways to make sure resources are freed but the problem still there. The only solution is to stop the app server and then deploy. Needless to say, it is a pain having to stop the app server every time I need to deploy.
    Hope someone has seen this and can help, thanks in advance.

    Hi all,
    I apologize for this long post but I want to provide as much info as possible. Also, I am not sure this is the right place for this posting. I will appreciate it if anyone could direct me to a better place.
    I have this ongoing problem deploying my application. The app server is unable to completely delete the previously deployed files. It goes into a series of timeout loops saying it is running the gc to try and free up resources. The files that can't be deleted are all in the web application's lib folder. I tried deleting them manually while waiting for the app server timeout loop and indeed each one is busy and can't be deleted. None of the files here are my code. The files are all in the folder:
    domain1\applications\j2ee-apps\TS5529\U04A1_war\WEB-INF\lib
    and the files are: appbase.jar, commons-fileupload.jar, dataprovider.jar, errorhandler.jar, jsfcl.jar, json2.jar, rowset.jar, sqlx.jar, webui-jsf.jar, webui-jsf-suntheme.jar
    I have made sure destroy() method in my SessionBean nulls out any resources used, even variables containing injected EJBs but the problem remains.
    The application is a NetBeans Enterprise application with a couple of Session Beans, Entity classes and Entity Facades. The presentation is JSF with Visual Web Pack and consists of two simple pages. The SessionBean holds a reference to a Stateful Bean and 4 variables each containing a custom ListDataProvider for JSF tables data binding. The SessionBean destroy method sets all of these variables to null.
    The first page backing bean does most of the work. It accesses the SFSB and DataProviders through the SessionBean. This page includes four EJB injections like this:
    @EJB AuthorFacadeLocal af;
    @EJB PublisherFacadeLocal pf;
    @EJB SearchDBLocal sDB;
    @EJB TitleFacadeLocal tf;
    and a variable holding an empty, unmanaged Entity object. I tried setting all of these to null in the page's destroy() method, which I don;t think I need to do.
    Is there a problem with these injections in the page's backing bean?? I've been at this for about a week, trying various ways to make sure resources are freed but the problem still there. The only solution is to stop the app server and then deploy. Needless to say, it is a pain having to stop the app server every time I need to deploy.
    Hope someone has seen this and can help, thanks in advance.

  • Deploying on EC2 and Deployment Template Problems

    Hello,
    Im trying to configure a Endeca install on a EC2 micro instance as a proof of concept.
    So far i have deployed the following:
    /mnt/endeca/endeca/MDEX/6.2.1
    /mnt/endeca/endeca/PlatformServices/6.1.1/
    /mnt/endeca/endeca/Workbench/2.1.1/
    I can visit the Workbench admin console etc so everything is up and running. The problem im having is deploying and forging the sample pipeline contained in the deployment template app.
    I run the deployment template app to configure the pipeline but then when i come to run:
    ./initialize_services.sh
    I get a lot of warnings then an error and it crashes:
    [root@ip-10-58-182-152 control]# ./initialize_services.sh > /tmp/output.txt
    [04.30.12 16:24:01] INFO: Removing application. Any active components will be forced to stop.
    [04.30.12 16:24:02] INFO: Removing Web Studio config files.
    [04.30.12 16:24:02] INFO: [ITLHost] Starting shell utility 'emgr_update_remove_all_settings'.
    [04.30.12 16:24:02] INFO: Removing definition for custom component 'ConfigManager'.
    [04.30.12 16:24:02] INFO: Updating provisioning for host 'ITLHost'.
    [04.30.12 16:24:03] INFO: Updating definition for host 'ITLHost'.
    [04.30.12 16:24:03] INFO: Removing definition for application 'morrisons'.
    [04.30.12 16:24:03] INFO: Application 'morrisons' removed.
    [04.30.12 16:24:04] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
    [04.30.12 16:24:05] INFO: Setting definition for application 'morrisons'.
    [04.30.12 16:24:05] INFO: Setting definition for host 'ITLHost'.
    [04.30.12 16:24:05] INFO: Setting definition for host 'MDEXHost'.
    [04.30.12 16:24:05] INFO: Setting definition for host 'webstudio'.
    [04.30.12 16:24:06] INFO: Setting definition for script 'BaselineUpdate'.
    [04.30.12 16:24:06] INFO: Setting definition for script 'PartialUpdate'.
    [04.30.12 16:24:06] INFO: Setting definition for script 'ConfigUpdate'.
    [04.30.12 16:24:06] INFO: Setting definition for custom component 'ConfigManager'.
    [04.30.12 16:24:06] INFO: Updating provisioning for host 'ITLHost'.
    [04.30.12 16:24:06] INFO: Updating definition for host 'ITLHost'.
    [04.30.12 16:24:06] INFO: [ITLHost] Starting shell utility 'mkpath_dgraph-config'.
    [04.30.12 16:24:06] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_dgraph-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:06] INFO: [ITLHost] Starting shell utility 'mkpath_temp'.
    [04.30.12 16:24:07] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_temp' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:07] INFO: [ITLHost] Starting shell utility 'mkpath_complete-index-config'.
    [04.30.12 16:24:07] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_complete-index-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:07] INFO: [ITLHost] Starting shell utility 'mkpath_config'.
    [04.30.12 16:24:07] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:07] INFO: Setting definition for component 'Forge'.
    [04.30.12 16:24:07] INFO: [ITLHost] Starting shell utility 'mkpath_incoming'.
    [04.30.12 16:24:08] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_incoming' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:08] INFO: [ITLHost] Starting shell utility 'mkpath_complete-index-config'.
    [04.30.12 16:24:08] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_complete-index-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:08] INFO: [ITLHost] Starting shell utility 'mkpath_temp'.
    [04.30.12 16:24:08] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_temp' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:08] INFO: Setting definition for component 'PartialForge'.
    [04.30.12 16:24:08] INFO: [ITLHost] Starting shell utility 'mkpath_incoming'.
    [04.30.12 16:24:09] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_incoming' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:09] INFO: [ITLHost] Starting shell utility 'mkpath_cumulative-partials'.
    [04.30.12 16:24:09] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_cumulative-partials' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:09] INFO: Setting definition for component 'Dgidx'.
    [04.30.12 16:24:09] INFO: Setting definition for component 'Dgraph1'.
    [04.30.12 16:24:09] INFO: [MDEXHost] Starting shell utility 'mkpath_cumulative-partials'.
    [04.30.12 16:24:10] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_cumulative-partials' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:10] INFO: [MDEXHost] Starting shell utility 'mkpath_dgraph-config'.
    [04.30.12 16:24:10] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_dgraph-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:10] INFO: [MDEXHost] Starting shell utility 'mkpath_local-dgraph-input'.
    [04.30.12 16:24:10] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-dgraph-input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:10] INFO: [MDEXHost] Starting shell utility 'mkpath_local-cumulative-partials'.
    [04.30.12 16:24:15] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-cumulative-partials' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:16] INFO: [MDEXHost] Starting shell utility 'mkpath_local-dgraph-config'.
    [04.30.12 16:24:27] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-dgraph-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:32] INFO: [MDEXHost] Starting shell utility 'mkpath_local-xquery'.
    [04.30.12 16:24:43] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-xquery' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:46] INFO: Setting definition for component 'Dgraph2'.
    [04.30.12 16:24:57] INFO: [MDEXHost] Starting shell utility 'mkpath_cumulative-partials'.
    [04.30.12 16:24:57] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_cumulative-partials' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:57] INFO: [MDEXHost] Starting shell utility 'mkpath_dgraph-config'.
    [04.30.12 16:24:57] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_dgraph-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:58] INFO: [MDEXHost] Starting shell utility 'mkpath_local-dgraph-input'.
    [04.30.12 16:24:58] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-dgraph-input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:58] INFO: [MDEXHost] Starting shell utility 'mkpath_local-cumulative-partials'.
    [04.30.12 16:24:58] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-cumulative-partials' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:58] INFO: [MDEXHost] Starting shell utility 'mkpath_local-dgraph-config'.
    [04.30.12 16:24:59] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-dgraph-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:59] INFO: [MDEXHost] Starting shell utility 'mkpath_local-xquery'.
    [04.30.12 16:24:59] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_local-xquery' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host MDEXHost.
    [04.30.12 16:24:59] INFO: Setting definition for component 'LogServer'.
    [04.30.12 16:24:59] INFO: [ITLHost] Starting shell utility 'mkpath_input'.
    [04.30.12 16:24:59] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:24:59] INFO: Setting definition for script 'DailyReports'.
    [04.30.12 16:25:00] INFO: Setting definition for script 'WeeklyReports'.
    [04.30.12 16:25:00] INFO: Setting definition for script 'DailyHtmlReports'.
    [04.30.12 16:25:00] INFO: Setting definition for script 'WeeklyHtmlReports'.
    [04.30.12 16:25:01] INFO: Setting definition for component 'WeeklyReportGenerator'.
    [04.30.12 16:25:01] INFO: [ITLHost] Starting shell utility 'mkpath_input'.
    [04.30.12 16:25:01] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:25:01] INFO: Setting definition for component 'DailyReportGenerator'.
    [04.30.12 16:25:02] INFO: [ITLHost] Starting shell utility 'mkpath_input'.
    [04.30.12 16:25:02] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:25:02] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'.
    [04.30.12 16:25:02] INFO: [ITLHost] Starting shell utility 'mkpath_input'.
    [04.30.12 16:25:02] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:25:03] INFO: Setting definition for component 'DailyHtmlReportGenerator'.
    [04.30.12 16:25:03] INFO: [ITLHost] Starting shell utility 'mkpath_input'.
    [04.30.12 16:25:03] WARNING: Failed to create custom directory: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Utility 'mkpath_input' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    [04.30.12 16:25:03] INFO: Definition updated.
    [04.30.12 16:25:03] INFO: Updating IAP Workbench configuration...
    [04.30.12 16:25:03] INFO: Downloading config files from Web Studio.
    [04.30.12 16:25:03] INFO: [ITLHost] Starting shell utility 'emgr_update_get_ws_settings'.
    [04.30.12 16:25:03] SEVERE: Utility 'emgr_update_get_ws_settings' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    Occurred while executing line 5 of valid BeanShell script:
    2|
    3| if (ConfigManager.isWebStudioEnabled()) {
    4| log.info("Updating IAP Workbench configuration...");
    5| ConfigManager.updateWsConfig();
    6| log.info("Finished updating IAP Workbench.");
    7| }
    8|
    [04.30.12 16:25:03] SEVERE: Caught an exception while invoking method 'run' on object 'InitialSetup'. Releasing locks.
    Caused by java.lang.reflect.InvocationTargetException
    sun.reflect.NativeMethodAccessorImpl invoke0 - null
    Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
    com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
    Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
    com.endeca.soleng.eac.toolkit.utility.Utility run - Utility 'emgr_update_get_ws_settings' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
    Can anyon shed any light on this?
    Thanks
    Ben

    Hello,
    It looks like you are working with the Endeca Experience Management product (previously known as InFront), rather than Endeca Information Discovery product (previously known as Latitude).
    You might have more luck posting this question on the Endeca Experience Management forum:
    Technical Questions

  • Help Please with media pending problem!!

    I've been using PP CS6 for a couple of years on a Rain system with no problems at all.  Yesterday evening I deleted several old files on my scratch disc, one of them I think contained all of the cache files for all the projects on that drive.  Now every project I open it takes forever to load the media, and I get "media pending"  Once it all does load I can't hardly play it back because it keeps locking up.  I have several projects that I have to get out and am really in a bind here, can anyone give me a hand??

    Ronin,
    If we're talking about a laptop, then are you running the 2630 or 2630qm?  Most likely the qm version, no?  It appears that the 2630qm DOES have integrated graphics:
    http://ark.intel.com/products/52219/Intel-Core-i7-2630QM-Processor-6M-Cache-up-to-2_90-GHz
    You ALSO have an NVIDIA card.  Again "Optimus" is simply an "Apple-ism" (like "Retina" or "Flash Storage") for Integrated (aka On-board) graphics working in tandem WITH a more powerful graphics card (i.e. the gtx 560m).  I would take a serious look at disabling it via the instructions in the link I sent previously.  They may not even have thought up the moniker "Optimus" when your laptop was released.  I don't know.  Regardless, when the computer tries to switch between the on-board (power-saving and weak) graphics card to the NVIDIA card, you might experience exactly the type of symptoms you've described.
    By way of example:  Take the Asus g75vx.  It comes stock with a 3630qm chip.  The 3630qm has no option for on-board graphics at all (aka Intel HD 3000, 4000, etc).  The g75vx comes with a gtx 670mx, but if paired with the "wrong" i7 mobile chip, it might just as easily have on-board (Intel HD) graphics, too.
    Another way to check might be to open up Device Manager and see what entries are listed under under Display Adapters.

Maybe you are looking for