JMSBC application is not deploying

Hi all,
i am creating an bpel in which i am using an soap BC to pass input and get response, after that invoking an HL7BC after that i am using an JDBC BC to get result, then i am invoking an JMSBC which collects result from jdbc and then write it to queue in application server then again i am using an JMSBC to get result from queue and send it to our 1st soap BC.
when i am deploying my composite application it is giving following error.
[#|2008-05-13T13:54:13.758+0530|INFO|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.JMSBindingDeployer|_ThreadID=70;_ThreadName=JMSTestCompApp-sun-jms-binding;JMSTestCompApp-sun-jms-binding;E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\jbi\service-assemblies\JMSTestCompApp\JMSTestCompApp-sun-jms-binding\sun-jms-binding;|JMSBC-I0713: Service unit JMSTestCompApp-sun-jms-binding has been undeployed; service unit path is E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\jbi\service-assemblies\JMSTestCompApp\JMSTestCompApp-sun-jms-binding\sun-jms-binding |#]
[#|2008-05-13T13:54:14.930+0530|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=26;_ThreadName=httpWorkerThread-4848-4;|JBIMA0412: Service Assembly with ID : JMSTestCompApp has been undeployed.|#]
[#|2008-05-13T13:54:23.305+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Timer-36;_RequestID=d6ba5662-0045-476f-9e30-5668c34b279f;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Error expanding archive E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\autodeploy\amserver.war; please see the server log file for more information
     at com.sun.enterprise.deployment.backend.J2EEModuleExploder.explodeJar(J2EEModuleExploder.java:359)
     at com.sun.enterprise.deployment.backend.WebModuleDeployer.preDeploy(WebModuleDeployer.java:131)
     at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:171)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
     at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
     at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:564)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:545)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:492)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:267)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
|#]
[#|2008-05-13T13:54:23.305+0530|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Timer-36;Error expanding archive E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\autodeploy\amserver.war; please see the server log file for more information
;_RequestID=d6ba5662-0045-476f-9e30-5668c34b279f;|"DPL8011: autodeployment failure while deploying the application : Error expanding archive E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\autodeploy\amserver.war; please see the server log file for more information
"|#]
[#|2008-05-13T13:54:23.305+0530|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Timer-36;|[AutoDeploy] Autodeploy failed : E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\autodeploy\amserver.war.|#]
I am not getting what it is saying.
please help me.
thanks and regards,
bikkie

Error expanding archive E:\Softwares\OpenEsb\glassfish-v2-ur2-b02-patch-20080402\domains\domain1\autodeploy\amserver.waris the visible error. Yo may have a previous deploy where the files are locked or in use. Maybe a readonly issue with the directories.
What version of Java and Glassfish?
You may need to clean out the previous deploy. Delete your war folder under
C:\glassfish\domains\domain1\applications\j2ee-modules
or if it is an ent app
C:\glassfish\domains\domain1\applications\j2ee-apps
Then in C:\glassfish\domains\domain1\config\domain.xml carefully take out all tags referencing your app.
Maybe backup first...

Similar Messages

  • Webdynpro Application is not Deploying into Netweaver 2004s From NWDS CE

    Hi,
    I Developed Webdynpro Application in NWDS CE 7.1 SP5.
    I Am using Netweaver 2004s AS JAVA .
    After Deploying application i will get page can not be displayed and in the browser url is following below
    http://localhost:-1/webdynpro/dispatcher/demo.sap.com/firstapp/FirstApp?SAPtestId=2
    my actual port is 50000 but it gives -1.
    and also i need one clarification NWDS CE 7.1 Applications Supports the Netweaver 2004s or
    it requires Netweaver CE 7.1 AS JAVA.
    We have to develop applications using webdynpro,mobile perspectives in NWDS CE 7.1 SP5
    Is it Supports Netweaver 2004s.
    Thanks
    Subbarao

    Hi
    NetWeaver CE 7.1 uses Java 5 and so does the NWDS CE 7.1 by default. The server you have is NW 2004s SP 9 which runs on Java 1.4. So you simply can not build with Java 5 and deploy it to a server with JRE 1.4, you will get a class unsupported version error.
    Next you are using NWDS CE 7.1 to connect to server 2004s. The architecture of the Java servers in SAP is changed. 2004s has SDM and dispatcher and a server process at its simplest form. In CE theres an ICM and server. (SDM & Dispatcher combined). You no more give the message port number when you set up the JEE server of NWDS 7.1 instead you would use instance number. When you register a NW 2004s server with NWDS 7.1 (instance numbers are available for 7.0 servers as well), the studio fails to find the deploy mechanism (SDM or ICM) hence you see a port -1.
    Lastly the architecture of WebDynpro is greatly changed from NW 7.0 to NW 7.1 so dont even think of deployment to previous versions.
    Regards
    LNV

  • ADf mobile application is not deploy in device

    I use following video for configuring ios setting.
    http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/adfmobiledeployios.html
    But, When i deploye application in device i get following error.
    [03:27:06 PM] xcrun: Error: could not stat active Xcode path '/Volumes/Xcode/Xcode.app/Contents/Developer'. (No such file or directory)
    [03:27:06 PM] Command-line execution failed (Return code: 0)
    [03:27:06 PM] Deployment cancelled.
    [03:27:06 PM] ---- Deployment incomplete ----.
    [03:27:06 PM] Failed to package the XCode application.
    [03:27:06 PM] Failed to build the iOS application bundle.
    [03:27:06 PM] Deployment failed due to one or more errors returned by '/usr/bin/xcrun'. The following is a summary of the returned error(s):
    xcrun: Error: could not stat active Xcode path '/Volumes/Xcode/Xcode.app/Contents/Developer'. (No such file or directory)

    Can you clarify which version of JDeveloper you are using?
    Can you try the configuration steps here:
    http://docs.oracle.com/cd/E18941_01/tutorials/MobileTutorial/jdtut_11r2_54_1.html

  • EJBTutorial application does not deploy

    Hello
    I used Workshop for Weblogic 9.2(on Windows) to go through the steps to create the EJB application which comes as part of the tutorial(Visit Bean). The tutorial uses Beehive controls to build the app. After building the app, i created an EAR file via the workshop Export option to be able to deploy it on a WL server running on Linux.
    On the Linux system, i first created a regular WL domain and then extended the domain to include the Beehive template. When i attempt to deploy the application EAR that was generated using Workshop, i get the following exception
    javax.enterprise.deploy.model.exceptions.DDBeanCreateException: [J2EE Deployment SPI:260142]The descriptor at 'META-INF/annotation-manifest.xml' in module 'VisitWebTest.war' is not recognized, and could not be parsed
    Any clues as to why this might be happening?
    Thanks
    Ramdas

    Raj,
    I was able to create a regular WLS domain and then extend it to include the workshop template. But the same error persists. This time I imported the pre-created EJB Tutorial zip file into my Workshop on windows and exported it to a EAR. I used this EAR to deploy it to the domain on Linux. When i attempt to activate the deployment changes, this is what i get:
    An error occurred during activation of changes, please see the log for details.
    Message icon - Error     Exception preparing module: EJBModule(VisitEJBProject.jar) Unable to deploy EJB: VisitEJBProject.jar from VisitEJBProject.jar: There are 1 nested errors: weblogic.ejb.container.compliance.ComplianceException: In EJB VisitBean, there is an ejbPostCreate method ejbPostCreate(java.lang.Integer) that has no matching ejbCreate method. at weblogic.ejb.container.compliance.EntityBeanClassChecker.doCheckCreatesMatchPostCreates(EntityBeanClassChecker.java:117) at weblogic.ejb.container.compliance.EJB20EntityBeanClassChecker.checkCreatesMatchPostCreates(EJB20EntityBeanClassChecker.java:68) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object
    I checked the VisitBean code and it did not have an ejbPostCreate(java.lang.Integer) method.
    -Ramdas

  • Superseding Application Installed when NOT deployed and NOT set to Automatically Upgrade

    SCCM 2012 SP1  
    I have an application of Adobe Reader X which is deployed as "available" to the "All Workstations" collection.  (It is also installed as part of our OSD task sequence for all workstations, if that matters.) 
    Some months ago I packaged Adobe Reader XI and did NOT set it to supersede Adobe Reader X.  It was deployed as available to a small user collection.
    Flash forward to yesterday.  I wanted Reader XI to be available to all IS staff, but not to automatically install for any of them or to automatically replace existing Reader X installs for anyone.   I went into my existing Adobe Reader XI application
    and set it to supersede the Adobe Reader X deployment type.  I then deployed Adobe Reader XI as "Available" to my "IS Staff" user collection and did NOT select the "Automatically upgrade any superseded versions of this application." 
    Overnight, all existing installs of Adobe Reader X were replaced by Adobe Reader XI on all workstations that were powered on during the maintenance window.  I was understandably surprised and double-checked my deployment settings.  It *is* deployed
    as "available" to all IS staff and to the pre-existing user collection.  and verified that I do not have Adobe Reader XI deployed to ANY other collections other than the original small user collection and now to my IS Staff collection, both
    as "Available".
    I checked APPINTENTEVAL.log on some of the affected workstations and noted that once I had created the supersedence relationship, all workstations that I've checked started logging as "Applicability = Applicable" and as soon as the maintenance window
    started, they installed.
    I'm very confused.  I've used Application Supersedence many times, and it has never applied to a collection to which the superseding application was not deployed.  Can anyone suggest a mechanism I might have missed that made this app evaluate as
    applicable on every workstation that had Reader X deployed to it?  I'm confident that it should have have.

    Is Reader XI used in a (OSD) task sequence?
    Torsten Meringer | http://www.mssccmfaq.de

  • Applications not deploying on startup / multiple applications

    On one of our production servers (just one), when I restart weblogic,
    my web applications are not deploying; I have to deploy them manually.
    This is bad, obviously, because the server won't restore properly
    after a restart.
    After a while, I get target="box,box,box,box" that represents the
    multiple times I've deployed that application to the target "box".
    From config.xml:
    <Application Deployed="true" Name="revx" Path="F:\revx">
    <WebAppComponent Name="revx"
    Targets="giocm,giocm,giocm,giocm,giocm,giocm,giocm"
    URI="revx"/>
    </Application>
    The operating system is Windows 2000 5.00.2195 ... everything was
    working fine until I re-installed the Windows service this weekend.
    I've checked permissions on the folder, on the file, and who the
    service is running as. I've manually edited config.xml to remove the
    duplicate target entries.
    I've seen some other posts from people who have also experienced
    applications not deploying on WL restart, but I don't see any
    resolutions.
    Rob

    Thank you, but the problem is a little different from that. These are
    exploded web apps outside the applications dir. I deployed them
    through the console initially; on the other servers, when WL restarts,
    the apps are deployed back to their targets just fine. It's only this
    box that loses sense of the targets on WL restart.
    We're on 6.1, so a few people have suggested upgrading to 6.1 sp4 --
    they've said they've seen this problem, and the sp corrects it.
    That said, this is a production box and upgrading it is a hassle. I'll
    get started on scheduling that, but if anyone has any ideas in the
    meantime, I'd greatly appreciate it. If not, thanks anyway. :)
    Rob
    "Deepak Vohra" <[email protected]> wrote in message news:<3eebae8e$[email protected]>...
    WLServer should start in development mode for a application
    in the applications dir to deploy.
    STARTMODE=false
    [email protected] (Rob Young) wrote:
    On one of our production servers (just one), when I restart weblogic,
    my web applications are not deploying; I have to deploy them manually.
    This is bad, obviously, because the server won't restore properly
    after a restart.
    After a while, I get target="box,box,box,box" that represents the
    multiple times I've deployed that application to the target "box".
    From config.xml:
    <Application Deployed="true" Name="revx" Path="F:\revx">
    <WebAppComponent Name="revx"
    Targets="giocm,giocm,giocm,giocm,giocm,giocm,giocm"
    URI="revx"/>
    </Application>
    The operating system is Windows 2000 5.00.2195 ... everything was
    working fine until I re-installed the Windows service this weekend.
    I've checked permissions on the folder, on the file, and who the
    service is running as. I've manually edited config.xml to remove the
    duplicate target entries.
    I've seen some other posts from people who have also experienced
    applications not deploying on WL restart, but I don't see any
    resolutions.
    Rob

  • Jenkins not deploying on Tomcat; SSH Service not starting

    So I've had a couple of problems happening. My first problem is that even though sshd.service and sshd.socket are enabled with systemctl, it does not automatically start. There are no errors reported in journalctl, it just does not start. When issuing systemctl status sshd.service and systemctl status sshd.socket, there is nothing to report. Once I manually start them, there are no errors reported, and everything works as expected.
    sshd.socket
    [Unit]
    Conflicts=sshd.service
    Wants=sshdgenkeys.service
    [Socket]
    ListenStream=22
    Accept=yes
    [Install]
    WantedBy=sockets.target
    sshd.service
    [Unit]
    Description=OpenSSH Daemon
    Wants=sshdgenkeys.service
    After=sshdgenkeys.service
    After=network.target
    [Service]
    ExecStart=/usr/bin/sshd -D
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    Restart=always
    [Install]
    WantedBy=multi-user.target
    # This service file runs an SSH daemon that forks for each incoming connection.
    # If you prefer to spawn on-demand daemons, use sshd.socket and [email protected].
    The second problem is my tomcat service. It won't start the Jenkins. I've linked the jenkins.war file to the webapps folder. When I start tomcat using systemctl start tomcat8, this is the output of journalctl -xn
    -- Logs begin at Sat 2014-08-30 06:46:59 PDT, end at Sun 2014-09-14 15:45:38 PDT. --
    Sep 14 15:45:15 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:15 PM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["http-nio-8080"]
    Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["ajp-nio-8009"]
    Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["http-nio-8080"]
    Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["ajp-nio-8009"]
    Sep 14 15:45:27 localhost systemd[1]: [/usr/lib/systemd/system/systemd-journal-upload.service:20] Unknown lvalue 'After' in section 'Install'
    Sep 14 15:45:38 localhost systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
    Sep 14 15:45:38 localhost jsvc[28476]: Cannot locate Java Home
    Sep 14 15:45:38 localhost systemd[1]: tomcat8.service: control process exited, code=exited status=1
    Sep 14 15:45:38 localhost systemd[1]: Failed to start Tomcat 8 servlet container.
    -- Subject: Unit tomcat8.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tomcat8.service has failed.
    -- The result is failed.
    Sep 14 15:45:38 localhost systemd[1]: Unit tomcat8.service entered failed state.
    Here is the tomcat8.service file before my changes, as suggested here
    [Unit]
    Description=Tomcat 8 servlet container
    After=network.target
    [Service]
    Type=forking
    PIDFile=/var/run/tomcat8.pid
    Environment=CATALINA_PID=/var/run/tomcat8.pid
    Environment=TOMCAT_JAVA_HOME=/usr/lib/jvm/java-7-openjdk
    Environment=CATALINA_HOME=/usr/share/tomcat8
    Environment=CATALINA_BASE=/usr/share/tomcat8
    Environment=CATALINA_OPTS=
    ExecStart=/usr/bin/jsvc \
    -Dcatalina.home=${CATALINA_HOME} \
    -Dcatalina.base=${CATALINA_BASE} \
    -Djava.io.tmpdir=/var/tmp/tomcat8/temp \
    -cp /usr/share/java/commons-daemon.jar:/usr/share/java/eclipse-ecj.jar:${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \
    -user tomcat8 \
    -java-home ${TOMCAT_JAVA_HOME} \
    -pidfile /var/run/tomcat8.pid \
    -errfile SYSLOG \
    -outfile SYSLOG \
    $CATALINA_OPTS \
    org.apache.catalina.startup.Bootstrap
    ExecStop=/usr/bin/jsvc \
    -pidfile /var/run/tomcat8.pid \
    -stop \
    org.apache.catalina.startup.Bootstrap
    [Install]
    WantedBy=multi-user.target
    And after
    [Unit]
    Description=Tomcat 8 servlet container
    After=network.target
    [Service]
    Type=forking
    PIDFile=/var/run/tomcat8.pid
    Environment=CATALINA_PID=/var/run/tomcat8.pid
    Environment=TOMCAT_JAVA_HOME=/usr/lib/jvm/java-7-openjdk
    Environment=CATALINA_HOME=/usr/share/tomcat8
    Environment=CATALINA_BASE=/usr/share/tomcat8
    Environment=CATALINA_OPTS=-DJENKINS_HOME=/usr/share/java/jenkins
    ExecStart=/usr/bin/jsvc \
    -Dcatalina.home=${CATALINA_HOME} \
    -Dcatalina.base=${CATALINA_BASE} \
    -Djava.io.tmpdir=/var/tmp/tomcat8/temp \
    -cp /usr/share/java/commons-daemon.jar:/usr/share/java/eclipse-ecj.jar:${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \
    -user tomcat8 \
    -java-home ${TOMCAT_JAVA_HOME} \
    -pidfile /var/run/tomcat8.pid \
    -errfile SYSLOG \
    -outfile SYSLOG \
    $CATALINA_OPTS \
    org.apache.catalina.startup.Bootstrap
    ExecStop=/usr/bin/jsvc \
    -pidfile /var/run/tomcat8.pid \
    -stop \
    org.apache.catalina.startup.Bootstrap
    [Install]
    WantedBy=multi-user.target
    EDIT:
    The SSHD problem is fixed. I read more closely at the sshd.socket config, and it clearly states it conflicts with sshd.service. I disabled service and everything works fine. But I am still having trouble getting Jenkins to work with Tomcat.
    Last edited by ZMoore (2014-09-15 00:33:18)

    Thank you, but the problem is a little different from that. These are
    exploded web apps outside the applications dir. I deployed them
    through the console initially; on the other servers, when WL restarts,
    the apps are deployed back to their targets just fine. It's only this
    box that loses sense of the targets on WL restart.
    We're on 6.1, so a few people have suggested upgrading to 6.1 sp4 --
    they've said they've seen this problem, and the sp corrects it.
    That said, this is a production box and upgrading it is a hassle. I'll
    get started on scheduling that, but if anyone has any ideas in the
    meantime, I'd greatly appreciate it. If not, thanks anyway. :)
    Rob
    "Deepak Vohra" <[email protected]> wrote in message news:<3eebae8e$[email protected]>...
    WLServer should start in development mode for a application
    in the applications dir to deploy.
    STARTMODE=false
    [email protected] (Rob Young) wrote:
    On one of our production servers (just one), when I restart weblogic,
    my web applications are not deploying; I have to deploy them manually.
    This is bad, obviously, because the server won't restore properly
    after a restart.
    After a while, I get target="box,box,box,box" that represents the
    multiple times I've deployed that application to the target "box".
    From config.xml:
    <Application Deployed="true" Name="revx" Path="F:\revx">
    <WebAppComponent Name="revx"
    Targets="giocm,giocm,giocm,giocm,giocm,giocm,giocm"
    URI="revx"/>
    </Application>
    The operating system is Windows 2000 5.00.2195 ... everything was
    working fine until I re-installed the Windows service this weekend.
    I've checked permissions on the folder, on the file, and who the
    service is running as. I've manually edited config.xml to remove the
    duplicate target entries.
    I've seen some other posts from people who have also experienced
    applications not deploying on WL restart, but I don't see any
    resolutions.
    Rob

  • Spring application won't deploy but nothing relevant is logged?

    Hi
    I'm trying to deploy a WAR application to OC4J using DCMCTL. The problem I am experiencing is that if I include certain Spring configuration directives inside the application, a Spring BeanCreationException is thrown and the application will not deploy.
    So far, so my bad. But in order to debug what is wrong with the application, I need to see the log that Spring has written as it fails to start up. However OC4J apparently removes this log because the application doesn't start successfully. DCMCTL merely gives an error that it's RMI layer can't de-serialize the BeanCreationException, which is to be expected as of course the deployer doesn't know classes inside the WAR it is deploying. Oracle support have been contacted and so far their help has been underwhelming to say the least ('check the web-inf/lib has the BeanCreationException' was the last less-than-useful suggesstion from them, whcih of course it does, spring-beans.jar is definitely in the WAR as is the rest of Spring that we are using).
    I have been trying unsuccessfully to add either a log4j.xml or logging.properties file into my web-app's classes directory in order to make Spring send its log output someplace where it will be kept after the application fails to deploy. But so far there has been no joy. A little bit of 'flying blind' fiddling has reduced the area of spring configuration to approx where the problem is located, but I'm afraid I need some sort of decent log output in order to locate the precise nature of the problem. If I comment out that section of the config the app starts OK, so in general Spring is working (as is the other application WAR wired with Spring). How do I get to see that log output that I need? It's nowhere in any Oracle log. What logging configuration do I need to change to make Spring's stack trace visible - OC4J's configuration seems awfully strange to me, not at all like a usuall logging configuration?
    At this stage we are desparate to get that stacktrace as it's a massive blocker on development. So even if anyone can tell me how to bypass all of oracle's overly-complex logging system and send it through the JVM's global configuration it would still be a win for us for the time being.
    thanks

    Just FYI incase anyone ever googles this question. So far the issue is unsolved. It is logged still with Oracle support.
    We isolated the area of troublesome Spring configuration by 'flying blind' (that is, making small changes one by one and trying to redeploy until finally it did).
    Then we edited the edited the configuration of the deployed application in-container and restarted the container.
    At THIS point it logged several illuminating entries into the server.log. These were generally 'Duh!' moments regarding missing jars that various bits of Spring or Hibernate depended on. Using this extremely tedious method eventually we got the app into a state where it could be deployed.
    I will note here that it is massive design fail for the error not to be correctly logged into the server.log when deployment attempted, which is why the issue is still logged with oracle and we will be pressing for resolution.

  • Deployed application does not contain javascript files

    Hello,
    I am a unexperienced user of the BPM Studio. When I start my application in Oracle BPM my application does not contain the javascript files. It is quite weird, because the path to the .js files is proper - the application works on other computers. I have observed several weird things:
    - when I lookup the application in Firebug, when I try to lookup the source of the .js files, firebug console presents something like this (i deleted most of the html so that it is easy to read):
    <html><head><title>Apache Tomcat/5.5.15 - Error report</title>
    <body>HTTP Status 404 - /workspace//webRoot/webResources/js/jquery-1.4.2.min.js
    Status report message /workspace//webRoot/webResources/js/jquery-1.4.2.min.js
    The requested resource (/workspace//webRoot/webResources/js/jquery-1.4.2.min.js) is not available.
    <h3>Apache Tomcat/5.5.15</h3></body></html>- as i said - the application works just fine on other computers, without having to edit the path to the .js files
    - the application doesn't deploy the application (at least I think it does not) in the OraBPMStudioHome - the application is in the following folder:
    C:\Users\<username>\AppData\Local\VirtualStore\Program Files\OraBPMStudioHome\webapps\workspace\webRoot
    I am using OracleBPM Studio 10gR3, my system is Windows 7 Proffessional 64bit. Could the fact, that my system is 64 bit, cause the error?
    I haven't changed anything in the web.xml, workspace.properties files.
    It looks as if the server didn't include my js files. What may be causing this? I tried to locate the folder where the Tomcat Server deployes the application, and copying the js files where they should be manually, but that didn't work out well - the web application still does not see them.
    By the way, the double // slashes in the path to the .js file are fine on other computers, but is that proper?
    My application uses other scripts, not only jQuery, so changing the link to the jQuery file, won't work.
    I'd be very happy for any solution, thanks in advance!
    Chris Mejka
    Edited by: 789731 on 2010-08-20 01:20

    Nope, that's not the case; all the imports are handled by the <fuego:webResources /> tag, like this:
    <script type="text/javascript" src="<fuego:webResources relativePath='js/jquery-1.4.2.min.js'/>"></script>If that helps, the folder structure, with the .js files is as follows: ../webRoot/webResources/js/ ....
    As I said before - none of my colleagues, who use this application, has this problem, the application runs fine on other computers. The only (or at least that's what I think) difference, is that I use a 64 bit OS... Maybe that's the problem? Or maybe something is wrong in one of my BPM configuration files?
    Edited by: 789731 on 2010-08-20 02:29
    Edited by: 789731 on 2010-08-20 04:42

  • Can not deploy after upgrading application from workshop 8.1 to 9.2

    Hi,
    We have an application developed on workshop 8.1 worked fine. when we upgrade the application to 9.2, the application can not be deployed on weblogic server. The error is
    weblogic.application.ModuleException: [HTTP:101064][WebAppModule(SynDesk:SynDesk
    Web)] Error parsing descriptor in Web appplication "C:\build\weboutput"
    "weblogic.application.ModuleException: Unmarshaller failed'
    Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists:
    "weblogic.j2ee.descriptor.ParamValueBeanImpl@dccea29(/[NTLM HTTP Authentication
    Filter]/InitParams[jcifs.netbios.wins])"
    When I remove the NTLM filter part in the web.xml, the application is able to be deployed. But of course application does not work propertly due to no authentication.
    How can I fix the web.xml file with everything works as before? Thanks for your help
    Here is my web.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>SyndeskWeb Application</display-name>
    <description/>
    <filter>
    <filter-name>NTLM HTTP Authentication Filter</filter-name>
    <filter-class>com.mycompany.BofaNtlmFilter</filter-class>
    <init-param>
    <description/>
    <param-name>jcifs.netbios.wins</param-name>
    <param-value>crpsecwin00.mycompany.com</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>jcifs.netbios.wins</param-name>
    <param-value>crpchiwin00.mycompany.com</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>debug</param-name>
    <param-value>true</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>jcifs.util.log</param-name>
    <param-value>ALL</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>bofa.retryCount</param-name>
    <param-value>1</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>bofa.retrySleepTime</param-name>
    <param-value>60</param-value>
    </init-param>
    </filter>
    <filter-mapping>
    <filter-name>NTLM HTTP Authentication Filter</filter-name>
    <url-pattern>*.jsp</url-pattern>
    </filter-mapping>
    <filter-mapping>
    <filter-name>NTLM HTTP Authentication Filter</filter-name>
    <url-pattern>*.jpf</url-pattern>
    </filter-mapping>
    <filter-mapping>
    <filter-name>NTLM HTTP Authentication Filter</filter-name>
    <url-pattern>*.do</url-pattern>
    </filter-mapping>
    <servlet>
    <description/>
    <servlet-name>action</servlet-name>
    <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
    <init-param>
    <description/>
    <param-name>config</param-name>
    <param-value>/_pageflow/struts-config.xml</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>config/-global</param-name>
    <param-value>/_pageflow/struts-config--global.xml</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>debug</param-name>
    <param-value>2</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>detail</param-name>
    <param-value>2</param-value>
    </init-param>
    <load-on-startup>2</load-on-startup>
    </servlet>
    <welcome-file-list>
    <welcome-file>Controller.jpf</welcome-file>
    </welcome-file-list>
    <error-page>
    <error-code>500</error-code>
    <location>/error.jsp</location>
    </error-page>
    <error-page>
    <error-code>505</error-code>
    <location>/error.jsp</location>
    </error-page>
    <error-page>
    <error-code>404</error-code>
    <location>/Controller.jpf</location>
    </error-page>
    <jsp-config>
    <taglib>
    <taglib-uri>netui-tags-html.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/netui-tags-html.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>netui-tags-databinding.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/netui-tags-databinding.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>netui-tags-template.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/netui-tags-template.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>c.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/c.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>fmt.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/fmt.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>sql.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/sql.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>x.tld</taglib-uri>
    <taglib-location>/WEB-INF/tld/x.tld</taglib-location>
    </taglib>
    </jsp-config>
    <filter>
    <filter-name>PageFlowJspFilter</filter-name>
    <filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
    </filter>
    <filter>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
    <init-param>
    <param-name>response-code</param-name>
    <param-value>404</param-value>
    </init-param>
    </filter>
    <filter-mapping>
    <filter-name>PageFlowJspFilter</filter-name>
    <url-pattern>*.jsp</url-pattern>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowJspFilter</filter-name>
    <url-pattern>*.jspx</url-pattern>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.java</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.jsfb</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.jpfs</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>/_pageflow/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <listener>
    <listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
    </listener>
    <listener>
    <listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
    </listener>
    <servlet>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>action</servlet-name>
    <url-pattern>*.jpf</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>action</servlet-name>
    <url-pattern>*.do</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <url-pattern>*.xhr</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <url-pattern>*.render</url-pattern>
    </servlet-mapping>
    </web-app>
    Edited by cynthialiu at 05/28/2008 12:16 PM

    Hi. The issue is a level or two above JDBC. I suggest
    opening an official support case. It's probably a
    WLW issue.
    Joe

  • Crawl issue - warning: "This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of ....a start address"

    Hello all,
    I have a multi-tenant environment in SharePoint 2010 server. Different tenants are hosted by one web app.
    One content source has been created to crawl the all shared environment. (the only URL added in the content source settings = URL of the
     web app)
    Crawl everything under the hostname for each start address has been selected when creating this content source.
    Now I have created a new tenant hosted by the same web app. For this new tenant I want to have a different crawl schedule. Simple , I just create a new content source and add the host URL of this tenant. With the same settings has the other content source.
    After having started a full crawl I get 0 success and 1 warning : “This URL is part of a host header SharePoint deployment and the search application is not configured to crawl
    individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.”
    The first content source is well crawling the new tenant freshly created. Could you tell me where I’m wrong?
    Thanks in advance
    Regards
    Baldo

    Baldo,
    In the configuration that you described you now have 2 content sources set to crawl the same content. If you have a content source with a start address of http://servername/ then it is going to crawl everything past that address. If you are now changing
    the crawl schedule based on the individual site collections, you will need to move your start addresses further down the URL.
    For Example:
    1st Content Source:
    http://servername/ as a start address would now become
    http://servername/site1
    http://servername/site2
    2nd Content Source:
    http://servername/site3
    Also remember that all crawling must happen on the default zone. If you are trying to crawl a zone that the web application has been extended into, that will not work.
    ScottC - Microsoft SharePoint Support

  • Deployed application is not picked up during weblogic startup

    I'm having this strange problem, my application is deployed with java.Deployer
    tool, works fine, then when ever i reboot the weblogic server, the application
    is not accessible untill i explicitly redeploy it again.
    Please help!

    http://e-docs.bea.com/wls/certifications/certs_810/overview.html
    Looks 141_03. But you have to understand what "certification" means.
    Typically within minor revs of the VM 141_03 and 142 you are ok and there
    should be no problems.
    As for the proving it to you... There were lots of changes and improvemetns
    to the 8.1 code line for deployment. As for knowing what your testing for,
    OOM is a general error with no clear indication of where the problem lies,
    its not clear if it is WLS version or the VM itself. I am sure you know the
    hard answer there, it takes digging in with a profiler to find the culprit.
    You have two options:
    1) Drill down with a profiler in your env and figure out exactly WHAT is the
    cause of the leak in the current environment
    2) switch between different app verndors/versions and VMs.
    Either way you have alot of varialbes to track, take care of and compare.
    There is no silver bullet as always.
    Cheers
    mbg
    "Stephen" <[email protected]> wrote in message
    news:[email protected]...
    >
    BTW, is 8.1 certified with 1.4.2 on Solaris/Sparc yet? Otherwise it is anon-starter
    >
    "Stephen" <[email protected]> wrote:
    SOS, we hear this one all the time, the new and improved version fixes
    the problem.
    Is this a 1.4.2 fix that helps 8.1 or something in the code that is
    different?
    be specific, I have this problem as well and am not willing to give it
    another
    try unless I know what I am testing for.
    "Mark Griffith" <[email protected]> wrote:
    My suggestion would be to try 8.1, I developed many sample applications
    over
    the course of the release and never had to restart the server and could
    continually redeploy. The worst it got was having to completely
    undeploy
    and redeploy the application. (undeploy + redeploy is different that
    just
    redeploy).
    Cheers
    mbg
    "Tom Wilson" <[email protected]> wrote in message
    news:[email protected]...
    This probably doesn't help but....we were doing our initial
    development
    using
    Weblogic 7.0 using 1.3.1_08 but finally we got tired of dealing withthe
    out
    of memory issues resulting from continuously deploying new versionsof JSP
    pages on our system. We found that running into the "Out of Memory"exceptions
    combined with restarting and redeploying the app wasted too much time- an
    average of 7 minutes about 7-8 times a day resulting in about 1 hourworth
    of downtime for each developer using Weblogic. We finally trieddeveloping
    our system with Tomcat and OpenEJB and now we never get "Out of
    Memory"
    exceptions requiring us to restart Tomcat - provided we are onlyworking
    on JSP's.
    Also, we used JDK 1.4.2 with Tomcat which helps get around the memoryleak
    issue
    that results from compiling JSP's using JDK 1.3.1.
    My suggestion...try something else
    "Stephen Westbom" <[email protected]> wrote:
    I have had the same problem with Weblogic 7.0 sp4 using 1.3.1_08.
    I
    found that
    turning off deadspot helps (otherwise known as hotspot).
    It makes it unusable after a while in a production environment.
    Our
    firm is considering
    switching to JBoss because it is simpler and more reliable, despiteno
    good user
    friendly deployment tools.
    Weblogic concentrates too much on bells and whistles that sound good
    rather than
    reliability and usability. I guess existing customers are not asimportant
    as
    new business.
    "Dmitry Amelchenko" <[email protected]> wrote:
    Also, I don't know if that helps, but in general we've been
    experiencing
    some
    other problems with the web logic deployment. For instance, aftera
    number
    of
    redeployments, the application throwth OutOfMemoryException (about
    10
    deployments
    MAX).
    Internally we've been discussing what's the best way of deployingthe
    ear application
    into the weblogic -- using java deploy tool, or using hot deployby
    just
    dropping
    the app in a particular bea folder.
    Is there a prefered/recommended way of deployment?
    If not, what people have found to be the most stable way of
    deploying?
    >>>>>>
    Please help!
    P.S. I'm little dissappointed, isn't bea an industry leader? Isn'tit
    supposed
    to take all these little issues away from the developpers so theycan
    concentrate
    on solving the business problems? It has not been the case for usso
    far. BTW
    -- JBOSS just works.
    "Dmitry" <[email protected]> wrote:
    I'm having this strange problem, my application is deployed with
    java.Deployer
    tool, works fine, then when ever i reboot the weblogic server,
    the
    application
    is not accessible untill i explicitly redeploy it again.
    Please help!

  • Could not deploy policy for resource: type= url , application=MySecurex,

    Hi
    My situation :
    I have 2 managed weblogic portal 10.3.0 managed servers in a cluster and 1 admin server. All are running as a service.
    Deployments of new versions of applications are submitted by an automated script.
    The steps in the script are :
    - stop the services of the managed servers
    - undeploy the previous version by using ant task
    <target name="undeploy_old" description="undeploy old application" depends="downloadFiles">
                   <java classname="weblogic.Deployer" output="./temp/${buildProject}_${deployEnv}/${buildVersion}/undeploy.txt" fork="yes">
                        <arg value="-adminurl" /> <arg value="${adminurl}" />
                        <arg value="-username" /> <arg value="${weblogic_user}" />
                        <arg value="-password" /> <arg value="${weblogic_pwd}" />
                        <arg value="-undeploy" />
                        <arg value="-name" />
                        <arg value="${buildProject}" />
                        <arg value="-verbose" />
                        <classpath refid="project.class.path"/>
                   </java>     - deploy the new version by using ant task
         <java classname="weblogic.Deployer"
                   output="./temp/${buildProject}_${deployEnv}/${buildVersion}/deploy.txt"
                   fork="yes"
                   maxmemory="512m"
                   inputstring="" >
             <arg value="-adminurl" /> <arg value="${adminurl}" />
             <arg value="-username" /> <arg value="${weblogic_user}" />
             <arg value="-password" /> <arg value="${weblogic_pwd}" />
             <arg value="-stage" />
             <arg value="-verbose" />
              <arg value="-upload" />
             <arg value="-deploy" />
             <arg value="-name" /> <arg value="${buildProject}" />
             <arg value="-source" /> <arg value="./temp/${buildProject}_${deployEnv}/${buildVersion}/${buildProject}.ear" />
             <arg value="-targets" /> <arg value="${deploytargetinstances}" />
              <classpath refid="project.class.path"/>
         </java>- start the services of the managed servers
    Problem:
    When the managed servers are restarting and the new version is going to prepared status, an error occurs for the new version of the application :
    ####<27-dec-2011 13.42 u. CET> <Info> <Deployer> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758076> <BEA-149059> <Module MySecurexEarAdmin of application MySecurex is transitioning from STATE_NEW to STATE_PREPARED on server s40beaportacc1p9106.>
    ####<27-dec-2011 13.42 u. CET> <Error> <Security> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-090064> <The DeployableAuthorizer "myrealm_weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl" returned an error: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.>
    ####<27-dec-2011 13.42 u. CET> <Error> <HTTP> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-101199> <Could not deploy policy for resource: type=<url>, application=MySecurex, contextPath=/MySecurexEarAdmin, uri=/campaigns/emails/*.
    weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
         at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.deployPolicy(PolicyDeploymentServiceImpl.java:173)
         at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.deployPolicy(Unknown Source)
         at weblogic.security.service.AuthorizationManager$HandlerAdaptor.deployPolicy(Unknown Source)
         at weblogic.security.service.AuthorizationManager.deployPolicy(Unknown Source)
         at weblogic.servlet.security.internal.ResourceConstraint.deploy(ResourceConstraint.java:108)
         at weblogic.servlet.security.internal.WebAppSecurityWLS.deployPolicies(WebAppSecurityWLS.java:253)
         at weblogic.servlet.security.internal.WebAppSecurity.registerSecurityConstraints(WebAppSecurity.java:140)
         at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:1189)
         at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1121)
         at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:449)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:424)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:119)
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:162)
         at weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl.deployPolicy(XACMLAuthorizationProviderImpl.java:281)
    weblogic.management.utils.CreateException:
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:241)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
         at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:112)
    com.bea.security.xacml.PolicyStoreException: <openjpa-1.1.0-r422266:657916 fatal store error> kodo.jdo.FatalDataStoreException: The transaction has been rolled back.  See the nested exceptions for details on the errors that occurred.
         at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:684)
         at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:576)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:222)
         at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
    <openjpa-1.1.0-r422266:657916 nonfatal store error> kodo.jdo.ObjectNotFoundException: The instance "netscape.ldap.LDAPException: error result (32)" does not exist in the data store.
    FailedObject: netscape.ldap.LDAPException: error result (32)
         at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:370)
         at org.apache.openjpa.abstractstore.AbstractStoreManager.flush(AbstractStoreManager.java:277)
         at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
         at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:554)
         at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
         at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2007)
    ....>
    My workaround:
    Delete the <domain>\servers\s40beaportacc1p9106\data\ldap directory on the managed servers and restart
    Does anyone knows what causes the error and how to solve it?
    The goal is to be able to deploy our application by automation.

    You must use not the original bean that you coded. You must use the bean generated by axis-wsdl2java.
    The bean generated by axis-wsdl2java is:
    - in the first beanMapping: MSPCSService.SMSMO
    - in the second beanMapping: MSPCSService.SMSMOResponse
    As you can see, the bean the axis-wsdl2java will generate is build with the namespace + "." + qname. If you use an domain like java.sun.com in namespace, then the package name you will use is inverted (in the sample, com.sun.java). Look at the code generated.
    You client must use this beans, not the original coded by you.
    This must work, worked for me :)

  • Deployment and application do not have matching security zones

    Hello community,
     I have developed an application in VSExpress 2013 (Win 8.1)) and I'm trying to deply using ClickOnce. I have set the options to:
     1) Sign the ClickOnce manifests (checked)
     2) Sign the assembly (checked)
     3) On the security tab: "Enable ClickOnce security settings "(checked) and "This is a full trust application" selected
      4) On the "Publish" tab: "The application is available offline as well..." Selected
    The qeustion is that, when I publish the application based on this settings and run the "Setup.exe" on a Windows 7 machine I have the exception: "Deployment
    and application do not have matching security zones"
    Any idea on how to solve this?
    Below is the error log:
    ERROR DETAILS
            Following errors were detected during this operation.
            * [28-02-2015 14:52:30] System.Deployment.Application.InvalidDeploymentException (Zone)
                    - Deployment and application do not have matching security zones.
                    - Source: System.Deployment
                    - Stack trace:
                            at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest
    deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
                            at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest
    deploymentManifest, String targetDir, Uri deploymentUri, Uri& appSourceUri, String& appManifestPath)
                            at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState
    subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
                            at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState&
    subState, ActivationDescription actDesc)
                            at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri
    activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
                            at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
    state)
    COMPONENT STORE TRANSACTION DETAILS
            No transaction information is available.

    Hello,
    To clarify this issue, I would confirm with you the following tips.
    >> 2) Sign the assembly (checked)
    1. If you select the pfx file which is generated by Visual Studio for "Choose a strong name key file",
    will it has the same result?
    2. Where did you published your project? Local folder ,web server or any other?
    3. If you create a simple sample with the same stesps, will it has the same issue? If so, you could share that sample with us.
    Regards,
    Carl
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • FYI - EPMA not deploying members/hierarchies to downstream Applications

    I had encountered this problem last week and recently found the issue. In EPMA for 11.1.1.3 (and other versions Im sure) you can have a hierarchy validate, but when you deploy the application - either entire hierarchies or certain members may not actually be deployed, even if the cubes said they were in synch. I had tried everything from copying the dimension and disassociating/reassociating, validating, to deleting and rebuilding the dimensions via ADS file...
    Essentially what was happening was that during the initial creation of these dimensions via ADS file, each propery is case sensitive. There were entire files (or some members in a file) using 'storedata' instead of 'StoreData', etc... The load of the ADS file will be successful - as will the deployment. Only when you do a hierarchy comparison or examining the dimension stats will you notice that the members were not deployed. There were numerous dimensions with 1 member (the dimension name itself).
    Anyways... I figured that others would run into this and wanted to make sure no one else felt my misery :)
    Make sure you have all of the proper cases in your ADS Files!
    -Matt

    I had encountered this problem last week and recently found the issue. In EPMA for 11.1.1.3 (and other versions Im sure) you can have a hierarchy validate, but when you deploy the application - either entire hierarchies or certain members may not actually be deployed, even if the cubes said they were in synch. I had tried everything from copying the dimension and disassociating/reassociating, validating, to deleting and rebuilding the dimensions via ADS file...
    Essentially what was happening was that during the initial creation of these dimensions via ADS file, each propery is case sensitive. There were entire files (or some members in a file) using 'storedata' instead of 'StoreData', etc... The load of the ADS file will be successful - as will the deployment. Only when you do a hierarchy comparison or examining the dimension stats will you notice that the members were not deployed. There were numerous dimensions with 1 member (the dimension name itself).
    Anyways... I figured that others would run into this and wanted to make sure no one else felt my misery :)
    Make sure you have all of the proper cases in your ADS Files!
    -Matt

Maybe you are looking for

  • 10.6.8 Fine on one account, freezes on other?! Need help please!

    Hi, I have 10.6.8 installed on one account on my hard drive and 10.6.8 installed on the other, and on one acccount, it boots up just fine -- on the other, it locks up at desktop about 5 seconds after my wallpaper have loaded. I can still move the mou

  • Adding a server into a failover cluster

    Hi all, i have the following question: i have a Failover Cluster with 3 servers and now i have to add another server. The cluster is in a pruction environment and the service cant be cut off during working hours. Adding this new server will cut off t

  • Styling rule question in mapbuilder

    To define query in Styling Rules, can I join spatila data table with another non-spatial data table by non-spatial column? If yes, can you give me any link? Thanks

  • Message timestamps missing in latest version

    I have "Show timestamp next to instant messages" checked in my IM appearance options but there are no timestamps showing in the new chat bubble version of Skype. How do I get my timestamps back? Solved! Go to Solution.

  • CRM ORG Model Setup

    Hi Gurus, We have setup the Org Model in sync with R/3 in our Dev Client. CRM => O 050000001 /20/00 (Sales Org/ Distribution Channel/ Division) Corresponding R/3=> USAO/20/00 (Sales Org/ DChannel/ Division) How do we transport it to Quality Client of