Empty JDEV\j2ee\home\admin.jar

I tried to add a connection to a remote OC4J. When I tried to install DCM, I got this error:
C:\JDeveloper\j2ee\home>java -jar admin.jar ormi://DOMAIN:1810 ias_admin PASSWORD -deploy -file C:\JDeveloper\dcm\lib\Oc4jDcmServlet.ear -deploymentName Oc4jDcmServlet
Error: javax.naming.NamingException: Lookup error: java.io.EOFException: Disconn
ected; nested exception is:
java.io.EOFException: Disconnected
I found the reason of the error. My admin.jar file is empty! Only a manifest file in the jar. Do you guys know why? Where can I get the admin.jar file.
Thanks!

Yes.
The first step is to:
C:\JDeveloper\j2ee\home>java -jar admin.jar ormi://DOMAIN:1810 ias_admin PASSWORD -deploy -file C:\JDeveloper\dcm\lib\Oc4jDcmServlet.ear -deploymentName Oc4jDcmServlet
I got this error:
Error: javax.naming.NamingException: Lookup error: java.io.EOFException: Disconn
ected; nested exception is:
java.io.EOFException: Disconnected
Search through the discussion board and the internet and found several people have exactly same problem, but no answers!
Any clue?

Similar Messages

  • JDev - J2EE Deployment Problem

    I'm not sure if I should be posting this here or in the J2EE forum but here is my problem. Whenever I try to deploy a web application to our J2EE server I get the following error.
    Invoking Oracle9iAS admin tool...
    D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\HW\HW.ear -deploymentName HW
    Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
    Exit status of Oracle9iAS admin tool (-deploy): 0
    -If i try to deploy a war file I get this slightly different error.
    D:\jdk1.3.1\jre\bin\javaw.exe -Xmx128m -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\Project1\webapp1.ear -deploymentName webapp1
    Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
    Exit status of Oracle9iAS admin tool (-deploy): 0
    D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -bindWebApp webapp1 webapp1 http-web-site /JSPTest-Project1-context-root
    Error: com.evermind.server.rmi.OrionRemoteException: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
    Exit status of Oracle9iAS admin tool (-bindWebApp): 1
    Here is what I do to run our J2EE server.
    java -Xmx268435456 -jar $j2ee_home/orion.jar
    Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
    I'm running JDev 9.0.2.829
    I have confirmed that the J2EE server is listening on port 23791 and I can browse to it on port 8888. Any help would be appreciated.
    -Eric Dalquist

    See Infrastructure Serrver is down and Re: Lov values filtered by the value selected in other LOV for related discussions.
    Here is a cut-and-paste of the important part:
    When JDeveloper deploys to a remote OC4J, JDeveloper must use client-side classes to communicate with the server-side administrative objects via RMI. Since communication over RMI uses object serialization to send object instances across the wire, if there is a difference in version in the client-side objects and the server-side objects, there are likely to be deploy-time problems. The incompatibility would be due to implementation decisions made by the OC4J development team.
    By default, JDeveloper uses the client-side OC4J classes that ship with JDeveloper. However, if you need to deploy to a different version of OC4J than what ships with JDeveloper, you can tell JDeveloper to use a different set of client-side classes when defining an OC4J connection in the JDeveloper connection manager. On step 3 of the Connection Wizard, there is a field labeled "Local Directory Where admin.jar for Oracle9iAS is Installed". Point that to the OC4J 1.0.2.2 directory containing admin.jar, and you should then be able to deploy from JDev 9i (9.0.2) production to OC4J 1.0.2.2.
    There are a few other less common causes for hanging at deploy-time. Let's say you've specified a target server URL of "ormi://myserver".
    1) Try specifying the full host name instead of the abbreviated name -- works around problems with hostname resolution.
    2) Try specifying the IP address of the target server instead of the hostname -- works around problems with DNS lookups.
    3) Try specifying "http:ormi://myserver" as the URL instead -- works around problems with a proxy server that is between the JDeveloper machine and the server (by using HTTP tunnelling).
    Hope that helps.

  • Admin.jar connection refused

    I have an EAR file built in JBuilder 7 which I'm trying to deploy to my demonstration Application Server using the JBuilder 7 plug-in for OC4J. Whenever I try to deploy, I get
    ...\jdk1.3.1\bin\java -jar "...\ora90\j2ee\home\admin.jar" ormi://localhost:23791 admin narf -deploy -file "C:/devt/010Plus/010Plus.ear" -deploymentName 010Plus
    Error!!!: Error: javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
         java.net.ConnectException: Connection refused: connect
    Now, doing anything "admin.jar" from the command line gives me the same result -
    ...\ora90\j2ee\home>java -jar admin.jar ormi://127.0.0.1:23791 admin narf -list
    Error: javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
    java.net.ConnectException: Connection refused: connect
    I've been through the 9ias installation guide and the JBuilder plug-in documentation with a pretty fine-toothed comb, but still there is obviously something that eludes me. Help! Stuck!
    Anyone got any ideas? I'm pretty new to the Oracle side of this, so don't hold back on offering "obvious" tips - what may be "obvious" to you gurus will most likely be black magic to me at this point ;)
    Thanks for your help,
    =Per

    It's probably bad form to reply to my own post, but I've just repeated the problem on a clean machine, so I thought I'd submit a quick update.
    OS: Windows XP Professional
    Product: Oracle 9i Application Server Release 2 (9.0.3)
    1) Install 9iAS with WebCache
    2) Select "No Infrastructure"
    3) Complete installation
    4) Verify installation complete and 9iAS started -
    http://localhost:7777/
    5) Verify OC4J instance(s) created and started -
    http://localhost:1810/
    6) Attempt to list all sites -
    ...\j2ee\home>java -jar admin.jar ormi://127.0.0.1 admin password -list
    Error: javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
    java.net.ConnectException: Connection refused: connect
    Ok - I admit it - I'm dumb. What did I miss/forget/not grok?
    Any pointers would be greatly appreciated.
    Cheers,
    =Per

  • Javax.naming.NamingException: when deploying to OC4J using admin.jar

    Additional details to posting (Problem Deploying to OC4J from Jbuilder8)
    Jul 8 2003 @3:27
    enter:-
    java -jar "\ora9ias\j2ee\home\admin.jar" ormi://myhost:23791 admin password
    and you get the error message:-
    javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
    java.net.ConnectionException: Connection refused: connect
    My server.xml contains entry <rmi-config path="./rmi.xml" />
    and my rmi.xml reads:-
    <?xml version="1.0" standalone="yes" ?>
    <!DOCTYPE rmi-server (View Source for full doctype...)>
    - <rmi-server port="23791" host="[ALL]">
    - <log>
    <file path="../log/rmi.log" />
    </log>
    </rmi-server>
    I have repeatedly checked my hostname port user name and password
    along with the statements in the server.xml and rmi.xml as above, but with no
    success.
    Regards
    Gary.

    I am facing the same problem from this morning. I was able to start oc4j jvm without any problem today in the morning and i could deploy the war file and was able to test the web pages. But due to some unavoidable reasons i had to restart my machine and ever since then i am running into the following error.
    My server.xml has a reference to rmi.xml.
    Any help is highly appreciated.
    Regards
    Kiran
    D:\Java\JDev9i\j2ee\home>java -jar oc4j.jar
    Node started with id=647722646
    Error initializing web-site at ./http-web-site.xml: default-web-app not specifie
    d for Oracle9iAS Containers for J2EE HTTP Web Site
    Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized

  • Can admin.jar create oc4j users and connection pools that use those users

    Hi
    I have an ADF BC application written in jdev 10.1.3.3 deployed to standalone oc4j 10.1.3
    When I deploy the application I use the enterprise manager to create the users on the security provider/realms tab. I then set up the connection pools in jdbc resources to use those users via the username and indirect password fields. I also set the minimum number of connections on the attributes tab.
    I have read the following document but I cannot find any reference to setting up users, connection pools with indirect passwords or minimum number of connections.
    http://download-uk.oracle.com/docs/cd/B31017_01/web.1013/b28950/adminclient.htm#BABHJAFE
    Is it possible to do using admin.jar?
    thanks
    paul schweiger

    I'm not sure about setting indirect passwords on the connection pool creation -- never tried it. It's probably treated purely as a lexical string, so may well be able to to issue the CP creation command with the "->USER" entry as the password.
    To create realms, users, groups, etc. you need to use the $ORACLE_HOME/j2ee/home/jazn.jar utility: http://download.oracle.com/docs/cd/B25221_04/web.1013/b14429/admintool.htm#g1022417
    The options for connection pool parameters such as min/max connections aren't directly expressable in the command. I'll need to look at the code and see if they can be passed in as non checked options via the factoryproperties. If not, then you can create a JMX client to use the MBeans that are created for the CP post deployment to change its behaviour.
    -steve-

  • [jdev]\j2ee

    Hi;
    We have an standalone oc4j at jdev\j2ee\home directory, it was working fine until some days ago and now it gives the following error; when startup
    06/07/03 11:49:08 Error instantiating application 'bc4j' at file:/D:/jdev/BC4J/r
    edist/bc4j.ear: Error loading web-app 'webapp' at D:\jdev\BC4J\redist\bc4j\webap
    p: Unable to find/read assembly info for D:\jdev\BC4J\redist\bc4j\webapp (WEB-IN
    F/web.xml)
    Error initializing server: Error loading web-app 'webapp' at D:\jdev\BC4J\redist
    \bc4j\webapp: Unable to find/read assembly info for D:\jdev\BC4J\redist\bc4j\web
    app (WEB-INF/web.xml)
    I also tried to reinstal the bc4j framework but adf installer says that it has not an oc4j root directory, i've pointed to jdev\j2ee\home;
    Some one has ideias : ?
    thanks

    Hi,
    if its is the embedded OC4J I suggest to re-install JDeveloper as it seems that you messed up with the default BC directory
    Frank

  • OC4J: Class not found for class in jar file placed in \j2ee\home\applib\

    I have an ADF application which uses external libraries (jars), which works fine when running the application from within JDeveloper (TP4).
    However if I deploy the application to the embedded OC4J server it won't find any classes imported in those external libraries at runtime (deploy does work). E.g. one library class imports oracle.jbo.server.DBTransaction. If a method of this class is called I get the following exception:
    Unexpected exception caught: java.lang.NoClassDefFoundError, msg=oracle/classloader/util/AnnotatedNoClassDefFoundError
    oracle/classloader/util/AnnotatedNoClassDefFoundErrorThe same exception, when using a german locale, explicitely states that it cannot find oracle.jbo.server.DBTransaction.
    The jar files are placed in the \j2ee\home\applib\ directory and a <library> element to this path is present in application.xml.
    Any further hints what could be wrong?

    Hi Edwin,
    tried your suggestions but without success.
    when I add this library to server.xml then following error occures when starting OC4J
    17.09.2008 17:10:33 oracle.oc4j.util.SystemLog log
    SCHWERWIEGEND: Server start failed processing configuration
    java.lang.InstantiationException: Illegal tag, 'library': The library tag has moved from config/server.xml to config/application.xml, please update your configuration manually or reinstall.
            at com.evermind.server.XMLApplicationServerConfig.parseDeploymentMainNode(XMLApplicationServerConfig.java:1227)
            at com.evermind.xml.XMLConfig.parseRootNode(XMLConfig.java:342)
            at com.evermind.xml.XMLConfig.init(XMLConfig.java:222)
            at com.evermind.xml.XMLConfig.init(XMLConfig.java:154)
            at com.evermind.server.XMLApplicationServerConfig.<init>(XMLApplicationServerConfig.java:237)
            at com.evermind.server.ApplicationServer.createConfig(ApplicationServer.java:661)
            at oracle.oc4j.server.ServerFactory$Worker.prepareConfig(ApplicationServerFactory.java:225)
            at oracle.oc4j.server.ServerFactory$Worker.start(ApplicationServerFactory.java:244)
            at oracle.oc4j.server.ServerFactory$Worker.run(ApplicationServerFactory.java:259)
            at java.lang.Thread.run(Thread.java:619)
    17.09.2008 17:10:33 oracle.oc4j.util.SystemLog logNoStack
    SCHWERWIEGEND: Server exiting: ApplicationServer entered state EXITING--> I added this to application.xml
    Than I enabled more logging of classloader "-Duser.country=US -Dclass.load.log.level=finest"
    Here a snippet of the output at starttime of OC4J:
    ================================
    08/09/18 10:17:07 Initial class loaders created. Uptime: 3156ms.
    08/09/18 10:17:07 Loading main class com.evermind.server.OC4JServer...
    08/09/18 10:17:07 com.evermind.server.OC4JServerMain class loaded. Uptime: 3344ms.
    08/09/18 10:17:07 Transferring to com.evermind.server.OC4JServer.main()...
    08/09/18 10:17:15 Ignoring non-existent code source: D:\oracle\jdevstudio1111_preview4_standalone\j2ee\home\config\..\..\..\BC4J\lib\jmxdc.jar(from <code-source> (ignore manifest Class-Path) in /D:/oracle/jdevstudio1111_preview4_standalone/j2ee/home/config/server.xml)
    08/09/18 10:17:15 Ignoring <code-source> (ignore manifest Class-Path) in /D:/oracle/jdevstudio1111_preview4_standalone/j2ee/home/config/server.xml entry: code-source /D:/oracle/jdevstudio1111_preview4_standalone/j2ee/home/lib/api-ext/adflogginghandler.jar (from system property api.ext.dirs) is already visible in the search path of adf.oracle.domain:11.1.4949.
    08/09/18 10:17:15 Ignoring non-existent code source: D:\oracle\jdevstudio1111_preview4_standalone\j2ee\home\config\..\..\..\BC4J\lib\jmxdc.jar(from <code-source> (ignore manifest Class-Path) in /D:/oracle/jdevstudio1111_preview4_standalone/j2ee/home/config/server.xml)
    08/09/18 10:17:15 Import was not resolved for adf.oracle.domain:11.1.4949: shared library "oracle.fabric.runtime" could not be found.
    08/09/18 10:17:15 Import was not resolved for adf.generic.domain:11.1.4949: shared library "oracle.fabric.runtime" could not be found.Seems that oracle.fabric.runtime couldn't be found but the jar's are located in D:\oracle\jdevstudio1111_preview4_standalone\lib\java\shared\oracle.fabric.runtime\11.1.1.0.0
    It's the same as with my jdeveloper installation where I don't have this problems.
    regards
    Peter

  • Updated JAR files in j2ee/home/lib

    We are developing and deploying j2ee applications to a 9.0.2.3 9iAS server. We have a framework.jar file that we have a number of applications in two OC4J instances (home and portal) that need to use this jar file. As a result, we place the jar file in the j2ee/home/lib directory since this could be seen by all applications. My question comes in when we try and update this jar file. We seem to experience problems when moving a new framework.jar file into the directory. We mainly notice this issue in our EM Website. We begin to get the following error in the EM Website after we move an updated jar file into the directory:
    Servlet error: Renderer failed: java.lang.InternalError: jzentry == 0
    I've seen this error before and it seems to link back to a problem with jar files. If I remove the new jar file the error disappears. We are eventually able to get the jar file in, but only after restarting the whole mid-tier. Is this normal? Should we have to restart the server everytime we update the jar file? If so, what would be the best way to implement the new jar files? Stop mid-tier, move new file in and restart??
    Would you recommend a different location for this jar file?? Our biggest concern is that we only want to deploy this jar file one time and have all applications that need it find it. Thanks in advance for any input you might have.
    Beth

    Libraries loaded from the j2ee/home/lib directory are opened and loaded at the J2EE container level. So they are accessed from the very start of the server, to the point where it is stopped.
    Therefore if you modify a class library which has already been loaded, you may run into file locking related issues (which will be OS dependent, Windows for example probably won't even let you overwrite the file) so that is what you are likely to be seeing.
    JAR files loaded at the J2EE container level aren't really suitable for dynamic updating -- the classes can be referenced in a multitude of other classloaders.
    As you have seen, replacing a J2EE container level class file, then a restart will be required along the lines of what you have written.
    Stop mid-tier, move new file in and restart?? cheers
    -steve-

  • Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

              Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
              Acelet is the leader in J2EE tools area. If you google "j2ee tools",
              "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
              is at the top of the result.
              Super 4.00 comes with:
              SuperEnvironment
              SuperLogging
              SuperPeekPoke
              SuperReport
              SuperScheduler
              SuperStress
              and SuperPatrol, as a schedule job.
              The evaluation edition can be anonymously downloaded from:
              http://www.ACElet.com.
              Super is a component based monitor and administration tool
              for EJB/J2ee. It provides built-in functionality as well as
              extensions, as SuperComponents. Users can install
              SuperComponents onto it, or uninstall them from it.
              Super has the following functions:
              * A J2EE monitor.
              * A gateway to J2EE/EJB servers from different vendors.
              * A framework holding user defined SuperComponents.
              * A full-featured J2EE logging and J2EE tracing tool for centralized,
              chronological logging.
              * An EJB tool for Peeking and Poking attributes from EJBs.
              * An EJB Stress test tool.
              * A J2EE global environment tool.
              * A J2EE report tool.
              * A J2EE Scheduler tool.
              * A J2EE Business patrol tool.
              It is written entirely in the Java(TM) programming language.
              The current version support:
              * JOnAS 2.4 and 2.6
              * SunONE 7.0
              * Universal servers.
              * Weblogic 6.1, 7.0 and 8.1
              * Websphere 4.0 and 5.0.2
              * jBoss 3.0 and 3.2
              ********** What is new:
              Version 4.00 November, 2003
              Enhancement:
              1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
              (with/without proxy) protocol mode for SuperEnvironment,
              SuperLogging, SuperReport and SuperScheduler.
              2. SuperLogging 4.00: tracing can work on both live database and retired database.
              3. SuperReport 3.00: works for both live database and retired database.
              4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
              Panel.
              Bug fix:
              1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
              Version 3.00 July, 2003
              Enhancement:
              1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
              scope,
              with enhancements and bug fixes.
              2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
              password.
              Add MenuTreePanel.
              3. Improved GUI and document.
              4. Add support to WebLogic 8.1.
              Bug fix:
              1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
              2. SuperScheduler 2.0: Startup should never be reported as missed.
              3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
              Version 2.20 Jan. 2003
              Enhancement:
              1. Add desktop and start menu shortcuts for MS-Windows.
              2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
              3. SuperLogging 2.40: Add new sendAlarmEmail() method.
              4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
              direct database is not practical; Allow user to choose
              favorite logging software; Add Last day as Monthly
              repeating attribute.
              Change:
              1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
              Bug fix:
              1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
              open Environment Manager.
              2. SuperLogging client 1.52: Annoying exception thrown when you use
              JDK 1.4 (the program runs okay).
              3. SuperPeekPoke 1.61: Fix bug where input object contains
              java.lang.Double and alike.
              4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
              PatrolAlarm for SuperPatrol; Composite task with members;
              Non-scheduled run on other host; Around edges of last
              days in Monthly with holiday policy.
              Version 2.10 July 2002
              Enhancement:
              1. SuperScheduler 1.3: Add Future View to check future schedule in
              both text and Gantt-chart mode.
              2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
              activities.
              3. SuperEnvironment 1.3: uses new graphic package adding print and
              preference facilities.
              4. SuperPeekPoke 1.6: uses new graphic package adding print and
              preference facilities.
              5. SuperStress 1.21: uses new graphic package.
              Bug fix:
              1. SuperStress 1.21: fixed graphic related bugs.
              Version 2.01 June 2002
              Enhancement:
              1. Add options for Look & Feel.
              2. Preference is persistent now.
              Bug fix:
              1. Installation for WebLogic 7.0: extEnv may not be installed on the
              right place, so SuperLibrar on the server side was not loaded and
              causes other problems.
              Version 2.00 June 2002
              Enhancement:
              1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
              when any Doer causes things to change.
              2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
              3. SuperReport 1.2: Support default HTML browser for reading HTML document.
              4. Support WebLogic 7.0.
              5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
              6. SuperEnvironment 1.21: New SuperEnvironment tour.
              Bug fix:
              1. WebSphere Envoy did not always list all JNDI names.
              Version 1.90 May 2002
              Enhancement:
              1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
              2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
              effective period. Add Patrol job type as SuperPatrol.
              3. Add support for both JOnAS and jBoss.
              4. Add more elements on Report criteria.
              Change:
              1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
              and descend.
              2. New log database.
              Bug fix:
              1. Alert email should be sent once in the interval, regarding number of servers
              in the clustering.
              2. Minor bug fixes to make errors handled better on SuperLogging.
              3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
              them.
              4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
              Version 1.80 March 2002
              Enhancement:
              1. Add new component: SuperScheduler
              Bug fix:
              1. SuperLogging: Verbose should ignore class registration.
              2. SuperLogging-tracing: an exception was thrown if the java class without package
              name.
              Version 1.70 January 2002
              Enhancement:
              1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
              weblogic 6.1, need download an application).
              2. Add alias names for log threshold as new Java suggests.
              3. New component: SuperReport.
              Change:
              1. SuperLogging: Log database parameters are specified in a properties file, instead
              of EJB's deployment descriptor. It is more convenient and it avoids some potential
              problems. No change for development, easier for administration.
              Bug fix:
              1. Add Source Path Panel now accepts both directory and jar file.
              2. Bug in SuperEnvironment example (for version 1.60 only).
              Version 1.60 December 2001
              Enhancement:
              1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
              2. Add timeout parameter to logging access.
              3. New installation program with A). Easy install. B). Remote command line install.
              4. Support EJB 2.0 for Weblogic 6.1.
              5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
              was supported since version 1.5).
              Change:
              1. Poke: argument list is set at define time, not invoke time.
              2. Default log database change to server mode from web server mode, booting performance
              to 10-20 times.
              Bug fix:
              1. If the returned object is null, Peek did not handle it correctly.
              2. If the value was too big, TimeSeries chart did not handle it correctly. Now
              it can handle up to 1.0E300.
              3. Help message was difficult to access in installation program.
              4. Source code panel now both highlights and marks the line in question (before
              it was only highlight using JDK 1.2, not JDK 1.3).
              5. Delete an item on PeekPoke and add a new one generated an error.
              Version 1.50 August, 2001
              Enhancement:
              1. Source code level tracing supports EJB, JSP, java helper and other
              programs which are written in native languages (as long as you
              write correct log messages in your application).
              2. Redress supports JSP now.
              3. New installation with full help document: hope it will be easier.
              4. Support WebSphere 4.0
              Version 1.40 June, 2001
              Enhancement:
              1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
              and PieView for GlobalProperties.
              GlobalProperties is an open source program from Acelet.
              2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
              Changes:
              1. The structure of log database changed. You need delete old installation and
              install everything new.
              2. The format of time stamp of SuperLogging changed. It is not locale dependent:
              better for report utilities.
              3. Time stamp of SuperLogging added machine name: better for clustering environment.
              Bug fix:
              1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
              Style Panel may not show up.
              Version 1.30 May, 2001
              Enhancement:
              1. Add ConnectionPlugin support.
              2. Add support for Borland AppServer.
              Version 1.20 April, 2001
              Enhancement:
              1. Redress with option to save a backup file
              2. More data validation on Dump Panel.
              3. Add uninstall for Super itself.
              4. Add Log Database Panel for changing the log database parameters.
              5. Register Class: you can type in name or browse on file system.
              6. New tour with new examples.
              Bug fix:
              1. Redress: save file may fail.
              2. Install Bean: some may fail due to missing manifest file. Now, it is treated
              as foreign beans.
              3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
              on the original file, do not need copy to a temporary directory anymore.
              4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
              Now it pick up all availble ones and give warning messages.
              5. Stress: Launch>Save>Cancel generated a null pointer exception.
              Changes:
              1. installLogDatabase has been changed from .zip file to .jar file.
              2. SuperLogging: If the log database is broken, the log methods will not try to
              access the log database. It is consistent with the document now.
              3. SuperLogging will not read system properties now. You can put log database
              parameters in SuperLoggingEJB's deployment descriptor.
              Version 1.10 Feb., 2001
              Enhancement:
              1. Re-written PeekPoke with Save/Restore functions.
              2. New SuperComponent: SuperStress for stress test.
              3. Set a mark at the highlighted line on<font size=+0> the Source Code
              Panel (as a work-a-round for JDK 1.3).</font>
              4. Add support for WebLogic 6.0
              Bug fix:
              1. Uninstall bean does physically delete the jar file now.
              2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
              Version 1.00 Oct., 2000
              Enhancement:
              1. Support Universal server (virtual all EJB servers).
              2. Add Lost and Found for JNDI names, in case you need it.
              3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
              for Envoys which do not support JNDI list).
              Version 0.90: Sept, 2000
              Enhancement:
              1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
              and alike) as input values.
              2. Reworked help documents.
              Bug fix:
              1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
              further time-out.
              2. MDI related bugs under JDK 1.3.
              Version 0.80: Aug, 2000
              Enhancement:
              1. With full-featured SuperLogging.
              Version 0.72: July, 2000
              Bug fix:
              1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
              Version 0.71: July, 2000
              Enhancement:
              1. Re-worked peek algorithm, doing better for concurent use.
              2. Add cacellable Wait dialog, showing Super is busy.
              3. Add Stop button on Peek Panel.
              4. Add undeploy example button.
              Bug fix:
              1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
              1.2 and 1.3
              Version 0.70: July, 2000
              Enhancement:
              1. PeekPoke EJBs without programming.
              Bug fix:
              1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
              Changes:
              1. All changes are backward compatible, but you may need to recompile monitor
              windows defined by you.
              Version 0.61: June, 2000
              Bug fix:
              1. First time if you choose BUFFER as logging device, message will not show.
              2. Fixed LoggingPanel related bugs.
              Version 0.60: May, 2000
              Enhancement:
              1. Add DATABASE as a logging device for persistent logging message.
              2. Made alertInterval configurable.
              3. Made pace for tracing configurable.
              Bug fix:
              1. Fixed many bugs.
              Version 0.51, 0.52 and 0.53: April, 2000
              Enhancement:
              1. Add support to Weblogic 5.1 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Context sensitive help is available for most of windows: press F1.
              2. Fix installation related problems.
              Version 0.50: April, 2000
              Enhancement:
              1. Use JavaHelp for help system.
              2. Add shutdown functionality for J2EE.
              3. Add support to Weblogic 4.5 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Better exception handling for null Application.
              Version 0.40: March, 2000
              Enhancement:
              1.New installation program, solves installation related problems.
              2. Installation deploys AceletSuperApp application.
              3. Add deploy/undeploy facilities.
              4. Add EJB and application lists.
              Change:
              1.SimpleMonitorInterface: now more simple.
              Version 0.30: January, 2000
              Enhancement:
              1. Add realm support to J2EE
              2. Come with installation program: you just install what you want
              the first time you run Super.
              Version 0.20: January, 2000
              Enhancement:
              Add support to J2EE Sun-RI.
              Change:
              1. Replace logging device "file" with "buffer" to be
              compliant to EJB 1.1. Your code do not need to change.
              Version 0.10: December, 1999
              Enhancement:
              1. provide SimpleMonitorInterface, so GUI experience is
              not necessary for developing most monitoring applications.
              2. Sortable table for table based windows by mouse
              click (left or right).
              Version 0.01 November., 1999:
              1. Bug fix: An exception thrown when log file is large.
              2. Enhancement: Add tour section in Help information.
              Version 0.00: October, 1999
              Thanks.
              

  • OC4J spitting out ejb's in j2ee/home

    Hi all,
    we recently noticed that during deployment of our application (ear file) when oc4j wants to compile the ejb's he spits them out in j2ee/home and compiles them there, then deletes the files.
    We probably wouldn't notice, but a couple of colleagues' deployment got stuck. The files are not deleted and oc4j's java proccess won't close, they have to restart the machine.
    Any idea what could be wrong? Maybe a misconfigured ejb-jar.xml or something?

    If your used the older deploytool then use the bottom two 'remote' boxes and leave the top two 'local' boxes empty.
    Basically Local means within the container
    and
    remote means outside the container.
    If you want to change yours to be local I think you need to subclass differently. I have not done it yet!
    EricLemle

  • Admin.jar deploy error

    I am using OC4J standalone version 9.0.3 on Windows 2000. I played around a little with the admin.jar deploy tools but I could not get it to work. The application runs fine if I edit the configuration files manually (but it seems like it would be nice to get the deploy tool to do the job for me).
    Here is my information (some names have been changed to protect the innocent):
    I am running the command:
    java -jar admin.jar ormi://localhost:23791 admin <pwd> -deploy -file D:\dist\MyApp.ear -deploymentName MyAppHere is the error I get:
    Fatal Error: Unable to find/read assembly info for C:\oracle\ora81\j2ee\home\applications\MyApp/log4j-1.2.7.jar (META-INF/ejb-jar.xml)
    Auto-unpacking C:\oracle\ora81\j2ee\home\applications\MyApp.ear... done.
    Auto-unpacking C:\oracle\ora81\j2ee\home\applications\MyApp\MyApp.war... done.
    Auto-deploying MyApp (Assembly had been updated)...
    com.evermind.server.ConfigFileNotFoundException: Unable to find/read assembly info for C:\oracle\ora81\j2ee\home\applications\MyApp/log4j-1.2.7.jar (META-INF/ejb-jar.xml)
    at com.evermind.server.ServerComponent.init(ServerComponent.java:238)
    at com.evermind.server.ejb.EJBPackageDeployment.getPackage(EJBPackageDeployment.java:672)
    at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplicationInstallation.java:517)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:119)
    at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
    at java.lang.Thread.run(Thread.java:484)
    hmmmm...log4j-1.2.7.jar is not an ejb so of course it does not have an ejb-jar.xml file. I am definitely not a J2EE deployment guru, but I feel well read up on the topic.
    Here is the structure of my ear file:
    META-INF/application.xml
    META-INF/MANIFEST.MF
    commons-logging.jar
    log4j-1.2.7.jar
    MyApp.war
    MyAppEjb.jar
    MyAppUtil.jar
    tl_core.jar
    tl_tools.jar
    Here is the content of the ear's META-INF/application.xml file:
    <?xml version="1.0"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
    <application>
    <display-name>MyApp</display-name>
    <module>
    <ejb>MyAppEjb.jar</ejb>
    </module>
    <module>
    <web>
    <web-uri>MyApp.war</web-uri>
    <context-root>/MyApp</context-root>
    </web>
    </module>
    </application>
    Here is the content of the MyAppEjb.jar's meta-inf/Manifest.mf (that is the case of the directory and file in the jar file, does that make a difference?):
    Manifest-Version: 1.0
    Created-By: Apache Ant 1.5
    Class-Path: MyAppUtil.jar commons-logging.jar log4j-1.2.7.jar tl_tools.jar tl_core.jar
    Any tips on getting this working would be greatly appreciated.
    Thanks,
    Brent

    I was just about to write and tell you that we make use of BCEL now, and given this line in the stacktrace:
    05/01/31 15:06:23 Caused by: java.lang.NoSuchMethodError: org.apache.bcel.generic.Type.getType(Ljava/lang/Class;)Lorg/apache/bcel/generic/Type;
    it appears as if there's a version mismatch somewhere along the line.
    But you've already sorted it out yourself, thanks for the repost!
    -steve-

  • Oc4j deployment error - admin.jar

    I am using JDeveloper 9.0.5.1, java_version 1.4.2_03
    When I deploy my J2EE application to our server (via JDeveloper) I get the following error:
    Error: Deploy error: Invocation error: java.lang.NoSuchMethodException; nested exception is:
         java.lang.NoSuchMethodException
    com.evermind.client.orion.AdminCommandException: Deploy error: Invocation error: java.lang.NoSuchMethodException; nested exception is:
         java.lang.NoSuchMethodException
         at com.evermind.client.orion.DeployCommand.execute(DeployCommand.java:95)
         at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:118)
         at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java:27)
    com.evermind.server.rmi.OrionRemoteException: Invocation error: java.lang.NoSuchMethodException
         at com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1497)
         at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
         at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
         at __Proxy0.deploy(Unknown Source)
         at com.evermind.client.orion.DeployCommand.execute(DeployCommand.java:92)
         at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:118)
         at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java:27)
         Nested exception is:
    java.lang.NoSuchMethodException
         at com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1527)
         at com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1480)
         at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
         at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
         at __Proxy0.deploy(Unknown Source)
         at com.evermind.client.orion.DeployCommand.execute(DeployCommand.java:92)
         at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:118)
         at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java:27)
    ---- Embedded exception
    java.lang.NoSuchMethodException
         at com.evermind.server.rmi.RMIConnection.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1527)
         at com.evermind.server.rmi.RMIConnection.invokeMethod(RMIConnection.java:1480)
         at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:55)
         at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:22)
         at __Proxy0.deploy(Unknown Source)
         at com.evermind.client.orion.DeployCommand.execute(DeployCommand.java:92)
         at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:118)
         at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java:27)
    Exit status of OC4J admin tool (-deploy): 1
    **** Note: The OC4J connection 'XXX' is configured to use the default admin.jar be used when deploying.
    **** Note: However, the remote server version does not appear to be compatible with this admin.jar.
    **** Note: Please edit the connection to point to an admin.jar version that is compatible with the remote server.
    Elapsed time for deployment: 5 seconds
    #### Deployment incomplete. #### Jan 24, 2005 8:32:30 AM
    Must I replace the admin.jar file with a more newer version of it? How do I determine the version of the admin.jar and if I update it to a newer version will it still be compatible with the rest of the settings?
    Thank you

    The admin.jar for the OC4J connection should be the same as the admin.jar in the remote server.
    For version, is the zip file size and date the same.

  • Difference between admin.jar and admin_client.jar

    OC4J provide two commad-line utility: admin.jar and admin_client.jar for performing configuration tasks on OC4J. admin_client.jar can work in Oracle Application Server clustered environment as well as on a standalone OC4J server, but admin.jar only works in a standalone OC4J installation. Do they have any other difference?
    If used in a standalone OC4J installation, are they the same?

    The documentation on the OC4J management tools covers this to some degree:
    http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28950/admin.htm#CEGHHGGB
    In a nutshell
    1. admin.jar is the old command line utility we kept in the release for backwards compatibility. It uses a set of internal/proprietrary APIs to work against OC4J. It works only against OC4J standalone.
    2. admin_client.jar is a new command line utility that is based on JMX and its associated set of specifications to manage and deploy to a J2EE container. It can connect to and manage all variants of OC4J -- standalone, single AS instance, clustered AS instance. It has many more resource configuration options added to it. For simplicity, we maintained the "feel" of admin.jar so the command structure is very similar to what was provided in admin.jar, but the way it works is completely different under the covers.
    While admin.jar still works and is supported, you should use admin_client.jar whenever you want to do command line operations with 10.1.3.x. I was considering putting a note to that effect on stdout whenever admin.jar was used, but we didn't end up doing it.
    Another two nice aspects about admin_client.jar are
    1. The common library it uses to perform its operations is also used by the Oracle Ant tasks -- so in effect there are two faces to it -- admin_client.jar and Ant tasks. There's a near 100% compatibility between the two meaning what you can do with admin_client.jar you can most likely do with a set of Ant tasks from a development environment.
    2. We have isolated the dependencies for admin_client.jar and produced a separate, small distribution called oc4j_admin_client.zip (which is 6MB from memory) that can be unzipped onto any remote server and you have the full admin_client.jar utility -- meaning that to perform administration options against ant of the OC4J variants (standalone, single and clustered AS instance) you only need this one, very small distribution.
    cheers
    -steve-

  • J2EE Home

    I have Oracle 9iAS and Sun AppServer on one windows system. How do I set J2EE_HOME so that I can use any one of the two servers. I will use one server at a time. Is there a restriction to number of J2EE appservers you can have on one system?

    Hi Ryan,
    Here're the options to include addtional jar files in OC4J:
    1. copy them to j2ee/home/lib
    2. modify j2ee/home/config/application.xml, add <library path="location_of_your_jar_file" /> for each jar file, the jar file will be available to the entire OC4J instance.
    3. modify j2ee/home/application-deployments/your_app_name/orion-application.xml, add <library path="location_of_your_jar_file" /> for each jar file, the jar file will be only available to the deployed application.
    Hope this helps.
    Chen.

  • FILE not found error: j2ee/home/applib/applications-mapping.xml (No such fi

    Hi EveryBody
    i have my applications-mapping.xml file already in the applib directory, but when i try to conect to a remote ejb i had this error[b]
    FILE not found error: j2ee/home/applib/applications-mapping.xml (No such file or directory)
    can anyone help??

    gday
    Is the error on the client or server?
    What role in the application does applications-mapping.xml fulfill?
    How are you loading the file in?
    -steve-

Maybe you are looking for

  • Split combined signals

    Hello, I have two combined signals (sine waves) one with a frequency of 2MHz and another one @2.7MHz. I haven't been succesful in finding the proper algorithm to split the combined signal into its two different components. Could anyone give me a push

  • How do i update my itunes so that i can use my new ipad?

    i need to upgrade my itunes to 10.7 or more recent version in order that i can sync my ipad with it.  how do i do this?

  • Import pictures using my computer

    iiphone is not showing up in my computer when plugged in, under device manager there is a yellow esclamation mark on iphone,  every time I try to reinstall driver it comes up with the device wizard or whatever and gives me option to insert disk or fl

  • Still no threaded discussions in iCloud webmail??

    .... How rubbish is that?? Come on Apple it's years overdue now. Obviously it means I wouldn't have to upgrade to OSX 10.7.x to be able to use Mail with iCloud to get this functionality ... so it's basically another Apple effort to put us through the

  • Issues opening XLS (2007) documents in Office Excel 2013

    I recently upgraded my computer from Windows XP/Office 2007 to a completely new computer with Windows 8.1/Office 2013.  I am unable to open any of my .xls spreadsheets. The error I am getting from Office 2013 is: "The file format and extension of "Bl