8 Replies Latest reply on Aug 16, 2011 11:43 AM by Udo

    apex listener start with port 8080

    Rafi (Oracle DBA)
      Hi All,
      If I want the apex listener to start with port 8080.How can I do this?


      -bash-3.2$ java -Dapex.images=/home/tomcat/apache-tomcat/webapps/ROOT/i -Dapex.port=8080 -jar apex.war
      INFO: Starting: /apex_4.0.2/apex.war
      See: 'java -jar apex.war --help' for full range of configuration options
      INFO: Extracting to: /tmp/apex
      SEVERE: method java.lang.System.console with signature ()Ljava.io.Console; was not found.
      java.lang.NoSuchMethodError: method java.lang.System.console with signature ()Ljava.io.Console; was not found.
      at ____embedded.____EntryPoint.apexImages(____EntryPoint.java:104)
      at ____embedded.____EntryPoint.main(____EntryPoint.java:91)

      What can be the issue...




      Best regards,

      Rafi.

      Edited by: Rafi (Oracle DBA) on Aug 12, 2011 3:36 AM
        • 1. Re: apex listener start with port 8080
          Udo
          Hi Rafi,

          this should work if your environment is configured properly.
          Which JDK version do you have on your system? Note that you need at least JDK 1.6.0_20 to run the APEX Listener.

          -Udo
          • 2. Re: apex listener start with port 8080
            Rafi (Oracle DBA)
            Hi Udo,
            Thanks for reply.I have jdk6.Is the above command correct?For configuration can you please suggest the steps to do correctly.


            Best regards,

            Rafi.

            Edited by: Rafi (Oracle DBA) on Aug 12, 2011 5:54 AM
            • 3. Re: apex listener start with port 8080
              Udo
              Which minor version (upadte) of JDK 6 do you have? It really has to be 20 or higher...
              The command looks good. If the directories are in place and readable and in case of /tmp also writable for your user (which should always be the case) and with at least some megabytes space left, this should work.
              What makes me wonder a bit: You start with an image directory located in a Tomcat path. Is the Tomcat running as well? If so, could it be it uses the default port 8080 already? If you intend to run the APEX Listener on Tomcat, you don't need the Java Command, but just deploy the war file... (Well, actually you'll need to do some additional configuration with the Tomcat to get the Listener to work correctly, but I won't bother with that unless you really want to deploy there...)
              The java <options> -jar apex.war is just for running the APEX Listener in Standalone Mode.

              -Udo
              • 4. Re: apex listener start with port 8080
                Rafi (Oracle DBA)
                Hi Udo,
                Still the same issue exists,how to resolve any idea,there is no tomcat here.
                I'm using standalone method to start the listener.

                [root@test_ebs apex_listener_status]# java -jar apex.war -Dapex.port=8081 -Dapex.images=/apex_4.0.2/apex/images/
                INFO: Starting: /apex_listener_status/apex.war
                See: 'java -jar apex.war --help' for full range of configuration options
                INFO: Extracting to: /tmp/apex
                SEVERE: method java.lang.System.console with signature ()Ljava.io.Console; was not found.
                java.lang.NoSuchMethodError: method java.lang.System.console with signature ()Ljava.io.Console; was not found.
                at ____embedded.____EntryPoint.apexImages(____EntryPoint.java:104)
                at ____embedded.____EntryPoint.main(____EntryPoint.java:91)

                Any ideas friends how to resolve this issue.


                Best regards,

                Rafi.
                • 5. Re: apex listener start with port 8080
                  Udo
                  Hi Rafi,

                  you have to put the parameters in front of the jar file. And I'm still unsure about your JDK version, since you didn't post the acutal version yet. What's the output of
                  java -version
                  on your system? And is your "java" actually pointing to the JDK installed or is it pointing to a JRE? You could try to start by giving the full path to the java executable in your startup command, e.g.
                  /usr/lib/jvm/jdk1.6.0_27/bin/java -Dapex.port=8081 -Dapex.images=/apex_4.0.2/apex/images/ -jar apex.war
                  -Udo
                  1 person found this helpful
                  • 6. Re: apex listener start with port 8080
                    Rafi (Oracle DBA)
                    Hi Udo,
                    I'm feeling I'm very near for solving this issue:

                    Details are here:


                    -bash-3.2$ java -version
                    java version "1.4.2"
                    gij (GNU libgcj) version 4.1.2 20080704 (Red Hat 4.1.2-44)

                    Copyright (C) 2006 Free Software Foundation, Inc.


                    How to make it point to latest version also check the below details:


                    -bash-3.2$ cd java
                    -bash: cd: java: Not a directory
                    -bash-3.2$ ls -altr j*
                    -rwxr-xr-x 1 root root 12570 Jul 12 2006 jw
                    -rwxr-xr-x 1 root root 18260 Jul 13 2006 jpegicc
                    -rwxr-xr-x 1 root root 6372 Jul 14 2006 jstest
                    -rwxr-xr-x 1 root root 14120 Jul 14 2006 jscal
                    -rwxr-xr-x 1 root root 5932 Jul 14 2006 jsattach
                    -rwxr-xr-x 1 root root 20616 Jul 27 2006 jpegtran
                    -rwxr-xr-x 1 root root 1757 Sep 20 2006 jvmjar
                    -rwxr-xr-x 1 root root 25288 Oct 2 2006 jpegtopnm
                    -rwxr-xr-x 1 root root 214776 Oct 2 2006 jpeg2ktopam
                    -rwxr-xr-x 1 root root 59856 Oct 31 2006 jwhois
                    -rwxr-xr-x 1 root root 149472 Nov 2 2007 jbibtex
                    -rwxr-xr-x 1 root root 13168 Jul 3 2008 jsaccess
                    -rwxr-xr-x 1 root root 73608 Sep 18 2008 jv-scan
                    -rwxr-xr-x 1 root root 3440 Sep 18 2008 jv-convert
                    -rwxr-xr-x 1 root root 88292 Sep 18 2008 jcf-dump
                    -rwxr-xr-x 1 root root 30668 Oct 31 2008 join
                    lrwxrwxrwx 1 root root 8 Feb 14 2011 jade -> openjade
                    lrwxrwxrwx 1 root root 4 Feb 14 2011 jadetex -> etex
                    lrwxrwxrwx 1 root root 22 Feb 14 2011 java -> /etc/alternatives/java
                    lrwxrwxrwx 1 root root 23 Feb 14 2011 javah -> /etc/alternatives/javah
                    lrwxrwxrwx 1 root root 25 Feb 14 2011 javadoc -> /etc/alternatives/javadoc
                    lrwxrwxrwx 1 root root 23 Feb 14 2011 javac -> /etc/alternatives/javac
                    lrwxrwxrwx 1 root root 27 Feb 14 2011 jarsigner -> /etc/alternatives/jarsigner
                    lrwxrwxrwx 1 root root 21 Feb 14 2011 jar -> /etc/alternatives/jar
                    lrwxrwxrwx 1 root root 28 Aug 13 04:28 javaws -> /usr/java/default/bin/javaws
                    lrwxrwxrwx 1 root root 30 Aug 13 04:28 jcontrol -> /usr/java/default/bin/jcontrol

                    I installed the below file:

                    jdk-6u26-linux-i586-rpm.bin successfully is this correct?

                    can you please show the location to download correct jdk6 for the below os:


                    -bash-3.2$ cat /etc/redhat-release
                    Red Hat Enterprise Linux Server release 5.3 (Tikanga)



                    Best regards,

                    Rafi.
                    • 7. Re: apex listener start with port 8080
                      Rafi (Oracle DBA)
                      Hi,
                      After making sure I have jdk-6u26-linux-i586-rpm.bin installed.

                      I just ran the apex.war file from oracle user.It is EBS environment but I didn't set my environment.


                      $./apex.war


                      It worked....


                      Best regards,

                      Rafi.
                      • 8. Re: apex listener start with port 8080
                        Udo
                        Hi Rafi,

                        great to hear that you've got it working now!
                        Please mark this thread as answered if your problem is solved.

                        Thanks,

                        Udo