Redeploying with 7.0.4 in redhat 7.3

I'm having some trouble with redeployment of ear files.
I'll describe what is happening:
1 - I deploy my appl, all works OK
2 - I make a few changes in the body of an auxiliary class
(not part of an Entity nor a Session)
3 - I make my ear from scratch, an recompile the jar file with ejbc
4 - I redeploy the application, no error is given, when I try to use
my new code, its using the old one
5 - If I stop the appl-server and restart it, all works fine.
I also removed de application and then redeployed it, and it has the
same problem.
Te appl-server is configured whith ProductionModeEnabled=false
Any help will be welcomed, thanks in advance

While I try to get a way to post to support (everybody is in holliday here), I
send
you a jar with the sources.
I suppose you won't get any trouble compiling it, just:
0 - cd to the directory where build.xml is
1 - Change build.properties
2 - Call "ant ear"
3 - call "bin/deploy.sh"
4 - to test "./run.sh test.PetClient create"
To see the problem, just change the string in the BasicBean.debug() method, redeploy,
run the test, and you will see the old version running.
Any help, I'll be every now and then watching the mailing-list.
Hope this is not to much trouble for you.
Thanks again.
Rob Woollen <[email protected]> wrote:
Thanks for the update.
Can you post an EAR file here that I can use to reproduce the problem?
It might take me a little while to look into it. If you want a quicker
response, you could open a case with [email protected]
-- Rob
Tonio Caputo wrote:
Rob,
I just forgot to tell you some important things:
In my previous mail I described what happened, when I used
an extra jar named "base.jar", but in my early tests I didn't use
BasicBean in a separate jarfile, I just included this class in my application
jar. Under this conditions all work perfectly well.
So I suppose there is some trouble unloading the jar files which arenot
the ones containing de EJB stuff.
Thanks again for your help.
Rob Woollen <[email protected]> wrote:
Thanks that would be very helpful for us to track down what's going
on.
-- Rob
Tonio Caputo wrote:
Hi Rob,
Yes I'm running "ejbc" on the jar file before generating the ear file.
What I'm going to do, is to write a very simple example
(no DB connection, etc...) with the same architecture of what I'm
doing
see what happens an tell you any news.
Thanks very much for your help, I'll be back as soon as I can.
Rob Woollen <[email protected]> wrote:
Interesting.
Are you running weblogic.ejbc on your ejb-jar before you upload the
new
version?
If not, please try this and let me know if it changes anything.
If you're still having problems, can you outline exactly (step by
step)
what you're doing and show me the output from the server?
If all else fails, I'll try to reproduce it here, and see if I cantrack
it down.
-- Rob
Tonio Caputo wrote:
Hi,
Another try, a new problem.
Now I modified my stateless session-bean "CbsProductosEjbSn", I
added
a new method
called "getAllPreciosForPremio(CbsPremioPKey pk, Date from, Date
to)"
When I deployed it I get an Exception:
Unable to deploy EJB: CbsProductosEjbSn from cbsEjb-compiled.jar:
Unable to bind a cluster-aware stateless session EJBObject to thename:
cbscbsEjb-compiled.jarCbsProductosEjbSn_EO.
Please ensure that the jndi-name in the weblogic-ejb-jar.xml is
correct.
The error was:
javax.naming.NamingException. Root exception is java.rmi.RemoteException:Failed
to parse descriptor file; nested exception is:
java.rmi.server.ExportException: Failed to export crm.appl.cbs.canje.ejb.CbsProductosEjbSn_7hot6v_EOImpl
problem with rmi descriptor signature getAllPreciosForPremio(Lcrm.appl.cbs.canje.bobj.CbsPremioPKey;Ljava.util.Date;Ljava.util.Date;)
Of course if I stop the server and restart it, all works fine.
I'm guessing, redeploying is not working at all, I hope this is
no
true.
As always, thanks in advance for your help.
[basic.jar]

Similar Messages

  • How to view and restore sharepoint 2013 designer workflows and how to redeploy with newer version to environments

    how to view and restore sharepoint 2013 designer workflows and how to redeploy with newer version to environments
    MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

    Hi,
    In SharePoint Designer 2010, we could not save the workflow as a template directly except the reusable workflow.
    However, in SharePoint Designer 2013, we can just save all the types workflow as a template, then you can import the workflow into the new environment.
    http://blogs.msdn.com/b/workflows_for_product_catalogs/archive/2012/11/02/deploying-a-workflow-on-a-different-server.aspx
    In SharePoint Designer 2013, every time we publish the workflow, we would get a newer version workflow, and the old workflow version would be overwritten.
    So, when you deploy the workflow in the environment, the workflow would the newer version.
    Thanks,
    Jason
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Jason Guo
    TechNet Community Support

  • Is Oracle Hyperion SQR Production Reporting certified with Oracle 12 on the redhat linux ?

    s Oracle Hyperion SQR Production Reporting certified with Oracle 12 on the redhat linux ?

    As per the support matrix Oracle 12 will be supported with 11.1.2.3.500. Check the support matrix at : Supported Platforms Matrices - Oracle Enterprise Performance Management System
    Thanks,
    KK

  • FTP Adapter redeployment with new plan

    We have a WebLogic development server (Admin server alone) which hosts the SOA Suite. The connection pools for the FTP Adapter was configured with its own deployment plan (Plan_FTPAdapter.xml). Now, we need to move to a cluster based environment with the Admin server and two managed servers in their own respective boxes. After installing the SOA suite in the cluster, I am trying to redeploy the FTP Adapter to use the deployment plan file extracted from the Dev environment. I get a NullPointerException when updating the deployment with this plan file. Any idea what's going wrong?
    ####<May 11, 2010 11:54:19 AM PDT> <Error> <Console> <xxxx.server> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4d078b1df33caaab:55c8672c:128887ad51b:-8000-0000000000000106> <1273604059367> <BEA-240003> <Console encountered the following error java.lang.NullPointerException
         at weblogic.deploy.internal.targetserver.DeployHelper.getState(DeployHelper.java:235)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.getState(AbstractOperation.java:747)
         at weblogic.deploy.internal.targetserver.operations.RedeployOperation.validatePrepare(RedeployOperation.java:156)
         at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:102)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<May 11, 2010 11:54:19 AM PDT> <Warning> <Deployer> <xxxx.server> <AdminServer> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <4d078b1df33caaab:55c8672c:128887ad51b:-8000-0000000000000107> <1273604059369> <BEA-149004> <Failures were detected while initiating update task for application 'FtpAdapter'.>
    ####<May 11, 2010 11:54:19 AM PDT> <Warning> <Deployer> <xxxx.server> <AdminServer> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <4d078b1df33caaab:55c8672c:128887ad51b:-8000-0000000000000107> <1273604059370> <BEA-149078> <Stack trace for message 149004
    java.lang.NullPointerException
         at weblogic.deploy.internal.targetserver.DeployHelper.getState(DeployHelper.java:235)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.getState(AbstractOperation.java:747)
         at weblogic.deploy.internal.targetserver.operations.RedeployOperation.validatePrepare(RedeployOperation.java:156)
         at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:102)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    To answer my own question, the Plan.xml has to be manually copied to all managed servers at the same location in the file system as in the Admin server. Found the information here - http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10231/life_cycle.htm#BABBEFFJ

  • Environnement with pro-cobol and linux redhat

    Hi,
    I have a linux redhat Linux 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
    and oracle 11g database where we have installed Pro-cobol with a launcher xframe ( not me !)
    we want to use command-line with pro-cobol :
    exemples :
    export COBOLOPTS="-dy -shared -M -lxconv -L$XFRAMEHOME/lib -I $PWD -WC,""DLOAD"" -WC,""SOURCE"" -WC,""COPY"" -WC,""XREF"" -WC,""FLAG(E)"" -WC,""MODE(STD)"" -WC,""ALPHAL(WORD)"" -WC,""NOTRUNC"" -WC,""NOSDS"" -WC,""SRF(FIX)"" -WC,""MAP"" -do ./ -dp ./ "
    cobol -o OV1SLSP.e OV1SLSP.pre OV1MADR0.o $ORACLE_HOME/precomp/lib/cobsqlintf.o OV1MADR1.pre.o OV1MSNT0.pre.o 2> OV1SLSP.errors
    execution:
    OV1SLSP.e
    results
    Erreur de segmentation
    we have a this error.
    but when we use xframe launcher :
    execution:
    xrun OV1SLSP
    results
    XRUN: STARTING OV1SLSP
    OV1MADR0 PLANTAGE SQL RNVP : -1012
    SQLERRMC ORA-01012: non connecté
    COBOL:rts: HALT: JMP0015I-U [PID:000004A0 TID:B7FFC940] CANNOT CALL PROGRAM 'COBCANC'. xvsamRts: undefined symbol: COBCANC PGM=OV1MADR0
    XRUN: TERMINATED WITH CODE 134
    =>This message is normal because we have connect to database !
    It's working perfect.
    My question is : what is the correct librairies to have to make static compiling pro-cobol's programs?
    hope to be cleared.
    Thanks.
    Edited by: french_dam on 28 janv. 2011 10:07
    Edited by: french_dam on 28 janv. 2011 10:11

    Have you checked the system requirements for using Pro-Cobol with Oracle 11g and Linux? See here:
    Pro*COBOL® Programmer's Guide 11g Release 1 (11.1)
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28428/pcoabops.htm#insertedID1
    Hope this helps,
    Ben

  • Problems with installing applications 11i on redhat 8.0

    Has anyone installed apps 11i on a redhat 8.0 box. With a lot of finagling I have managed to get the Rapid Install Wizard screen to appear but then ... nothing. It hangs with no indications of what is wrong. I do have DISPLAY set correctly. I have installed openmotif-2.1.30, but everything still hangs. There is no word on this site, technet, or metalink as to if this is even possible or if so how it can be done. Does anyone have any ideas?
    Thanks,
    Steve

    Exactly the same problem in the same environment.
    keep trying.
    Please let me know if you find something. I'll do the same,:).

  • Help with Oracle 9i/10g on RedHat 4?

    If anybody can help would be greatly appreciated...
    I get the same error with Oracle 9i & 10g when installing on Red Hat Fedora 4, it's java related...
    Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2007-03-16_01-09PM/jre/lib/i386/libawt.so: connat restore segment prot after reloc: Permission Denied
    Red Hat Fedora is weak on java, it only has the Java 1.4 JRE installed. I tried to upgrade to Sun's JRE 6 but got dependency errors.
    Jon

    Red Hat Fedora 4Does not exist.
    Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2007-03-16_01-09PM/jre/lib/i386/libawt.so: connat restore segment prot after reloc: Permission DeniedSolution 1: Modify /etc/selinux/config and change value of SELINUX to "disabled" and reboot computer.
    Solution 2: Upgrade selinux-policy-targeted-1.25.2-4.noarch.rpm (Use command: "yum upgrade selinux-policy-targeted")
    Red Hat Fedora is weak on java, it only has the Java 1.4 JRE installed. I tried to upgrade to Sun's JRE 6 but got dependency errors.??? OUI does not have to do with external JRE.
    Oracle Installation comes with bunled JRE.
    If you are using Fedora then you might consider these articles useful:
    http://ivan.kartik.sk/oracle/install_ora9_fedora.html
    http://ivan.kartik.sk/oracle/install_ora10gR2_fedora.html

  • Weblogic 10.3.3 Silent Install with registry corrupted message on Redhat 6.

    I successfully un-installed Weblogic that had been installed previously on the VM. Then I created silent.xml on the VM and attempted to install WL in Silent Mode but got the following error
    [root@VA33-PROOFAPP01 opt]# java -d64 -jar wls1033_generic.jar -mode=silent -silent_xml=/opt/scripts/silent.xml
    Extracting 0%....................................................................................................100%
    The local BEA product registry is corrupted. Please select another Middleware Home or contact Oracle Support
    Here is my silent.xml which looks correct.
    [root@VA33-PROOFAPP01 opt]# cat /opt/scripts/silent.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Silent installer option -mode=silent -silent_xml=/opt/scripts/silent.xml -->
    <bea-installer>
    <input-fields>
    <data-value name="BEAHOME" value="/opt/oracleHome" />
    <data-value name="WLS_INSTALL_DIR" value="/opt/oracleHome/weblogic10.3.3" />
    <data-value name="COMPONENT_PATHS" value="WebLogic Server/Core Application Server|WebLogic Server/Administration Console|WebLogic Server/Configuration Wizard and Upgrade Framework|WebLogic Server/Web 2.0 HTTP Pub-Sub Server|WebLogic Server/WebLogic JDBC Drivers|WebLogic Server/Third Party JDBC Drivers|WebLogic Server/WebLogic Server Clients|WebLogic Server/WebLogic Web Server Plugins
    |WebLogic Server/UDDI and Xquery Support|WebLogic Server/Server Examples|Oracle Coherence/Coherence Product Files" />
    <data-value name="INSTALL_NODE_MANAGER_SERVICE" value="no" />
    <data-value name="NODEMGR_PORT" value="5559" />
    </input-fields>
    </bea-installer>
    Any inputs would be greatly appreciated.
    Joe in South Carolina.

    Well i read another thread and got it solved by putting the value on the same line
    <data-value name="COMPONENT_PATHS"
    value="WebLogic Server/Core Application Server|WebLogic Server/Administration Console|WebLogic Server/Configuration Wizard and Upgrade Framework|WebLogic Server/Web 2.0 HTTP Pub-Sub Server|WebLogic Server/WebLogic JDBC Drivers|WebLogic Server/Third Party JDBC Drivers|WebLogic Server/WebLogic Server Clients|WebLogic Server/WebLogic Web Server Plugins|WebLogic Server/UDDI and Xquery Support|WebLogic Server/Server Examples|Oracle Coherence/Coherence Product Files" />
    Thanks for reading!
    Joe

  • Servlet redeploy with wls 5.1, sp9

    Hi,
              the "reload servlet" command doesn't seem to work from the console in
              wls 5.1: After pressing the corresponding button in the console, I get
              the message:
              <ServletContext-General> GatewayServlet: destroy
              ...but init(ServletConfig config) gets called only once: when the
              servlet is first loaded. After the destroy() call, the servlet is still
              able to process requests, but the init() method doesn't get called
              again...
              Any ideas?
              Javier
              

    [att1.html]
              

  • Oracle 8.0.5 not run on RedHat 5.9

    I have used Oracle 8.0.5 on RedHat 5.2 well.
    But I try to install it on another machine with RedHat 5.9,
    and the server halt with segment fault.
    Anyone know what is the problem?
    null

    I cannot seem to find that patch anywhere. Can someone direct
    me to it?
    Thanks.
    Rick Jolley (guest) wrote:
    : Oracle8i is being designed to work with glibc2.1. There is
    also a
    : patch for Oracle8 to work with glibc2.1 as well.
    : Michael Pilgrim (guest) wrote:
    : : RedHat's newest version 6.0 (or the beta version of 6.0,
    : : which is what 5.9 is) uses glibc 2.1. I haven't tried
    Oracle8
    : : on glibc 2.1 myself, but from what I've seen from others is
    : that
    : : Oracle8 is not compatible with glibc 2.1, and you must use
    : : something from the 2.0 series of glibc (and it must be at
    least
    : : 2.0.6). You'd have to use something like RedHat 5.2, which
    : comes
    : : with glibc 2.0.7. It would be interesting to see whether
    : : Oracle8i will work with glibc 2.1 and RedHat 6.0, especially
    : : since Oracle has become an investor/parter with RedHat.
    : : Maro (guest) wrote:
    : : : I have used Oracle 8.0.5 on RedHat 5.2 well.
    : : : But I try to install it on another machine with RedHat 5.9,
    : : : and the server halt with segment fault.
    : : : Anyone know what is the problem?
    null

  • Can't remove or redeploy one process on 10.1.3.5

    The 10.1.3.5.0 WEB BPEL Console appears to be different from the older one. I use to always be able to undeploy a BPEL process to clean up an deployment issue, but this new interface is different. I have one BPEL process which some how got deployed (sorta) on the server, and I can't get rid of it. The process has a yellow triangle showing and when I click on the triangle or process name I get the following WEB page:
    >
    ServerException
    The process handle "MSS_DEV_Master" (revision "2.6") has not been loaded. The process may have failed to load properly. Please use the method "getErrors" for more information.
    An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
    Build Information
    Oracle BPEL Server version 10.1.3.5.0
    Build: 0
    Build time: Thu Aug 06 22:23:54 PDT 2009
    Build type: release
    Source tag: PCBPEL_10.1.3.5.0_GENERIC_090806.2156.1900
    Exception Trace
    1. com.oracle.bpel.client.BPELProcessHandle.checkIfLoaded BPELProcessHandle.java@671
    2. com.oracle.bpel.client.BPELProcessHandle.getMetaData BPELProcessHandle.java@234
    3. displayProcess.jspService _displayProcess.java@96
    4. com.collaxa.cube.fe.JspPage.service JspPage.java@42
    5. javax.servlet.http.HttpServlet.service HttpServlet.java@856
    6. oracle.jsp.runtimev2.JspPageTable.service JspPageTable.java@473
    7. oracle.jsp.runtimev2.JspServlet.internalService JspServlet.java@594
    8. oracle.jsp.runtimev2.JspServlet.service JspServlet.java@518
    9. javax.servlet.http.HttpServlet.service HttpServlet.java@856
    10. com.evermind.server.http.ResourceFilterChain.doFilter ResourceFilterChain.java@64
    11. oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
    12. java.security.AccessController.doPrivileged
    13. javax.security.auth.Subject.doAsPrivileged Subject.java@517
    14. oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
    15. com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@644
    16. com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
    17. com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward ServletRequestDispatcher.java@280
    18. com.evermind.server.http.ServletRequestDispatcher.access$100 ServletRequestDispatcher.java@68
    19. com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun ServletRequestDispatcher.java@214
    20. oracle.oc4j.security.OC4JSecurity.doPrivileged OC4JSecurity.java@284
    21. com.evermind.server.http.ServletRequestDispatcher.forward ServletRequestDispatcher.java@219
    22. com.collaxa.cube.fe.DomainFilter.doFilter DomainFilter.java@231
    23. com.evermind.server.http.EvermindFilterChain.doFilter EvermindFilterChain.java@15
    24. oracle.security.jazn.oc4j.JAZNFilter$1.run JAZNFilter.java@400
    25. java.security.AccessController.doPrivileged
    26. javax.security.auth.Subject.doAsPrivileged Subject.java@517
    27. oracle.security.jazn.oc4j.JAZNFilter.doFilter JAZNFilter.java@414
    28. com.evermind.server.http.ServletRequestDispatcher.invoke ServletRequestDispatcher.java@642
    29. com.evermind.server.http.ServletRequestDispatcher.forwardInternal ServletRequestDispatcher.java@391
    30. com.evermind.server.http.HttpRequestHandler.doProcessRequest HttpRequestHandler.java@908
    31. com.evermind.server.http.HttpRequestHandler.processRequest HttpRequestHandler.java@458
    32. com.evermind.server.http.AJPRequestHandler.run AJPRequestHandler.java@313
    33. ...
    >
    How can I clear this up for the server? I tried redeploying with the same BPEL process and version, but that appears to be ignored (though the server says it was successful). I then got rid of the *.../bpel/domains/grc/tmp/{bpel suitcase folder}* but that didn't affect anything as well. Bouncing the 10g server after removing the TMP folder for the suitcase jar didn't do anything as well.
    Any suggestions would be appreciated.

    ok... please follow the below steps.
    go to your orabpel schema in the db and execute the below queries
    delete from process where process_id="BPEL_PROCESS_NAME"
    delete from process_descriptor where process_id="BPEL_PROCESS_NAME"
    delete from process_log where process_id="BPEL_PROCESS_NAME"
    delete from process_default where process_id="BPEL_PROCESS_NAME"
    and the rebounce the server.. you will not see that process in the BPEL Console

  • Problem installing weblogic 6.0 on Redhat 7.1

    When trying to begin the install proccess of 'WebLogic Server 6.0 with Service Pack 2 For Redhat 7.1sh filename.bin I get the following:"Preparing to install...The included VM could not be unarchived(tar). Please try to downloadthe installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy."I've allocated an alternate directory for use as a temporary directorywith export IATEMPDIR=tmpdirnameThis dir has over 26 gigs.Note the group name is below 8 charsDoes anyone have a solution to this? ThanksJubran

    Found it. Same problem as on Oracle 8.1.7 on RedHat 7.1.
    1. Install the compat* RPMs from the RedHat 7.1 CD1 and CD2. These RPMs
    allow compatibility with RedHat 6.2.
    2. Put the following two statements in your environment prior to running
    the install.
    export LD_ASSUME_KERNEL=2.2.5
    . /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh
    These two statements will allow you to run your shell in a 6.2 compatibility
    mode, for glibc 2.1.3 instead of the new glibc 2.2.2 libs.
    It sounds to me like Sun needs to update the JDKs to support the new glibc
    and the 2.4 kernel. I'm not sure this is even BEA's problem?
    Glen Austin
    OmniSYS, Inc.
    "Glen Austin" <[email protected]> wrote in message
    news:3b2e5873$[email protected]..
    I installed jdk 1.3.1 from java.sun.com on a RedHat 7.1 O/S.
    Originally, I was not pointing to the JDK correctly. I fixed the PATH,
    CLASSPATH, JAVA_HOME, JAVA_PATH to point to the jdk1.3.1 dir.
    Then I got an error saying that cut could not be found in /usr/bin, so I
    ln -s /bin/cut cut in the /usr/bin directory.
    I ran the install script a 3rd time and I'm seeing a [<defunct>] for myJava
    VM in a ps -aef entry, which is in the process list along with the WLS 6.0
    SP1 install bin file. I will try it one more time, but it's not looking
    good.
    Glen Austin
    "Henri Jubin" <[email protected]> wrote in message
    news:3b078ede$[email protected]..
    You need to install the JDK 1.3.1 to have wls 6.0 working.
    The JDK could be found at the developpers zone at javasoft.
    root <[email protected]> wrote:
    i tried installing the wls by using the command :
    sh weblogic600sp1_linux.bin
    i got the message ,
    "Preparing to install..."
    and thats where it stops !
    any ideas ??
    cheers
    Pac

  • Security Provider for a web dynpro with tool Visual Administrator

    Hello all,
    after deploying successfully my web dynpro on the J2EE 7.0 WAS, I'm trying to set up authentication to it but I cannot find my applicaiton in the list of policy configurations of the Security Provider entry. When I try to add the path to my local web dynpro, the engine doesn't find it.
    I have noticed that all other policy configurations reference a servlet_jsp application. Should I transform my web dynpro into a servlet_jsp? How do I do that?
    Thanks for your input,
    Tanguy Mezzano

    Hello Marcel,
    in fact, I don't succeed to redeploy with another provider name... I have undeployed my webdynpro with SDM on the Java stack, but from NWDS, when I change the application-j2ee-engine.xml and application.xml files, and that I rebuild the webdynpro, when I run and deploy, it always redeploys under the former provider: local.
    When I create the application, I tell to use the existing component, should I select create a new one, but that means that I have to rebuild the whole application.
    Will then the webdynpro be in the Security Provider list, so that I can configure it with http header?
    Thx for your help,
    Tanguy

  • JMS Adapter Config issues with Plan.xml

    Hi All,
    I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
    1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
    2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
    Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
    3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
    On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
    Oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
    The deployment plan reads as follows :
    <deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
    <application-name>connectors</application-name>
    <variable-definition>
    <variable>
    <name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
    <value>eis/wls/Queue</value>
    </variable>
    <variable>
    <name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
    <value>weblogic.jms.XAConnectionFactory</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>JmsAdapter.rar</module-name>
    <module-type>rar</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-connector</root-element>
    <uri>META-INF/weblogic-ra.xml</uri>
    <variable-assignment>
    <name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
    <xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
    <origin>planbased</origin>
    </variable-assignment>
    <variable-assignment>
    <name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
    <xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
    </variable-assignment>
    </module-descriptor>
    <module-descriptor external="false">
    <root-element>connector</root-element>
    <uri>META-INF/ra.xml</uri>
    </module-descriptor>
    <module-descriptor external="true">
    <root-element>wldf-resource</root-element>
    <uri>META-INF/weblogic-diagnostics.xml</uri>
    </module-descriptor>
    </module-override>
    <config-root>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
    </deployment-plan>
    Thanks
    JB
    Edited by: 939260 on Jun 20, 2012 5:13 AM

    Hi JB,
    Please follow the below steps from beginning...
    1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
    2. create new JMS Module.
    3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
    4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
    5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
    6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
    If you have followed the abpve steps correctly, you should not face any problem.
    Hope this helps,
    N

  • Corrupt blocks with RH6.2 and 8.1.7

    Hi
    We have following problem: while running Oracle 8.1.7 on a Compqa DL580 with Smartarray controller 5304 on RedHat 6.2 system we encounter corrupt data blocks after a certain time.
    We can see corrupt data blocks e.g after reboot, but also during normal operation. This happens again and again after some weeks after we had reinstalled the database. Oracle support lead us to install RH6.2 (after having the problems on 7.1), but it crashed again ...
    Any tips?
    System details:
    kernel 2.2.19-6.2.7
    glibc 2.1.3-22
    mount 2.10r-0.6.x
    fs.file-max=8192 (in /etc/sysctl.conf)
    Dietmar

    Hi
    I work with linux RH (6.2, 7.0, 7.1) and 8i (8.1.5 since 8.1.7.0.1) and 9i and I only two times I find just a block corruption warning, but database keeps working fine.
    This data corruption affects only Oracle? You can turn extra CRC check into oracle data blocks (of course it slows all process ;)
    Maybe the linux RAID drivers have some bug, a simple solution is to install one datafile of the tablespace in a nother disk (IDE for example) and check if this datafile is corrupted too.
    Anyway just make a simple script (using dd or random) or C, Perl.. program that writes/reads intensively (one week ir more) "1" on a big file (at least 1G) and check if you get some error. Oracle just calls system I/O, so if one crashes, other must too.
    A10!

Maybe you are looking for