I'm trying to connect to a Master scheduler running on
Solaris (Java Edition) from the web console. When I try
to login I get a "Connection Refused" error displayed
on the login page. The web console application and
Master scheduler are running on separate servers.

Please make sure the Remote Control option is checked in the scheduler's Options and the selected port number is the same one you have on the web console side. Note the default port is 1096.

: I'm trying to connect to a Master scheduler running on
: Solaris (Java Edition) from the web console. When I try
: to login I get a "Connection Refused" error displayed
: on the login page. The web console application and
: Master scheduler are running on separate servers.

: Please make sure the Remote Control option is checked in the scheduler's
: Options and the selected port number is the same one you have on the web
: console side. Note the default port is 1096.

I have the option checked. The default shown in the Master
Scheduler GUI is actually 1097, not 1096. How do I check what it is in the
web console? Also, should I be running the Master in nogui
mode, or does it not matter?

NoGUI mode makes no difference.

Try setting remote control port to 1096 and the other port to 1095. The console is set to 1096 because it is set to be compatible by default with 24x7 for Windows version.

PS. Just in case... ensure you are running JSP version of the console for use with the Java scheduler. ASP version is not currently compatible with the Java scheduler. A compatible ASP version will be provided with the next maintenance release.

: I have the option checked. The default shown in the Master
: Scheduler GUI is actually 1097, not 1096. How do I check what it is in the
: web console? Also, should I be running the Master in nogui
: mode, or does it not matter?

: NoGUI mode makes no difference.

: Try setting remote control port to 1096 and the other port to 1095. The
: console is set to 1096 because it is set to be compatible by default with
: 24x7 for Windows version.

: PS. Just in case... ensure you are running JSP version of the console for use
: with the Java scheduler. ASP version is not currently compatible with the
: Java scheduler. A compatible ASP version will be provided with the next
: maintenance release.

Changing the port and re-starting the Master seems to have worked OK.

I can use the tree OK, but when trying to run e.g. the job monitor or
tools, I get an internal server error:

06/01/12 10:08:41 scheduler: Servlet error
java.lang.IllegalStateException: OutputStream already retrieved

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.EvermindHttpServletResponse.getWriter(EvermindHttpServletResponse.java:997)

at _loading._jspService(_loading.java:77)

at com.orionserver[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)

at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)

at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)

at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)

at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)

at java.lang.Thread.run(Thread.java:536)

Any ideas?

I don't see any references to the console pages and belive the exeption occurs in the servlet engine. It is hard to say what is happenning without a complete log.

Try reproducing this with a regular Apache/Tomcat server. If you get the same or similar error this would indicate a problem with console installation. If you don't get the same error then the problem would be then in Oracle AS or caused by differences between JDK used with the server and JDK used to compile console Java classes.

: Changing the port and re-starting the Master seems to have worked OK.

: I can use the tree OK, but when trying to run e.g. the job monitor or
: tools, I get an internal server error: 06/01/12 10:08:41 scheduler: Servlet
: error
: java.lang.IllegalStateException: OutputStream already retrieved

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.EvermindHttpServletResponse.getWriter(EvermindHttpServletResponse.java:997)

: at _loading._jspService(_loading.java:77)

: at com.orionserver[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)

: at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)

: at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)

: at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)

: at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)

: at com.evermind[Oracle Application Server Containers for J2EE 10g
: (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)

: at java.lang.Thread.run(Thread.java:536)

: Any ideas?

: I don't see any references to the console pages and belive the exeption
: occurs in the servlet engine. It is hard to say what is happenning without
: a complete log.

: Try reproducing this with a regular Apache/Tomcat server. If you get the same
: or similar error this would indicate a problem with console installation.
: If you don't get the same error then the problem would be then in Oracle
: AS or caused by differences between JDK used with the server and JDK used
: to compile console Java classes.

In every case, the internal server error occurs in the loading.jsp
servlet. Here's a section for the Apache log:

10.1.11.232 - - [14/Jan/2006:19:43:10 +0000] "GET /scheduler/loading.jsp?url=tools/log.jsp HTTP/1.1" 500 1863

and

10.1.11.232 - - [14/Jan/2006:19:43:07 +0000] "GET /scheduler/loading.jsp?url=tools_menu.jsp HTTP/1.1" 500 1863

The JVM version that the Oracle AS is running is:

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02)

Thanks for the info. We are looking into it.

: In every case, the internal server error occurs in the loading.jsp
: servlet. Here's a section for the Apache log: 10.1.11.232 - -
: [14/Jan/2006:19:43:10 +0000] "GET
: /scheduler/loading.jsp?url=tools/log.jsp HTTP/1.1" 500 1863

: and

: 10.1.11.232 - - [14/Jan/2006:19:43:07 +0000] "GET
: /scheduler/loading.jsp?url=tools_menu.jsp HTTP/1.1" 500 1863

: The JVM version that the Oracle AS is running is: Java(TM) 2 Runtime
: Environment, Standard Edition (build 1.4.1_03-b02)

: Thanks for the info. We are looking into it.

Any news on this problem?

We've sent you 2 WAR files to try. Please let us know the results.

: Thanks for the info. We are looking into it.

: We've sent you 2 WAR files to try. Please let us know the results.

I haven't received any e-mail as yet. Did you use:
dean.logan_wood@swapswire.com

Alternatively try dean.logan-wood@btconnect.com

Does your email server block messages with .WAR attachments? Neverless it is now being sent to the alternative addresss

: I haven't received any e-mail as yet. Did you use:
: dean.logan_wood@swapswire.com

: Alternatively try dean.logan-wood@btconnect.com

: Does your email server block messages with .WAR attachments? Neverless it is
: now being sent to the alternative addresss

Tried both the .war files - same result: Internal Server Error at the
loading.jsp stage.

A couple of things I noted - not sure of they're relevant:

1. At the login dialog, I had to chose the Windows scheduler
rather than Unix/Linux from the drop-down as I got a "Connection
Refused" error when chosing Unix/Linux

2. All the .jsp files appear to have the two characters "^M" at the
end of every line e.g.

^M
^M
^M
^M
^M
^M

^M
^M
^M
^M
^M

Loading, please wait... ^M
^M
^M
^M

parent.frames["Container"].location=unescape(" ");^M
^M
^M
^M

Aha... You need to choose Unix/Linux if you are connecting to 24x7 Java Edition. I know this is an old naming and might be confusing. We used to call the Java version as 24x7 Scheduler for Unix/Linux while 24x7 Scheduler for Windows version was called simply Windows.

Anyway, the reason you were getting "connection refused" because of different preferences. The Windows version uses just single port (default 1096) for all connection types including master/standby, remote control and remote agent. The Java version uses 2 separate ports, one for remote control (default 1097) and 1096 for everything else so that it can intercommunicate with the Windows version. You can change the default port numbers using Tools/Options menu.

If you set the Java scheduler to use 1096 for remote control and 1095 for other you should be able to use the web console to connect to any version. You can also adjust the connection settings in constants.jsp file.

: Tried both the .war files - same result: Internal Server Error at the
: loading.jsp stage.

: A couple of things I noted - not sure of they're relevant: 1. At the login
: dialog, I had to chose the Windows scheduler
: rather than Unix/Linux from the drop-down as I got a "Connection
: Refused" error when chosing Unix/Linux

: 2. All the .jsp files appear to have the two characters "^M" at the
: end of every line e.g.

: ^M
: ^M
: ^M
: ^M
: ^M
: ^M

: ^M
: ^M
: ^M
: ^M
: ^M

: Loading, please wait... ^M
: ^M
: ^M
: ^M

: parent.frames["Container"].location=unescape(" ");^M
: ^M
: ^M
: ^M

: Aha... You need to choose Unix/Linux if you are connecting to 24x7 Java
: Edition. I know this is an old naming and might be confusing. We used to
: call the Java version as 24x7 Scheduler for Unix/Linux while 24x7
: Scheduler for Windows version was called simply Windows.

: Anyway, the reason you were getting "connection refused" because of
: different preferences. The Windows version uses just single port (default
: 1096) for all connection types including master/standby, remote control
: and remote agent. The Java version uses 2 separate ports, one for remote
: control (default 1097) and 1096 for everything else so that it can
: intercommunicate with the Windows version. You can change the default port
: numbers using Tools/Options menu.

: If you set the Java scheduler to use 1096 for remote control and 1095 for
: other you should be able to use the web console to connect to any version.
: You can also adjust the connection settings in constants.jsp file.

I changed the port to 1097 and was able to connect using the
Unix/Linux option from the login form. I'm still getting
internal server errors though. It seems to be just on those options
where the loading.jsp is called. Functions such as Disable, Delete, Edit
,Audit and Run work fine.