Error using weblogic.deploy tool, while deploying a war

          Hi all, I'm trying to deploy a war with the follw command:
          java weblogic.deploy -host localhost -port 7001 -component NewScreenWar:BEAserver
          deploy beasystem NewScreenWar d:\newsscreen\weblogic\NewScreenWar.war
          It gives me following error:
          weblogic.j2ee.DeploymentException: Application NewScreenWar does not contain com
          ponent NewScreenWar at weblogic.deploy.deploy(deploy.java:668) at weblogic.deploy.runBody(deploy.java:358)
          at weblogic.utils.compiler.Tool.run(Tool.java:79) at weblogic.deploy.main(deploy.java:1601)
          Application NewScreenWar does not contain component NewScreenWar
          how do I resolve this...??
          thanx --anjaly
          

Hi,
For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
see...
http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
thank you
/michael
www.eclipselink.org

Similar Messages

  • How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

    Hi,
    I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
    Regards,
    Neeraj

    Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
    Could you try the t3 protocol, for example,
    java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

  • Weblogic 8.1 and Eclipse using Weblogic Server Tools

    I am working on a project that has been developed with Weblogic 8.1 without integration into an IDE (Eclipse, etc.) We are trying to convert the source tree to a form usable within Eclipse using Weblogic Server Tools. We want to make deployment on developer workstations quicker and easier and provide for server side debugging. There is not much documentation on how to do this that I have been able to find. I have just finished reading the details of the split directory strucuture in the Weblogic documentation and understand that Server Tools uses the split directory concept. My question is basically how we create the project in Eclipse (with Server Tools plug-ins) initially. Is anyone out there still using Weblogic 8.1 and Eclipse 3.3 (Europa) using Weblogic Server Tools that can help?

    There isn't much in a way of documentation that's explicit to WebLogic Server Tools, but a lot of Workshop 10.2 documentation applies. Basically, you will want to create Dynamic Web Projects to house your code. On the first page of Dynamic Web Project wizard, you will get a chance to define and target a server (WLS 8.1 in your case). That will configure your project classpath for WLS 8.1 and get everything else squared away.
    Note that there is only very basic support for 8.1. In particular, the split-directory concept is not supported, but deployment is taken care of for you behind the scenes, so the details shouldn't matter that much.

  • Error in using the Socket Adapter while deploying the composite

    I am going through a Socket Adapter sample given in Oracle JCA Adapters for Sockets"Oracle Socket Adapter Hello World".
    This sample demonstrates inbound request/response and synchronous outbound request/response modes of communication using using Oracle Socket Adapter.
    The HelloWorld business process takes an input string from the Socket Adapter inbound service and
    publishes the message to the BPEL process.
    The BPEL process invokes the Socket Adapter outbound service and returns the received string using synchronous reply.
    Before going into this sample i did the configuration in the Weblogic server by following the steps below:-
    1)Log into Weblogic server console
    2)Click Deployments in the left pane for Domain Structure
    3)Click Socket Adapter.The settings for SocketAdapter page is displayed.
    4)Click the configuration tab
    5)Click the Outbound Connection Pools tab, and expand java.resource.cci.ConnectionFactory to see connection
    factories
    6)Click eis/socket/SocketAdapter
    7)Set the KeepAlive connection property to true
    8)Save the setting.
    After this i did the necessary configurations in the Socket Adapter Configuration Wizard(Inbound/Outbound).
    The BPEL process has:-
    1)A receive which receives input from a Socket Adapter which serves as an inbound synchronous service.
    2)An invoke acitvity which invokes a socket adapter which serves as a outbound synchronous service.
    3)Two Assign activites to do the necessary assignment.
    After Deploying the sample i encountered with the following errors:-
    <Sep 9, 2012 1:19:48 PM IST> <Error> <oracle.integration.platform.blocks.deploy.servlet> <SOA-21537> <Sending back error message: There was an error deploying the composite on soa_
    server1: [JCABinding] [Middleware.ServerConnection/6.0]Unable to complete unload due to: Cannot locate Java class oracle.tip.adapter.socket.SocketInteractionSpec: Cannot locate Jav
    a class oracle.tip.adapter.socket.SocketInteractionSpec..>
    Can any one please tell me the solution for this error.
    Edited by: 957910 on Sep 12, 2012 1:10 AM

    Did you find a solution for this issue. I see the same error while deploying the same very sample code.

  • Receiving ERRORS using WEBLOGIC.DEPLOY

    Hi everybody,
    I am getting strange errors when using the weblogic.deploy command-line
    function. I am using WL6.0 on W2000.
    Deploy/Update
    command: java weblogic.deploy -port 7001 -host localhost update
    beapasword MyWebApplication stage\MyWebApplication.war
    error: java.lang.NullPointerException
    at
    weblogic.deploy.deployApplication(deploy.java:383)
    at weblogic.deploy.deploy(deploy.java:340)
    at weblogic.deploy.runBody(deploy.java:219)
    at weblogic.utils.compiler.Tool.run(Tool.java:81)
    at weblogic.deploy.main(deploy.java:954)
    Undeploy
    Command: java weblogic.deploy -port 7001 -host localhost undeploy
    beapasword MyWebApplication
    error: giving up after two minutes
    And it looks that just a Update doens't work. I have to undeploy first and
    the do a update to see the changes I've made in my file.
    Any suggestions....
    M-

    Hi.
    WLS version and service pack level? Please post the entire weblogic.deploy command along
    with the exception that follows.
    Thanks,
    Michael
    Harjeet Singh wrote:
    I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
    on 7001. When I try to run it gives me following error:
    [java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: password
    system password is correct. I have tried http://localhost:7001 to but doesen't seem
    to work.
    Any ideas.
    HS--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • 'weblogic.application.ModuleException:'while deploying the EAR file to WLS

    Hi
    i am trying to deploy the ADf11g app on to external WLS 10.3 server.
    My WLS is having the shared libraries .so i didn't include the liibraries in WAR.
    while deploying i am facing errors.
    My domain log:
    Nov 12, 2008 2:40:30 PM EST     J2EE     Warning     BEA-160195     The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dep2EARapplication1 is not versioned.
         Nov 12, 2008 2:40:30 PM EST     HTTP     Error     BEA-101371     There was a failure when processing annotations for application F:\oracleWls\user_projects\domains\sailu1base_domain\servers\AdminServer\tmp\_WL_user\Dep2EARapplication1\6e738n\Dep2webapp1.war. Please make sure that the annotations are valid. The error is org.apache.myfaces.trinidad.webapp.ResourceServlet
         Nov 12, 2008 2:40:30 PM EST     Deployer     Error     BEA-149265     Failure occurred in the execution of deployment request with ID '1226518830484' for task '4'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root'' weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149004     Failures were detected while initiating deploy task for application 'Dep2EARapplication1'.
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149078     Stack trace for message 149004 weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) 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:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Console     Error     BEA-240003     init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         Nov 12, 2008 2:41:04 PM EST     netuix     Warning     BEA-423420     Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29.
    Can anyone plz tell me why i am getting errors.
    what is the 'weblogic.application.ModuleException:' error.
    and the HTTP error.

    Hi,
    My EAR file size is about 25 MB.this size is becoz of libraries.so i decided to make a jar file of all libraries.and i installed that jar as library on wls10.3. so that my ear apps later refer this jar.by this no need to include the libraries in every EAR and also size of ear is reduced.
    In my weblogic-application.xml file i refer this jar using the <library-ref> tag.when i am trying to install ear file i am facing this weblogic.application.ModuleException: error as posted above .
    Can you tell me where i went wrong.
    Is the way i am doing is right or not.

  • Application done using tomcat throwing eceptions while deploying in JBoss

    hi frds
    i devoloped an application using tomcat and its working fine. now i deploying the war generated by tomcat in JBOSS. after deploying application working fine with JBOSS also but the log contains the exception. the stack trace from log file is
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.WebModule] Starting jboss.web.deployment:war=LPCIntex.war,id=1039069946
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] webContext: null
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] warURL: file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp29121LPCIntex-exp.war/
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] webAppParser: org.jboss.web.AbstractWebDeployer$DescriptorParser@12c937c
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]}
    2007-11-20 12:06:47,234 INFO  [org.jboss.web.tomcat.tc5.TomcatDeployer] deploy, ctxPath=/LPCIntex, warUrl=file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp29121LPCIntex-exp.war/
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] AbstractWebContainer.parseWebAppDescriptors, Begin
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Creating ENC using ClassLoader: java.net.FactoryURLClassLoader@186dd93
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..org.jboss.mx.loading.UnifiedClassLoader3@ef9d00{ url=file:/C:/jboss-4.0.2/server/default/tmp/deploy/tmp29121LPCIntex-exp.war/ ,addedOrder=39}
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..org.jboss.system.server.NoAnnotationURLClassLoader@ab95e6
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..sun.misc.Launcher$AppClassLoader@e39a3e
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] ..sun.misc.Launcher$ExtClassLoader@a39137
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Linked java:comp/UserTransaction to JNDI name: UserTransaction
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] addEnvEntries
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkResourceEnvRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkResourceRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkMessageDestinationRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkEjbRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkEjbLocalRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkServiceRefs
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] linkSecurityDomain
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] No security-domain given, using default: java:/jaas/other
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Linking security/securityMgr to JNDI name: java:/jaas/other
    2007-11-20 12:06:47,234 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] AbstractWebContainer.parseWebAppDescriptors, End
    2007-11-20 12:06:47,281 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer] Using session cookies default setting
    2007-11-20 12:06:50,343 INFO  [org.apache.catalina.loader.WebappClassLoader] validateJarFile(C:\jboss-4.0.2\server\default\.\tmp\deploy\tmp29121LPCIntex-exp.war\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
    2007-11-20 12:06:50,625 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)/Tomcat-5.5'
    2007-11-20 12:06:50,671 INFO  [org.apache.struts.util.PropertyMessageResources] Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
    2007-11-20 12:06:50,671 INFO  [org.apache.struts.util.PropertyMessageResources] Initializing, config='org.apache.struts.action.ActionResources', returnNull=true
    2007-11-20 12:06:51,859 ERROR [org.apache.commons.digester.Digester] Parse Error at line 99 column 17: The content of element type "struts-config" must match "(display-name?,description?,data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
    org.xml.sax.SAXParseException: The content of element type "struts-config" must match "(display-name?,description?,data-sources?,form-beans?,global-exceptions?,global-forwards?,action-mappings?,controller?,message-resources*,plug-in*)".
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
         at org.apache.commons.digester.Digester.parse(Digester.java:1572)
         at org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1006)
         at org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
         at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
         at javax.servlet.GenericServlet.init(GenericServlet.java:211)
         at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
         at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
         at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857)
         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118)
         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
         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:585)
         at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
         at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.apache.catalina.core.StandardContext.init(StandardContext.java:5005)
         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:585)
         at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
         at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:274)
         at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91)
         at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
         at org.jboss.web.WebModule.startModule(WebModule.java:68)
         at org.jboss.web.WebModule.startService(WebModule.java:46)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:418)
         at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy28.start(Unknown Source)
         at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy8.deploy(Unknown Source)
         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
         at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
         at $Proxy0.start(Unknown Source)
         at org.jboss.system.ServiceController.start(ServiceController.java:418)
         at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy4.start(Unknown Source)
         at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
         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:585)
         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
         at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
         at $Proxy5.deploy(Unknown Source)
         at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
         at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
         at org.jboss.Main.boot(Main.java:195)
         at org.jboss.Main$1.run(Main.java:463)
         at java.lang.Thread.run(Thread.java:595)any workaround to stop the exception
    thanks
    R

    The error message seems pretty clear : the order of your XML elements in your struts config file is wrong.
    These XML elements must be in the order defined in the parenthesis after "must match".

  • Can any body help me in creating a jar using Weblogic server tool

    I have created the class files of the container manged bean successfully.I want to create the jar file using the weblogic tool.
    I have created a new jar file and now I have to add a bean class file and a home class file to it.In the tool I choose a the path using the choose button.When I say next it complaints that it cannot locate the bean files.
    Can any body please help me soon..
    waiting for your reply.

    I had similar problems with the WLS deploy tool. I think they were solved by making sure that I started the tool from the directory that contained the root package of my EJBs.
    It might work...

  • Deployment aborted while deploying a webdynpro application

    Hi SDNers,
    While deploying a webdynpro application deployment aborted and shown the following error.
    Aug 8, 2006 4:51:38 PM /userOut/deploy
    (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]]
    ERROR:
    [010]Deployment aborted
    Settings
    SDM host : incata90
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/veer/LOCALS1/Temp/temp9590TutWD_DynamicForm.ear
    Deployment exception : Server incata90 did not accept login request as apiadmin on port
    50018 - Cannot log in. There are already active sessions:
    Session id 8 / An administrator logged in via API /
    Inner exception was :
    Server incata90 did not accept login request as apiadmin on port 50018 - Cannot log in.
    There are already active sessions:
    Session id 8 / An administrator logged in via API /
    can somebody help me in resolving this problem?
    Regards
    Veeru

    Hi,
    Sometimes I get this error. It is usually solved by restarting the SDM server.
    Switch to the J2EE Engine view in NWDS and right click the SDM server. Restart process.
    Good luck,
    Roelof

  • Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

              Hi,
              I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
              to use Container Managed Transaction through a Session Bean.
              Connection Pool Settings: -------------------------
              Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
              TXDataSource Settings : -----------------------
              Name - myXADS
              JNDIName - myXADS
              PoolName - myXAPool
              Everything works fine but once in a while I get the following exception:
              java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
              in the transaction branch start() failed on resource 'myXAPool' Unexpected error
              during start for XAResource 'myXAPool': null
              The connection pool size is 30 and the number connections high reached was 5,
              which means there are enough connections in the pool available at all time.
              It would be really great if you can help me out.
              Thanks in Advance, Sudhir.
              

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • XA error: using Weblogic 6.1 and Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpected error
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reached was 5,
    which means there are enough connections in the pool available at all time.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • Error Using weblogic.jspc --- java.lang.ExceptionInInitializerError

    Hi,
              I am trying to use the weblogic.jspc compiler to pre-compile my jsp
              files so that I can verify that they compile w/o having to visit the
              page. I am using Weblogic 4.5.1. I am encountering the following
              error:
              java.lang.ExceptionInInitializerError
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Error.<init>(Compiled Code)
              at java.lang.LinkageError.<init>(Compiled Code)
              at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
              at java.beans.Beans.instantiate(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
              at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
              at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
              at weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled
              Code)
              at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
              at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
              at weblogic.jhtmlc.runBody(Compiled Code)
              at weblogic.jspc.runBody(Compiled Code)
              at weblogic.utils.compiler.Tool.run(Compiled Code)
              at weblogic.jspc.main(Compiled Code)
              Have any of you seen this? Can you tell me what I am doing wrong
              (Classpath, etc.)?
              Any and all help would be greatly appreciated.
              The command line I am using is:
              java -verbose -classpath
              $CLASSPATH:/apps/weblogic/license:/apps/weblogic/classes:/apps/weblogic/lib/weblogicaux.jar
              weblogic.jspc -d $HOME/weblogic/myserver/classfiles/examples
              100-Welcome.jsp
              Regards,
              Richard
              

    Fixed with a patch CR0737797 and CR062538 for the 6.1 sp3 source line
              Prasanna Yalam

  • Errors using weblogic sql driver: "No JDBC connection can be made because the transaction state is marked rollback"

    One of our customers starts to encounter this error message recently.
    We checked our log files. It seems that the error happens when
    to obtain a jdbc connection. Have anyone seen similar problems
    and knows how to fix it? thanks in advance.
    We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
    The functions that invoke the jdbc calls are stateless session bean
    methods with their transaction attributes marked as Required.
    There is no nested calls of these methods.
    A partial stack trace we obtained is as following:
    java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Marked Rollback
         at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    lixin

    Joseph Weinstein <[email protected]> wrote:
    >
    >
    YuanHui Liu wrote:
    Joe,
    We got the exact same error message. The error came after we got theJDBC connection,
    and trying to create statement off it.
    It occurs intermitently when we are running another standalone JAVAapp to do
    some end of day work, which results in the DB Server being very busy(90+%CPU
    usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
    pool. This would sometimes result in all our subsequent DB requeststo fail and
    lead to a crash.
    We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
    connection timeout that caused this(rather it is the end effect).
    Can you give us a more detailed explanation? Is there a miscommunicationbetween
    our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
    it's when the server is
    gettng the pool connection. For performance/synchronization reasons we
    do a clever
    delay: When your code asks for a pool connection we quickly give you
    the pool wrapper,
    but we delay actually reserving the real underlying DBMS connection until
    your first
    real need for a connection, at your first JDBC call, such as createStatement()
    etc.
    It is while waiting for a pool connection long enough for the transaction
    coordinator
    to have timed you out before you ever get a chance. It's nothing to do
    with the
    DBMS or even JDBC, I believe. I think the weblogic server either has
    too few execute-threads
    and/or too few CPU cycles to do the work load.
    Okay, so there's a lazy initialization of the connection.
    From reading our log I believe our failur is immediate rather
    than waiting for 30+ seconds(the default setting) from the DB,
    the timeout occurred later as a result. At the time either because the DB Server
    is very busy.
    Since we are running WLS6.0 we have only one connection pool,
    we have defined a max of 150 threads in the pool. While this
    is happening the DB Server is being pinned by an overnight job,
    but the WLS Server is not busy at all. The DB and WLS resides
    on different physical boxes.
    We also have a thread dump from the WLS console when we rebooted the server, it
    showed that we are hanging on to the thread & jdbc
    connections after these exceptions has occurred instead of releasing them, note
    "16083"(~4.5 hours) seconds has passed:
    142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
    [EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
    Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
    begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
    weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
    Scheduled Trigger
    So I would argue this problem actually chewed up resources on the WLS server.
    -Yuanhui Liu
    >>
    >>
    Thanks.
    -YuanHui Liu
    Joseph Weinstein <[email protected]> wrote:
    lixin wrote:
    One of our customers starts to encounter this error message recently.
    We checked our log files. It seems that the error happens when
    to obtain a jdbc connection. Have anyone seen similar problems
    and knows how to fix it? thanks in advance.
    We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
    The functions that invoke the jdbc calls are stateless session bean
    methods with their transaction attributes marked as Required.
    There is no nested calls of these methods.
    A partial stack trace we obtained is as following:
    java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Marked Rollback
    at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
    load
    issue. What is
    happening is that the transaction is started, and times out beforethe
    SSB even gets to
    the first JDBC work. I would first verify that the customer is using
    the very latest JVM
    available for the machine.
    Joe Weinstein
    at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
    at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
    at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    lixin

  • Error using "Rotate View Tool" and warning on load Photoshop CS4

    on load Photoshop send warning:
    "Photoshop has encountered a problem with the display driver, and has temporarily disabled GPU enhancements. Check the video card manufacturer's website for the latest software.
    GPU enhancements can be enabled in the Performance panel of Preferences."
    on using "Rotate View Tool" send error
    "Could not complete your request because it only works with OpenGL enabled document windows."
    Windows XP SP3
    VideoDriver: 178.24_geforce_winxp_32bit_international_whql
    Athlon 4400+
    GF 8600GT (OpenGL: 2.1, Shader model: 3)
    RAM: 2 gb.
    How to fix???
    Thanks!

    Hello,
    On CS4 with RADEON 9800 XT card and 256 MB DDR SGRAM/SDRAM and with AGP 8x capability and latest drivers (as of Nov.10) I can't get the Open GL feature to work (it is blanked out in Preferences) and it also says that "No GPU options available with Photoshop Standard" !!!
    Is this the case? I can't use the rotate tool, etc because I'm using PS standard and not Enhanced?
    Thanks, Dan

  • Error using BEx Analyzer - tools - 'copy sheet' function

    Hello,
    We are getting an error using BEx Analyzer, when we execute a query or workbook and select the 'copy sheet' function.  The error is:
    An error occurred when communicating with the BI Server
    As a result of this the system has been disconnected from the BI server.
    Exception Condition 'BAD_VALUE_COMBINATION' raised.
    We are using BEx Analyzer 7.10.
    Thanks very much.
    Gayle

    Hi
    Implement this note first
    Note 1086904 - BW 7.0 BEx: Transactions RRMX/RRMXP
    in case if nottting works
    Run the Same query in RSRT  transaction code , see if you get the same error.
    if you get the same error.
    Go to RSRT give the query name and Generate the query (using generate button in RSRT)
    hope this helps
    santosh
    Edited by: Santhosh Nagaraj on Oct 31, 2009 5:44 AM

Maybe you are looking for