Simple J2EE application fails under activation

Hi,
I have a simple J2EE application which contains one Servlet.
I have two DCs: SSORedirector (Enterprise application project) and SSORedirectWebModuleWebModule (Web Module)
(there is a third DC which is a child DC to SSORedirector, but I don't think it causes any problems)
The web module has by default public part called war (an I haven't touched this).
The Enterprise application project I have addeed the required references to the web module in the application.xml(this automatically set a Used DC reference).
When right-clicking the enterprise application and selecting build, it builds a correct ear file, and if I deploy it to my local workplace installation, the J2EE application works as expected.
However, when I try to check in and activate the activity the SDM deployment fails with the message: Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
I've retrieved the .sda file on the file system (shouldn't it be an .ear file) and it contains the application.xml under the folder meta-inf. The complete contents of the sda file is
./d1c66970ddbec7e6ffcc4d01c4705600.HASH
./META-INF/application-j2ee-engine.xml
./META-INF/application.xml
./META-INF/MANIFEST.MF
./META-INF/SAP_MANIFEST.MF
./META-INF/sda-dd.xml
./src/java/src.zip
./bouvet.com~SSORedirectorServlets.war
What could possibly be wrong?
Below are some logs.
<b>Deployment log</b>
SAP Change Management Service
System sapJDI.st.bouvet.no
Build space JDI_ZEPSSO_D
Request 8554
Step Deployment
Log /sapmnt/JDI/global/TCS/LOG/JDI_ZEPSSO_D2006021618420025.log
Info:deploy every archive associated to the buildspace: JDI_ZEPSSO_D
Info:getting DC SSORedirector from CBS for buildspace: JDI_ZEPSSO_D
Info:archive /sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda for DC SSORedirector was transfered
Info:Start deployment:
Info:The following archives will be deployed (on http://sapED2.st.bouvet.no:50018)
Info:/sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:SDM log:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:Feb 16, 2006 7:39:58 PM  Info: -
Starting deployment -
Info:Feb 16, 2006 7:40:01 PM  Info: Loading selected archives...
Info:Feb 16, 2006 7:40:01 PM  Info: Loading archive '/usr/sap/ED2/JC00/SDM/program/temp/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda'
Info:Feb 16, 2006 7:40:11 PM  Info: Selected archives successfully loaded.
Info:Feb 16, 2006 7:40:11 PM  Info: Actions per selected component:
Info:Feb 16, 2006 7:40:11 PM  Info: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:14 PM  Info: The deployment prerequisites finished withtout any errors.
Info:Feb 16, 2006 7:40:14 PM  Info: Saved current Engine state.
Info:Feb 16, 2006 7:40:15 PM  Info: Error handling strategy: OnErrorSkipDepending
Info:Feb 16, 2006 7:40:15 PM  Info: Update strategy: UpdateAllVersions
Info:Feb 16, 2006 7:40:15 PM  Info: Starting: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:15 PM  Info: SDA to be deployed: /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:Feb 16, 2006 7:40:15 PM  Info: Software type of SDA: J2EE
Info:Feb 16, 2006 7:40:15 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM  Error: Aborted: development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596':
Info:Caught exception during access of archive "/usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda":
Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Info:Feb 16, 2006 7:40:26 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Info:Feb 16, 2006 7:40:27 PM  Error: -
At least one of the Deployments failed -
Info:end of log received from SDM
Info:End deployment:
Info:deploy finished for SSORedirector (8554) with rc=12
Info:deployment finished for buildspace: JDI_ZEPSSO_D
<b>CBS log</b>
  CBS Request Log - [  8554/JDI_ZEPSSO_D  ]
  sapjdi.st.bouvet.no SAP Component Build Server   
Build number assigned: 8596
Change request state from QUEUED to PROCESSING
ACTIVATION request in Build Space "JDI_ZEPSSO_D" at Node ID: 37,956,050
     [id: 8,554; parentID: 0; type: 4]
     [options: NO OPTIONS]
REQUEST PROCESSING started at 2006-02-16 18:41:35.949 GMT
===== Pre-Processing =====
List of activities to be activated:
     1 activity in compartment "bouvet.com_PASSTHROUGH_SSO_1"
          C049689.6 - Passthrough SSO
               [seq. no 17][created by 433937 at 2006-02-16 19:41:49.0][ID 44ed44bc9f1911daae5b0012799e50b6]
Analyse activities... started at 2006-02-16 18:41:35.967 GMT
     Synchronizing component "bouvet.com/SSORedirector" from repository... finished at 2006-02-16 18:41:37.129 GMT and took 1 s 10 ms
          Component "bouvet.com/SSORedirector" is to be CHANGED by this activation.
     Synchronizing component "bouvet.com/SSORedirectWebModule" from repository... finished at 2006-02-16 18:41:37.933 GMT and took 802 ms
          Component "bouvet.com/SSORedirectWebModule" is to be CHANGED by this activation.
     Synchronizing component "bouvet.com/SSORedirectorServlets" from repository... finished at 2006-02-16 18:41:39.144 GMT and took 1 s 211 ms
     3 components to be build in compartment "bouvet.com_PASSTHROUGH_SSO_1"
Analyse activities... finished at 2006-02-16 18:41:39.202 GMT and took 3 s 235 ms
Calculate all combinations of components and variants to be built...
     "bouvet.com/SSORedirector" variant "default"
     "bouvet.com/SSORedirectorServlets" variant "default"
     "bouvet.com/SSORedirectWebModule" variant "default"
Prepare build environment in the file system... started at 2006-02-16 18:41:39.410 GMT
     Synchronize development configuration... finished at 2006-02-16 18:41:39.430 GMT and took 20 ms
     Synchronize component definitions... finished at 2006-02-16 18:41:39.469 GMT and took 38 ms
     Synchronize sources...
     Synchronize sources... finished at 2006-02-16 18:41:40.891 GMT and took 1 s 422 ms
     Synchronize used libraries...
          public part "war" of component "bouvet.com/SSORedirectWebModule" ... OK
               [PP "war" of DC 381 variant "default"][SC 142][last successfull build: 0]
          public part "default" of component "sap.com/ejb20" ... OK
               [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jdbc20" ... OK
               [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jms" ... OK
               [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/servlet" ... OK
               [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/ejb20" ... OK
               [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jdbc20" ... OK
               [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jms" ... OK
               [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/servlet" ... OK
               [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
     Synchronize used libraries... finished at 2006-02-16 18:41:43.712 GMT and took 2 s 820 ms
Prepare build environment in the file system... finished at 2006-02-16 18:41:43.712 GMT and took 4 s 302 ms
===== Pre-Processing =====  finished at 2006-02-16 18:41:43.713 GMT and took 7 s 755 ms
===== Processing =====
BUILD DCs
     "bouvet.com/SSORedirectorServlets" in variant "default"
          Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
          The build was SUCCESSFUL. Archives have been created.
     "bouvet.com/SSORedirectWebModule" in variant "default"
          Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
          The build was SUCCESSFUL. Archives have been created.
     "bouvet.com/SSORedirector" in variant "default"
          The build was SUCCESSFUL. Archives have been created.
===== Processing =====  finished at 2006-02-16 18:41:56.154 GMT and took 12 s 436 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
     "bouvet.com/SSORedirectorServlets" in variant "default"   OK
     "bouvet.com/SSORedirectWebModule" in variant "default"   OK
     "bouvet.com/SSORedirector" in variant "default"   OK
Update component metadata...
     "bouvet.com/SSORedirector"  has been CHANGED
     "bouvet.com/SSORedirectWebModule"  has been ACTIVATED
STORE build results...
     "bouvet.com/SSORedirectorServlets": store meta-data
     "bouvet.com/SSORedirectorServlets" in "default" variant  is PROCESSED
     "bouvet.com/SSORedirectWebModule": store meta-data
     "bouvet.com/SSORedirectWebModule" in "default" variant  is PROCESSED
     "bouvet.com/SSORedirector": store meta-data
     "bouvet.com/SSORedirector" in "default" variant  is PROCESSED
Change request state from PROCESSING to SUCCEEDED
Analyse effect of applied changes to buildspace state... started at 2006-02-16 18:41:56.364 GMT
Handle Cycles...
     No cycles detected.
Determine components that have become DIRTY due to the results of this request...
     No such components have been found.
Integrate activities into active workspace(s)...
     Integration of activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" started at 2006-02-16 18:41:56.785 GMT
          "C049689.6 - Passthrough SSO"   OK
     Integration of 1 activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" finished at 2006-02-16 18:42:16.614 GMT and took 19 s 829 ms
Analyse effect of applied changes to buildspace state... finished at 2006-02-16 18:42:16.615 GMT and took 20 s 251 ms
Request SUCCEEDED
===== Post-Processing =====  finished at 2006-02-16 18:42:16.617 GMT and took 20 s 451 ms
REQUEST PROCESSING finished at 2006-02-16 18:42:16.618 GMT and took 40 s 669 ms

Managed to solve it in a obscure way.
I had earlier deployed the .ear file directly from NWDS to our dev system (hadn't installed dev workplace then). By removing the application from the deploy service in visual admin, the import suddenly worked.
Dagfinn

Similar Messages

  • BEA-160197: Simple ADF application fails to deploy on integrated weblogic

    JDeveloper 11.1.1.6.0
    Simple JSF ADF application fails to test localy on integrated weblogic. I have never seen this and have no clue where to look for the problem. Anyone?
    [01:11:01 PM] Deploying Application...
    <23.05.2012. 13.11.01 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Documents and Settings\drtodor\Application Data\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\TrackingSystem11g/META-INF/weblogic-application.xml of module TrackingSystem11g. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:161)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:324)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:67)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:315)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
         at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
         at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
         ... 27 more
    Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         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.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
         ... 35 more
    .>
    <23.05.2012. 13.11.01 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean TrackingSystem11g#V2.0. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    <23.05.2012. 13.11.01 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1337771461093' for task '1'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    <23.05.2012. 13.11.01 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'TrackingSystem11g [Version=V2.0]'.>
    <23.05.2012. 13.11.01 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@86e4fd19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setLibraryRefs(WeblogicApplicationBeanImpl.java:1440)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         Truncated. see log file for complete stacktrace
    >
    [01:11:01 PM] #### Deployment incomplete. ####
    [01:11:01 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    #### Cannot run application TrackingSystem11g due to error deploying to IntegratedWebLogicServer.
    [Application TrackingSystem11g stopped and undeployed from Server Instance IntegratedWebLogicServer]

    OK I found it and opened it. This is the content before I started the application:
    <?xml version = '1.0' encoding = 'windows-1250'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                          xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd"
                          xmlns="http://xmlns.oracle.com/weblogic/weblogic-application">
      <listener>
        <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
      </listener>
      <library-ref>
        <library-name>adf.oracle.domain</library-name>
      </library-ref>
    </weblogic-application>I kept it open and ran the app. It got edited in front my eyes just like this:
    <?xml version = '1.0' encoding = 'windows-1250'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                          xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd"
                          xmlns="http://xmlns.oracle.com/weblogic/weblogic-application">
      <listener>
        <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
      </listener>
      <listener>
        <listener-class>
          oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener
        </listener-class>
      </listener>
      <listener>
        <listener-class>
          oracle.mds.lcm.weblogic.WLLifecycleListener
        </listener-class>
      </listener>
      <library-ref>
        <library-name>adf.oracle.domain</library-name>
      </library-ref>
      <library-ref>
        <library-name>
          adf.oracle.domain
        </library-name>
      </library-ref>
    </weblogic-application>

  • What is wrong in this simple J2EE application?

    Hello everyone,
    I am an undergraduate studying J2EE and I don't understand why the JavaBean that I create in the servlet is not correctly passed to the JSP page (I am trying to create a very simple Model 2 application that gets authentication data from an html form and return a jsp page that says if the login is ok or not, access to database is simulated by an if statement).
    In particular, the problem that I experience is that all values that I try to get from the JavaBean object in the JSP page are null instead of having the correct value that I set in the domain logic classes.
    The war archive is available at http://www.webalice.it/m.soderi/ApplicazioneLogin.war
    Can you give me a suggestion?
    Many thanks,
    Mirco Soderi.

    Hi,
    In the login result page you are creating a new instamce of the bean
    by calling
    <jsp:useBean id="UserInformation" class="login.LoginBean" scope="request"/>
    and using "UserInformation" in
    <jsp:getProperty
    you will always get null..
    In your approch you have to use scriplets to print the informatiom required from the session attribute "User information"
    dont declare a new bean using <jsp:useBean id="UserInformation"
    if you want to set the values to the bean then use setproperty method

  • Running ssl client from multiple applications fails in Sap j2ee engine

    There are two applications making ssl connections to third party.
    At a time only one application is able to make connection while other
    throws error message <b>"No trusted certificate found".</b>
    Currently we have  two j2ee applications running in SAP j2ee server. Both applications makes ssl connection to third party servers. Lets call first application as A1 and second application as A2.
    A1 is an internet shopping application . It makes ssl connection to third party services at two places . One is while fetching the shipping charges from UPS site.
    Code Snippet:
    java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    System.getProperties().put("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
    String lo_url = new URL("https://wwwcie.ups.com/ups.app/xml/Rate");
    lo_connection = (URLConnection) lo_url.openConnection();
    At other place A1 connects to cybersource service using webservice +ssl  for credit card authentication using cybersource API. It uses certificate in p12 format.
    Code Snippet:
    com.cybersource.ws.client.axis.soap.RequestMessage lo_requestMessage = new  com.cybersource.ws.client.axis.soap.RequestMessage();
    Properties lo_cybsProperties = new Properties();
    lo_cybsProperties.setProperty("merchantId","arvato");
    lo_cybsProperties.setProperty("merchantRefCode","1234")
    lo_requestMessage.setMerchantID( "arvato");
    lo_requestMessage.setMerchantReferenceCode( "1234" );
    lo_cybsProperties.setProperty("cybersourceURL","https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor");
    lo_cybsProperties.setProperty("keysDir", "./WEB-INF/config");     
    lo_requestMessage.setBillTo(setBillToAddress(po_mdsBillingAddress) );
    // add ship to address
    lo_requestMessage.setShipTo(setShipToAddress(po_mdsShiToAddress));
    lo_requestMessage.setPurchaseTotals( setPurchaseTotal() );
    //set cc details
    lo_requestMessage.setCard( setCardDetails(po_mdsCreditCard) );
    Set Items and total tax calculation
    lo_replyMessage = com.cybersource.ws.client.axis.soap.Client.runTransaction( lo_requestMessage, lo_cybsProperties );
    A2 Application
    This application connects to Motorola secured web service to fetch details of mobile hand set. It uses keystore to create ssl connection with Motorola webservice.
    Code Snippet
    try {
    TrustManager[] trustAllCerts = new TrustManager[]{
    new X509TrustManager() {
    public java.security.cert.X509Certificate[] getAcceptedIssuers() {
              return new java.security.cert.X509Certificate[0];
         public void checkClientTrusted(java.security.cert.X509Certificate[] certs, String authType) {}
    public void checkServerTrusted(
    java.security.cert.X509Certificate[] certs, String authType) {
    SSLContext sc = SSLContext.getInstance("SSL");
    sc.init(null, trustAllCerts, new java.security.SecureRandom());
    } catch (Exception e) {
    e.printStackTrace();
    System.setProperty("javax.net.ssl.trustStore","SapWSM.keystore");
    System.setProperty("javax.net.ssl.trustStorePassword","xxxx");
    System.setProperty("javax.net.ssl.keyStore","SapWSM.keystore");
    System.setProperty("javax.net.ssl.keyStorePassword","xxxx");
    Problem Cases :
    Case 1
    Step 1 : Server starts
    Step 2 : User access A1 first
    Step3: A1 Connects to UPS using https (It is able to connect)
    Step4: A1 connects to cybersource using webservice+ssl  (It is able to connect)
    Step 5: Another user access A2
    Step6: A2 tries connection to Motorola webservice over ssl
    Result connectivity fails with description "No trusted certificate found".
    Case2
    Step 1 : Server starts
    Step 2 : User access A2 first
    Step3:  A2 tries connection to Motorola webservice over ssl (It is able to connect)
    Step 5: Another user access A1
    Step6: A1 connects to cybersource using webservice+ssl 
    Result connectivity fails with description "No trusted certificate found".
    Case3
    Step 1 : Server starts
    Step 2 : User access A2 first
    Step3:  A2 tries connection to Motorola webservice over ssl (It is able to connect)
    Step 5: Another user access A1
    Step6: A1 connects to  UPS using ssl
    Result connectivity fails with description "No trusted certificate found".

    Hi Please answer my query it is really <b>
    urgen
    t</b> and we are not able to run both the applications in same server

  • JNDI lookup fails in a thread created by J2EE application on WAS 8.0.0.4 running on Red Hat Enterprise Server 5.8(2.6.18-308.e15).

    I am using Jackrabbit Repository (jcr's implementation) as backend in my Web Appl.Whose data persists on Oracle Database. To make connection with Oracle database jackrabbit provide provision of JNDI Lookup to read the data source defined in WAS (using WAS 8.0.0.4 as App Server).
    I am able to perform JNDI Lookup everywhere in my application,But in a flow where i am creating a Thread using Java Concurrent Api and insidethread's call() method when I am trying for JNDI Look following exception occurs –
    [8/20/13 10:57:35:163 IST] 000000dd System Out     O ERROR 20-08 10:57:35,163 (DatabaseFileSystem.java:init:209)            failed to initialize file system
    javax.jcr.RepositoryException: JNDI name not found: java:comp/env/jdbc/ofsds
    at org.apache.jackrabbit.core.util.db.ConnectionFactory.getJndiDataSource(ConnectionFactory.java:295)
    at org.apache.jackrabbit.core.util.db.ConnectionFactory.createDataSource(ConnectionFactory.java:233)
    at org.apache.jackrabbit.core.util.db.ConnectionFactory.getDataSource(ConnectionFactory.java:166)
    at org.apache.jackrabbit.core.fs.db.DbFileSystem.getDataSource(DbFileSystem.java:226)
    at org.apache.jackrabbit.core.fs.db.DatabaseFileSystem.init(DatabaseFileSystem.java:190)
    at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$6.getFileSystem(RepositoryConfigurationParser.java:1057)
    at org.apache.jackrabbit.core.config.RepositoryConfig.getFileSystem(RepositoryConfig.java:911)
    at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:285)
    at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:605)
    at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:232)
    at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:280)
    at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:376)
    at com.mmpnc.icm.server.repository.RepositoryStartupService.newSession(RepositoryStartupService.java:408)
    at com.mmpnc.icm.server.repository.RepositoryStartupService.newSession(RepositoryStartupService.java:355)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
    at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
    at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
    at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
    at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
    at com.mmpnc.icm.server.repository.RepositoryStartupService_$$_javassist_1.newSession(RepositoryStartupService_$$_javassist_1.java)
    at com.mmpnc.icm.server.repository.ICMHouseKeepingSessionManager.create(ICMHouseKeepingSessionManager.java:37)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
    at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
    at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
    at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
    at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
    at com.mmpnc.icm.server.repository.ICMHouseKeepingSessionManager_$$_javassist_8.create(ICMHouseKeepingSessionManager_$$_javassist_8.java)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
    at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
    at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
    at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
    at org.jboss.seam.Component.newInstance(Component.java:2054)
    at org.jboss.seam.Component.getInstance(Component.java:1948)
    at org.jboss.seam.Component.getInstance(Component.java:1910)
    at org.jboss.seam.Component.getInstance(Component.java:1904)
    at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2271)
    at org.jboss.seam.Component.getValueToInject(Component.java:2223)
    at org.jboss.seam.Component.injectAttributes(Component.java:1663)
    at org.jboss.seam.Component.inject(Component.java:1481)
    at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
    at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
    at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
    at com.mmpnc.icm.server.repository.ICMHouseKeepingRepository_$$_javassist_7.create(ICMHouseKeepingRepository_$$_javassist_7.java)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
    at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
    at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
    at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
    at org.jboss.seam.Component.newInstance(Component.java:2054)
    at org.jboss.seam.Component.getInstance(Component.java:1948)
    at org.jboss.seam.Component.getInstance(Component.java:1910)
    at org.jboss.seam.Component.getInstance(Component.java:1904)
    at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2271)
    at org.jboss.seam.Component.getValueToInject(Component.java:2223)
    at org.jboss.seam.Component.injectAttributes(Component.java:1663)
    at org.jboss.seam.Component.inject(Component.java:1481)
    at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
    at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
    at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
    at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
    at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
    at com.mmpnc.icm.server.repository.ICMHouseKeepingManager_$$_javassist_6.create(ICMHouseKeepingManager_$$_javassist_6.java)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
    at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:138)
    at org.jboss.seam.Component.callComponentMethod(Component.java:2171)
    at org.jboss.seam.Component.callCreateMethod(Component.java:2094)
    at org.jboss.seam.Component.newInstance(Component.java:2054)
    at org.jboss.seam.Component.getInstance(Component.java:1948)
    at org.jboss.seam.Component.getInstance(Component.java:1910)
    at org.jboss.seam.Component.getInstance(Component.java:1904)
    at org.jboss.seam.Component.getInstance(Component.java:1899)
    at com.mmpnc.icm.server.concurrent.PerformCloseTask.call(PerformCloseTask.java:136)
    at com.mmpnc.icm.server.concurrent.PerformCloseTask.call(PerformCloseTask.java:1)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
    at java.util.concurrent.FutureTask.run(FutureTask.java:149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
    at java.lang.Thread.run(Thread.java:770)
    Caused by:
    javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component.  This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request.  Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application.  Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. [Root exception is javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".]
    at com.ibm.ws.naming.java.javaURLContextImpl.throwExceptionIfDefaultJavaNS(javaURLContextImpl.java:522)
    at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:552)
    at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:481)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLContextRoot.java:485)
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:370)
    at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)
    at javax.naming.InitialContext.lookup(InitialContext.java:436)
    at org.apache.jackrabbit.core.util.db.ConnectionFactory.getJndiDataSource(ConnectionFactory.java:280)
    ... 114 more
    Caused by:
    javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".
    at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1969)
    at com.ibm.ws.naming.ipbase.NameSpace.retrieveBinding(NameSpace.java:1376)
    at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1219)
    at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1141)
    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImpl.java:1436)
    at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:477)
    ... 119 more

    Okay "damorgan", you seem to have me confused with a newbie. All I'm posting is the info that I got from my Sys Admin on the fix to my problem I encountered when trying to install Oracle 11g (11.2.0.0) on Red Hat Linux Enterprise 5. Since we're mouting onto an NFS, these are the steps he took. I'm not trying to "hide" information or post as little as possible. What other info do you want? I don't know what you are referring to when you mention "Filer, make, model, software version"? Please elaborate. I was just trying to post to others that may have encountered this problem, and I get somewhat attacked by you. I don't assume anyone can read my mind (especially you).

  • Double submission problem in J2EE application under Weblogic 8.1 SP2 server

    Hi,
    We are facing double submission problem in our J2EE application which is running under Weblogic 8.1 SP2 and for the same we already implemented or added the below preventive solutions.
    1. We disable the SUBMIT button once the user clicks it.
    2. We preventated pressing 'F5' button and clicking 'Refresh' button in the browser.
    3. Also we tried to prevent by declaring the idempotent is 'true' under weblogic-ejb-jar.xml as below.
    <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempotent>
    So please somebody help us on this issue like how to prevent in some other way.
    Regards,
    Dinesh.

    I have no idea why you would think changing your EJB configuration would have anything to do with preventing double submission at your servlet layer.
    One technique I've seen for preventing double submission was first used in the Struts framework several years ago. When a page is "prepared" for display, a token value is created and stored in the session. The page is displayed with a hidden field containing that value. When the page is submitted, the value of the hidden field is compared with the value stored in the session. If they're not equal, the submission is ignored.

  • J2EE Application Server fails to start...........

    When I tried to run the J2EE Application Server on WindowsXP Professional, I am getting the following error message. Any help will be appreciated.
    Logging for J2EE Server Version: 1.3.1-b17 started at: Thu Feb 28 13:39:24 MST 2002..
    Using the Java HotSpot(TM) Client VM and the version number 1.3.0 from Sun Microsystems Inc..
    VM is using the classpath:
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\cloudscape.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\tools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\RmiJdbc.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\cloudclient.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\classes;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\classes;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\toolclasses;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2eetools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\locale;
    .;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
    c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\jhall.jar .
    J2EE Home Directory has been set to: c:\home\sukesh\J2EE\j2sdkee1.3.1.
    java.lang.NoSuchMethodError
         at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
         at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
         at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
         at javax.rmi.CORBA.Util.writeAny(Util.java:80)
         at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
         at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188)
         at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202)
         at javax.naming.InitialContext.rebind(InitialContext.java:370)
         at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:192)
         at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:149)
         at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
         at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.java:473)
         at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
         at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
    My environment variables are set as follows:
    CLASSPATH=.;c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar
    JAVA_HOME=c:\home\sukesh\J2EE\jdk1.3
    J2EE_HOME=c:\home\sukesh\J2EE\j2sdkee1.3.1
    PATH=c:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;c:\home\sukesh\J2EE\jdk1.3\bin;
    c:\home\sukesh\J2EE\j2sdkee1.3.1]\bi

    When I tried to run the J2EE Application Server on WindowsXP Professional, I am getting the following error message. It is a classpath problem. Any help will be appreciated.
    Logging for J2EE Server Version: 1.3.1-b17 started at: Thu Feb 28 13:39:24 MST 2002..
    Using the Java HotSpot(TM) Client VM and the version number 1.3.0 from Sun Microsystems Inc..
    VM is using the classpath:
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\cloudscape.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\system\tools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\RmiJdbc.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\cloudscape\cloudclient.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\classes;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\classes;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\toolclasses;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2eetools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\locale;
    .;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar;
    c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\jhall.jar .
    J2EE Home Directory has been set to: c:\home\sukesh\J2EE\j2sdkee1.3.1.
    java.lang.NoSuchMethodError
    at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
    at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
    at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
    at javax.rmi.CORBA.Util.writeAny(Util.java:80)
    at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.rebind(Unknown Source)
    at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188)
    at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202)
    at javax.naming.InitialContext.rebind(InitialContext.java:370)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:192)
    at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManagerImpl.java:149)
    at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
    at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.java:473)
    at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
    at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
    My environment variables are set as follows:
    CLASSPATH=.;c:\home\sukesh\J2EE\jdk1.3\lib\tools.jar;c:\home\sukesh\J2EE\j2sdkee1.3.1\lib\j2ee.jar
    JAVA_HOME=c:\home\sukesh\J2EE\jdk1.3
    J2EE_HOME=c:\home\sukesh\J2EE\j2sdkee1.3.1
    PATH=c:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;c:\home\sukesh\J2EE\jdk1.3\bin;
    c:\home\sukesh\J2EE\j2sdkee1.3.1\bin

  • Is anyone doing disaster recovery for a J2EE application?

    We generally use database log shipping to maintain a standby database for our ABAP instances.  We can successfully fail over our production application to our disaster recovery site with no real issues.  With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
    hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
    fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
    we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
    Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them?  Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
    Regards,
    David Hull
    The Walt Disney Company

    I haven't done this personally, but I do have some experience with these issues in different HA environments.
    To your first point:  You can change the hostname, note 757692 tells you exactly how to do it.  However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP."  When it says "supported by SAP" I think it means SAP the company, not SAP's software.  So I would contact SAP to see if this configuration would be covered under your service agreement.  Then you have to think about whether you want to do something that isn't "officially supported" by SAP.  Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
    To your second point:  As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same.  I don't think they are hostname or fqdn dependant.  For BSPs I would think they would still work as long as they use relative paths rather than absolute paths.  And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
    Again, I haven't done what you're describing myself.  This is just based on my HA experiences.
    Hope this helps a little,
    Glenn

  • J2EE application not getting started.

    Hi there,
    I have depoyed my J2EE application successfully but it is not getting started, below is the log trace that is being shown.
    My java path seems fine but cudn't get to know why the initializing is failing.
    Favour would be definitely appreciated.
    One Observation is, WAR file seems like not got deployed properly even though at the time of deployment every acknowledgement message shown was fine.
    **My version is Oracle Weblogic 11g (10.3.0) on IBM AIX 64-bit 6.1 power series system.**
    **JDK used is 1.6.0**
    BEA-149231:
    *Unable to set the activation state to true for the application 'SAMPLEAPP1'. weblogic.application.ModuleException: [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) 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.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) ... 43 more at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) 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.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) 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.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    Cheers.. PCZ

    with the same problem but with weblogic, i tried this solution but i still get this error
    Exception:
    [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3046) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:463) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) 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: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:417) at java.lang.Integer.parseInt(Integer.java:499) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:92) at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) ... 3 more
    and my deployment state is failed

  • Compiling simple web application in samples

    I recently downloaded the J2EE SDK and opened the indexSamplesDomain.html file under the samples directory. Clicked the simple web application link and proceeded to follow instructions to build the application. In this very first example I received an error stating that asant tool could not find the common-ant.xml file in the samples directory. Anyone have any idea the simplest example application has a bug in the build script????
    thanks

    Hi
    You should have a variable called FORMACTION_22_0 ,what you could try as well is to remove the forms autocorrelation from the script:
    In OpenScript: View -> OpenScript Preferences -> Correlation -> HTTP, click on the +* to open DOM Correlation, then double click on it and uncheck the action check box.
    Then you will need to re-correlate the script.
    Script -> Correlate Script
    That should remove all the form variables.
    Alex

  • Application failed codesign verification - solved issue

    Hey all, I just spent many many hours trying to figure this out, so thought I would share what I finally figured out, and hopefully save someone else from the frustration.
    I finished my iOS app using Flash CS5.5 air 2.6, and wanted to post it to the app store. It worked fine on iPad's, iPhone's, and iPod touch's using the development certificates and provisioning profiles. When trying to upload it using Application Loader, though, I kept getting the error "application failed codesign verification...". It didn't give me information to try and guess what might be going on, which was incredibly frustrating. I must have tried a hundred different variations on creating keys, creating certificates, creating app ids, creating provisioning profiles, etc.
    for reference (again, for others having this problem reading this), common issues that I saw on other posts when you get this error are using development provisioning profiles instead of distribution, development certificates instead of distribution, or not using the correct settings when publishing in flash. Make sure in the deployment tab in iOS settings in flash cs5, you have the correct distribution certificate and distribution provisioning profile - not development - and that the app ID under the provisioning profile (e.g. com.mycompany.myapp, without the numbers in front) matches the bundle id in iTunes connect, and that you are set to publish as Deployment - Apple App Store at the bottom.
    In the end, here are some things I was wondering might be the mysterious issue, that are ok to do
    -- you can use OpenSSL to generate all the certificates and keys you need, publish with flash on a PC using those files, then move the file to a mac to use with Application Loader
    -- you don't have to unzip the ipa file anymore (some posts I read say that you used to need to unzip it, then re-zip the folder within the ipa file)
    -- Apple's procedures for checking codesign verification were not helpful. They indicated problems that in the end weren't really problems. They don't really seem to work on a non-xcode based app (I was getting desparate, trying everything I could to figure out what might be the issue).
    -- I'm still not positive how careful you need to be, when creating your key with OpenSSL if you use the correct CN and email address, but that didn't seem to be my problem in the end.
    to get all the files you need, I basically followed the instruction here
    http://www.adobe.com/devnet/air/articles/packaging-air-apps-ios.html#articlecontentAdobe_n umberedheader
    even though it isn't for flash, the provisioning and certificate stuff is the same.
    so... the thing that was keeping my app from successfully uploading was the name for my .fla file. That is a pretty lame place for it to fail, and even worse that a simple name matching created an error that makes it seem like the keys and provisioning had a problem. I had made sure my app name within the settings within Flash matched the name on iTunes connect. I even unzipped the ipa file at one point, and changed the name within to match the name on iTunes connect (which was a pretty close guess). I guess that name propogates in the ipa file structure somehow, such that you have to make sure the file you even use to open your flash document, unrelated to specific settings within flash, needs to match your app name.
    Hope that saves someone else the frustration I had. Hopefully my app is out next week (a kids Customizabooks book app, I'm Scared )
    thx
    tomlucient.

    I'm using CS6 now. I haven't tried using a fla filename with a name different than the iTunes name, but I know that if you do keep the names the same with CS6 then it works My guess is that the 'content' name in the *-app.xml file needs to match up so that Apple knows you're uploading the correct IPA file. I haven't tested that that is really where it grabs the name from, but that's my best guess. One other thing I'll add is that the <filename> and <name> values in the xml file can be different. Those values are what are shown on the iPhone/iPad main desktop/app chooser screen. In CS6, you set the screen name in air for ios settings -> App name:. Changing this does not cause problems with uploading to Apple. thx, Tom

  • HELP!!! Cannot deploy J2EE application with Oracle JDBC driver...

    Hi,
    I am writing a J2EE application which (in theory, at least)
    connects to an Oracle 9i database.
    I have written a simple Java test app utilising only the
    java.sql package classes (e.g. Connection, ResultSet) to directly
    connect to the database. As long as the classes12.zip is in the
    CLASSPATH it works fine.
    Now I have written an Enterprise application (SessionBean,
    Remote and Home interface and Client) which I am attempting to
    deploy via deploytool.
    If I include just the client jar and EJB jar in the application
    it deploys okay but when I run the application (using runclient)
    it produces the following error:
    java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
    (It is nested within other error output but that is the core
    issue).
    However if I try to include the JAR libraries into the app
    (classes12.jar and nls_charset.jar from $ORACLE_HOME/jdbc/lib),
    then I get the following output from deploytool when I hit the
    "deploy" (or "redeploy") button:
    Deployment error: invalid entry compressed size
    (expected 14411 but got 14580 bytes)
    Can someone please tell me what is going on???
    How can I deploy the J2EE application including the Oracle
    JDBC Driver???
    My only other option at the moment is to place all the function-
    -ality in the client and not use the J2EE framework.
    Any help is greatly appreciated.
    Regards,
    Ben New
    Leftclick Software Development
    [email protected]

    OK Ben,
    I admit I'm a bit confused. Let me see if I understand where you're
    coming from.
    You have written a J2EE application that includes a session bean,
    correct? If so, your session bean needs to be deployed to an EJB
    container. What container are you using? The Oracle 9i database
    has an embedded EJB container which (theoretically) you can use.
    However, as far as I know, Oracle recommends you use OC4J as the
    EJB container. So again I ask, what EJB container are you using?
    If, as you say, you are new to EJB, then I think you should
    immediately start working wiht OC4J as your EJB container.
    Did you look at the tutorial link I gave in my previous post? It
    explains -- step by step -- how to create, deploy and run a J2EE
    application using OC4J as the EJB container. It also has links to
    introductory material for people without little knowledge of J2EE
    and EJB.
    I have 9iAS Enterprise Edition and 8.1.7.1.0 database server (and
    OC4J) installed on my SUN machine. I cannot find any of the
    utilities you mention -- "j2eeadmin","runclient" or "deploytool".
    What Oracle software have you installed? What are the versions?
    What platform are you using?
    A J2EE application (according to the specification from SUN)
    consists of modules. A module can either be a client module or an
    EJB module. A client module can either be a java application client
    or a web-based client (servlet or JSP). A J2EE application usually
    contains one client module and one EJB module. A J2EE application
    needs to be deployed to a J2EE container.
    Hopefully the J2EE picture is becoming clearer. I think you need
    to read some introductory material regarding J2EE if you intend
    to become proficient at it.
    I feel that you are under the impression that a J2EE application
    is a glorified JDBC application. It isn't (as far as I'm aware).
    Good Luck,
    Avi.

  • LR2:  1st Launch of Demo - The application failed to initialize properly (0xc0150004)

    Hello all,
    I've never used Lightroom nor had any need to really justify buying it when PS meets my needs, but thought I'd at least take a look at Lightroom 2 to see what it's like. Well, upon installing the trial to my Vista 64 system, the subsequent launch of LR2 only gave the subject "application failed to initialize properly (0xC150004)" error. I see no posts regarding this particular error, and Google searches only turn up that this error could be due to a wealth of things, inclusive of the usual talk regarding viruses or spyware.
    Notwithstanding that I've got quite a number of applications installed, I keep my system relatively clean and do not suspect anything awry. Many speak ill of Norton products, of which I use Norton Internet Security 2008 and have had nothing negative to say about it...no issues from it with reagard to PS CS2 or CS3, so I'd expect none with LR2.
    Oh...and as far as any departure from the default installation goes, I installed LR2 to a separate partition where most of my applications get installed, rather than to the system partition. Of course, that should be transparent and not matter.
    I'm largely looking to see if there are any known obvious LR2 problems that might cause such an error to arise. If not, I'll just uninstall and forget about it. It's not worth spending too much time to resolve.
    I have installed LR2 under the Windows XP/SP2 boot configuration of my system, using a separate installation path on my programs partition than used for the 64-bit version, and all looks to be working fine there. So, this may be more of an LR2 issue with Vista 64.
    Thanks,
    Daryl

    Hi Ian,
    Thanks, but no luck with that idea either. I know 32- and 64-bit O/Ses are different, but I largely expected LR2 to work with both my installations under Norton Internet Security 2008 since all else does. A leap of assumption perhaps, but at least this exercise suggests the problem is unrelated to Norton software. I disabled all services and startup processes for both NIS2008 and Norton Ghost 14, via msconfig, even uninstalled and reinstalled LR2 under those conditions, and the problem persists.
    One additional thing I did observe, as I decided to monitor Task Manager while the LR2 installer ran, is that even after the installation completed and I left the box selected to launch LR2, the MS installer 'msiexec' did not close out. So, I rebooted and with no msiexece active in the list afterwards, again tried launching LR2 with no success.
    The only thing I can glean from this is a similar issue I had with Raxco PerfectDisk 2008, which launched 3 instances of msiexec during its installation, and never closed those. If I killed all related processes and attempted to launch PerfectDisk, it would freeze up at the splash screen with those 3 msiexec processes active again. I sent in some detailed notes to Raxco support for some feedback and if they come up with anything to offer that resolves the issue, perhaps it will be related to why the LR2 installer also doesn't close, or can't close, the msiexec. Perhaps a problem unique to my Vista 64 installation in spite of all else working. As with LR2, PerfectDisk works fine under XP32.
    Regards,
    Daryl

  • Version control J2EE applications

    Hello,
    This is a fairly general question regarding version control. I want to bundle a J2EE application as an EAR file and deploy it to a number of different application servers. On every server where the EAR file is deployed, I would like to keep a history of what version of the J2EE application was installed, and when.
    For example, say I have 3 servers (S1, S2, and S3), and want to deploy myApp.ear to all 3. Something's gone wrong (the application doesn't deploy to S2), and we're not aware of any problems until users start complaining. How can I check which version of my J2EE application has been successfully deployed on each server at a glance?
    Are there any logs kept regarding J2EE deployment histories in the Enterprise Manager? How are these logs maintained? Are they self maintianing?
    We currently have a custom made installation system for non J2EE apps that adds an entry to a table on one of our databases that records the username, date, time and version of a particular application when it is installed. We can't use this custom installation system when we bundle our applications as EARs.
    Basically, how have you guys (other professionals) managed software releases with EARs? Can you recommend any methods, articles, or utilities? Does 10g Application Server provide any means of managing releases?
    Thanks for your input!

    Hello,
    You bring up an interesting problem. At the moment 10.1.2 does not have anyway to manage releases, however there is a simple way out of this.
    When creating the ear file (i.e. pre-deploy), you can add a versions.txt to your ear file which will have the version number of the application. In regards to the time-stamp, the application server will create a directory (under applications and application-deployments) for the respective deployment. In conjunction with the version.txt and the timestamp of your files on the OS, you could get a pretty good feel of releases.
    If you implement your own logging into a file system (which means writing more code), you could do this as well.
    You could also write a servlet that starts-up and writes this data to the DB, however please note that this write will happen every time you start the OC4J instance, so this might not be a good solution.
    Hope this helps.
    Deepak

  • Obtaining SAP User information from J2EE Application

    Hi All,
    I am using SAP NetWeaver Developer Studio to create a J2EE Application, which requires accessing user information from SAP coming from Windows Active Directory.
    My question is as follows;
    Is there a possibility in a J2EE application to use an API to obtain user information (ie. from com.sap.security.api.jar) just like in a regular WebDyn Pro Application?
    For Archive Build Info (compile time), do I need to import specific JARs? For runtime, do I need to load any project reference?
    Thanks in advance,
    Michael

    Yes, I have added 'Run time' as well as 'Build time' for the com.sap.security.api.sda DC as well as for com.sap.tc.Logging DC.
    I have also added the following references to application-j2ee-engine.xml file:
    <application-j2ee-engine>
         <reference
              reference-type="hard">
              <reference-target
                   provider-name="sap.com"
                   target-type="library">com.sap.security.api.sda</reference-target>
         </reference>
         <reference
              reference-type="hard">
              <reference-target
                   provider-name="sap.com"
                   target-type="library">com.sap.tc.Logging</reference-target>
         </reference>
         <provider-name>srl.com</provider-name>
         <fail-over-enable
              mode="disable"/>
    </application-j2ee-engine>
    I am still experiencing the same problem:
    java.lang.NoClassDefFoundError: com/sap/tc/logging/Location
         at com.sap.security.api.UMFactory.<clinit>(UMFactory.java:178)
         at srl.com.birthday.daemon.BirthdaysDaemon.loadEmployeesUser(BirthdaysDaemon.java:114)
         at srl.com.birthday.daemon.BirthdaysDaemon.run(BirthdaysDaemon.java:72)
         at java.lang.Thread.run(Thread.java:534)
    Is there any other JAR I forgot to add to my used DC? Is the security JAR dependant on something else?
    Thanks,
    Michael

Maybe you are looking for