WebLogic 12.1.2 fails when injecting extension in jar into bean in same jar

WebLogic 12.1.2 fails when deploying a web application that contains a jar in which an extension is injected into a bean that resides within that same jar. The following exception is thrown:
"weblogic.management.DeploymentException: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [SampleExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.ApplicationBean.extension]"
weblogic.management.DeploymentException: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [SampleExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.ApplicationBean.extension]
  at weblogic.application.internal.BaseDeployment.throwAppException(BaseDeployment.java:123)
  at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:260)
  at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
  at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
  at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
  Truncated. see log file for complete stacktrace
Caused By: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [SampleExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.ApplicationBean.extension]
  at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:311)
  at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
  at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
  at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
  at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
The problem can be easily reproduced by a minimal case with the following structure:
war-root
     WEB-INF
         beans.xml
         lib
            somejar.jar
And with somejar.jar having the following structure:
test
    ApplicationBean.java
    SampleExtension.java
META-INF
    services
        javax.enterprise.inject.spi.Extension
    beans.xml
ApplicationBean can looks as follows:
@Named
@ApplicationScoped
public class ApplicationBean {
    @Inject
    private SampleExtension extension;
    @Inject
    private BeanManager manager;
    public void myMethod() {
        System.out.println("Extension:" + extension + " Manager:" + manager);
And SampleExtension can be:
public class SampleExtension implements Extension {
    public void onBeanDiscovery(@Observes AfterBeanDiscovery beanDiscovery, BeanManager beanManager) {
        out.println("Extension called");
I published a minimal web application (as Maven multi-module project) that reproduces the case here: https://github.com/arjantijms/inject-extension
This application runs fine on basically every other Java EE server (tried specifically JBoss EAP 6.1, GlassFish 4.0 and TomEE 1.5.2), but not on WebLogic 12.1.2.
Note that I'm not really a WebLogic user. I'm an open source library writer who's trying to make our library (OmniFaces) to run on all Java EE implementations. This case is part of a functionality in our upcoming release.

Hi,
If it is war then try to apply following  Patch 13893259.
Regards,
Kal

Similar Messages

  • WebLogic 12.1.2 fails when deploying ear with injecting extension and bean with injection of this extension in ejb

    WebLogic 12.1.2 fails when deploying an enterprise application(ear) that contains a ejb in which injected 1) an extension 2)bean with injection of this extension.
    The following exception is thrown:
    Caused By: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [CdiExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.extension.Bean1.extension].
    Possible dependencies [
    [Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@1115deb],
    Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@ed791f]]]
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:314)
        at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
        at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
        at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
        at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
        at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:367)
        at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
        at com.oracle.injection.provider.weld.WeldInjectionContainer.start(WeldInjectionContainer.java:106)
        at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:70)
        at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:47)
        at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:37)
        at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
        at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
        at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)
        at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    Problem can be easily reproduced by a minimal case:
    test.ear:
    \lib\test-extension-0.0.1-SNAPSHOT.jar
    test-ejb-0.0.1-SNAPSHOT.jar
    where
    test-extension-0.0.1-SNAPSHOT.jar contains:
    CdiExtension.java:
    package test.extension;
    import javax.enterprise.inject.spi.Extension;
    public class CdiExtension implements Extension {
        private String someString = "Some String";
        public String getSomeString() {
            return someString;
    Bean1.java:
    package test.extension;
    import javax.enterprise.context.ApplicationScoped;
    import javax.inject.Inject;
    @ApplicationScoped
    public class Bean1 {
        @Inject
        private CdiExtension extension;
        public String get() {
            return extension.getSomeString();
    test-ejb-0.0.1-SNAPSHOT.jar contains:
    EjbBean.java:
    package test;
    import test.extension.Bean1;
    import test.extension.CdiExtension;
    import javax.ejb.Stateless;
    import javax.inject.Inject;
    @Stateless
    public class EjbBean {
        @Inject
        private CdiExtension extension;
        @Inject
        private Bean1 bean1;
        public String getSomeString() {
            return extension.getSomeString() + "\n" + bean1.get();
    p.s. i seen same problem in community.oracle.com/thread/2577403 , but it happen in "war", not "ear", and seems successfully patched with patch №17424706

    Hi,
    It looks like there is patch exists for this issue.
    Patch 17198187
    Please try to download from the MOS or try to open a ticket with support.
    Regards,
    Kal

  • I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build.  The same call works fine when running on the device

    I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
    I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
    The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
    I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
    I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
    By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
    Anyone have an idea on other things to try to debug/resolve this?
    Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
    Thanks!

    After a week's worth of debugging, I found the issue.
    The Java type returned from the call was defined as ArrayList.  Changing it to List resolved the problem.
    I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid.  And, why it works in Debug mode and not in Release build is even stranger.  Maybe someone can shed some light on the logic here to me.

  • Extension install failing Adobe Exchange extension

    Mutiple users, our test systems from Mac and Windows are failing when installing extensions from the Adobe Exchange extension.
    Install Extension from Adobe Exchange Panel in Adobe CC application, Ps, Ai, Id,…
              click to download extension
              installing
              ask to open Extension Manger CC, choose yes
    Extension Manager CC
              Asked to quit Adobe CC application
              Sometimes: in Adobe CC application Panel shows "Installation failed. Please close Extension Manager and try again."
              Quit Adobe CC application, click Retry
              Extension Manager error - "File cannot be found... Extension will not be installed."
    Result: Installed extension not shown installed in Extension Manager or Adobe Exchange Panel, but extension is installed.
    Attempting to reinstall has same failure. Extension is installed, but has no method to remove.
    Note installing steps in Panel and in Extension Manager can last 5+ minutes.

    I am sorry about that. These extensions should have been specified force-quit="true" in mxi file by their producers. This attribute means that the application must be closed in order to install these extensions. Because the Exchange Panel runs in applications, so these extensions can't be installed by Exchange Panel. User have to quit applications and launch Extension Manager to install them. This is bad user experience so we  hope the extension developers use this attribute only if it is indeed necessary.
    To get the real root cause, please create a file named ExManCoreLibLog.YES in the "C:\Users\<UserName>\AppData\Roaming\Adobe\Extension Manager CC\Log" (Windows) or "/Users/<UsreName>/Library/Application Support/Adobe/Extension Manager CC/Log" folder (Mac), then launch Extension Manager CC and reproduce your problem, then send the ExManCoreLibrary.log in this folder to [email protected] Thanks!

  • I keep getting a " the connection to the server failed" when trying to use hotmail

    I keep getting a "The connectioin to the server failed" when trying to use hotmail

    Go into Settings, Mail, Contacts, Calendars, select the Hotmail account and check the account settings. Did you set it up with the Hotmail preset? Has this account ever worked on the iPhone? What other troubleshooting have you done?

  • PSCS6 - licensing verification fails when installing an extension

    I receive the error message when using Extension Manager "this extension cannot be installed because licensing verification failed".  I have checked the My Products and Services section of the Adobe web site and it shows my correct serial number for PSCS6.  How can I overcome this problem so that Adobe knows I have a valid license and let me install the extension?
       Russell

    Hi Russel,
    I'm the panel developer; I'm investigating the issue even though it looks quite strange because (unless something weird has happened) the ZXP you've got is the very same that is distributed through Exchange.
    Jonathan, I'll keep you updated on the topic - please do the same if you happen to understand what could fire that licensing error. (by the way the package has been built with a Comodo certificate that will expire in October, so it shouldn't be a packaging problem).
    Kind regards
    Davide Barranca
    www.davidebarranca.com

  • Weblogic.management.DeploymentException: Unmarshaller failed

    Hi,
    I'm facing an error when I deploy an EAR project to Oracle Weblogic Server 10gR3 in Eclipse (server view).
    I get the error message (as a popup):
    'Publishing to Oracle Server 10gR3 failed at localhost...' has encountered a problem.
    Module named 'xxxEAR' failed to deploy. See Errpr Log for more detail.
    Module named 'AvgiftshanteringEAR' failed to deploy. See Error Log view for more detail.
    weblogic.management.DeploymentException: Unmarshaller failed
    Exception received from deployment driver. See Error Log view for more detail.
    And the error in the Error Log view:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1558)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1338)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:795)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:615)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:508)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.management.DeploymentException: Unmarshaller failed
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
    at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
    at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
    at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
    at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
    And this in the Console View:
    <2010-apr-23 kl 9:08 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Utveckling\svnProd\.metadata\.plugins\org.eclipse.core.resources\.projects\xxxEAR\beadep\EVis\xxxEAR/META-INF/application.xml of module xxxEAR. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
         ... 27 more
    .>
    <2010-apr-23 kl 9:08 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean xxxEAR. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 9:08 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1272006514452' for task '6'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 9:08 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxEAR'.>
    <2010-apr-23 kl 9:08 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    2010-apr-23 09:09:18 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    2010-apr-23 09:09:18 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    <2010-apr-23 kl 9:09 CEST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    This however does not occur when I deploy the EAR from the Weblogic Server Administration Console.
    Any ideas?
    //Luc
    Edited by: user13028996 on 2010-apr-23 00:15

    Maybe Eclipse is building/packaging application.xml with the wrong header.
    As soon as I build the EAR project, the changes I made are lost.
    That is why the Stacktrace seems to be the same as earlier.
    <2010-apr-23 kl 14:12 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Utveckling\svnProd\.metadata\.plugins\org.eclipse.core.resources\.projects\xxxEAR\beadep\EVis\AvgiftshanteringEAR/META-INF/application.xml of module xxxEAR. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
         ... 27 more
    .>
    <2010-apr-23 kl 14:12 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean xxxEAR. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 14:12 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1272024728473' for task '2'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 14:12 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxEAR'.>
    <2010-apr-23 kl 14:12 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    //Luc

  • Failed to load extension com.NAI.SysCallExt

    In system preferences, I made 'cd' my startup disk.
    Now, when I try to override and startup from hard disk, computer screen ends up with a black box in middle of screen.
    command-v yields text that includes this statement several times in yellow: "Failed to load extension com.NAI.SysCallExt.
    I want to start up from hard disk, but always get black box on screen and/or this statement (when I use command-v.
    SOLUTION???

    -1-
    I had backups of most important documents.
    -2-
    I never heard of Terminal.app, and many of the other applications mentioned throughout this thread. I'm sure I'm typical of the majority of Mac users. Now, I will read up on them!
    -3-
    I decided that (1) since my essential docs were backed up, and (2) it seemed obvious what the major instigator was (TechTool 3.0.3), I decided to take the risk and use DiskWarrior NEXT, rather than taking a different strategy.
    -4-
    DiskWarrior successfully, and as far as I can tell, completely recovered my directory and files, so that I am now up and running again.
    -5-
    Even though a warning bulletin was posted and several discussions occurred on this site, surely Apple and MicroMat could act more proactively to keep their customers informed. That said, it was MY fault for not having at least consulted the latest information before using the disk utility.

  • Weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non clusterable object with jndiName ]

    Hi,
    I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
    I am getting following error during deployment.
    Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
         Module: Sample.jar     Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
    Unable to deploy EJB: SampleBean from Sample.jar:
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
    clusterable object with jndiName ]
         at weblogic.utils.Debug.assertion(Debug.java:57)
         at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
         at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
         at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Any clue?, what its talking about?
    Thanks
    Naresh

    Hi,
    I am trying to deploy an EJB module have 4-5 EJB's on weblogic 8.1 through JBuilder.
    I am getting following error during deployment.
    Exception:weblogic.management.ApplicationException: prepare failed for Sample.jar
         Module: Sample.jar     Error: Exception preparing module: EJBModule(Sample.jar,status=NEW)
    Unable to deploy EJB: SampleBean from Sample.jar:
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot export non
    clusterable object with jndiName ]
         at weblogic.utils.Debug.assertion(Debug.java:57)
         at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:272)
         at weblogic.ejb20.internal.BaseEJBHome.setup(BaseEJBHome.java:95)
         at weblogic.ejb20.internal.StatelessEJBHome.setup(StatelessEJBHome.java:67)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:979)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:983)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Any clue?, what its talking about?
    Thanks
    Naresh

  • Spring bean creation fails when statefull ejb created in other component

    Hi All,
    We have two components A and B. A creates stateful ejb as well calls B.
    B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
    Error creating bean with name 'dataSource' defined in file ....
    Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
    This happens only when A is using stateful beans.
    when the flow uses A's stateless beans this is working fine.
    For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
    Env: Weblogic 10.3.2
    Thanks and Regards
    Veeramani

    Hi All,
    We have two components A and B. A creates stateful ejb as well calls B.
    B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
    Error creating bean with name 'dataSource' defined in file ....
    Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
    This happens only when A is using stateful beans.
    when the flow uses A's stateless beans this is working fine.
    For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
    Env: Weblogic 10.3.2
    Thanks and Regards
    Veeramani

  • Install OBIEE Failed When Creating Domain

    Hi all,
    I tried to install OBIEE on 64bit redhat linux, but failed when creating domain, the error log shows:
    Starting the domain ...
    oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    An error occurred while starting the domain.
    Action:
    See logs for more details.
         at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3180)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3043)
         at oracle.as.provisioning.engine.WorkFlowExecutor._startAdminServer(WorkFlowExecutor.java:1645)
         at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:635)
         at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
         at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
         at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:49)
         at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
         at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
         at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
         at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
         at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
         at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
         at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
         at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
         at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    An internal WLST operation has failed.
    Action:
    See logs for more details.
         at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
         at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3126)
         ... 19 more
    oracle.as.provisioning.exception.ASProvisioningException
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:872)
         at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
         at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:49)
         at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
         at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
         at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
         at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
         at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
         at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
         at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
         at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
         at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.
         at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:686)
         at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
         at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
         ... 14 more
    the following steps(steps after creating domain) raised:
    Caused by: java.net.ConnectException: t3://hostname:7001: Destination unreachable; nested exception is:
        java.net.ConnectException: Connection refused; No available router to destination
    It's unlikely a hosts file issue which I've met before.
    Install OBIEE Failed on Linux 64bit
    the log caused by hosts file shows:
    Caused by: oracle.as.provisioning.util.ConfigException:
    Error while starting the domain.
    Cause:
    Starting the Admin_Server timed out.
    BTW, the port was tested to be available.
    any idea?
    thanks in advance
    Nathaniel

    we had this issue couple of days back ,,
    Resolved by doing below
    1. uninstall obiee 2. drop the repository 3, remount /tmp folder
    with this we could successfully install obiee 11.1.1.7

  • Internal error when implementing extension

    Hello everyone
    At the moment I create a new contract (transaction RECN) an error occurs and I can not solve.
    Someone could help me?
    Internal error when implementing extension (see long text)
    Message no. RECAAP093
    Diagnosis
    Call of GET_EXTENSION( ) method for enhancement CL_FILACI_VICN01_EXTENSION failed.
    It tried to use an add-on or customer-specific enhancement that is not implemented in your system.
    To be able to determine the technical attributes of enhancement CL_FILACI_VICN01_EXTENSION, the RECA_STORABLE_EXT Business Add-In has to supply the desired information. However, this was not the case. In an implementation of RECA_STORABLE_EXT, the GET_OBJNAME_EXT( ) method must supply the required enhancement CL_FILACI_VICN01_EXTENSION.
    Below is example code for GET_OBJNAME_EXT( ):
    CASE ID_OBJNAME_STD.
        WHEN '...'.
          APPEND 'CL_FILACI_VICN01_EXTENSION' TO CT_OBJNAME_EXT.
      ENDCASE.
    For more information, refer to the documentation for the RECA_STORABLE_EXT Business Add-In.
    Start BAdI Builder
    Procedure
    Contact your system administrator.
    tks a lot!

    Hi Fabio,
    I would kindly ask you appy the SAP note [1521903|https://service.sap.com/sap/support/notes/1521903] and proceed as described in the note to resolve the issue.
    Hope this information is helpful for you.
    Regards, Franz

  • Redeployment fails when using WLP + WLS 10.2 + hibernate

    Hi all,
    When using WLP, WLS 10.2 version, Oracle 10g database and application which uses hibernate as JPA, redeployment fails:
    <10.9.2008 11:44:11 EEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1221036201093' for task '4
    '. Error is: 'java.lang.ClassCastException: org.hibernate.dialect.Oracle10gDialect'
    java.lang.ClassCastException: org.hibernate.dialect.Oracle10gDialect
    at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:101)
    at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:65)
    at org.hibernate.cfg.SettingsFactory.determineDialect(SettingsFactory.java:460)
    at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:155)
    at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)
    Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: org.hibernate.dialect.Oracle10gDialect
    at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:101)
    at org.hibernate.dialect.DialectFactory.buildDialect(DialectFactory.java:65)
    at org.hibernate.cfg.SettingsFactory.determineDialect(SettingsFactory.java:460)
    at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:155)
    at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)
    Truncated. see log file for complete stacktrace
    Persistence.xml looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0">
    <persistence-unit name="abc_order" transaction-type="JTA">
         <provider>org.hibernate.ejb.HibernatePersistence</provider>
    <jta-data-source>abcDataSource</jta-data-source>
    <class>xxx</class>
    <properties>
    <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/>
    <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/>
    <property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory"/>
    <property name="hibernate.transaction.flush_before_completion" value="true"/>
    <property name="hibernate.transaction.auto_close_session" value="true"/>
    </properties>
    </persistence-unit>
    </persistence>
    And included persistence libs are:
    antlr-3.1.jar
    asm.jar
    asm.attrs.jar
    cglib-2.1.3.jar
    commons-collections-3.2.jar
    commons-logging-1.0.4.jar
    commons-net-1.4.1.jar
    dom4j-1.6.1.jar
    ehcache-1.3.0.jar
    ejb3-persistence.jar
    hibernate3.jar
    hibernate-annotations.jar
    hibernate-commons-annotations.jar
    hibernate-entitymanager.jar
    hibernate-tools.jar
    javassis.jar
    jta-spec1_0_1.jar
    ojdb14-jar
    slf4j-api-1.5.2.jar
    slf4j-jdk4-1.5.2.jar
    In hibernate.orgs resolution on the weblogic side is add weblogic-application.xml descriptor the following:
    <prefer-application-packages>
    <package-name>antlr.*</package-name>
    </prefer-application-packages>
    which helps to this error but then you have to undeploy you application and restart the server before you can deploy the application again.
    This slows down the development of applications and in addition of that when your environment has two portal applications it is impossible to deploy both applications in that environment.
    Is there any solution for this kind of problems ? Or do we have wrong configuration or librarys in our environment ?

    11g PS2 : Deployment fails- ADF page having WebService as a DataControl

  • Iisproxy.dll causes "DLL initialization routine has failed" when serving JSPs

              Hi,
              We are experiencing problems with the Weblogic ISAPI plug-in. Often the webservers
              are giving the following error:
              "A dynamic link library (DLL) initialization routine has failed"
              when trying to serve JSP requests (the only ones that are using this plug-in),
              without crashing the IIS service. Which causes our load-balancers to hit the affected
              webservers as the IIS service is running, but the clients (browsers) only seen
              this error.
              Our configuration is the following:
              - 2 WLS 4.5.1 SP11 on Solaris 2.5.7 boxes running in a cluster
              - 3 IIS4 using the iisproxy.dll from WLS 4.5.1 SP14 on NT4 SP6a boxes.
              Our iisproxy.ini is the following:
              WebLogicCluster=10.194.34.32:7005,10.194.34.34:7005
              ErrorPage=http://212.0.161.16/media/site_down.htm
              ConnectTimeoutSecs=15
              ConnectRetrySecs=2
              DebugConfigInfo=ON
              Debug=ON
              The plug-in is registered to only serve JSP requests and the "Run in separate
              memory space" is checked. Does anyone knows what's the problem? I'm also attaching
              the plug-in log from one of the affected webservers.
              Thanks in advance.
              [Wlproxy.zip]
              

    Thanks, JLS.
    We figured it out. There's an entry in the registry that lvanyls.dll points to specifying the location of the LV shared directory (and therefore the MKL directory). If it's not found in that exact location, the dll load aborts.
    We're trying to not include the runtime installer in our application installer because of the size, so we're figuring out our own workaround (and trying to CYA in the meantime ).
    -Scott

  • Install of Elements trial fails when installing Shared Technologies

    Have tried installing the Elements 10 trial on both an XP Pro and a Win7 Pro PC and have the same problem.
    Install of trial fails when installing Shared Technologies and then rolls back the install of the Elements Organiser.
    Anyone seen this before?   Any ideas?

    Can you please make your question a seperate thread?
    It would be helpful if you could please provide us the install log for it. Install logs can be found at C:\Program Files(x86)\Common Files\Adobe\Installers\ with name Elements STI Installer 1.0 <date>.log.gz
    Use a decompression utility such as Winzip to uncompress the .gz file. Once uncompressed, you will have a new file without the .gz extension. The filename could now be something like "Elemens STI Installer 1.0 11-21-2012.log."
    Open the .log file using notepad
    Copy the whole log and paste it here.
    http://helpx.adobe.com/photoshop-elements/kb/troubleshoot-installation-photoshop-elements- premiere.html#main_Error__Below_mentioned_applications_have_failed_to_install__Shared_tech nologies_

Maybe you are looking for