BEA WLS and OraclePoolConnection

Hi,
Using the Oracle (9i) JDBC OCI driver, i am trying to get a proxy
connection going in BEA WLS.
If i define the connection pool using the Oracle classes in my program
everything is fine (i can get a connection and then proxy as as another
user). But if I define the pool using the Weblogic console then I have a
ClassCastException after doing a the lookup().
InitialContext initial = new InitialContext();
// HERE the classcastexception :
OracleOCIConnectionPool ds =
(OracleOCIConnectionPool) initial.lookup("jdbc/OracleOciDS");
oracle.jdbc.OracleConnection conn = null;
Properties p = new Properties();
p.setProperty(PROXY_USER_NAME, username);
conn = ds.getProxyConnection( PROXYTYPE_USER_NAME, p);
OracleOciDS is an OCI Connection pool (defined via the WLS console) and it's
working ok if I don't try to use the ProxyConnection mechanism of the JDBC
OCI.
If I do everything "by hand" without defining the Datasource in the BEA WLS console (using Oracle example), it's ok but the best would be to use the BEA console to do the administration and monitoring of the pool.
Thanks.
Real Gagnon from Quebec, Canada
* Looking for Java or PowerBuilder snippets ? Visit Real's How-to
* http://www.rgagnon.com/howto.html
* http://www.rgagnon.com/bigindex.html

Hi,
I am facing the same problem. Any luck on this?

Similar Messages

  • Re: BEA WLS and OraclePoolConnection

    Any examples about using Oracle proxy connection inside Bea Weblogic
    would be very welcomed.
    1 - Tell the Weblogic server what you want for your pool:
    Say what DBMS driver to use, and the URL and properties it
    needs etc. Define the DataSource for connecting to the pool
    2 - Read the Weblogic documentation on how to obtain the Datasource for
    the pool.
    What ClassCastException do you get?InitialContext initial = new InitialContext();
    // HERE the classcastexception :
    OracleOCIConnectionPool ds =
    (OracleOCIConnectionPool) initial.lookup("jdbc/OracleOciDS");
    oracle.jdbc.OracleConnection conn = null;
    Properties p = new Properties();
    p.setProperty(PROXY_USER_NAME, username);
    conn = ds.getProxyConnection( PROXYTYPE_USER_NAME, p);
    OracleOciDS is an OCI Connection pool (defined via the WLS console) and it's
    working ok if I don't try to use the ProxyConnection mechanism of the JDBC
    OCI.
    Bye.
    * Real Gagnon from Quebec, Canada
    * Looking For Java Or PowerBuilder Snippets? Visit Real's How-to
    * http://www.rgagnon.com/howto.html
    * http://www.rgagnon.com/bigindex.html

    Real Gagnon wrote:
    Any examples about using Oracle proxy connection inside Bea Weblogic
    would be very welcomed.
    1 - Tell the Weblogic server what you want for your pool:
    Say what DBMS driver to use, and the URL and properties it
    needs etc. Define the DataSource for connecting to the pool
    2 - Read the Weblogic documentation on how to obtain the Datasource for
    the pool.
    What ClassCastException do you get?InitialContext initial = new InitialContext();
    // HERE the classcastexception :
    OracleOCIConnectionPool ds =
    (OracleOCIConnectionPool) initial.lookup("jdbc/OracleOciDS");Ok, you aren't going to be getting direct access to Oracle classes when you connect to
    weblogic via our data sources. The actual oracle objects are in the server jvm, and
    aren't serializable across the net to your client.
    Joe
    >
    >
    oracle.jdbc.OracleConnection conn = null;
    Properties p = new Properties();
    p.setProperty(PROXY_USER_NAME, username);
    conn = ds.getProxyConnection( PROXYTYPE_USER_NAME, p);
    OracleOciDS is an OCI Connection pool (defined via the WLS console) and it's
    working ok if I don't try to use the ProxyConnection mechanism of the JDBC
    OCI.
    Bye.
    * Real Gagnon from Quebec, Canada
    * Looking For Java Or PowerBuilder Snippets? Visit Real's How-to
    * http://www.rgagnon.com/howto.html
    * http://www.rgagnon.com/bigindex.html

  • Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?

    Hello
    Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
    Thanks

    Hi a,
    The short answer is no B or R yet, but stay tuned.
    The somewhat longer story is that we are very much engaged with this
    emerging binding standard to be used inconjuction with and beyond the
    built-in types specified in JAX-RPC 1.1, it should be seen as a
    compelling story for J2EE if JAXB could be used as a mechanism for
    extending type mapping and offer a vendor neutral way to deal with user
    defined types and to easily utilize user types that are developed for
    XML applications in web services.
    Concerning JAXR, I've experimented with SUN's RI using our UDDI server
    and it works fine. As to the arguable merits of JAXR, all I can say is
    that it is part of J2EE 1.4.
    HTHs,
    Bruce
    a wrote:
    >
    Hello
    Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
    Thanks

  • PageFlow Bea 9 and BIRT

    hello!
    I'm trying to integrate in one project my old bea8 sp5 project updated with the workshop to bea 9.2 AND reports in eclipse BIRT.
    i have build a war app with reports in this new bea 9.2, and it works fine, but it needs the
    <wls:container-descriptor>
    <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
    </wls:container-descriptor>
    OR
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    modification into weblogic.xml, to work properly.
    in the other hand, i have my old app made in workshop 8 sp5, imported in the new enviroment. It works just fine too.
    but, when i try to join both, i need to add the
    container-descriptor tag in the updated application (where i am making the mixture) to get access to reports pages, then i have an error:
    Module named 'prototipo' failed to deploy.
    weblogic.application.ModuleException:
    where prototipo is the name of the old app, updated to w9.
    the complete stack trace in log file is
    ####<19-jul-2006 16H27' GMT-03:00> <Error> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254341> <BEA-149265> <Failure occured in the execution of deployment request with ID '1153337225730' for task '0'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
         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.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
         at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
         at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
         at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
         at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at java.lang.Class.newInstance0(Class.java:350)
         at java.lang.Class.newInstance(Class.java:303)
         at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
         at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
         at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
         at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
         at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
         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.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254856> <BEA-149004> <Failures were detected while initiating distribute task for application 'prototipo'.>
    ####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254872> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
         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.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
         at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
         at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
         at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
         at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
         at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at java.lang.Class.newInstance0(Class.java:350)
         at java.lang.Class.newInstance(Class.java:303)
         at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
         at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
         at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
         at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
         at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
         at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
         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.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    data that could help
    i tried change weblogic.xml with "wls:" form, and without it. i don't understand the difference... but in both cases nothing changed.
    i search for LogFactoryImpl class in jar files and i had find one, so i delete it from webcontent/web-inf/lib, but the problem stills goes on.
    if all the code and jar files are together but prefer-web-inf-classes tag is not used, i have no deployment error, but i can't view reports, of course.
    the application has pageflows, ejb's and controls, from bea products. and when i imported it, i choose use beehive in the options.
    BIRT version is 2.1.0
    JDK version jdk150_04
    weblogic.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:wls="http://www.bea.com/ns/weblogic/90">
         <wls:container-descriptor>
              <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
         </wls:container-descriptor>
         <context-root>procesoIngreso</context-root>
         <wls:library-ref>
              <wls:library-name>jstl</wls:library-name>
              <wls:specification-version>1.1</wls:specification-version>
              <wls:implementation-version>1.1.2</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>beehive-controls-1.0-war</wls:library-name>
              <wls:specification-version>1.0</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>weblogic-controls-1.0-war</wls:library-name>
              <wls:specification-version>1.0</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>struts-1.1</wls:library-name>
              <wls:specification-version>1.1</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>struts-1.2</wls:library-name>
              <wls:specification-version>1.2</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>beehive-netui-resources-1.0</wls:library-name>
              <wls:specification-version>1.0</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
         <wls:library-ref>
              <wls:library-name>beehive-netui-1.0</wls:library-name>
              <wls:specification-version>1.0</wls:specification-version>
              <wls:implementation-version>1.0</wls:implementation-version>
         </wls:library-ref>
    </wls:weblogic-web-app>
    The original weblogic.xml (when workshop imports the old project) was
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns="http://www.bea.com/ns/weblogic/90"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
         <jsp-descriptor>
              <debug>true</debug>
         </jsp-descriptor>
         <url-match-map>
              weblogic.servlet.utils.SimpleApacheURLMatchMap
         </url-match-map>
         <context-root>procesoIngreso</context-root>
         <!-- container-descriptor>
              <prefer-web-inf-classes>true</prefer-web-inf-classes>
         </container-descriptor> -->
         <library-ref>
              <library-name>struts-1.1</library-name>
              <specification-version>1.1</specification-version>
              <implementation-version>1.0</implementation-version>
         </library-ref>
         <library-ref>
              <library-name>beehive-netui-resources-1.0</library-name>
              <specification-version>1.0</specification-version>
              <implementation-version>1.0</implementation-version>
         </library-ref>
         <library-ref>
              <library-name>beehive-netui-1.0</library-name>
              <specification-version>1.0</specification-version>
              <implementation-version>1.0</implementation-version>
         </library-ref>
         <library-ref>
              <library-name>jstl</library-name>
              <specification-version>1.1</specification-version>
              <implementation-version>1.1.2</implementation-version>
         </library-ref>
    </weblogic-web-app>
    procesoIngreso is the name of war module of the j2ee app.
    web.xml file is:
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>Workshop Application</display-name>
    <description/>
    <servlet>
    <description/>
    <servlet-name>action</servlet-name>
    <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
    <init-param>
    <description/>
    <param-name>config</param-name>
    <param-value>/_pageflow/struts-config.xml</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>config/-global</param-name>
    <param-value>/_pageflow/struts-config--global.xml</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>debug</param-name>
    <param-value>2</param-value>
    </init-param>
    <init-param>
    <description/>
    <param-name>detail</param-name>
    <param-value>2</param-value>
    </init-param>
    <load-on-startup>2</load-on-startup>
    </servlet>
    <welcome-file-list>
    <welcome-file>index.html</welcome-file>
    <welcome-file>index.htm</welcome-file>
    <welcome-file>index.jsp</welcome-file>
    <welcome-file>default.html</welcome-file>
    <welcome-file>default.htm</welcome-file>
    <welcome-file>default.jsp</welcome-file>
    </welcome-file-list>
    <error-page>
    <error-code>500</error-code>
    <location>/error.jsp</location>
    </error-page>
    <jsp-config>
    <taglib>
    <taglib-uri>netui-tags-html.tld</taglib-uri>
    <taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>netui-tags-databinding.tld</taglib-uri>
    <taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
    </taglib>
    <taglib>
    <taglib-uri>netui-tags-template.tld</taglib-uri>
    <taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
    </taglib>
    </jsp-config>
    <filter>
    <filter-name>PageFlowJspFilter</filter-name>
    <filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
    </filter>
    <filter>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
    <init-param>
    <param-name>response-code</param-name>
    <param-value>404</param-value>
    </init-param>
    </filter>
    <filter-mapping>
    <filter-name>PageFlowJspFilter</filter-name>
    <url-pattern>*.jsp</url-pattern>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowJspFilter</filter-name>
    <url-pattern>*.jspx</url-pattern>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.java</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.jsfb</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>*.jpfs</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <filter-mapping>
    <filter-name>PageFlowForbiddenFilter</filter-name>
    <url-pattern>/_pageflow/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    </filter-mapping>
    <listener>
    <listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
    </listener>
    <listener>
    <listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
    </listener>
    <servlet>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
    </servlet>
    <servlet-mapping>
    <servlet-name>action</servlet-name>
    <url-pattern>*.jpf</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>action</servlet-name>
    <url-pattern>*.do</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <url-pattern>*.xhr</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>XmlHttpRequestServlet</servlet-name>
    <url-pattern>*.render</url-pattern>
    </servlet-mapping>
    <-- MENU CONFIGURATION -->
    <context-param>
              <param-name>menuConfigLocation</param-name>
              <param-value>/WEB-INF/menu-config.xml</param-value>
         </context-param>
         <listener>
         <listener-class>net.sf.navigator.menu.MenuContextListener</listener-class>
         </listener>
    <-- END MENU CONFIGURATION -->
    <-- BIRT CONFIGURATION -->
    <context-param>
              <param-name>BIRT_VIEWER_LOCALE</param-name>
              <param-value>en-US</param-value>
         </context-param>
         <context-param>
              <param-name>BIRT_VIEWER_REPORT_ROOT</param-name>
              <param-value></param-value>
         </context-param>
         <!-- Absolute downloaded image/chart directory. Default to ${birt home}/report/images -->
         <context-param>
              <param-name>BIRT_VIEWER_IMAGE_DIR</param-name>
              <param-value></param-value>
         </context-param>
         <!-- Absolute engine log directory. Default to ${birt home}/logs -->
         <context-param>
              <param-name>BIRT_VIEWER_LOG_DIR</param-name>
              <param-value></param-value>
         </context-param>
         <servlet>
              <servlet-name>ViewerServlet</servlet-name>
              <servlet-class>org.eclipse.birt.report.viewer.servlets.ViewerServlet</servlet-class>
         </servlet>
         <servlet-mapping>
              <servlet-name>ViewerServlet</servlet-name>
              <url-pattern>/frameset</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>ViewerServlet</servlet-name>
              <url-pattern>/run</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>ViewerServlet</servlet-name>
              <url-pattern>/navigation</url-pattern>
         </servlet-mapping>
         <servlet-mapping>
              <servlet-name>ViewerServlet</servlet-name>
              <url-pattern>/toolbar</url-pattern>
         </servlet-mapping>
    <-- END BIRT CONFIGURATION -->
    </web-app>
    that's all i think that i cant give you, i guess...
    (all xml comments have not the "!" because in preview, those lines are not shown, for example <-- END BIRT CONFIGURATION -->)
    can you help me please with this issue?
    thank in advance.
    best regards
    julio

    julio,
    Hey I'm having the exact same problem when I add
    <wls:container-descriptor>
    <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
    </wls:container-descriptor>
    to my weblogic.xml??? Did you ever get a resolution for this problem if so can you help me out.
    Thanks,
    Greg

  • JAX-WS SOAPHandler can not deployed in BEA WLS 10.0 - Bug?

    Hi,
    currently I'm trying tp deploy a simple JAX-WS webservice with JAX-WS SOAPHandler in BEA WLS 10.0.
    Therefore I provide a WAR file with the webservice and handler classes.
    The SOAP Handler is defined in the webservice via the @HandlerChain(file="handler.xml")
    My handler.xml looks as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <javaee:handler-chain>
    <javaee:handler> <javaee:handler-class>com.bmw.wss.server.handler.AuthenticationHandler</javaee:handler-class>
    </javaee:handler>
    </javaee:handler-chain>
    </javaee:handler-chains>
    This handlers.xml is in the classpath within the WAR file.
    If i trying to deploy this WAR file I always get the following exception from BEA WLS 10:
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "WSAATestService" failed to preload on startup in Web application: "wsaa-jaxwshandlertest.war".
    java.lang.NullPointerException
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsHandlers(WseeRuntimeMBeanManager.java:108)
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsPort(WseeRuntimeMBeanManager.java:80)
    at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsMBean(WseeRuntimeMBeanManager.java:57)
    I seems BEA WLS 10 has some problems with the JAX-WS SOAPHandler. I've deployed the same WAR-file on a Glassfish v2 server... without any problems!
    Does anyone already used the JAX-WS handler mechanism in BEA WLS 10? Any ideas?
    Thx.

    Hi,
    thx for your answer. Now I've found the problem. The BEA WLS don't accept null return value of the SOAPHandler method getHeaders(). If I return a dummy object everything wotks fine:
    public Set<QName> getHeaders() {
    return new TreeSet<QName>();
    However I think this behaviour of the BEA WLS 10 is some kind of strange. Why do I have to implement the method getHeaders() if I don't want to use it.
    Sun's Glassfish allows a null return value like expected.

  • What BEA WLS for Oracle 10.2.0.4?

    Hi,
    I'm going migration DB from 9.2.0.6 with BEA WLS 8.1 SP2 to 10.2.0.4 and I would like what's the certificate version of BEA WLS target.
    Thanks!

    You have already posted this in the correct forum - Upgrade Oracle DB from 9.2.0.6 to 10.2..0.4
    This forum is meant for issues related to database upgrades - pl clarify your question in your other post. AFAIK, there is no co-relation between database upgrades and WLS upgrades - but I have no expertise in WLS
    HTH
    Srini

  • BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction, so I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now I receive the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
    start() failed on resource 'OracleDB' Unexpected error during start for XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

    Hi Klaus,
    if you want to implement a global transaction over two different JDBC Resource Managers
    (update on both + 2PC) they have to be both XA compliant.
    Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
    for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
    and configuring a TXDataSource with "enable two-phase commit" = true (but only one
    non-XA JDBC driver at a time can participate in a distributed transaction).
    Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
    transactions or distributed transactions without XA drivers as well (using a single
    resource manager).
    But if you want to update multiple resource managers in the same transaction using
    EJBs, this is a "global" transaction, and WL server fully supports it.
    But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
    Sergi
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    >
    Hi Sergi, hello world,
    thanks a lot for this message. So the conclusion is that I hava no chance
    at all
    to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
    a prerequisite
    for EJB are XA-transactions.
    Is this conclusion correct.
    Many thanks again
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    distributed transaction (XA) features require version
    Oracle8i release 8.1.6 or later of the Oracle server.
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hi Sergi,
    1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
    2.) I didn´t use a special driver but that that was delivered with thewls
    server
    in the package "weblogic.jar".
    Could I enable you helping me with this information?
    Best wishes
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    which
    1) Oracle server version (I don't think it's a 8.3.2.)
    2) Oracle JDBC driver version
    are you you using ?
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction,so
    I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now
    I
    receive
    the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating itsSQL
    Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction
    branch
    start() failed on resource 'OracleDB' Unexpected error during start
    for
    XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

  • Embedded WLS and JDev 12.1.2: java.lang.OutOfMemoryError: PermGen space

    This problem happens after about 10-15 application restarts during development phase. I have read somewhere that this was a known bug in 11g versions of JDev and its integrated WLS (10.3.5 or 10.3.6?). I have then increased memory parameters in configuration file. The only thing I achieved is that this crash now occurs later then sooner. Still very frustrating. When this happens I have to restart WLS and sometimes kill frozen JDeveloper.
    Any other idea/workaround?
    <Dec 30, 2013 12:37:04 PM CST> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:ADFOracleReports@ADFOracleReports-FwkExtensions-context-root, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
    <Dec 30, 2013 12:37:04 PM CST> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:ADFOracleReports@ADFOracleReports-ViewController-context-root, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
    <Dec 30, 2013 12:37:22 PM CST> <Warning> <HTTP> <BEA-101162> <User defined listener org.apache.myfaces.trinidadinternal.webapp.TrinidadListenerImpl failed: java.lang.OutOfMemoryError: PermGen space.
    java.lang.OutOfMemoryError: PermGen space
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
      at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
      at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
      Truncated. see log file for complete stacktrace
    >
    <Dec 30, 2013 12:37:33 PM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1388428621416" for task "10". Error is: "weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space"
    weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space
      at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.OutOfMemoryError: PermGen space
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
      at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
      at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
      Truncated. see log file for complete stacktrace
    >
    <Dec 30, 2013 12:37:33 PM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application "ADFOracleReports".>
    <Dec 30, 2013 12:37:33 PM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "ADFOracleReports".>
    <Dec 30, 2013 12:37:33 PM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space
      at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.OutOfMemoryError: PermGen space
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
      at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
      at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
      at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
      Truncated. see log file for complete stacktrace
    >
    [12:37:53 PM] Cancel requested
    [Application ADFOracleReports stopped and undeployed from IntegratedWebLogicServer]
    <Dec 30, 2013 12:37:53 PM CST> <Error> <Deployer> <BEA-149062> <The task containing ID 10 cannot be canceled, since it has already completed execution.>
    <Dec 30, 2013 12:37:53 PM CST> <Warning> <RMI> <BEA-080003> <A RuntimeException was generated by the RMI server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
    javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution..
    javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution.
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839)
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852)
      at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:821)
      at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
      at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:375)
      Truncated. see log file for complete stacktrace
    Caused By: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution.
      at weblogic.management.deploy.DeploymentTaskRuntime.prepareToCancel(DeploymentTaskRuntime.java:881)
      at weblogic.management.deploy.DeploymentTaskRuntime.cancel(DeploymentTaskRuntime.java:854)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      Truncated. see log file for complete stacktrace
    >

    You can try to change the garbage collector algorithm. Refere to http://bexhuff.com/2012/09/jdeveloper-memory-and-performance
    Timo

  • Which BEA WLS version (+ service packs) used which JDK/JRockit-JDK version

    Hello,
    I'm looking for an overview about the JDK and JRockit JDK versions which are used in the different BEA WLS versions.
    Specialy im interested on all BEA WLS server versions (incl. the different Service Packs) starting with version 7.0.
    The overview should contain the following information if possible:
    - BEA WLS Version Number including SP
    - Plattform (Windows, HPUX, Solaris, ...)
    - JDK version
    - JRockit JDK version
    Here is an example (??? = I do not know currently):
    WLS vers. (incl. SP)|Plattf.|JDK vers.|JRockit vers.
    7.0.1 |Solaris|??? |???
    8.1.5 |Windows|1.4.2_08 |rockit81sp5_142_08
    9.2 MP1 |HPUX |??? |???
    Thanks a million if somebody could provide me those information. :-x
    Cheers,
    Markus Jessl

    Please check :
    http://edocs.bea.com/platform/suppconfigs/index.html
    Jin

  • ANNOUNCE: BEA WLS 6.0 Beta available

    ANNOUNCE: BEA WLS 6.0 Beta available
    We are proud to announce that the BEA WebLogic Server version 6.0 public
    beta has begun. You can download the Beta at http://commerce.BEA.com. The
    Beta is free and open to anyone.
    More information can be found at the above URL.
    Thanks,
    Michael
    Michael Girdley
    BEA Systems Inc

    Hi,
              why wasn't that email sent to weblogic.announce??
              I'm starting to believe weblogic.annouce is truly useless since neither
              service packs nor betas are announced there. What is the official way of
              monitoring releases of SP,etc. from bea?
              Mathieu
              Michael Girdley wrote:
              >
              > ANNOUNCE: BEA WLS 6.0 Beta available
              >
              > We are proud to announce that the BEA WebLogic Server version 6.0 public
              > beta has begun. You can download the Beta at http://commerce.BEA.com. The
              > Beta is free and open to anyone.
              >
              > More information can be found at the above URL.
              >
              > Thanks,
              > Michael
              >
              > --
              > ----
              > Michael Girdley
              > BEA Systems Inc
              

  • Jdeveloper, WLS and Log4j logging

    All,
    I want to route all the ADF application log messages to a log file using log4j.
    I have created a log4j.properties and put in the ViewController/src folder. The application finds that config file, and produces the desired output - so far, so good.
    Now I would like to route all the WLS logging using log4j.
    To first try it, I've opened the integrated WLS console, and set, under server/logging, that the log implementation uses log4j instead of jdk. I have also checked the "redirect stdout", "redirect stderr", and "logging bridge" check boxes.
    I've also:
    - included the wllog4j.jar and log4j-1.2.16.jar in the classpath (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file).
    - put a copy of log4j.properties also in the WLS path - which is, in my case: /home/semar/Oracle/Middleware/wlserver_10.3/server/bin
    - put the path of the log4j.properties in the WLS CLASSPATH (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file)
    I've then re-started the integrated wls, and now what happens is:
    - the log appender for my application is no more found (log4j complains that the appender is not configured)
    - no log file is produced/updated
    Am I missing something obvious here ? Where should I put the log4j.properties then ? Are other extra tasks I should perform, in order to get all the ADF and WLS logging routed through log4j, and configured using a single log4j property file ?
    I'm using WLS 10.3.5.0 and Jdeveloper 11g rel 2 11.1.2.1.0, running on a Linux OpenSuse 11.4
    Sergio.

    Still no joy.
    I have put the two JARs + log4j.properties into domain_root/lib folder.
    I have also modified the startWeblogic.sh by adding the following:
    JAVA_VM="${JAVA_VM} -Dlog4j.configuration=${DOMAIN_HOME}/lib/log4j.properties"
    export JAVA_VM
    Both the .jar files and the log4j.properties are in the classpath and in the java options of the WLS starting log.
    In my application I have:
    package logging;
    import org.apache.log4j.Logger;
    import...
    public class loggingBean {
    /* Get actual class name to be printed on */
    Logger log = Logger.getLogger(loggingBean.class.getName());
    public loggingBean () {
    System.out.println("hello from loggingBean constructor");
    //_logger.info("Creating a new instance");
    log.debug("Hello this is a debug message");
    log.info("Hello this is an info message");
    In the log4j.properties I have:
    # Define the root logger with appender file
    log = /tmp
    log4j.rootLogger = DEBUG, FILE
    # Define the file appender
    log4j.appender.FILE=org.apache.log4j.FileAppender
    log4j.appender.FILE.File=${log}/log.out
    # Define the layout for file appender
    log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
    log4j.appender.FILE.layout.conversionPattern=%m%n
    # end of the log4j.properties
    And in the standard log file (nohup.out since I start the server with it):
    <11.04.2012 14:56 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <hello from loggingBean constructor>
    <11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN No appenders could be found for logger (logging.loggingBean).>
    <11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN Please initialize the log4j system properly.>
    <11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.>
    The file /tmp/log.out does not exist.
    Any thought ?
    Sergio.

  • JCOM and BEA support and license issues

    After going round and round with first tier support, I'd like to post this message
    to the newsgroup to clarify how jCOM finds the license.bea file.
    Here is an e-mail I sent to support...
    The beahomelist file gets created in a bea directory in the user's home directory
    ($HOME/bea/beahomelist).
    The problem is that the WebLogic server and the Jcom classes are looking for the
    license in two different ways.
    WLS uses the $BEA_HOME variable and jCOM uses the user.home System property (this
    may or may not be $HOME).
    Your were incorrect when you stated that the WebLogic server needs to runnning by
    the user that installed the software. Any user can start the server and use the
    jCom classes as long as jCom can find the license, this requires that the user wanting
    to use jCOM have a bea directory and beahomelist file in the directory that the user.home
    system property resolves to.
    It would be much easier for jCOM users to have the server and jcom find the license
    in the same manner.
    You've been so helpful.

    "Michael Jones" <[email protected]> wrote:
    >
    After going round and round with first tier support, I'd like to post this
    message
    to the newsgroup to clarify how jCOM finds the license.bea file.
    Here is an e-mail I sent to support...
    The beahomelist file gets created in a bea directory in the user's home
    directory
    ($HOME/bea/beahomelist).
    The problem is that the WebLogic server and the Jcom classes are looking
    for the
    license in two different ways.
    WLS uses the $BEA_HOME variable and jCOM uses the user.home System property
    (this
    may or may not be $HOME).
    Your were incorrect when you stated that the WebLogic server needs to runnning
    by
    the user that installed the software. Any user can start the server and
    use the
    jCom classes as long as jCom can find the license, this requires that the
    user wanting
    to use jCOM have a bea directory and beahomelist file in the directory that
    the user.home
    system property resolves to.
    It would be much easier for jCOM users to have the server and jcom find
    the license
    in the same manner.
    You've been so helpful.
    Hi Michael,
    thanks a lot!! this was the right hint!!
    Michael

  • Com.bea.wls.EJBGenException

    Hi All,
    I have recently started to work on ejb's,I have created a project that has 2 modules
    and ejb and a web module.
    I am trying to use ANT to build my application.But here is the problem that I don't understand..
    when I try to compile using ANT,I get the following error
    com.bea.wls.EJBGenException:Error:Couldn't determine the type of the EJB 'xx.xx.path..XXBean'
    Please make sure that :
    -Its an Enterprise Java Bean
    -Its superclass is in your classpath
    Now as far as I can see I know that its an entity bean..
    here is tags
    * @ejbgen:entity
    * ejb-name = "LoginBean"
    * data-source-name = "DevDataSource"
    * table-name = "LOGIN"
    * prim-key-class="java.lang.Long"
    * enable-call-by-reference = True
    * default-transaction = Required
    I know the parent class is accesible totherwise my IDE would scream that it can not extend it....
    Please some one help me and elaborate what exactly is missing thats causing this

    I have a totaly seprate question to put forward to you so I hope you dont mind. I was rather interested in this posting that you made sometime ago:
    http://forum.java.sun.com/thread.jsp?thread=454215&forum=31&message=2070364
    Is there any chance I could get a sample of the complete code you have done?
    I would greatly appreciate it.
    Many thanks -

  • Diferences between BEA Framework and Beehive

    Hi,
    Anyone can tell me what are the main diferences, in terms of functionalities, between BEA Framework and Beehive?
    Thanks,
    rjc

    You'd probably have to be a little more specific to get a better answer, but I can try to provide some information.
    I don't know what you mean by the "BEA framework". That could mean lots of things. Beehive is a framework for building web applications. It requires JDK 5. In WLS 9 and Workshop 9, Beehive is part of the "BEA framework". In WLS 8.1, Workshop applications use the NetUI framework, the functionality of which has been subsumed into Beehive.

  • WLS and WLE

    What is difference between WLS and WLE?
    Thanks
    harden

    WLS is the WebLogic Server which is primarily a J2EE compliant APP
    Server. Applications can only be written in Java(or shall I say-- can
    primarily be written in Java ). WLS comes originally from WebLogic, the
    company that BEA bought.
    WLE is a CORBA compliant ORB and the TUXEDO TP engine packaged into
    one.It has nothing to do with the original company WebLogic-BEA renamed
    it from M3 to WLE. BEA bought ObjectBroker from DEC and TUXEDO I think
    from AT&T and merged them together. They have made the recent version
    J2EE compliant.
    WLE enables cross-platform/cross language development.It supports Java,
    C++, Active X clients and server currently. (You can have a Java Client
    talking to a C++ Server. BEA advertises WLE for medium to large
    enterprise systems and WLS for others especially web based applications
    Ram Ramesh
    [email protected]
    www.cicube.com
    A BEA Solutions Partner
    hzhu wrote:
    What is difference between WLS and WLE?
    Thanks
    harden

Maybe you are looking for

  • "The volume for "IMAGE.JPG" cannot be found" problem when importing images

    This first started when I hooked up my card reader to my mac. I'd get the above image when I tried to import files off of it. My options are" - Cancel - Find Photo- - OK - OK = Nothing. It flashes and stays. Find Photo = Navigating to the image, (all

  • Oracle Linux 6.1 asm packages - oracleasm and oracleasmlib for OEL 6.1 ???

    Hello everyone I am not ULN subscriber, I am trying to learn Oracle ASM/RAC at work. I am running OEL 6.1 (uname -rm output is: 2.6.32-100.34.1.el6uek.x86_64) I am looking for two ASM support libraries which are compatible with above Oracle Linux 6.1

  • Getting Error while trying to create table using entity beans

    This is the output on console. javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; neste d exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExcepti on: [Oracle][ODBC][Ora]ORA-00942: table or view does not

  • Oracle Email Server - Ofcguard problem

    I always get ORA-28575 error from the log file after I start the ofcguard daemon. The oracle email server is install together with my 9ias in a machine where the 8i db server is on other server, I actaully have read the technet and metalink that prov

  • Stupid is as stupid asks...

    Hi I am new and embarrassed to write in the forum asking silly questions. Thing is I am learning all from scratch without help from anyone. I have created a database (have previous knowledge only from Access) and have managed to create a beautiful re