Weblogic 12c exam

Does any one know answers for the below questions ??
Question 1: Which four of the following NOT included in Weblogic lighter version (WLS Zip Distribution for only development)
A. JVM
B. Webserver plug-in
C. Samples
D. Smart update
E. Deployment plan
Question 2: A WebLogic team is developing an enterprise application from their desktop WebLogic environment. All development systems are connected to the same eight data sources for testing. As a WebLogic Administrator supporting this team, which two actions should you perform to free the developers from creating and configuring all the data sources on their desktop WebLogic environment?
A. Provide the team with a WebLogic domain template with the testing data sources configured.
B. Provide the development team with a preconfigured domain archive file.
C. Provide the development team with the [datasource] -jdbc.xml file to overwrite their local copy.
D. Create the data sources on behalf each of the developer.
E. Provide the development team with WLST scripts to create and configure the testing data sources.
Question 3: What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the initial settings in a production environment?
A. Ensure the maximum size is increased to an appropriate setting.
B. Set the minimum and maximum size of the connection pool to the same value.
C. Increase the statement cache size.
D. Add more heap to the JVM.
E. Add more nodes to the cluster.
Question 4: A customer needs to ensure that the number of threads servicing an application does not exceed the number of database connections available to the application. What step must you take to address this situation?
A. Configure a Max Threads Constraint and add your application to the list of applications for the Constraint.
B. Configure a Work Manager with a Maximum Threads Constraint tied to the Connection Pool and configuration your application to use the Work Manager.
C. Configure a Work Manager with a Minimum Threads Constraint tied to the Connection Pool and configure your application to use the Work Manager.
D. Configure a global MaxThreads constraint and target it to the server or clusters where your application is deployed.
E. Configure the startup parameter "-Dwls-maxThreads" to be the same as the number of database connections configured.
Question 5: In a Java EE messaging application, one MDB is consuming a lot of memory at high traffic. What configuration should you use to prevent possible out-of-memory error at high traffic and at the same time not losing messages?
A. Configure a Work Manager for the MDB with a Maximum Thread Constraint.
B. Configure a Work Manager for the MDB with a Minimum Thread Constraint.
C. Configure a Work Manager for the MDB with a Maximum Thread Constraint and a Capacity Constraint.
D. Configure a Work Manager for the MDB with a Minimum Thread Constraint and a Capacity Constraint.
E. Configure a Work Manager for the MDB with both a Maximum Thread Constraint and Minimum Thread Constraint.
Question 6: An airline is building a booking system for its premium and general customers. The goal is to ensure premium members are given higher access priority when user traffic is high.
What configuration will achieve this goal?
A. Configure a Work Manager for premium users with a Minimum Thread Constraint.
B. Configure a Work Manager for premium users with a higher fair-share-request-class.
C. Configure a Work Manager for premium users with a higher response-time-request-class.
D. Configure a Work Manager general users with a Maximum Thread Constraint.
E. Configure a Work Manager for premium users with a custom request-class.
Question 7: Which WebLogic optimization allows one non-XA resource to participate in a distributed transaction?
A. enabling Pinned to Thread
B. enabling Logging Last Resource
C. increasing the Statement cache size
D. setting the statement cache type to LRU
E. setting the initial and maximum capacity to the same number
Question 8: You deploy two different applications to the WebLogic container. One application use Xerces parser version A and the other application uses Xerces parser version B. Both these versions are different from the parser version that the WebLogic server uses internally. You want to use the Filtering Classloader feature to solve this problem. What action would you take to generate proper filtering Classloader entries?
A. Modify the applications to use the same version that WebLogic uses internally.
B. Based on available examples of Filtering Classloader entries, try to modify get the proper entries.
C. Deploy and use the Classloader Analyzing Tool to resolve all conflicts with conflicting libraries. This tool will generate all proper entries.
D. Split the application into separate WebLogic containers and use different WLS versions of Xerces but identical that applications require.
E. Look for a WebLogic release that uses the same version of Xerces that the applications use.
Question 9: Identify the two options that can be used to patch WebLogic Server without Incurring application downtime.
A. automated process using the Admin Server
B. automated using JDeveloper
C. manual process with or without Smart Update
D. scripted with WLST
E. automated process using Enterprise Manager 12c
Question 10: WebLogic 12c, the Maven plug-in has been enhanced with which Maven goal?
A. wls:unzip, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
B. wls:install, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
C. wls:unzip, wls:create-domain, wls:start-domain, wls:wlst, wls:appc
D. wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:

Hello user7776, I am also looking for answers to the above Questions. Can you please send me the correct answers if you got the answers already? I really appreciate your response. Thank you sir.
-VCS

Similar Messages

  • Error while deploying an application on weblogic 12c. An error occurred while reading the deployment descriptor. The error was: Error processing annotations

    Anyone please help me solve this error. I am trying to deploy an application on weblogic 12c  i am getting an error but the same application gets successfully deployed on weblogic 11g. The error is
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(gsCallbackAdapterLGTX-ejb.jar) An error occurred while reading the deployment descriptor. The error was: Error processing annotations: .
    [EJB:015001]Unable to link class com.aep.gridsmart.adapters.lgtx.buslogic.deliver.xform.AdapterTransfomerDeliverSession in Jar /appl/oracle/middleware/WLS/12.1.1.0/user_projects/domains/Gridsmart/servers/ManagedServer1/tmp/_WL_user/gsCallbackAdapterLGTX/34vz4d/gsCallbackAdapterLGTX-ejb.jar : java.lang.NoClassDefFoundError: com/aep/gridsmart/adapter/deliver/CommonAdapterDeliverBean

    Cotton please let me know what is the mistake i am
    doingThe following path does not exist.
    C:\Sun\AppServer7\domains\domain1\server1\
    applications\j2ee-modules\task_1\WEB-INF\web.xml

  • Deployement problem in weblogic 12c and as well as weblogic 10.3.0.0

    Hello All,
    I am newbie to Ejb and weblogic so i need your assist, please help me guys.
    while deploying my jar file into weblogic i got these errors on admin console i.e
    *"An error occurred during activation of changes, please see the log for details.*
    *Exception preparing module: EJBModule(demo) [EJB:011023]An error occurred while reading the deployment descriptor.*
    *The error was: Error processing annotations: .*
    *There are 1 nested errors: weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load class com.ejb.model.MyIntfImpl in Jar F:\Oracle\Middleware\user_projects\domains\phanidevnew\servers\AdminServer\upload\demo.jar : java.lang.ClassNotFoundException: Class bytes found but defineClass()failed for: 'com.ejb.model.MyIntfImpl'*
    *The deployment has been successfully installed. "*
    and in server console displaying like this
    "*<30 Apr, 2012 11:39:02 AM IST> <Warning> <Deployer> <BEA-149004> <Failures were*
    *detected while initiating deploy task for application 'demo'.>*
    *<30 Apr, 2012 11:39:02 AM IST> <Warning> <Deployer> <BEA-149078> <Stack trace fo*
    *r message 149004*
    *weblogic.application.ModuleException: Exception preparing module: EJBModule(demo*
    *[EJB:011023]An error occurred while reading the deployment descriptor. The error*
    *was:*
    *Error processing annotations: .*
    *at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)*
    *at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu*
    *leListenerInvoker.java:93)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl*
    *oymentCallbackFlow.java:387)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:58)*
    *Truncated. see log file for complete stacktrace*
    *weblogic.utils.ErrorCollectionException:*
    *There are 1 nested errors:*
    *weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load clas*
    *s com.ejb.model.MyIntfImpl in Jar F:\Oracle\Middleware\user_projects\domains\pha*
    *nidevnew\servers\AdminServer\upload\demo.jar : java.lang.ClassNotFoundException:*
    *Class bytes found but defineClass()failed for: 'com.ejb.model.MyIntfImpl'*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(B*
    *aseJ2eeAnnotationProcessor.java:1264)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingEr*
    *ror(BaseJ2eeAnnotationProcessor.java:1269)*
    *at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotatio*
    *ns(EjbAnnotationProcessor.java:172)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandard*
    *Annotations(EjbDescriptorReaderImpl.java:324)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyD*
    *escriptorFromJarFile(EjbDescriptorReaderImpl.java:190)*
    *at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJar*
    *File(EjbDescriptorFactory.java:93)*
    *at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule*
    *.java:1198)*
    *at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)*
    *at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu*
    *leListenerInvoker.java:93)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl*
    *oymentCallbackFlow.java:387)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:58)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:42)*
    *at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja*
    *va:615)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j*
    *ava:191)*
    *at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo*
    *duleDeployment.java:16)*
    *at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme*
    *ntStateChecker.java:155)*
    *at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App*
    *ContainerInvoker.java:60)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr*
    *eateAndPrepareContainer(ActivateOperation.java:197)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do*
    *Prepare(ActivateOperation.java:89)*
    *at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr*
    *epare(AbstractOperation.java:217)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym*
    *entPrepare(DeploymentManager.java:723)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy*
    *mentList(DeploymentManager.java:1190)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare*
    *(DeploymentManager.java:248)*
    *at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre*
    *pare(DeploymentServiceDispatcher.java:159)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
    *at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin*
    *gWorkManagerImpl.java:516)*
    *at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
    *at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(B*
    *aseJ2eeAnnotationProcessor.java:1263)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingEr*
    *ror(BaseJ2eeAnnotationProcessor.java:1269)*
    *at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotatio*
    *ns(EjbAnnotationProcessor.java:172)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandard*
    *Annotations(EjbDescriptorReaderImpl.java:324)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyD*
    *escriptorFromJarFile(EjbDescriptorReaderImpl.java:190)*
    *Truncated. see log file for complete stacktrace*
    *>*
    *<30 Apr, 2012 11:39:02 AM IST> <Error> <Console> <BEA-240003> <Console encounter*
    *ed the following error weblogic.application.ModuleException: Exception preparing*
    *module: EJBModule(demo)*
    *[EJB:011023]An error occurred while reading the deployment descriptor. The error*
    *was:*
    *Error processing annotations: .*
    *at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)*
    *at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu*
    *leListenerInvoker.java:93)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl*
    *oymentCallbackFlow.java:387)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:58)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:42)*
    *at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja*
    *va:615)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j*
    *ava:191)*
    *at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo*
    *duleDeployment.java:16)*
    *at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme*
    *ntStateChecker.java:155)*
    *at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App*
    *ContainerInvoker.java:60)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr*
    *eateAndPrepareContainer(ActivateOperation.java:197)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do*
    *Prepare(ActivateOperation.java:89)*
    *at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr*
    *epare(AbstractOperation.java:217)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym*
    *entPrepare(DeploymentManager.java:723)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy*
    *mentList(DeploymentManager.java:1190)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare*
    *(DeploymentManager.java:248)*
    *at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre*
    *pare(DeploymentServiceDispatcher.java:159)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
    *at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin*
    *gWorkManagerImpl.java:516)*
    *at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
    *at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    *Caused by: weblogic.utils.ErrorCollectionException:*
    *There are 1 nested errors:*
    *weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load clas*
    *s com.ejb.model.MyIntfImpl in Jar F:\Oracle\Middleware\user_projects\domains\pha*
    *nidevnew\servers\AdminServer\upload\demo.jar : java.lang.ClassNotFoundException:*
    *Class bytes found but defineClass()failed for: 'com.ejb.model.MyIntfImpl'*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(B*
    *aseJ2eeAnnotationProcessor.java:1264)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingEr*
    *ror(BaseJ2eeAnnotationProcessor.java:1269)*
    *at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotatio*
    *ns(EjbAnnotationProcessor.java:172)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandard*
    *Annotations(EjbDescriptorReaderImpl.java:324)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyD*
    *escriptorFromJarFile(EjbDescriptorReaderImpl.java:190)*
    *at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJar*
    *File(EjbDescriptorFactory.java:93)*
    *at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule*
    *.java:1198)*
    *at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)*
    *at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu*
    *leListenerInvoker.java:93)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl*
    *oymentCallbackFlow.java:387)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:58)*
    *at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep*
    *loymentCallbackFlow.java:42)*
    *at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja*
    *va:615)*
    *at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD*
    *river.java:37)*
    *at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j*
    *ava:191)*
    *at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo*
    *duleDeployment.java:16)*
    *at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme*
    *ntStateChecker.java:155)*
    *at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App*
    *ContainerInvoker.java:60)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr*
    *eateAndPrepareContainer(ActivateOperation.java:197)*
    *at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do*
    *Prepare(ActivateOperation.java:89)*
    *at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr*
    *epare(AbstractOperation.java:217)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym*
    *entPrepare(DeploymentManager.java:723)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy*
    *mentList(DeploymentManager.java:1190)*
    *at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare*
    *(DeploymentManager.java:248)*
    *at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre*
    *pare(DeploymentServiceDispatcher.java:159)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
    *at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb*
    *ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
    *at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin*
    *gWorkManagerImpl.java:516)*
    *at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
    *at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(B*
    *aseJ2eeAnnotationProcessor.java:1263)*
    *at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingEr*
    *ror(BaseJ2eeAnnotationProcessor.java:1269)*
    *at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotatio*
    *ns(EjbAnnotationProcessor.java:172)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandard*
    *Annotations(EjbDescriptorReaderImpl.java:324)*
    *at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyD*
    *escriptorFromJarFile(EjbDescriptorReaderImpl.java:190)*
    *at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJar*
    *File(EjbDescriptorFactory.java:93)*
    *at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule*
    *.java:1198)*
    *at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)*
    *>*
    *My application is*
    *MyIntf:*
    package com.ejb.model;
    import javax.ejb.;
    @Remote
    public interface MyIntf
    public String getMsg();
    *MyIntfImpl:*
    +package com.ejb.model;+
    +import javax.ejb.*;+
    +import javax.annotation.*;+
    +@Stateless(mappedName="demoapp")+
    +public class MyIntfImpl implements MyIntf+
         public String getMsg()
              System.out.println("in getMsg() method" );
              return "Hello I am from getMsg() method" ;
         @PostConstruct
         public void init()
              System.out.println("in init() method" );
         @PreDestroy+
         public void destroy()
         System.out.println("in destroy() method" );
    *persistence.xml in META-INF folder is*
    +<persistence xmlns="http://java.sun.com/xml/ns/persistence"+
    +xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"+
    +xsi:schemaLocation="http://java.sun.com/xml/ns/persistence+
    http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0">
              <persistence-unit name="myunit" transaction-type="JTA">
              <jta-data-source>myds</jta-data-source>
              </persistence-unit>
              </persistence>
    The above code is compiled fine,
    I create it as demo.jar by using jar -cvf demo.jar com META-INF,
    After that i deployed then i got above errors,
    I deployed same app into glassfish then it works fine with out prob.
    I configured DATA SOURCE properly,
    But why i got these error and solve it..
    Please guys

    Note that WebLogic 12c endorses JavaEE6.
    Look ups and how JNDI works is explained in the JavaEE6 tutorial: http://docs.oracle.com/javaee/6/tutorial/doc/gipjf.html

  • Error while deploying on Weblogic 12c

    Hi all,
    I got an error while trying to deploy my WAR on Weblogic 12c. However, deployment on 11g for the same WAR is successful. Here is the error I got:
    [ERROR] Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:deploy (default-cli) on project pilot-web: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException: InvocationTargetException: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException
    -> [Help 1]
    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:deploy (default-cli) on project pilot-web: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:585)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:324)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
    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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
    Caused by: org.apache.maven.plugin.MojoExecutionException: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException
    at weblogic.tools.maven.plugins.deploy.DeployerMojo.handleDeployerException(DeployerMojo.java:459)
    at weblogic.tools.maven.plugins.deploy.DeployAppMojo.execute(DeployAppMojo.java:177)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:577)
    ... 14 more
    Caused by: java.lang.reflect.InvocationTargetException
    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.tools.maven.plugins.ClasspathMojo.invokeMain(ClasspathMojo.java:41)
    at weblogic.tools.maven.plugins.deploy.DeployAppMojo.execute(DeployAppMojo.java:174)
    ... 16 more
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException
    at weblogic.Deployer.run(Deployer.java:76)
    at weblogic.Deployer.mainWithExceptions(Deployer.java:63)
    ... 22 more
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 4 failed: [Deployer:149026]deploy application pilot-web on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.ArrayIndexOutOfBoundsException
    java.lang.ArrayIndexOutOfBoundsException
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:543)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.Deployer.run(Deployer.java:74)
    ... 23 more
    Any ideas?
    Thanks,
    Bassam

    Hi all,
    Any help?
    Thanks

  • How to use Derby database in embedded mode in WebLogic 12c?

    I have a JavaEE-6 application that uses Derby database in embedded mode. It uses JPA for persistence. Everything works fine in Glassfish but now I am trying to port it to WebLogic 12c and having issues setting up Derby database in WLS in embedded mode. The derby setup in WLS asks for Host/port and does not have the embedded mode option. Any help is appreciated.
    -Prantor

    I'm pretty sure this is the wrong forum. "Oracle Application Server" is iAS, not WebLogic.

  • Java.lang.StackOverflowError Running BASIC JSF 2 example on Weblogic 12c

    *I followed the very basic tutorial found here  example and cannot seem to get past the following error:*
    Error 500--Internal Server Error
    java.lang.StackOverflowError
    at weblogic.servlet.internal.ServletResponseImpl.addHeader(ServletResponseImpl.java:567)
    at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:200)
    at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:200)
    at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:200)
    at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:200)
    Pressing shift + F5 a couple times I can generate a slightly different stacktrace as follows:
    Error 500--Internal Server Error
    java.lang.StackOverflowError
    at com.sun.faces.application.ViewHandlerResponseWrapper.setStatus(ViewHandlerResponseWrapper.java:88)
    at javax.servlet.http.HttpServletResponseWrapper.setStatus(HttpServletResponseWrapper.java:224)
    at com.sun.faces.application.ViewHandlerResponseWrapper.setStatus(ViewHandlerResponseWrapper.java:88)
    at javax.servlet.http.HttpServletResponseWrapper.setStatus(HttpServletResponseWrapper.java:224)
    Here is my web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
    http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    id="WebApp_ID" version="2.5">
    <display-name>JavaServerFaces</display-name>
    <!-- JSF mapping -->
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <!-- Map these files with JSF -->
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.jsf</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.faces</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>*.xhtml</url-pattern>
    </servlet-mapping>
    </web-app>
    Here is the pom.xml
    <project xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
    http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>JavaServerFaces</artifactId>
    <packaging>war</packaging>
    <version>1.0-SNAPSHOT</version>
    <name>JavaServerFaces Maven Webapp</name>
    <url>http://maven.apache.org</url>
    <dependencies>
    <dependency>
    <groupId>com.sun.faces</groupId>
    <artifactId>jsf-api</artifactId>
    <version>2.1.7</version>
    </dependency>
    <dependency>
    <groupId>com.sun.faces</groupId>
    <artifactId>jsf-impl</artifactId>
    <version>2.1.7</version>
    </dependency>
    <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>jstl</artifactId>
    <version>1.2</version>
    </dependency>
    <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>servlet-api</artifactId>
    <version>2.5</version>
    </dependency>
    <dependency>
    <groupId>javax.servlet.jsp</groupId>
    <artifactId>jsp-api</artifactId>
    <version>2.1</version>
    </dependency>
    </dependencies>
    <build>
    <finalName>JavaServerFaces</finalName>
    <plugins>
    <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>2.3.1</version>
    <configuration>
    <source>1.6</source>
    <target>1.6</target>
    </configuration>
    </plugin>
    </plugins>
    </build>
    </project>
    I have exhausted several hours searching the web and constructing new projects with no luck. I understand that the StackOverflowError is produced from bad recursion calls and infinite loops, however I can't see this as the case here.
    My current dev stack is eclipse juno (oepe-12.1.1.2.1-juno-distro-win32-x86_64.zip), m2e-wtp, weblogic 12c, Java EE 6 using JSF 2.1
    *If I export the war file using eclipse (Right click the project -> Export -> WAR file) then manually deploy it via the weblogic admin counsel the app works as expected. As soon as I add the project to the server inside eclipse and start the server I can no longer view the page. I noticed that in the autogenerated_ear_ folder per my domain that each project project folder is actually empty.*
    Any help would me MUCH appreciated!!
    UPDATE - Solved the problem! After adding JSF 2.1 in the pom.xml the JSF 2.1 checkbox was checked in project facets, however it did not add the faces-config.xml to the project. I simple created a new xml file named faces-config.xml under the webapp folder and added the following xml:
    <?xml version='1.0' encoding='UTF-8'?>
    <faces-config xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
    http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd" version="2.1">
    <application></application>
    </faces-config>
    I hope this helps others!
    Edited by: 1006228 on May 15, 2013 8:21 PM
    Edited by: 1006228 on May 16, 2013 6:39 PM

    Hi.
    Try this http://oracleradio.blogspot.com/2012/01/error-durante-el-deployment-de-un.html
    It is in spanish, but the important part is that u may correct the issue, installing 11.1.1.5 with the Feature Pack.
    It seems to be happening with processes that have loop formed with boundary event inside a gateway circuit.
    Hope this helps.
    best

  • Weblogic 12c not picking up persistence unit in WAR

    I'm trying to get an example CRUD application to run on WebLogic 12c (for the app see: http://henk53.wordpress.com/2012/04/15/jsf2-primefaces3-ejb3-jpa2-integration-project/)
    So far the applications runs on JBoss AS 7.1, GlassFish 3.1.2 and TomEE beta 2. In all those application servers persistence.xml is picked-up, and processed so I'm at a loss what's wrong with WebLogic. I'm using Eclipse 3.7.2 and the Oracle WebLogic 12C WTP server adapter for the deployment.
    I'm getting the following exception:
    java.lang.IllegalArgumentException: No persistence unit named 'entityManager' is available in scope jsf_ejb_jpa. Available persistence units: []
         at weblogic.persistence.ModulePersistenceUnitRegistry.getPersistenceUnit(ModulePersistenceUnitRegistry.java:130)
         at weblogic.persistence.BasePersistenceContextProxyImpl.<init>(BasePersistenceContextProxyImpl.java:40)
         at weblogic.persistence.TransactionalEntityManagerProxyImpl.<init>(TransactionalEntityManagerProxyImpl.java:31)
         at weblogic.persistence.EntityManagerInvocationHandlerFactory.createTransactionalEntityManagerInvocationHandler(EntityManagerInvocationHandlerFactory.java:20)
         at weblogic.persistence.PersistenceManagerObjectFactory.createPersistenceContextProxy(PersistenceManagerObjectFactory.java:66)
         at weblogic.persistence.PersistenceManagerObjectFactory.getObjectInstance(PersistenceManagerObjectFactory.java:31)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:251)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
         at weblogic.j2eeclient.java.ClientReadOnlyContextWrapper.lookup(ClientReadOnlyContextWrapper.java:35)
         at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at javax.naming.InitialContext.doLookup(InitialContext.java:265)
         at com.oracle.pitchfork.inject.Jsr250Metadata.jndiLookup(Jsr250Metadata.java:307)
         at com.oracle.pitchfork.inject.Jsr250Metadata.resolveByName(Jsr250Metadata.java:303)
         at com.oracle.pitchfork.inject.Jsr250Metadata.resolve(Jsr250Metadata.java:266)
         at com.oracle.pitchfork.inject.Jsr250Metadata.applyInjections(Jsr250Metadata.java:228)
         at com.oracle.pitchfork.inject.Jsr250Metadata.inject(Jsr250Metadata.java:219)
         at com.oracle.pitchfork.spi.BaseComponentBrokerImpl.getBean(BaseComponentBrokerImpl.java:63)
         at com.oracle.pitchfork.spi.EjbComponentCreatorBrokerImpl.getBean(EjbComponentCreatorBrokerImpl.java:33)
         at weblogic.ejb.container.injection.EjbComponentCreatorImpl.getBean(EjbComponentCreatorImpl.java:76)
         at weblogic.ejb.container.manager.BaseEJBManager.createNewBeanInstance(BaseEJBManager.java:209)
         at weblogic.ejb.container.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:235)
         at weblogic.ejb.container.manager.StatelessManager.createBean(StatelessManager.java:293)
         at weblogic.ejb.container.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:185)
         at weblogic.ejb.container.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:114)
         at weblogic.ejb.container.manager.StatelessManager.preInvoke(StatelessManager.java:174)
         at weblogic.ejb.container.internal.BaseLocalObject.getBeanInstance(BaseLocalObject.java:146)
         at weblogic.ejb.container.internal.BaseLocalObject.preInvoke(BaseLocalObject.java:103)
         at weblogic.ejb.container.internal.BaseLocalObject.__WL_preInvoke(BaseLocalObject.java:67)
         at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:20)
         at com.example.dao.jpa.JpaUserDAO_wrkew_UserDAOImpl.add(Unknown Source)
         at com.example.backing.IndexBacking.addUser(IndexBacking.java:38)
    Notice that "entityManager" is the name of the instance variable in which injection is being performed:
    @PersistenceContext(name="example")
    private EntityManager entityManager;
    If I rename this variable to "em: as follows:
    @PersistenceContext(name="example")
    private EntityManager em;
    Then, lo and behold, the exception changes into:
    java.lang.IllegalArgumentException: No persistence unit named 'em' is available in scope jsf_ejb_jpa. Available persistence units: []
    As the example uses a data-source defined in web.xml, which is only marginally supported in most application servers, I tried to define a WebLogic specific application scoped data-source instead and let the persistence unit use that. I couldn't find a way to do this in a .war (is this even possible?), so I created an .ear archive instead. When deploying the EAR, the data-source is clearly being created, but I'm getting the same exception again.
    I finally created an EJB module with a persistence.xml and a simple Singleton that's injected with the entityManager, and added that to the EAR. This works for the EJB module, but in the web module injection of the other entity manager still fails.
    Any idea what might be the problem?

    After some more fiddling, I discovered it's not WebLogic itself that's at fault here, but most likely Oracle's WTP adapter. Apparently it doesn't include persistence.xml in the archive that gets deployed. When I export the project as an .ear archive and copy this to WebLogic's autodeploy directly, things do work.
    I tried to find out what the main difference was between the deployments, but I could not find where the Oracle WTP adapter creates the deployment. I tried to test where a resource inside the EAR resides on the filesystem via the following code inside a backing bean:
    URL url = Thread.currentThread().getContextClassLoader().getResource("com/example/backing");
    It looks like there isn't a real .war or .ear being created and deployed, but there's a link back to the workspace, as the URL resolves to:
    file:/Users/henk/eclipse37ee/workspace/jsf_ejb_jpa/build/classes/com/example/backing/
    If I execute the same code for the ear in the autodeploy folder, the URL resolves to some jar inside:
    /Users/henk/eclipse37ee/wls1211_dev/mydomain/servers/myserver/tmp/_WL_user/_appsdir_jsf_ejb_jpa_ear_ear/2jzks6/war/WEB-INF/lib/
    In case of the WTP 'deployment' linking back to the Eclipse workspace, META-INF/persistence.xml is actually there too, but for some reason Weblogic can't find it there?
    Edited by: Henk on Apr 29, 2012 2:57 PM

  • Problem in installing GoldenGate Director on weblogic 12c

    hello friends,
    we have a server with weblogic 12c and a basic domain namely "base_domain" on it.(i have no earlier experience about weblogic).its path is "D:\Oracle\Middleware_HOME\wlserver_12.1"
    i can start its AdminServer and we can login to its console.
    now i want to install GoldenGate Director Server.but in installing  process when i set Weblogic location it gives me error :
    "Please Select a valid weblogic install Directory"
    i tried all of these paths :
    "D:\Oracle\Middleware_HOME\wlserver_12.1"
    "D:\Oracle\Middleware_HOME"
    "D:\Oracle"
    but the error remains yet.
    i installed weblogic on another machine but nothing changed.
    another thin is that i checked all places that oracle documents tells that should be updated
    i mean :
    1 Update the registry.xml file in Weblogic home directory to point to the
    correct WebLogic Server home directory.
    2 Update all of the scripts under %WLS_SERVER_HOME%/server/bin and %WLS_
    SERVER%/common/bin to point to the correct WebLogic Server home directory.
    3 Update the .product.properties file under %WLS_SERVER_HOME% to point to the
    correct WebLogic Server home directory.
    1 & 2 are correct (i think) but i couldn't find third one "product.properties"
    please help me.
    Whats the problem?
    weblogic Servers : Windows Server 2008 64-bit SP2  and Windows Seven Ultimate 64bit
    Weblogic version : oepe-indigo-installer-12.1.1.0.1.201203120349-12.1.1-win32
    GoldenGate Director : gg-director-serversetup_win_v11_1_1_1_0_001

    You should specify the middle-ware home direction.
    The error normally caused by the wrong version installed, which doesn’t have the correct registry.xml in MW_HOME. I met this problem in the past which is because I installed a dev version of WLS in zip file.
    After I install the installable version( I think it is the same version you used: oepe-indigo-installer-12.1.1.0.1.201203120349-12.1.1-win32.exe of WLS, it works fine.

  • Weblogic 12c Servlet Response - Special characters show up as question mark

    My web app is running on Weblogic 12c (12.1.1) using WebWork + Hibernate. The program streams data (bytes making up a pdf) from a CLOB in an Oracle Database to the AsciiStream of the servlet output response. No exceptions are thrown, but the generated pdf contains blank pages. Comparing the bytes of the generated pdf, special characters are showing up as question marks.
    Some of the bytes read in from the database contain 8 bits (correct data), but the bytes that the servlet return contain only 7 (all bytes with 8 bits become "1111111"). The number of bytes returned from the servlet is correct.
    Code:
    //Response is HttpServletResponse
    response.setContentType("application/pdf");
    response.setHeader("Content-Disposition", "inline; filename=\"test.pdf\"");
    out = response.getOutputStream();
    byte[] buf = new byte[16 * 1024];
    InputStream in = clob.getAsciiStream();
    int size = -1;
    while ((size = in.read(buf)) != -1){
    // buf contains the correct data
    out.write(buf, 0, size);
    // other exception handling code, etc
    out.flush();
    out.close();
    "Correct" pdf byte example:
    10011100
    10011101
    1010111
    1001011
    1101111
    11011011
    Incorrect pdf byte example:
    111111
    111111
    1010111
    1001011
    1101111
    111111
    I have verified that the data read from the CLOB in the database IS correct. My guess is that the Weblogic server has some strange servlet settings that causes the bytes to be written to the servlet output stream incorrectly, or a character encoding issue. Any ideas?
    Edited by: 944705 on Jul 26, 2012 10:17 AM

    Solution found, I'll post the work around to those who might encounter the same problem.
    Somewhere in the layers of technology (webwork or weblogic I'd guess), the servlet response is encoded into UTF-8 regardless. The encoding in the database was ISO-8859-1. Sending ISO encoded bytes by UTF-8 caused the conflicting character codes (anything above 127) to show up as undefined.
    The fix is to decode the input byte array into ISO-8859 string, then encode that string into UTF-8, which can be send by Weblogic.
    isoConvert = new String(buf, "ISO-8859-1");
    out.write(isoConvert.getBytes("UTF-8"), 0, isoConvert.getBytes("UTF-8").length);

  • Error invoking WebService in Eclipse with WebLogic 12c plugin

    I am using Eclipse Indigo with WebLogic 12c plugin to create a standalone WebService Client which invokes a simple WebService. The WebService is protected by Security Policies Wssp1.2-2007-Wss1.0-X509-Basic256.xml and Wssp1.2-SignBody.xml.
    I get the following exception when I run the standalone client:
    h2. Exception in thread "main" java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider could not be instantiated: java.lang.ExceptionInInitializerError
    The same program works fine using JDeveloper 11g but not in Eclipse Indigo or in Juno. Has anyone faced this issue?
    Thanks,
    Madhav

    The stand-alone client JAR file does not, however, support invoking Web services that use the following advanced features:
    Web services reliable SOAP messaging
    Message-level security (WS-Security)
    http://docs.oracle.com/cd/E14571_01/web.1111/e13760/client.htm#i229632
    Can you try running by adding weblogic.jar. but if you run the client inside the wls Server it should work.
    Regards,
    Sunil P

  • Oracle weblogic 12c problem

    Hello,
    After you install the 32bit version of Oracle WebLogic 12c , jdevstudio11115install (Windows 7 32 bit platform) . These actions come after the installation of the domain ADF 's and then completed the installation.
    I receive the following error when I run startWebLogic.cmd. ( What is the solution. )
    WARNING: Opening of file based farm keystore failed.
    oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06514: Openin
    g of file based farm keystore failed.
    at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKe
    yStore(FileKeyStoreManager.java:351)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.do
    Init(FileKeyStoreServiceImpl.java:101)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
    nit>(FileKeyStoreServiceImpl.java:73)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
    nit>(FileKeyStoreServiceImpl.java:63)
    at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(Ke
    yStoreProvider.java:157)
    at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(Ke
    yStoreProvider.java:64)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServ
    iceInstance(ContextFactoryImpl.java:139)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getConte
    xt(ContextFactoryImpl.java:170)
    at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getConte
    xt(ContextFactoryImpl.java:191)
    at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getCo
    ntext(JpsContextFactoryImpl.java:132)
    at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getCo
    ntext(JpsContextFactoryImpl.java:127)
    at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.
    java:850)
    at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.
    java:844)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyS
    tore(PolicyUtil.java:844)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:291)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:284)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
    vaPolicyProvider.java:270)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
    onstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.lo
    adOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
    itialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:148)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    <Dec 12, 2011 11:43:27 AM EET> <Error> <Security> <BEA-090892> <The loading of O
    PSS java security policy provider failed due to exception, see the exception sta
    ck trace or the server log file for root cause. If still see no obvious cause, e
    nable the debug flag -Djava.security.debug=jpspolicy to get more information. Er
    ror message: oracle.security.jps.JpsException: [PolicyUtil] Exception while gett
    ing default policy Provider>
    <Dec 12, 2011 11:43:27 AM EET> <Critical> <WebLogicServer> <BEA-000386> <Server
    subsystem failed. Reason: weblogic.security.SecurityInitializationException: The
    loading of OPSS java security policy provider failed due to exception, see the
    exception stack trace or the server log file for root cause. If still see no obv
    ious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more in
    formation. Error message: oracle.security.jps.JpsException: [PolicyUtil] Excepti
    on while getting default policy Provider
    weblogic.security.SecurityInitializationException: The loading of OPSS java secu
    rity policy provider failed due to exception, see the exception stack trace or t
    he server log file for root cause. If still see no obvious cause, enable the deb
    ug flag -Djava.security.debug=jpspolicy to get more information. Error message:
    oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default p
    olicy Provider
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.lo
    adOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
    itialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:148)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsExcep
    tion: [PolicyUtil] Exception while getting default policy Provider
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:293)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:284)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
    vaPolicyProvider.java:270)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
    orAccessorImpl.java:39)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while gettin
    g default policy Provider
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyS
    tore(PolicyUtil.java:899)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:291)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:284)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
    vaPolicyProvider.java:270)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    Truncated. see log file for complete stacktrace
    Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsExcep
    tion: [PolicyUtil] Unable to obtain default JPS Context!
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyS
    tore(PolicyUtil.java:844)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:291)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:284)
    at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(Ja
    vaPolicyProvider.java:270)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain defau
    lt JPS Context!
    at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.
    java:860)
    at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.
    java:844)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyS
    tore(PolicyUtil.java:844)
    at oracle.security.jps.internal.policystore.PolicyDelegationController.<
    init>(PolicyDelegationController.java:291)
    Truncated. see log file for complete stacktrace
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06
    514: Opening of file based farm keystore failed.
    at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKe
    yStore(FileKeyStoreManager.java:351)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.do
    Init(FileKeyStoreServiceImpl.java:101)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
    nit>(FileKeyStoreServiceImpl.java:73)
    at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<i
    nit>(FileKeyStoreServiceImpl.java:63)
    at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(Ke
    yStoreProvider.java:157)
    Truncated. see log file for complete stacktrace
    >
    <Dec 12, 2011 11:43:30 AM EET> <Notice> <WebLogicServer> <BEA-000365> <Server st
    ate changed to FAILED.>
    <Dec 12, 2011 11:43:30 AM EET> <Error> <WebLogicServer> <BEA-000383> <A critical
    service failed. The server will shut itself down.>
    <Dec 12, 2011 11:43:33 AM EET> <Notice> <WebLogicServer> <BEA-000365> <Server st
    ate changed to FORCE_SHUTTING_DOWN.>
    Note: JDeveloper 11.1.2.1 and 11.1.1.5.0 install but it did not work.
    C:\oracle\Middleware\user_projects\domains\base_domain\config\fmwconfig\bootstrap\cwallet.sso I have full authority, but did not work folder. (permissions full controll)
    Edited by: 889612 on 12.Ara.2011 07:06

    I am having the exact same issue with Weblogic 12c on Windows Server 2003 SP1 on Intel Itanium processor with Java SE 1.6u29 and JDeveloper 11.1.2.1.0.
    Please advise!
    Thanks in advance.
    P.S.
    Unfortunately, problem also confirmed on Windows 7 64bit and JRockit-jdk1.6.0_29-R28.2.0-4.1.0 and JDeveloper 11.1.2.1.0.
    LOG
    WARNING: Failed to save farm keystore. Reason {0}
    Dec 12, 2011 10:51:29 PM oracle.security.jps.internal.keystore.file.FileKeyStore
    Manager createKeyStore
    WARNING: Failed to save farm keystore. Reason {0}
    oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.create KeyStore(FileKeyStoreManager.java:309)
    Edited by: rade.radenkovic on Dec 12, 2011 1:53 PM

  • Override Spring jar in Weblogic 12c

    Hi Folks,
    We have been facing an issue while overriding the Spring jar in Weblogic 12c. Basically we need to write a bean based on some 3rd party API calling their interfaces. Now they use Spring 2.5 jar for their own implementation. Since Weblogic inherently supports Spring 3.0 jar. As a result when we write our bean wrapping their interfaces and deploy it, it doesn't work. We replicated the issue by replacing Spring 2.5 jar with Spring 3 in local environment.
    If we modify the server classpath to load the Spring 2.5 jar (preceding Spring 3.0), entire soa-infra application goes down, so what We wanted to know if it is possible to override the Spring jar only for our application itself? While loading the application it will override the Spring 3.0 jar with Spring 2.5 in the application context but server will keep using Spring 3.0?
    Any ideas/suggestions highly appreciated!
    Thanks,
    Bhaskar

    Hi Bhaskar,
    have you tried packing the Spring libraries in your application and using the Filterring Classloader? Maybe this links can help you :
    Understanding WebLogic Server Application Classloading
    http://docs.oracle.com/cd/E24329_01/web.1211/e21049/weblogic_xml.htm#WBAPP601
    http://stackoverflow.com/questions/11476874/weblogic-10-3-5-overriding-spring-version
    best regards, Nicolas

  • Javax.jms.InvalidSelectorException occurs when upgrade to weblogic 12c

    Recently, our team upgrade weblogic server from 11g to 12c,  some errors occur when start web application in weblogic domain.
    The error is related to message driven bean,  below is the part of  ejb-jar.xml definition:
      <message-driven id="message-driven_1">
          <description>Message Driven Bean</description>
          <display-name>Message Configuration (MDB)</display-name>
          <ejb-name>Logger</ejb-name>
          <ejb-class>com.logging.mdb.Logger</ejb-class>
          <messaging-type>javax.jms.MessageListener</messaging-type>
          <transaction-type>Container</transaction-type>
          <message-destination-type>javax.jms.Queue</message-destination-type>
          <activation-config>
                <activation-config-property>
                    <activation-config-property-name>messageSelector</activation-config-property-name>
                    <activation-config-property-value>DELIVERY='IMMEDIATE'</activation-config-property-value>
                </activation-config-property>
                <activation-config-property>
                    <activation-config-property-name>acknowledgeMode</activation-config-property-name>
                    <activation-config-property-value>Auto-acknowledge</activation-config-property-value>
                </activation-config-property>
                <activation-config-property>
                     <activation-config-property-name>destinationType</activation-config-property-name>
                     <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
                </activation-config-property>
          </activation-config>
      </message-driven>
    When start application below errors show up:
    <Dec 18, 2013 6:24:05 AM PST> <Warning> <EJB> <SLC02PGO> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1387376645415> <BEA-010061> <The Message-Driven EJB Logger is unable to connect to the JMS destination edx/queue/logger. The Error was:
    javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
    Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
    Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
    Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
    Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "DELIVERY='IMMEDIATE'"
    ####<Dec 18, 2013 6:24:15 AM PST> <Warning> <EJB> <SLC02PGO> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1387376655414> <BEA-010096> <The Message-Driven EJB MessageDispatcher is unable to connect to the JMS destination or bind to JCA resource adapter edx.queue.outbound. The onnection failed after 124 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
    It works well in weblogic 11g,   not sure whether there's any changes in weblgic 12c.
    I'm appreciate if there's someone can help me on this issue.
        <message-driven id="message-driven_1">
          <description>Message Driven Bean</description>
          <display-name>Message Configuration (MDB)</display-name>
          <ejb-name>Logger</ejb-name>
          <ejb-class>com.edocs.fs.logging.mdb.Logger</ejb-class>
          <messaging-type>javax.jms.MessageListener</messaging-type>
          <transaction-type>Container</transaction-type>
          <message-destination-type>javax.jms.Queue</message-destination-type>
          <activation-config>
            <activation-config-property>
              <activation-config-property-name>messageSelector</activation-config-property-name>
              <activation-config-property-value>DELIVERY='IMMEDIATE'</activation-config-property-value>
            </activation-config-property>
            <activation-config-property>
              <activation-config-property-name>acknowledgeMode</activation-config-property-name>
              <activation-config-property-value>Auto-acknowledge</activation-config-property-value>
            </activation-config-property>
            <activation-config-property>
              <activation-config-property-name>destinationType</activation-config-property-name>
              <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
            </activation-config-property>
          </activation-config>
          <resource-ref id="ResRef_Logger_1">
            <res-ref-name>jdbc/LoggerDataSource</res-ref-name>
            <res-type>javax.sql.DataSource</res-type>
            <res-auth>Container</res-auth>
          </resource-ref>
        </message-driven>

    Hi,
    I debug the application, I found my @ViewScoped ManagedBeans, they're recreated after you click a button or select a item in combobox
    Here is a piece of code:
        @PostConstruct
        public void resolveEntity() {
            Object sEntity = FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("entity");
            entity = (BctTbOportunidade) sEntity;
             FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove("entity");
            if (entity == null) {
                entity = new BctTbOportunidade();
    I use @postConstruct to get a entity from another page in sessionMap(I set a item from a table and use this method to modify a entity in a other page).
    When I click a button or select a item in combobox in same page @PostConstruct method is called but values are lost. No Exceptions are thrown by server.
    I found a artice written by BalluC that some versions of jsf 2.1 has this behavior The BalusC Code: The benefits and pitfalls of @ViewScoped
    I already configured my web.xml to set false javax.faces.PARTIAL_STATE_SAVING 
    But this behavior continues.
    The jsf version deployed in my weblogic 12c is 2.1.7.

  • Weblogic 12c : Spring taglib No tag library could be found with this URI

    Hello,
    I have an application which deploy perfectly on JBOSS 7 and Websphere
    My WAR includes WEB-INF/lib/spring-webmvc.jar which contains all .tld files declaration (stardard stuff up to now....)
    When I try to acces ths page (JSP) I got : No tag library could be found with this URI
    Really don't know why ??

    I think that there is bug in JSP precompilation by weblogic 12c maven plugin and appc. Seems me that jsp compiler can lose sometimes tag libraries it's precompiling. Next retry using exactly same pom can be successful. I get same results using command line and OEPE 12.1.1.0 mave(pom). My java options for maven package are(-Xmx1024m -Xms1024m -XX:PermSize=512m).
    When I get the error it's something like
    "Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:appc (default) on project ui_elements:
    There are 1 nested errors:
    weblogic.utils.compiler.ToolFailureException: jspc failed with errors :weblogic.servlet.jsp.CompilationException: naviButtons.tag:23:6: The tag handler class was not found "jsp_servlet._tags.__pagelink_tag".
    <T:pageLink url="${naviStatus.previousPage.linkUrl}"
    ^--------^
    naviButtons.tag:23:6: The tag handler class was not found "jsp_servlet._tags.__pagelink_tag".
    <T:pageLink url="${naviStatus.previousPage.linkUrl}"
    Failed to execute goal com.oracle.weblogic:wls-maven-plugin:12.1.1.0:appc (default) on project ui_elements:"
    Next unsuccessful compilation can mention different tags. Very irregular behavior.
    Do you have resolution?

  • CDI Fails when deployed twice from OEPE 12c to WebLogic 12c

    Hi,
    First when I use CDI on WebLogic 12c it works the first time without any problems , First I had to do this ( From Steve Button ) else I get some inject problems
    Just as an out there kind of thought, OEPE does use the split-directory model for deployment by default -- perhaps try adjusting it to use the exploded archive model instead, just as a test to see if it removes the error?
    Right click the server config and select Properties > WebLogic > Publishing > Publish as exploded archive
    then it works once , when I deploy it twice then the Named beans are not found. ( I use a empty beans.xml in the web-inf )
    I need to restart the wls 12c then it works. Same project with OEPE 12c and glassfish works fine.
    thanks

    Arun,
    Do you see the application status active in the Admin console?
    Are you testing the web application by typing the complete URL in the browser that includes the name of the webpage including the context root , ipaddress/hostname and port number of Server..?
    404 indicates application doesn't exist.
    Please share the URL you are testing.
    Please check the server log if you found any deployment issues when deploying your application?
    Thanks,
    Vijaya

Maybe you are looking for