Creation of domain issues - migration from weblogic 10.3.0 to 10.3.5 versio

Hello,
i would like to kindly ask for a help with following issue:
Basically we are migrating from the 10.3.0 to the 10.3.5 version. We are building the domain using the template in "silent mode". And when i try to create the domain with new weblogic 10.3.5 im getting some errors.
The command to run the creation of the domain is following:
${WL_HOME}/common/bin/config.sh -mode=silent -silent_script=${SILENT_SCRIPT} -log=${WLLOGFILE} >> ${LOGFILE} 2>&1
returnCode=$?
SILENT_SCRIPT contains following commands:
read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar";
write domain to "/local/wg372/BM/appl/BmDomain";
set OverwriteDomain "true";
close template;
When i setup new env(solaris) with weblogic 10.3.5 im getting following error when the silent_script command (*write domain to "/local/wg372/BM/appl/BmDomain";*) is executed:
2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - succeed: read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar"
2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - write Domain to "/local/wg372/BM/appl/BmDomain"
2011-07-18 16:53:00,505 ERROR [runScript] com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask - There was an error executing the script: /local/wg372/BM/appl/installer/silent_script
java.lang.NullPointerException
     at com.oracle.cie.domain.security.SecurityGenerateLDIFT.buildSecurityInfo(SecurityGenerateLDIFT.java:460)
     at com.oracle.cie.domain.security.SecurityGenerateLDIFT.<init>(SecurityGenerateLDIFT.java:119)
     at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:718)
     at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.processWrite(ScriptParserClassic.java:573)
     at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.execute(ScriptParserClassic.java:429)
     at com.oracle.cie.domain.script.ScriptParserClassic.parseAndRun(ScriptParserClassic.java:148)
     at com.oracle.cie.domain.script.ScriptParserClassic.doExecute(ScriptParserClassic.java:110)
     at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:72)
     at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:35)
     at com.oracle.cie.wizard.domain.helpers.Executor.runSilentScript(Executor.java:68)
     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.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.runScriptWithExecutor(RunScriptTask.java:551)
     at com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.execute(RunScriptTask.java:335)
     at com.oracle.cie.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
     at java.lang.Thread.run(Thread.java:662)
In Windows env im getting following error:
create.domain:
[exec] -mode="silent" -silent_script=J:/_dev/build/installer/silent_script
[exec] << read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
[exec] >> succeed: read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
[exec] << write Domain to "J:/_dev/build/BmDomain"
[exec] CFGFWK-60550: Script execution aborted. The script may contain an error.
[exec] null
CFGFWK-60550: - doc says
CFGFWK-60550: Script execution aborted. The script may contain an error.
Cause:
Action:
Level: 1
Type: ERROR
Impact: Configuration
I tried to google for this issue, look into the weblogic documentation but with no luck.
So i would like to kindly ask, if anyone of you perhaps could give me a hint/advise with this problem.
Thanks in advance.

Hi,
thanks for the reply but im not sure if we are talking about the same thing. What i need is to upgrade the weblogic "DOMAIN" not the weblogic installation itself.
Anyway,
after some googling and testing im again stucked with another issue:
1. First i have created the old doman (10.3.0)
2. Then i have tested the domain with the new weblogic version 10.3.5 - as it should be (and is) compatible within those 2 versions
---> worked fine
3. Then via offline WLST(of weblogic 10.3.5) i have managed to create new template with command writeTemplate(nameOfTemplate.jar)
4. But when i try to create the new domain with the new template via WLST(of weblogic 10.3.5) im again stucked (im able to read the template in wlst but not able to writeDomain ) - error:
wls:/offline> readTemplate('/home/wg372/tmp/new_template.jar')
wls:/offline/BmDomain>writeDomain('/home/wg372/tmp/new_domain')
Error: writeDomain() failed. Do dumpStack() to see details.
wls:/offline/BmDomain>dumpStack()
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)
at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:803)
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 org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyInstance.invoke(Unknown Source)
at org.python.pycode._pyx3.writeDomain$15(/var/tmp/WLSTOfflineIni6651397525640719781.py:71)
at org.python.pycode._pyx3.call_function(/var/tmp/WLSTOfflineIni6651397525640719781.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx24.f$0(<console>:1)
at org.python.pycode._pyx24.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:173)
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 weblogic.WLST.main(WLST.java:29)
Caused by: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:757)
at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:795)
... 29 more
I tried to have a look around for the "The application location must have write permission." problem but again with no luck.
Furthemore when i try to do the same with old domain template, with old version of WLST (of weblogic 10.3.0), i have no problems with creating of the domain.
Any ideas?
Ill keep you updated :-)

Similar Messages

  • JMS issues when migration from weblogic 9.2 to 10.3.5

    We are facing some issues when migration from weblogic 9.2 to 10.3.5
    In  weblogic 9.2 :_
    BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>
    Company
    </ejb-name>
    <entity-descriptor>
    <pool>
    <max-beans-in-free-pool>300</max-beans-in-free-pool>
    <initial-beans-in-free-pool>150</initial-beans-in-free-pool>
    </pool>
    <entity-cache>
    <max-beans-in-cache>3500</max-beans-in-cache>
    <idle-timeout-seconds>100000</idle-timeout-seconds>
    <read-timeout-seconds>0</read-timeout-seconds>
    <concurrency-strategy>ReadOnly</concurrency-strategy>
    </entity-cache>
    Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
    migration to Weblogic 10.3.5_
    With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
    Can some one look into this and provide your inputs to resolve this issue.

    I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
    Tom

  • Migrating from Weblogic 9.2 to 10.3.2 getting Error

    While Migrating from Weblogic 9.2 to 10.3, I am getting the following error. Please help me to solve this issue.
    <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal user error> org.apache.openjpa.util.MetaDataException: Errors encountered while resolving metadata. See nested exceptions for details.
    at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:563)
    at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:219)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:139)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1874)
    at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1832)
    at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1749)
    at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1622)
    at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
    Truncated. see log file for complete stacktrace
    Dec 7, 2010 4:17:14 PM weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport preProcess
    WARNING: Error pre-processing class com.bac.fvo.model.exposure.RiskRatingExposure with weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl@1074a5f'
    <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal user error> org.apache.openjpa.util.MetaDataException: Errors encountered while resolving metadata. See nested exceptions for details.
    at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:563)
    at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:219)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:139)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:120)
    at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(PersistenceProviderImpl.java:210)
    at weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl.preProcess(PersistenceUnitInfoImpl.java:547)
    at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPreProcessor.java:102)
    at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:357)
    at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:301)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
    at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:107)
    at org.hibernate.ejb.Ejb3Configuration.classForName(Ejb3Configuration.java:1008)
    at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1080)
    at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871)
    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:758)
    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425)
    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:131)
    at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:227)
    at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:281)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1333)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:463)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:404)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:375)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:263)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:170)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:260)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:184)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:309)
    at org.springframework.beans.factory.BeanFactoryUtils.beansOfTypeIncludingAncestors(BeanFactoryUtils.java:270)
    at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.detectPersistenceExceptionTranslators(PersistenceExceptionTranslationInterceptor.java:122)
    at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.<init>(PersistenceExceptionTranslationInterceptor.java:78)
    at org.springframework.dao.annotation.PersistenceExceptionTranslationAdvisor.<init>(PersistenceExceptionTranslationAdvisor.java:70)
    at org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor.setBeanFactory(PersistenceExceptionTranslationPostProcessor.java:97)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1290)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:463)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:404)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:375)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:263)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:170)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:260)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:184)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
    at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:881)
    at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:597)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:366)
    at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:254)
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:198)
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1801)
    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.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    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.NullPointerException
    at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1874)
    at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1832)
    at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1749)
    at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1622)
    at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
    at org.apache.openjpa.meta.MetaDataRepository.resolveMeta(MetaDataRepository.java:616)
    at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:541)
    ... 95 more
    Thanks in Advance
    Sheejo Rapheal

    We have war application and we have antlr in preclasspath. have weblogic.xml entries as suggested. still it's going to OpenJPA.
    WARNING: Error pre-processing class com.bac.fvo.model.pricing.PricingVerificationPK with weblogic.de
    ployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl@3d8b1e3'
    <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal user error> org.apache.openjpa.util.MetaDataException:
    Type "class com.bac.fvo.model.pricing.PricingVerificationPK" with application identity and no superc
    lass does not declare an id class. This type is not eligible for builtin identity, so it must decla
    re an id class.
    at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1858)
    at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1834)
    at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1751)
    at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1624)
    at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
    at org.apache.openjpa.meta.MetaDataRepository.resolveMeta(MetaDataRepository.java:616)
    at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:542)
    at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
    at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:220)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:
    139)
    at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:1
    20)
    at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(Per
    sistenceProviderImpl.java:210)
    at weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl.preProcess(PersistenceU
    nitInfoImpl.java:620)
    at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPr
    eProcessor.java:102)
    at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:341)
    at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:322)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:285
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:
    56)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:
    42)
    at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:107)
    at org.hibernate.ejb.Ejb3Configuration.classForName(Ejb3Configuration.java:1008)
    at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1080)
    at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871
    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:761)
    at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425)
    at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersi
    stence.java:132)
    ApplicationContext.xml is
         <!--
              Activates various annotations to be detected in bean classes: Spring's
              @Required and @Autowired, as well as JSR 250's @PostConstruct,
              @PreDestroy and @Resource (if available) and JPA's @PersistenceContext
              and @PersistenceUnit (if available).
         -->
         <context:annotation-config/>
         <!--
              PostProcessors to perform resource injection according to the JPA specification
         (@PersistenceContext, @PersistenceUnit).
         -->
         <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/>
         <!--
              Post-processor to perform exception translation on @Repository classes (from native
              exceptions such as JPA PersistenceExceptions to Spring's DataAccessException hierarchy).
         -->     
         <bean class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/>
              <!--
              Will automatically be transactional due to @Transactional.
              EntityManager will be auto-injected due to @PersistenceContext.
              PersistenceExceptions will be auto-translated due to @Repository.
         -->
         <!-- enable the configuration of transactional behavior based on annotations -->
         <tx:annotation-driven transaction-manager="transactionManager"/>

  • Error while migrating from Weblogic 8.1 to 10.1.3

    Hi
    I am getting the below error while building the xml during migrating from Weblogic 8.1 to 10.1.3.
    Could anyone please suggest how to resolve the below error:
    Error:
    Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/i18n/logging/LogMessage
    [java]      at weblogic.application.compiler.Appc.runBody(Appc.java:179)
    [java]      at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [java]      at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [java]      at weblogic.application.compiler.Appc.main(Appc.java:188)
    [java]      at weblogic.appc.main(appc.java:14)
    [java] Caused by: java.lang.ClassNotFoundException: weblogic.i18n.logging.LogMessage
    [java]      at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    [java]      at java.security.AccessController.doPrivileged(Native Method)
    [java]      at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    [java]      at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    Regards
    Kiran
    [java]      at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    [java]      at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    [java]      ... 5 more

    You have to make sure the LogMessage class (weblogic/i18n/logging/LogMessage) is in the classpath
    Using WebLogic Internationalization utilities: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/utilities.htm#i1011073
    and an example: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/textformatterclasses.htm#g1016464
    and: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/loggerclasses.htm#g1020871

  • Migration from Weblogic 7.0 to 8.1

    Hi,
    I have this project where we have to migrate from Weblogic Portal 7.0 to 8.1 . I have a few questions,
    1. Is there any anything like a wildcard event in Page Flow, which existed in the Webflow?
    2. What about proxy nodes? Does Page flow support proxy nodes?
    The reason I ask is my webflow has these things and I need to manually convert it into a page flow.
    Thanks
    PS: This is just the beginning of a long path of migration.:-)

    Hi,
    I have this project where we have to migrate from
    m Weblogic Portal 7.0 to 8.1 . I have a few
    questions,
    1. Is there any anything like a wildcard event in
    Page Flow, which existed in the Webflow?i believe it does - you shoudl post your question on the pageflow newsgroups, as this is not portal specific
    2. What about proxy nodes? Does Page flow support
    proxy nodes?
    The reason I ask is my webflow has these things and I
    need to manually convert it into a page flow.
    Thanksfrom what i remember about webflow the proxy thing was just an IDE thing and as used to kind uf break up you weblows in to nested ones. Pageflow do support tru nested pageflows
    PS: This is just the beginning of a long path of
    migration.:-)

  • JCOM with Weblogic6.1(migrating from weblogic 6.0)

    Hello,
    We are currently running our application on Weblogic 6.0. Also we have a VB client
    which talks to Enity beans deployed in the Weblogic server, via JINTEGRA(jintegra.jar)
    Now, we are planning to migrate from Weblogic 6.0 to Weblogic 6.1. In this context,
    I have following questions,
    1]     Can I use JCOM for my requirement(talking to EJB's from VB client)
    2]     Is JCOM shipped along with Weblogic 6.1, if so is it shipped as a separate
    jar file or as part of weblogic.jar
    3]     With Weblogic 6.1, do I have to still install Jintegra.jar for accessing my
    beans from VB or does JCOM solve the purpose ?
    Would really appreciate if you could share your thoughts
    reg
    nilesh

    Hello,
    We are currently running our application on Weblogic 6.0. Also we have a VB client
    which talks to Enity beans deployed in the Weblogic server, via JINTEGRA(jintegra.jar)
    Now, we are planning to migrate from Weblogic 6.0 to Weblogic 6.1. In this context,
    I have following questions,
    1]     Can I use JCOM for my requirement(talking to EJB's from VB client)
    2]     Is JCOM shipped along with Weblogic 6.1, if so is it shipped as a separate
    jar file or as part of weblogic.jar
    3]     With Weblogic 6.1, do I have to still install Jintegra.jar for accessing my
    beans from VB or does JCOM solve the purpose ?
    Would really appreciate if you could share your thoughts
    reg
    nilesh

  • Migration from weblogic 9.2 to 11.g

    Hi
    I am trying to migrate from weblogic 9.2 to 11.g and I am getting the follwoing error :
    'weblogic.kernel.Default (self-tuning)'] - java.lang.NoSuchMethodError: org/apache/commons/pool/impl/GenericObjectPoolFactory.<init>(Lorg/apache/commons/pool/PoolableObjectFactory;IBJIIZZJIJZJZ)V
    My application is using commons-pool-1.4.jar and weblogic 11g is loading com.bea.core.apache.commons.pool_1.3.0 version from /apps/weblogic/Oracle/Middleware/modules
    How do I resolve this. I have a startup servlet class which will create a pool of objects using commons-pool-1.4 APIs.
    regards
    Hari
    Edited by: 997435 on 02-Apr-2013 00:50

    You can use filtering classloaders - http://docs.oracle.com/cd/E24329_01/web.1211/e24368/classloading.htm#i1097930
    Some examples are given here: http://middlewaremagic.com/weblogic/?p=6725 (see the "Manipulating class loading" section).

  • EJB perfomance issue while migrating from weblogic 10.0 to 10.3

    Hi,
    I have an EJB service which I am migrating from 10.0 to 10.3
    The service contains an entityManager.find() method which takes less than 2 secs to execute on 10.0 and more than 10 secs on 10.3.
    The code snippet and the log trace are as below --
    Code:
          logger.debug("Looking up Person for id " + personId);
       Person info = entityMngr.find(Person.class, personId);
        if(info != null) {
            logger.debug("Found Person" + info.getFirstName() + " " + info.getLastName() + " for id " + personId);
    log entries:
    05/31/2010 *02:35:25,197* DEBUG persistence.bean.PersistenceService [[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)':822] - Looking up Person for id 12014
    05/31/2010 *02:35:36,272* DEBUG persistence.bean.PersistenceService [[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)':829] - Found Person Vitasha Harinarine for id 12014
    Could somebody please help me debugging this issue? The code has not changed before migrating to 10.3. I have checked that the datasources on both environments are exactly the same.
    Any help would be greatly appreciated.
    Thanks in advance!
    Regards,
    Nishtha

    Don't do that. The ClassLoader used to manage web components is the child of the classloader used to manage EJB components - the servlet can use EJB classes, the EJB's cannot use web classes.
    This is also very poor practice as it couples the business logic layers of you system to the presentation - only the reverse should be done. WLS 6.0 is behaving appropriately.
    Chuck

  • Issue when Application Migration from Weblogic 8 to Weblogic 10

    Hi,
    I have an application developed in Java1.4 which we need to migrate to Weblogic 10 (currently the application resides in Weblogic 8)
    I have recompiled the application with Java1.5 compiler. I am new to this area and need some assistance.
    I am getting the following exceptions (snippets below)
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: No known valid port for: 'Default[t3]:t3(t3):null:8001:172.29.194.87:-1'; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:105)
    at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [com/bmw/cms/domain/config/domain-context.xml]: Invocation of init method failed; nested exception is javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost: No known valid port for: 'Default[t3]:t3(t3):null:8001:172.29.194.87:-1'; No available router to destination]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1148)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:427)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:276)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:360)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:91)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:75)
    at com.bmw.cms.domain.config.Application.<clinit>(Application.java:18)
    Though they speak about the connectivity errors, I want to reconfirm that any specific jar files that we need to have if we are migrating an application from WL8 to WL 10.
    My question: Is there any jar file(s) that is not compatible with WL10 that is compatible with WL8
    The application is making use of the following jar files.
    ant-antlr-1.6.5.jar
    cmdDomain.jar
    common.jar
    commons-beanutils.jar
    commons-collections-3.2.jar
    commons.dbcp.jar
    commons-digester.jar
    commons-lang-2.3.jar
    commons-logging.jar
    commons-net-1.4.1.jar
    commons-pool.jar
    commons-validator.jar
    dsf-spring.jar
    ibatis-2.3.0.677.jar
    ivsr-logging-adapter.jar
    jakarta-regexp-12.jar
    javax-security.jar
    jsr173_1_0_api.jar
    junit.jar
    jxl.jar
    log4j.jar
    spring.jar
    struts-request.jar
    struts-session.jar
    struts-validator.jar
    struts.jar
    tiles.jar
    utilities.jar
    xalan.jar
    xbean.jar
    xercesImpl.jar
    Please let me know if my question does not make any sense or am I missing something valid?
    Regards
    R.

    It's likely that something in your weblogic.xml is invalid according to the schema. If you have a tool that can validate XML against a schema, then do that. It should point to the problem. Otherwise, if you show the entire contents of the file here, we might be able to see what the problem is.

  • Migrated from weblogic 8.1 to 10.2. Issue with Message center transactions

    we recently migrated from webloguc 8.1 to weblogic 10.2. When mesasage center is accessed, we are getting below exception. It is working fine in weblogic 8.1 .
    <Name=[EJB AccountServicesBean.submitAddressChangeRequest(AccountServicesInfo,java.lang.String,java.lang.String)],
    Xid=BEA1-0310676F13BEAC935370(464474497),Status=Rolled back.
    [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 60 seconds
    BEA1-0310676F13BEAC935370],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,
    seconds since begin=131,seconds left=60,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=
    (ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=managed4),
    xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1baf6254,re-Registered = false),
    SCInfo[admin+managed4]=(state=rolledback),SCInfo[server_2+server_2_managed2]=(state=rolledback),
    properties=({weblogic.transaction.name=
    [EJB AccountServicesBean.submitAddressChangeRequest(AccountServicesInfo,java.lang.String,java.lang.String)],
    START_AND_END_THREAD_EQUAL=false, weblogic.jdbc=t3://myserver.com}),
    OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=
    (CoordinatorURL=managed4+myserver.com+admin+t3+,
    XAResources={WSATGatewayRM_managed4_admin, weblogic.jdbc.wrapper.JTSXAResourceImpl,
    WLStore_admin__WLS_managed4},NonXAResources={})],
    CoordinatorURL=managed4+myserver.com+admin+t3+) completed heuristically:
    (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException:
    No connection associated with
    xid = BEA1-0310676F13BEAC935370-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C)) >
    Please help us in resolving it.

    Hi,
    A general rule to follow is to make sure that WebLogic Server JTA timeout (either global, specific to an EJB or for individual transactions) is set to a lower value than the shortest timeout value configured/set for a participating XA resource (e.g., XA Transaction Timeout for Oracle XA JDBC connections). Not doing so can lead to an unexpected and inconsistent distributed transaction outcome, i.e., a participating XA Resource timing out before WebLogic Server JTA as the distributed transaction coordinator. The timed out XA Resource may take action to resolve its own part of the distributed transaction before WebLogic Server can take action. This will lead to heuristic error messages at the time when the WebLogic transaction manager tries to prepare/commit the distributed transaction.
    The solution was for the JDBC Connection Pools to set the XASetTransactionTimeout to true and XATransactionTimeout to zero. When this parameter is set to zero, the XAResource Session Timeout will be set to the global transaction timeout.
    Regards,
    Kal

  • Regarding Migration from Weblogic 10.3.0 to 10.3.3

    We have configured a domain in our weblogic 10.3.0 installation. With in this domain A J2EE application has been deployed with datasources configuration, JAAS configuration.
    Is it possible to migrate to Weblogic 10.3.3 without making any changes in our existing application configuration and domain setup?
    If yes can any one please tell us what is the procedure?
    Thanks in advance.

    Hi,
    first of all could you please clarify the need for migration from  BO XI 3.0 to 3.1, as you can simply apply SP1 on top of 3.0 and it becomes 3.1.
    if you have considered this and still needs to migrate, following are the 3 posible options.
    1. Live-Live Migration - Import Wizard is the tool
    2. BIAR - Live Migration - Import Wizard is the tool
    Please reffer the Import Wizrd User guide for the option 1 and 2 link provided in the above thread.
    Also the 3rd option is to perform the Databse and Filesystem copy, find the step below.
    Launch CCM from the Destination System
    Copy all of the file store from your Source implementation to the file store folder for your Destination implementation
    Stop SIA - right click and select properties - Go to the Configuration tab - Click on the button to specify the data source -
    Select "Copy Data from another Data Source". This will copy the data from your source to the Destination.
    Regards,
    Ramu.

  • Problems migrating from weblogic 8.1 to 9.2

    Hello All,
    I am in the process of migrating a J2EE/EJB application from weblogic 8.1 to 9.2. I am able to deploy the application but could not run it. The application was working fine in 8.1.
    weblogic 9.2 throws the following error...
    <Error> <HTTP> <AQ1647> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257288283875> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1e5d16d - appName: 'portal', name: '/', context-path: ''] Root cause of ServletException.
    javax.servlet.jsp.JspException: ServletException in '/common/layouts/column.jsp': Can't insert page '/phonebook/favouritePeople.do' : null
         at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:921)
         at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:460)
         at jsp_servlet._common._layouts.__portal._jsp__tag11(__portal.java:663)
         at jsp_servlet._common._layouts.__portal._jspService(__portal.java:205)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:394)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:309)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:530)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcessor.java:237)
         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:300)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at com.planetj.servlet.filter.compression.CompressingFilter.handleDoFilter(CompressingFilter.java:191)
         at com.planetj.servlet.filter.compression.CompressingFilter.doFilter(CompressingFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    I understand 9.2 is strict with standards, does this have to do something with the standards?
    Thank you in advance.

    This was an issue with flushing in tiles. I set flush="false" and all is working fine.
    Thank you.

  • Can't migrate from Weblogic 8.1 to 10.1. Problems with Web services.

    Hi,
    I'm beginner in the BEA Weblogic technologies. My current task is a migration of working application (from Weblogic 8.1 to Weblogic 10.1).
    I've created the new ear-file for WLS 10.1 successfully.
    But during deploying of new ear-file on server I retrieve the next error:
    java.lang.IllegalStateException: Could not find binding for QNameProperty ValidateRoles : BindingTypeName[com.actuate.schemas.actuate8.ArrayOfString;t=ArrayOfString@http://schemas.actuate.com/actuate8] Bean type :interface com.actuate.schemas.actuate8.Login XmlType {http://schemas.actuate.com/actuate8}Login
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createQNameProps(Deploytime109MappingHelper.java:1507)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:546)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:250)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:161)
         at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
         Truncated. see log file for complete stacktrace
    The short structure of my wsdl-file is follow:
    <wsdl:definitions name="ActuateAPI"
         xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
         xmlns:typens="http://schemas.actuate.com/actuate8"
         xmlns:wsdlns="http://schemas.actuate.com/actuate8"
         targetNamespace="http://schemas.actuate.com/actuate8">
              <wsdl:types>
              <xsd:schema xmlns="http://schemas.actuate.com/actuate8"
                        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                        xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/"
                        xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                        targetNamespace="http://schemas.actuate.com/actuate8"
                        elementFormDefault="qualified">
    <xsd:complexType name="Login">
    <xsd:sequence>
    <xsd:element name="User" type="xsd:string"/>
    <xsd:element name="Password" type="xsd:string" minOccurs="0"/>
    <xsd:element name="EncryptedPwd" type="xsd:string" minOccurs="0"/>
    <xsd:element name="Credentials" type="xsd:base64Binary" minOccurs="0"/>
    <xsd:element name="Domain" type="xsd:string" minOccurs="0"/>
    <xsd:element name="UserSetting" type="xsd:boolean" minOccurs="0"/>
    <xsd:element name="ValidateRoles" type="ArrayOfString" minOccurs="0"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="Login" type="Login"/>
         <xsd:complexType name="ArrayOfString">
                        <xsd:sequence>
                             <xsd:element name="String" type="xsd:string" maxOccurs="unbounded" minOccurs="0"/>
                        </xsd:sequence>
         </xsd:complexType>
              </xsd:schema>
              </wsdl:types>
         <wsdl:message name="Login">
                   <wsdl:part name="Request" element="typens:Login"/>
              </wsdl:message>
              <wsdl:message name="LoginResponse">
                   <wsdl:part name="Response" element="typens:LoginResponse"/>
              </wsdl:message>
              <wsdl:portType name="ActuateSoapPort">
                   <wsdl:operation name="login">
                        <wsdl:input message="wsdlns:Login"/>
                        <wsdl:output message="wsdlns:LoginResponse"/>
                   </wsdl:operation>
              </wsdl:portType>
              <wsdl:binding name="ActuateSoapBinding" type="wsdlns:ActuateSoapPort">
                   <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
                   <wsdl:operation name="login">
                        <soap:operation soapAction=""/>
                        <wsdl:input>
                             <soap:body use="literal" parts="Request"/>
                        </wsdl:input>
                        <wsdl:output>
                             <soap:body use="literal" parts="Response"/>
                        </wsdl:output>
                   </wsdl:operation>
              </wsdl:binding>
    Please let me know if you need additional information.
    Many thanks,
    Yuriy.

    Thanks for response.
    There is a full stack trace of problem from log file:
    weblogic.application.ModuleException: Could not setup environment
         at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:960)
         at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:345)
         at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:48)
         at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    java.lang.IllegalStateException: Could not find binding for QNameProperty ValidateRoles : BindingTypeName[com.actuate.schemas.actuate8.ArrayOfString;t=ArrayOfString@http://schemas.actuate.com/actuate8] Bean type :interface com.actuate.schemas.actuate8.Login XmlType {http://schemas.actuate.com/actuate8}Login
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createQNameProps(Deploytime109MappingHelper.java:1507)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:546)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:250)
         at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:161)
         at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
         at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:691)
         at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:405)
         at weblogic.wsee.ws.WsFactory.createClientService(WsFactory.java:45)
         at weblogic.wsee.jaxrpc.ServiceImpl.init(ServiceImpl.java:149)
         at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:139)
         at weblogic.wsee.jaxrpc.ServiceRefProcessorImpl.<init>(ServiceRefProcessorImpl.java:76)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at weblogic.deployment.ServiceRefProcessorFactory.constructProcessor(ServiceRefProcessorFactory.java:63)
         at weblogic.deployment.ServiceRefProcessorFactory.getProcessor(ServiceRefProcessorFactory.java:49)
         at weblogic.deployment.BaseEnvironmentBuilder.addServiceReferences(BaseEnvironmentBuilder.java:556)
         at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
         at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:2902)
         at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:958)
         at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:345)
         at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:48)
         at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
         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)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    Thanks.
    Yuriy.

  • Migration from Weblogic 8.1 SP1 server to Sun Java Application Server 8

    Hi,
    I have to migrate an existing application from Weblogic 8i to Sunone Application Server 8.
    Can anyone please help me to know the kind of problems encountered in such a migration.
    Also, If i have to port an application which uses 'Mssql' as the backend in weblogic and migrate it to sunone server and use Oracle as backend what r the changes to be made??
    Also, If any weblogic specific api's or tag libraries are used then what r the changes to be made at the time of migration.?
    Thanks in advance
    Geeta

    The type of issues you will encounter migrating this app depends on its complexity and how observant the programers were to writing portable code.
    You will need to determine how compatible Mssql is to Oracle.
    There may be changes you will need to make in the app deployment descriptors for this data.
    You will need to replace the weblogic specific API's and tags.
    This may require class substition, or writing emulators for the
    APIs, or rewriting the code to not use these APIs.
    The AVK can help you identify such portability issues.

  • Migrating from WebLogic v8.1.3 to v10.3:  Datasources and Connection Pools

    I took the liberty to migrate my OLD BEA WebLogic v8.1.3 domain (i.e. sample) to Oracle WebLogic v10.3. Everything appears to run smoothly BUT when I try to connect to the Hypersonic Database I had from the OLD environment, I get connection errors (i.e. weblogic.common.ResourceException). I can see from the NEW 10.3 environment that the migration utility creates two (2) datasources (sampleDS and samplePool). However, when clicking through the screens, I do not see how sampleDS refers to the samplePool out of the box from the migration utility. When I start the WebLogic domain with startWebLogic.cmd...here is the code to launch the actual DB instance:
    cd hsqldb
    start "Sample DB (HSQLDB)" %JAVA_HOME%\bin\java -classpath hsqldb.jar -Xms32m -Xmx128m org.hsqldb.Server -database sampleDB -port 15553 -silent false -trace false
    cd ..
    This works quite well and launches a window that has the following:
    | Sample DB (HSQLDB)
    | server.properties not found, using command line or default properties
    | Opening database: sampleDB
    | server.port =15553
    | server.database =sampleDB
    | server.silent =false
    | HSQLDB server 1.7.1 is running
    | Use SHUTDOWN to close normally, Use [CTRL] + [C] to abort abruptly
    | Wed Jun 16 10:18:48 EDT 2010 Listening for connections ...
    |_________________________________________________________
    This is the right screen and confirms my database is up and running and waiting for connections. Somehow, when I migrated from 8.1 to 10.3 something is not configured correctly and my sampleDS is not properly leveraging the samplePool. Can anyone shed any light on this problem?
    I have went through most of the posts and can not seem to understand what happens to the DS and Pools during the migration and specifically how do I reconnect the two to ensure that I can connect to the database. The app is up and running fine in WebLogic v10.3 but without the dB connection, I am stuck at the login screen.
    Thanks for any help...

    I took the liberty to migrate my OLD BEA WebLogic v8.1.3 domain (i.e. sample) to Oracle WebLogic v10.3. Everything appears to run smoothly BUT when I try to connect to the Hypersonic Database I had from the OLD environment, I get connection errors (i.e. weblogic.common.ResourceException). I can see from the NEW 10.3 environment that the migration utility creates two (2) datasources (sampleDS and samplePool). However, when clicking through the screens, I do not see how sampleDS refers to the samplePool out of the box from the migration utility. When I start the WebLogic domain with startWebLogic.cmd...here is the code to launch the actual DB instance:
    cd hsqldb
    start "Sample DB (HSQLDB)" %JAVA_HOME%\bin\java -classpath hsqldb.jar -Xms32m -Xmx128m org.hsqldb.Server -database sampleDB -port 15553 -silent false -trace false
    cd ..
    This works quite well and launches a window that has the following:
    | Sample DB (HSQLDB)
    | server.properties not found, using command line or default properties
    | Opening database: sampleDB
    | server.port =15553
    | server.database =sampleDB
    | server.silent =false
    | HSQLDB server 1.7.1 is running
    | Use SHUTDOWN to close normally, Use [CTRL] + [C] to abort abruptly
    | Wed Jun 16 10:18:48 EDT 2010 Listening for connections ...
    |_________________________________________________________
    This is the right screen and confirms my database is up and running and waiting for connections. Somehow, when I migrated from 8.1 to 10.3 something is not configured correctly and my sampleDS is not properly leveraging the samplePool. Can anyone shed any light on this problem?
    I have went through most of the posts and can not seem to understand what happens to the DS and Pools during the migration and specifically how do I reconnect the two to ensure that I can connect to the database. The app is up and running fine in WebLogic v10.3 but without the dB connection, I am stuck at the login screen.
    Thanks for any help...

Maybe you are looking for

  • Error while loading the Repository database using OAIIMPORT

    We are building a test oai environment I am trying to load the repository with the export dump from our production oai using the OAIIMPORT script. I get the following error message: Deleting all tables, indexes, and logs ... Executing: sqlplus system

  • Best Practice Using Data Access Object Pattern

    I was wondering what would be the best approach with regards to implementing the Data Access Object pattern: Given the following database tables: teacher {teacher_id, teacher_name, ...} subject {subject_id, subject_name, ...} teacher_subject {teacher

  • DB13 warnings

    Hi, I'm getting following DB13 warnings : BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPR3.ZJT01 BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPR

  • Mobile apps jar files

    Hi, I'm working in mobile apps customization So I need the corresponding jar( ora-apps.jar ) files. From where can I get these jar files. Thanks Govindan P Edited by: user3026675 on Sep 8, 2009 6:04 AM

  • Ezvpn client on router to windows vpn server

    Hi is it possible to connect cisco router using ezvpn to windows 2008r2 server? i spend a lot of time and got no success. i'm trying to connect cisco 881g using ezvpn to windows vpn server (RRAS) usign pre-shared key. or i should try to connect in an