WLS 8.0 SP5 JDBC deploy error

Heya,
I'm upgrading our servers from SP4 to SP5 and found that the application scoped JDBC Pool/Data Source to SQL Server 2000 in my EAR will no longer deploy. I'm using the ant task wldeploy and I tried using the Admin Console. I keep getting a NullPointerException. All worked fine under SP4, so has anyone else had this problem? I can post the error trace/weblogic-application.xml file if it'll help...
Thanks,
Anna

Anna Veirauchs wrote:
Thank you for your time.
The Admin Server log has the following:
####<Oct 26, 2005 3:37:24 PM PDT> <Warning> <RMI> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
     at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)Hi. At this point, I think official support should get involved.
Can you open a case with them? The exceptions aren't being generated
or at least reported from JDBC-related code, but if they can dig
more, it might end up in my court.
Joe
     at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149033> <failed application **** on ****>
####<Oct 26, 2005 3:37:25 PM PDT> <Info> <Management> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
####<Oct 26, 2005 3:37:25 PM PDT> <Warning> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Debug> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
================
The Managed Server log has:
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module JDBCDataSource of application **** is transitioning from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <JDBC> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-001155> <The following exception has occurred:
java.lang.NullPointerException
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
     at weblogic.management.internal.AdminMBeanHomeImpl_815_WLStub.getMBean(Unknown Source)
     at weblogic.jdbc.common.internal.JDBCDataSourceFactory.createDataSource(JDBCDataSourceFactory.java:74)
     at weblogic.jdbc.common.internal.JDBCModule.prepare(JDBCModule.java:140)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3149)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1590)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1234)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1077)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2530)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2480)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.lang.NullPointerException
     at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)
     at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     ... 2 more
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module JDBCDataSource of application **** failed to transition from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Error> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 3 for the application ****.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2413)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
====
My weblogic-application.xml is:
<!DOCTYPE weblogic-application PUBLIC '-//BEA Systems, Inc.//DTD WebLogic Application 8.1.0//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd'>
<weblogic-application>
     <jdbc-connection-pool>
          <data-source-name>JDBCDataSource</data-source-name>
          <connection-factory>
               <connection-properties>
                    <user-name>******</user-name>
                    <password>******</password>
                    <url>jdbc:bea:sqlserver://10.10.10.99\\MYINSTANCE</url>
                    <driver-class-name>weblogic.jdbc.sqlserver.SQLServerDriver</driver-class-name>
                    <connection-params>
                         <parameter>
                              <param-name>databaseName</param-name>
                              <param-value>****</param-value>
                         </parameter>
                    </connection-params>
               </connection-properties>
          </connection-factory>
<pool-params>
<size-params>
<initial-capacity>10</initial-capacity>
<max-capacity>10</max-capacity>
<capacity-increment>2</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>300</shrink-frequency-seconds>
<highest-num-waiters>100</highest-num-waiters>
<highest-num-unavailable>4</highest-num-unavailable>
</size-params>
<login-delay-seconds>1</login-delay-seconds>
<leak-profiling-enabled>false</leak-profiling-enabled>
<connection-check-params>
<table-name>SQL SELECT COUNT(*) FROM sysobjects</table-name>
<check-on-reserve-enabled>true</check-on-reserve-enabled>
<check-on-release-enabled>false</check-on-release-enabled>
<check-on-create-enabled>false</check-on-create-enabled>
<connection-reserve-timeout-seconds>30</connection-reserve-timeout-seconds>
<connection-creation-retry-frequency-seconds>360
</connection-creation-retry-frequency-seconds>
<inactive-connection-timeout-seconds>360
</inactive-connection-timeout-seconds>
<test-frequency-seconds>600</test-frequency-seconds>
</connection-check-params>
</pool-params>
<driver-params>
<prepared-statement>
<cache-size>10</cache-size>
<cache-type>LRU</cache-type>
</prepared-statement>
<row-prefetch-enabled>true</row-prefetch-enabled>
<row-prefetch-size>500</row-prefetch-size>
<stream-chunk-size>1024</stream-chunk-size>
</driver-params>
     </jdbc-connection-pool>
</weblogic-application>

Similar Messages

  • Wls 8.1 sp5 - cannot deploy exploded archive anymore

    Hi all,
    I used to deploy exploded archive in development mode with wls 8.1 sp4. When browsing the file system, the console used to show a radio button to the left of folders which contained an exploded war.
    Since I replace 8.1 sp4 with 8.1 sp5, this radio button does not appear anymore along folders that contain exploded war.
    Is this a known issue ? Anyone reproduced the same behaviour ?
    Thanks for letting me know of any workaround as this feature is really handy ...
    Kind regards,
    Regis

    Dear Prasanth,
    You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
    Thanks for your help!
    javax.servlet.jsp.JspException: Cannot find FacesContext
         at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
         at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)

  • Migrating from WLS 8.1 SP5 to Sp6

    We have successfully runned WLS 8.1 SP5
    When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
    l edxUserConnectionPool has already been referenced by the another TxDataSource.>
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
    dxUserConnectionPool has already been referenced by the another TxDataSource.>
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
    dxUserConnectionPool has already been referenced by the another TxDataSource.>
    All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?

    Anton Gavazuk wrote:
    We have successfully runned WLS 8.1 SP5
    When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
    l edxUserConnectionPool has already been referenced by the another TxDataSource.>
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
    dxUserConnectionPool has already been referenced by the another TxDataSource.>
    <Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
    dxUserConnectionPool has already been referenced by the another TxDataSource.>
    All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?Hi. This is a known issue with 81sp6. Ask support for the patch
    for CR308071. We document that it is forbidden to have multiple
    XA datasources pointing to the same pool, and we now enforce that,
    but the bug is that we were also preventing mulitple datasources
    to non-XA pools as well.
    Joe

  • Deployment error while deploying targeters in BCC

    Hi,
    I am trying to create a targeter with content groups and media internal texts. Whenever i deploy a project with these assets, i get deployment error.
    It says "Deployment '169200010' to target 'production' encountered a system level deployment error during data transfer. An automatic rollback deployment has successfully occurred, preserving the state of target 'production'. Click 'Resume' to re-attempt the deployment."
    I checked for the VFS set up for targeters and content groups and they are in place.
    There are 3 assets in the project. It says the asset already exists
    The error log below : I am struck up here and not able to take any step further. Please share your inputs on this
    2013-06-20 22:40:25,569 WARN  [nucleusNamespace.atg.epub.PublishingRepository] (http-172.19.0.197-40180-6) Using default JDBC type for: project:tar82 could not find this column in the table's meta data
    2013-06-20 22:40:51,348 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Run first apply phase: true
    2013-06-20 22:40:51,349 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Switch switchable CA datasources:
    2013-06-20 22:40:51,349 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   isDeploymentRollback(): false
    2013-06-20 22:40:51,360 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   Current Target live datasource name: DataSourceB
    2013-06-20 22:40:51,360 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   CA switching datasource: /atg/commerce/jdbc/ProductCatalogSwitchingDataSource_production
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     Current live datasource name: DataSourceA
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     Current offline datasource name: DataSourceB
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     The current CA live datasource is pointing at the Target offline datasource. No CA switch necessary.
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Switchable CA datasources switched.
    2013-06-20 22:40:51,408 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:DAF Deployment with ID: 169200010 not previously deployed.
    2013-06-20 22:40:51,414 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Creating standard DeploymentData
    2013-06-20 22:40:51,446 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Forward deploying following active workspaces: [workspace:118102]
    2013-06-20 22:40:53,770 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Deploy Data
    2013-06-20 22:40:53,771 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Starting DAF deployment with ID: 169200010
    2013-06-20 22:40:53,776 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Thread-103) Database: Oracle
    2013-06-20 22:40:53,922 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Polling Until Data Appplied
    2013-06-20 22:40:53,922 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Starting deployment with id: 169200010
    2013-06-20 22:40:53,950 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Executing deployment in LOCAL mode
    2013-06-20 22:40:55,442 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,461 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400001 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@17dc0e19
    2013-06-20 22:40:55,490 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,490 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400002 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@38d281d4
    2013-06-20 22:40:55,547 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,547 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400003 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@70126ca0
    2013-06-20 22:40:55,684 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleErrorLogging(FileWorkerThread.java:1261)
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1276)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 6 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
    2013-06-20 22:40:55,685 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400004 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@1f344a25
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 5 more
    SOURCE EXCEPTION:

    yes i checked. To clear this out, i created a new project with new set of content groups and targeters.
    It throws this error. I get this error at 30% of deployment
    2013-06-21 12:04:07,944 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Thread-124) Database: Oracle
    2013-06-21 12:04:07,959 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-124) DEBUG DistributedDeploymentAdapter:Polling Until Data Appplied
    2013-06-21 12:04:07,959 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Starting deployment with id: 135200010
    2013-06-21 12:04:07,970 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Executing deployment in LOCAL mode
    2013-06-21 12:04:09,708 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleErrorLogging(FileWorkerThread.java:1261)
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1276)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 6 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
    2013-06-21 12:04:09,715 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))  item = fileMarker:mark115500048 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null time = Fri Jun 21 12:04:09 CDT 2013  atg.deployment.DeploymentFailure@7bbc32e1
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 5 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
    2013-06-21 12:04:09,741 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))  item = fileMarker:mark115500048 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.

  • Deployment Error - failed to load deployment descriptor

    I'm getting the following error when I try to deploy an ear file for my application. I am able to successfully deploy the associated war and ejb jar files as separate modules, but when I try to deploy the application as an ear I get the error:
    Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler --
    -- Failed to load deployment descriptor for: pta
    cause: I/O error while reading web xml into object representation

    What was the solution for this problem?
    Because I have the same error and I tried 920 and 910 100 doe not seem to exist.
    I am using WLS 10.
    Help would be appreciated.
    Thanks

  • Deployment error in .ear in portal project

    After starting admin server in workshop for weblogic, I am trying to publish the .ear portal project.
    But its giving the following error,
    weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
    Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    Exception Stack Trace:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1557)
    at com.bea.workshop.wls.core.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:469)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1329)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:787)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:607)
    at com.bea.workshop.wls.core.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:503)
    at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
    at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
    at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: ProxyPagePersistenceManager from netuix.jar:
    Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
    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.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    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.ejb20.interfaces.PrincipalNotFoundException: Exception while attempting to deploy Security Policy: weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
    at weblogic.ejb.container.internal.SecurityHelperWLS.deployPolicy(SecurityHelperWLS.java:357)
    at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:306)
    at weblogic.ejb.container.internal.SecurityHelper.deployPolicy(SecurityHelper.java:294)
    at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:249)
    at weblogic.ejb.container.internal.SecurityHelper.deployAllPolicies(SecurityHelper.java:228)
    at weblogic.ejb.container.internal.RuntimeHelper.deployAllPolicies(RuntimeHelper.java:249)
    at weblogic.ejb.container.deployer.EJBDeployer.deployAllPolicies(EJBDeployer.java:770)
    at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:934)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
    FYI, I am using Oracle Weblogic server v10.3 and pointbase DB.

    I was unable to resolve it....!!
    Just found a workaround...I didnt' used a EAR after that....
    But still this SAP note could help u out.....!!
    Deployement error in EAR DC
    Required note is :
    SAP Note Number: 1270242
    "None of the available containers recognized the components"

  • Deployment error in SUP 2.2

    Hi
    I'm trying to deploy MBO project with SAP as backend, below is the error which comes up
    An error occurred deploying package, .pkg to server, trincula (Exception: Deploy error:
    runtime_error:
      ----Unknown error in server runtime: loader constraint violation: when resolving method "com.sybase.afx.jdbc.DataSourceInfo.setDataSource(Ljavax/sql/DataSource;)V" the class loader (instance of com/sybase/djc/util/NamedClassLoader_DJC) of the current class, FlightBooking/server/FlightBookingDB, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/sybase/afx/jdbc/DataSourceInfo, have different Class objects for the type javax/sql/DataSource used in the signature
    Please give some inputs.

    Following is the error which came up on verify
    varify_failed:
      ----Verify failed for deployment with mode VERIFY.
    ds_deploy_error:
      ----DataService deployment error: Operations Conflict in MBO "Booking" different nodes
    ds_deploy_error:
      ----DataService deployment error: Operations Conflict in MBO "Flight" different nodes
    What I changed is the Operation Type in Booking and Flight MBO.
    I had two operation in Booking 'confirm' and 'cancel' having operation type 'CREATE'. So I changed 'cancel' to 'UPDATE'. Same I did for Fight MBO.
    Its deploying successfully now but just to get to root cause of this. Is it related to the elements which I chosen for creating that operation has resulted in conflict??

  • A jdbc transaction error occur

    Hi Everybody
    A jdbc transaction error occur when I deploy the application on the server .
    Below is the stack trace
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot initiate transaction from a connection of "YTSQLS2K" DataSource. Local or distributed transaction has already started.
    #SAP J2EE Engine JTA Transaction : [03bfffffffd3a000ffffffc0]####Application [13]##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit transaction from this connection of "YTSQLS2K" DataSource. This resource participates in a local or distributed transaction.
    Any idea about it
    I use the jdbc version in datasource <jdbc-1.x>
    is there a need to replace it with <jdbc-2.0>
    Thank You
    Syed Saifuddin

    Hibernate allows you to choose transaction manager. As Nikolay pointed out, in a JEE envirnment it's prefferable to use JTA transactions. All you need to do is to configure hibernate to use a JTA transaction manager. It is all written in the Hibernate documentations. See
    http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#configuration-j2ee
    and
    http://www.hibernate.org/42.html#A5 .
    The relevant properties that need to be set in the configuration are:
    hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
    and
    hibernate.transaction.manager_lookup_class=<Class that knows how to lookup>
    You need to implement a class that knows how to lookup user transaction in SAP J2EE Egnine.
    The class must extend org.hibernate.transaction.JNDITransactionManagerLookup and only override its abstract method getName (simply returning the lookup string). Then provide the fully qualified name as value of the property and make sure that Hibernate can load the class.
    That should work.
    HTH
    -Georgi
    Message was edited by:
            Georgi Pavlov

  • Deployment Error as Enterprise application in Sun Application server 7

    Hi folks,
    I am tring to deploy some jdbc application in Sun Application server 7
    While deployment of jdbc-simple.ear as Enterprise application, I get following error.
    ==============================================================
    Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- -- Compilation failed: com.iplanet.ias.ejb.codegen.ProcessExecutorException: Abnormal process termination -- process returned: 11 Attempted command: $HOME/appserver7/studio4/bin/fastjavac/fastjavac.sun -jdk $HOME/appserver7/jdk -g -d $HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple -classpath $HOME/appserver7/lib/appserv-rt.jar:$HOME/appserver7/jdk/lib/tools.jar:$HOME/appserver7/lib/appserv-ext.jar:$HOME/appserver7/lib/appserv-cmp.jar:$HOME/appserver7/imq/lib/imq.jar:$HOME/appserver7/imq/lib/imqadmin.jar:$HOME/appserver7/imq/lib/imqutil.jar:$HOME/appserver7/lib/appserv-admin.jar:$HOME/appserver7/lib/appserv-ideplugin.jar::.:$HOME/lib/common/servlet.jar:/usr/java/lib/tools.jar:$HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple:$HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple:$HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple $HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple/samples/jdbc/simple/ejb/GreeterDBBean_RemoteHomeImpl.java $HOME/appserver7/domains/domain1/server1/generated/ejb/j2ee-apps/jdbc-simple/samples/jdbc/simple/ejb/GreeterDBBean_EJBObjectImpl.java Output from command:
    ==============================================================
    Any help would be appreciated.

    Hi Vchavan,
    can you see the that actual compilation problem in server.log?
    Thanks,
    -- markus.

  • ADF: Gracefully handling JDBC connection errors?  Part II

    Hi gang
    I while back I posted a forum post to find a solution to "display a specific web page when the JDBC connection drops out on our ADF application, specifically the following error: oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection"
    ...you can see the original post here:
    Re: ADF: Gracefully handling JDBC connection errors?
    For the life of me I can't get this to work now. It appears I can't redirect to another page during the call to reportException. I've had a play with different methods of redirecting, as seen in the following code sample:
    public class ErrorHandlerImpl extends DCErrorHandlerImpl {
      public ErrorHandlerImpl() {
        super(true);
      @Override
      public void reportException(DCBindingContainer dCBindingContainer, Exception exception) {
    //    try {
          String message = exception.getMessage();
          if (message.indexOf("JBO-26061") >= 0) {
            // Method 1
            FacesContext fc = FacesContext.getCurrentInstance();
            UIViewRoot viewRoot =
            fc.getApplication().getViewHandler().createView(fc, "faces/errorPage.jspx");
            fc.setViewRoot(viewRoot);
            fc.renderResponse();
            // Method 2              
            // FacesContext fc = FacesContext.getCurrentInstance();
            // fc.getApplication().getNavigationHandler().handleNavigation(fc, null, "goError");
            // fc.responseComplete();
            // Method 3 - required IOExcepition handler
            // FacesContext.getCurrentInstance().getExternalContext().redirect("faces/errorPage.jspx");
          } else
              super.reportException(dCBindingContainer, exception);
    //    } catch (IOException e) {
    }... with no success.
    Has anyobody any other solutions or advice on getting this to work?
    Your help appreciated.
    Thanks & regads,
    CM.
    PS. JDev 11gR1 ADF BC + ADF Faces RC

    Hi Frank
    Yep, I' tried redirect, that was method 3 (you can see all 3 methods I've attempted, last 2 are commented out).
    With the declarative ADFc exception handler, problem is it's a catch all, not specifically for JBO-26061. Can you think of a way I can tailor fit it for JBO-26061 with a custom message "Database down"?
    In addition the exception handler is not consistently called. As example, if you're moving between pages rather than operating on 1 page, the standard af:messages error dialog is shown if the db connection has been dropped, rather than navigating to the exception handler page. As such it seems the DCErrorHandlerImpl.reportExceptions is the better chokepoint to work from.
    Cheers,
    CM.

  • 10.1.3 HumanTask Forms deployment error is it a BUG

    Hi,
    Any one I am getting the following error. I have installed SOA 10.1.3 Midtier and am using OID as security provider. Now I am trying DocumentReview Sample but am getting the following error:
    Buildfile: C:\Oracle_Software\1013\soa\bpel\samples\demos\DocumentReview\build.xml
    validateTask:
    [echo]
    | Validating workflow
    [validateTask] url is file:/C:/Oracle_Software/jdevstudio10132/integration/bpm/support/files/WorkflowTaskDefinition.xsd
    [validateTask] Validation of workflow task definitions is completed without errors
    deployProcess:
    [echo]
    | Deploying bpel process DocumentReview on localhost, port 7779
    [deployProcess] Deploying process C:\Oracle_Software\1013\soa\bpel\samples\demos\DocumentReview\output\bpel_DocumentReview_1.0.jar
    [deployProcess] Successfully deployed the process "DocumentReview" on server "localhost" and port "7779"
    deployTaskForm:
    [echo]
    | Deploying workflow form for DocumentReview on localhost, port 7779
    [deployTaskForm] 07/07/07 08:25:19 Notification ==>Application Deployer for default_DocumentReview_1_0_DocumentReview STARTS.
    [deployTaskForm]
    [deployTaskForm] 07/07/07 08:25:19 Notification ==>Operation failed with error:
    [deployTaskForm] parent application (orabpel) is not found!
    [deployTaskForm]
    [deployTaskForm]
    [deployTaskForm]
    [deployTaskForm] Deploy error: Deploy error: Operation failed with error:
    [deployTaskForm] parent application (orabpel) is not found!
    [deployTaskForm]
    [deployTaskForm]
    BUILD FAILED
    C:\Oracle_Software\1013\soa\bpel\samples\demos\DocumentReview\build.xml:98: Error while deploying the form on server "localhost" Error message :
    java.lang.SecurityException
         at oracle.ide.IdeCore$7.checkExit(IdeCore.java:177)
         at java.lang.Runtime.exit(Runtime.java:88)
         at java.lang.System.exit(System.java:868)
         at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.executeCommand(Oc4jAdminCmdline.java:127)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployIAS(DeployForm.java:750)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:548)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:814)
         at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:840)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
         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:585)
         at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
         at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
         at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
    Total time: 45 seconds
    Thanks for any feedbacks.

    Hi HEWizard,
    I have set the ORACLE_HOME that points to SOA install directory i.e.
    C:\Documents and Settings>echo %ORACLE_HOME%
    C:\Oracle_Software\1013\soa
    One more thing is that if I install the Developer Version and even though the ORACLE_HOME is not set this works fine i.e. DocumentReview it's only that in the Midtier install version it doesn't work.
    The BPELProcess gets deployed and even the task is assigned but when logging into worklist and selecting the task I see the following error:
    Not Found
    The requested URL /default/DocumentReview/1.0/DocumentReview/DocumentReview.jsp was not found on this server.
    Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server Server at localhost Port 7779
    It's because at deployment time I get that security error and parent application not found and it never deploys the jsp's. Now in the logs I don't see anything. It's only in JDeveloper I see those errors at deployment time. Here is the domain.log:
    <2007-07-07 18:22:44,500> <INFO> <default.collaxa.cube> <ServerManager::loadDomain>
    Oracle BPEL Server version 10.1.3.1.0
    Build: 0
    Build time: Mon Oct 09 08:44:49 PDT 2006
    Build type: release
    Source tag: PCBPEL_10.1.3.1.0_GENERIC_061009.0802
    <2007-07-07 18:22:45,140> <INFO> <default.collaxa.cube.engine> <CubeEngine::load>
    Initializing BPEL domain from descriptor file
    "C:\Oracle_Software\1013\soa\bpel\domains\default\config\domain.xml"
    <2007-07-07 18:22:45,406> <INFO> <default.collaxa.cube.engine> <gsDomainSchemaManager::validateCompatibility> Detected database version '2.0.51'
    <2007-07-07 18:22:45,406> <INFO> <default.collaxa.cube.engine> <AdaptorManager::load> Loaded adaptors for platform 'ias_10g', datasource 'oracle'
    <2007-07-07 18:22:47,656> <INFO> <default.collaxa.cube.engine> <AdapterStats::init:Done initializing Adapter statistics holder for engine > default
    <2007-07-07 18:22:47,656> <INFO> <default.collaxa.cube.engine> <CubeEngine::init>
    OraBPEL "default" BPEL domain loaded.
    <2007-07-07 18:22:53,046> <INFO> <default.collaxa.cube.engine> <CubeEngine::loadAllProcesses>
    Loading processes for BPEL domain "default" ...
    <2007-07-07 18:22:55,500> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskManager" (revision "1.0") successfully loaded.
    <2007-07-07 18:22:57,234> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskActionHandler" (revision "1.0") successfully loaded.
    <2007-07-07 18:22:57,953> <INFO> <default.collaxa.cube.engine.deployment> Process "DocumentReview" (revision "1.0") successfully loaded.
    <2007-07-07 18:22:58,000> <INFO> <default.collaxa.cube.engine> <CubeEngine::loadAllProcesses>
    3 processes have been loaded for BPEL domain "default".
    <2007-07-07 18:23:33,062> <INFO> <default.collaxa.cube.services> <QuartzPublisherInit::init> Notification Retry publisher scheduled at every 15 minute(s)
    <2007-07-07 18:26:23,500> <INFO> <default.collaxa.cube.compiler> validating "C:\Oracle_Software\1013\soa\bpel\domains\default\tmp\.bpel_DocumentReview_1.0_e61483a0d5e873d381ae6bfbeaed5c60.tmp\DocumentReview.bpel" ...
    <2007-07-07 18:26:30,671> <INFO> <default.collaxa.cube.engine.deployment> <CubeProcessFactory::generateProcessClass>
    Process "DocumentReview" (revision "1.0") successfully compiled.
    <2007-07-07 18:26:30,750> <INFO> <default.collaxa.cube.engine.deployment> Process "DocumentReview" (revision "1.0") successfully loaded.
    Now even though the log says process deployed successfully it only deploys the BPEL Process but no jsp forms deployed. I hope there's nothing special we have to do. This issue can be recreated by installing the Midtier version of SOA and configure it with OID and then try deploying DocumentReview Process provided in the demos.
    I hope I have provided all the information.
    Thanks and waiting for a feedback as we have to decide on whether we go using BPEL 10.1.3 and this is a critical piece of it.

  • Deployment error while running the application

    Hi Every body,
    I am new to JEE though an old pro at JDK.I have also worked on tomcat.
    I have got Sun Java System Application Server 9.1 installed with NetBeans 6.1 on winXP.
    I am trying to create a EJB app-client module.I even tried to run the sample application AnnotationOverrideInterceptor given in NetBeans . Every thing goes fine.The Build is also Successful but when i run it, i recieve the error message Deployment error .The module has not been deployed.
    See the server log for details.
    I am posting a part of server log stack.:
    Application server startup complete.
    [AutoDeploy] Selecting file C:\Program Files\glassfish-v2-b53\domains\domain1\autodeploy\amserver.war for autodeployment.
    Initializing Sun's JavaServer Faces implementation (1.2_04-b19-p03) for context ''
    javax.ejb.EJB.description()Ljava/lang/String;
    Exception occured in J2EEC Phasejava.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [AnnotationOverrideInterceptor] -- javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388)
    at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
    at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
    at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
    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:905)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774)
    at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187)
    at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
    Caused by: java.lang.IllegalStateException: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
    at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:363)
    at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:318)
    at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:213)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readModulesDescriptors(ApplicationArchivist.java:321)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.open(ApplicationArchivist.java:238)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:763)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
    ... 10 more
    Caused by: javax.ejb.EJB.description()Ljava/lang/String;at com.sun.enterprise.deployment.annotation.AnnotationInfo@49bed2
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:360)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:368)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:282)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:264)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:192)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:129)
    at com.sun.enterprise.deployment.archivist.Archivist.processAnnotations(Archivist.java:445)
    at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:346)
    ... 17 more
    Caused by: java.lang.NoSuchMethodError: javax.ejb.EJB.description()Ljava/lang/String;
    at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processNewEJBAnnotation(EJBHandler.java:276)
    at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processEJB(EJBHandler.java:143)
    at com.sun.enterprise.deployment.annotation.handlers.EJBHandler.processAnnotation(EJBHandler.java:98)
    at com.sun.enterprise.deployment.annotation.handlers.AbstractResourceHandler.processAnnotation(AbstractResourceHandler.java:119)
    at com.sun.enterprise.deployment.annotation.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:337)
    ... 24 more
    Please help as i am trying the google and many other to find solution but i am unable to move forward.I am stuck up at this for last 15 days.It is very frustrating.
    I haven't posted the full log as it is very long.I can post the entire server log, if asked for.
    Please help
    yoodleyee

    Hi jwenting,
    Thanks alot for replying.
    But i am still unable to come out of the mess.Here is the program i am using please help me find out the error.
    Here we go:
    package hello;
    import javax.ejb.Stateless;
    @Stateless
    public class HelloBean implements HelloRemote {
    private String name="Yoodleyee";
    public String sayHello() {
    //return null;
    return "My Name is "+name;
    // Add business logic below. (Right-click in editor and choose
    // "EJB Methods > Add Business Method" or "Web Service > Add Operation")
    package hello;
    import javax.ejb.Remote;
    @Remote
    public interface HelloRemote {
    String sayHello();
    In the Hello-app-client module i have main()==>>
    package hello;
    import javax.ejb.EJB;
    public class Main {
    @EJB
    private static HelloRemote helloBean;
    * @param args the command line arguments
    public static void main(String[] args) {
    // TODO code application logic here
    System.out.println("Hi "+helloBean.sayHello());
    since this program does not require deployment descriptor and also NetBean creates its own deployment discriptor hence i have not written any.
    Please tell me where and waht i should change.Also tell me is diployment descriptor necessary.
    Awaiting for the reply.
    yoodleyee

  • Deployment Error in NWDS 7.2

    Hi All,
    My server and NWDS are on same patch level. Once i am trying to deploy a simple scenario, i am getting below deployment error.
    Status ERROR
    Plugin : com.sap.ide.tools.services
    code=0
    Deployment problems
    children=[
    Status ERROR
    Plugin : com.sap.ide.tools.services
    code=0
    Deploy Exception.
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [demo.sap.com_dc_my_name_age].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
    at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:178)
    at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:92)
    at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:236)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Nested exceptions :com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [demo.sap.com_dc_my_name_age].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:244)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_dc_my_name_age]. Cannot deploy it.
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:134)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Error while deploying ear file /usr/sap/BPD/J03/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/135/demo.sap.com~dc_my_name_age.sda; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: TxException
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4443)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:353)
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :com.sap.engine.services.deploy.container.DeploymentException: TxException
    atcom.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
    atcom.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
    atcom.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:273)
    atcom.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:577)
    atcom.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:297)
    atcom.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:211)
    atcom.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:697)
    atcom.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2238)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:401)
    atcom.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:351)
    atcom.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
    atcom.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
    atcom.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    atcom.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
    atcom.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    atcom.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
    atcom.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    atcom.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    atcom.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Nested exceptions :java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
         at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:587)
         at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
         at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
         at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
         at
    Please help me .
    Thanks
    Vidhi

    HI ,
    I am able to over deployment problem. It was due to some error in code of view i created. because of that, it was giving deployment error.
    Now, when i goto NWA->Configuration -> Process and Task -> Process Repository, I can see my deployed DC's. When i select my process and go to start process, Start Process button is blurred (means read only). Can you please help me on this?
    Thanks and Regards
    Vidhi

  • Deployment error in JDeveloper 11.1.1.4 when deploying 11.1.1.3 application

    We have built a bpm application using JDeveloper 11.1.1.3. Now we have upgraded the server to new version 11gR3 and have also upgraded our jdeveloper to 11.1.1.4.
    We have opened in Jdeveloper(11.1.1.4) the exisitng bpm application developed in older version (11.1.1.3) and when trying to deploy the application to the 11gR3 server getting the following deployment error in jdeveloper:      
    06:53:04 PM] Weblogic Server Exception: weblogic.application.ModuleException:
    [06:53:04 PM] Caused by: java.lang.ClassNotFoundException: oracle.bpel.services.datacontrol.types.Number
    [06:53:04 PM] See server logs or server console for more details.
    [06:53:04 PM] weblogic.application.ModuleException:
    [06:53:04 PM] Taskflow deployment failed to deploy to server. oracle.jdeveloper.deploy.DeployException: Remote deployment failed
    [06:53:04 PM] #### Deployment incomplete. ####
    [06:53:04 PM] Remote deployment failed
    This deployment error is happening only when the UI project is deployed along with the composite. When I open the Project Properties --> Library, I notice that a Library "ALE Component" is displayed in exclamation. Even after removing this library I am getting the same deployment error. Will be grateful if any help is suggested to this issue.

    Yes, you need to update the library reference apparently. (I just started again.)
    Try adding the following library ref to your weblogic.xml of UI project
    <library-ref> <library-name>oracle.soa.worklist.webapp</library-name> <specification-version>11.1.1</specification-version> </library-ref>
    Anthony

  • MYSQL Plug-in for Oracle grid deployment errors

    hello,
    having problems deploying the mysql plug-in. see error below....any ideas?
    this is the error in the emom.log
    2009-06-05 14:36:25,975 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
    2009-06-05 14:36:25,980 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.744 - XXXXXX name = mysql
    2009-06-05 14:36:25,983 [EMUI_14_36_25_/console/emx/deploy] ERROR em.emx exists.745 - XXXXXX version = 1.1
    2009-06-05 14:36:49,580 [Thread-278] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
    2009-06-05 14:36:49,590 [Thread-278] ERROR em.emx exists.744 - XXXXXX name = mysql
    2009-06-05 14:36:49,592 [Thread-278] ERROR em.emx exists.745 - XXXXXX version = 1.1
    2009-06-05 14:36:49,677 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
    2009-06-05 14:36:49,680 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.744 - XXXXXX name = mysql
    2009-06-05 14:36:49,681 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.745 - XXXXXX version = 1.1
    2009-06-05 14:36:51,636 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx runOperation.319 - RemoteOperationException: ERROR: NMO not setuid-root (Unix-only)
    java.io.IOException: RemoteOperationException: ERROR: NMO not setuid-root (Unix-only)
    at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.read(RemoteOperationInputStream.java:172)
    at oracle.sysman.emx.Util.pipe(Util.java:535)
    at oracle.sysman.emx.Util.pipeAndClose(Util.java:451)
    at oracle.sysman.emx.Util.pipeAndClose(Util.java:423)
    at oracle.sysman.emx.AgentFileHandler.runRemoteCommand(AgentFileHandler.java:563)
    at oracle.sysman.emx.AgentFileHandler.undeployFiles(AgentFileHandler.java:459)
    at oracle.sysman.emx.AgentFileHandler.runOperation(AgentFileHandler.java:256)
    at oracle.sysman.emx.AgentFileHandler.undeploy(AgentFileHandler.java:123)
    at oracle.sysman.emx.MPHandler.runOperation(MPHandler.java:165)
    at oracle.sysman.emx.MPHandler.undeploy(MPHandler.java:118)
    at oracle.sysman.emx.AgentDeployWorker.deployToAgent(AgentDeployWorker.java:121)
    at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:78)
    at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)
    2009-06-05 14:36:51,639 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.743 - XXXXXX sql = select mmp.target_type, mmp.mp_version, mmp.functional_description, mmp.requirements_description, mmp.hwm_status from mgmt_management_plugins mmp WHERE (mmp.target_type = ? AND mmp.mp_version = ?) AND mmp.hwm_status != ?
    2009-06-05 14:36:51,641 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.744 - XXXXXX name = mysql
    2009-06-05 14:36:51,643 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR em.emx exists.745 - XXXXXX version = 1.1
    2009-06-05 14:36:51,667 [ManagementPluginWorker(mysql:1.1,speck.lhsc.on.ca:3872)] ERROR threadPoolManager.WorkerThread run.281 - Exception message: null
    java.lang.Error
    at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:82)
    at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)
    2009-06-05 14:36:51,669 [Thread-279] ERROR em.emx workerDied.250 - java.lang.Error
    java.lang.Error
    at oracle.sysman.emx.AgentDeployWorker.run(AgentDeployWorker.java:82)
    at oracle.sysman.util.threadPoolManager.WorkerThread.run(Worker.java:260)

    See if this helps.
    After Installing DB Control, Getting RemoteOperationException.
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=824947.1

Maybe you are looking for

  • How to FaceTime and iMessage on multiple apple devices with one iTunes account

    We recently received iPad 2's for Christmas and was looking for some advice on how to FaceTime and iMessage on multiple apple devices with One iTunes Account (Apple Id).  I have created or attached other e-mail addresses to our apple id but do not kn

  • Cover Flow in iPad

    Hi friends, I am struck with the cover flow on iPad. The Code i m using was initially implemented for iphone, I tried to customize it but unable to do so. Please help in out. So is there anyone who who has implemented cover flow feature with iPad.

  • ALV-Header colour display

    hi i  need to display my header of alv in colour format... can u tell me function module what is used for this requirement..... advance thanks ........................urgent

  • Can't setup Tooltalk session for mulitple users

    I want to create a single tooltalk session that can be shared by a dynamic number of users. How would I set this up? What is difference between xauth and ttauth? I tried to join remote sessions and create/send messages using ttsnoop, but I get TT_ERR

  • Device name gone after upgrading to 2.2.1

    My iPod touch doesn't have its device name listed in in iTunes when it is connected. This has happened since upgrading to software version 2.2.1 and upgrading the sdk to 2.2.1. It still syncs with iTunes properly though. Any ideas of where to set the