View Full Version : No request type: media - Error
bozkeles
11-15-2003, 01:34 AM
Hi,
I installed the Laszlo PS (by downloading) on top of J2RE SDK 1.4.2 (new), Windows 2000 Server OS. I am constantly having the problem of "Error: No request type: media" and I can not run the LPS. Could you help me? I don't know why it is happening so far, although I re-insatalled the SW many times.
Thx.
Burak
bloch
11-15-2003, 09:42 AM
Hi,
Does the welcome page with the clocks come up?
Could you describe what actions or things you're trying that lead to the error message and where you see the error message (in the browser, in the console log window, or somewhere else) ?
Thanks,
-Eric
bozkeles
11-15-2003, 10:24 AM
Eric,
There are 2 screens. One is coming and there is a clock (and a web page saying that "LPS Now Launching...") After that web page, the tomcat starts and a new page opens stating that "LPS Initializing" and on that page on the top-left hand side of the screen, the message appears as "No request type: Media".
I also tried "hello.lzx" file with parameters as "lzt=html" or "lzt=xml" or "lzt=swf", but the same error appeared again. I hope these help for an explanation..
Burak
bloch
11-15-2003, 10:35 AM
A few questions to help me help you diagnose.
Can you surf to
http://localhost:8080/
to see the tomcat root?
And can you get to http://localhost:8080/lps-1.0.3
I'm hoping/assuming the answers to these q's are yes and that the tomcat console window is still up on your machine (it's a windows cmd shell).
Assuming it's up, could you cut and paste it s contents here?
-Eric
bozkeles
11-15-2003, 12:01 PM
Eric,
"Yes" to both of your questions.
The content of the shell window is as below;
--------------------------------------------------
Using CATALINA_BASE: C:\lps-1.0.2\jakarta-tomcat-4.1.12
Using CATALINA_HOME: C:\lps-1.0.2\jakarta-tomcat-4.1.12
Using CATALINA_TMPDIR: C:\lps-1.0.2\jakarta-tomcat-4.1.12\temp
Using JAVA_HOME: C:\j2sdk1.4.2_02
15.Kas.2003 21:44:50 java.util.jar.Attributes read
WARNING: Duplicate name in Manifest: Class-Path
15.Kas.2003 21:44:52 org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
15.Kas.2003 21:44:52 org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
15.Kas.2003 21:44:53 org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
15.Kas.2003 21:44:55 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
15.Kas.2003 21:45:31 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
15.Kas.2003 21:45:32 org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
15.Kas.2003 21:45:32 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=20/120 config=C:\lps-1.0.2\jakarta-tomcat-4.1.12\con
f\jk2.properties
--------------------------------------------------
Thanks for your help..
Burak
bloch
11-15-2003, 12:31 PM
The error message you're seeing probably
indicates that the LPS couldn't initialize for some really bad reason.
Could you look for the tomcat stderr, stdout files?
They can be hard to find on Windows. Sometimes thy're at C:\WINNT\system32\stderr.log and C:\WINNT\system32\stdout.log
or C:\Windows\...
Did you install anything in $JAVA_HOME/jre/lib/ext
(pardon the unix-y syntax).
-Eric
bozkeles
11-15-2003, 12:56 PM
Eric,
I could not find the std*.log files. Do they have a different name?
There's no other programs installed in the jre/ext directory other than 4 files; dnsns, ldapsec, localedata and sunjce_provider. All are jars.
The other log files that might be of interest are attached.
Thanks,
Burak
bloch
11-15-2003, 01:07 PM
Dang.
It's possible to diagnose without finding
those files, but it will be pretty hard. I'm expecting that those files will have the record of an exception stack trace that occurs in a place that our initialization code isn't expecting.
You might also look in
$TOMCAT_HOME/work/Standalone/localhost/lps-1.0.2/LPS/logs/lps-1.0.2.log
to see if there's anything there.
FYI, the stderr.log and stdout.log files are the java stderr and stdio streams.
Finally, you could edit $TOMCAT_HOME/webapps/lps-1.0.2/WEB-INF/lps/config/log4j.properties
and change the word INFO to DEBUG everywhere.
The restart the server and look for the lps-1.0.2.log file I mentioned above. This may help, but I think we might really need to find the stderr and stdout streams. It's also possible, but unlikely, that they're in a file called catalina.out.
I"m about to be out for a while...
-Eric
bozkeles
11-15-2003, 01:35 PM
Eric,
I did what you said, but nothing changed, I mean no weird message seemed to be present in the log file.
I am not able to find the stderr log files. Got stuck!
FYI,
Burak
bloch
11-15-2003, 05:38 PM
Hey Burak,
I'm sorry this is taking so long. I suspect it'll end up being something quite simple. I wonder if it's a permissions problem.
Let's try this. In a Windows cmd shell
cd %TOMCAT_HOME%\bin
catalina.bat run
and leave the cmd shell running
-------------
Then browse to http://localhost:8080/lps-1.0.2/examples/hello.lzx
I'm hoping you'll see some errors in the cmd shell.
-Eric
bozkeles
11-16-2003, 09:18 AM
Eric,
No improvement, yet!
The things written on the shell windows are as follows;
16.Kas.2003 19:00:45 org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
16.Kas.2003 19:00:45 org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
16.Kas.2003 19:00:49 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.12
16.Kas.2003 19:01:26 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
16.Kas.2003 19:01:26 org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
16.Kas.2003 19:01:26 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=90/110 config=C:\lps-1.0.2\jakarta-tomcat-4.1.12\con
f\jk2.properties
- ------------------------------------
- Laszlo Presentation Server, 1.0.2 Production, initialized
- Running in context:Apache Tomcat/4.1.12
- Build: lps-v1-000683-0003
- Built on: 06:57 PM 18-Sep-2003
- Expires: NEVER
- Running against JRE 1.4.2_02
- Running with Java CLASSPATH: C:\j2sdk1.4.2_02\lib\tools.jar;C:\lps-1.0.2\jakar
ta-tomcat-4.1.12\bin\bootstrap.jar
- Running on Windows 2000 5.0
- Running as user Administrator
- Total memory: 127.06 MB
- Available memory: 117.63 MB
- LPS_HOME is: C:\lps-1.0.2\jakarta-tomcat-4.1.12\webapps\lps-1.0.2\
- LPS developer
- Localhost (derintek) IP: 10.19.1.42
- Server IP(s): 127.0.0.1
- Cache is at C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1
.0.2\LPS\cache
- Cache is at C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1
.0.2\LPS\cache
- Responding with error (text/html): No request type: media
-------------------------------------
As you see it in the end, that gives the same error again.
Burak
bloch
11-16-2003, 10:15 AM
Normally the messages go:
.
.
.
- Cache is at C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS\cache
- Media Cache is at C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS\mcache
- Data Cache is at C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS\dcache
.
.
.
Hmm...could you report back the contents?
C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS\cache
and
C:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS\mcache
Does user Administrator have rights to read/create files in these directories?
This is puzzling...
-Eric
bloch
11-16-2003, 10:21 AM
Here's another important piece of debugging that will help us diagnose this one. Before you run catalina.bat, please do
set JAVA_OPTS="-verbose:class"
Thanks,
Eric
bloch
11-16-2003, 10:29 AM
Did you ever find the lps-1.0.2.log file either?
It should be there under
%TOMCAT_HOME%\work\Standalone\localhost\lps-1.0.2\LPS\logs
and if you've edited the log4j.properties file above, there maybe more info there for us to help diagnose more.
-Eric
bozkeles
11-16-2003, 11:01 AM
Eric,
Attached are the file for log.
No change, still. I am patient to see the results.
By the way, is this the 1st time you are having that problem?
Burak
bozkeles
11-16-2003, 11:03 AM
Also, I am the fully controlling the file system. No problem exists with writing.
Burak
bozkeles
11-16-2003, 11:12 AM
Eric,
Just to note:
My system is Win2K Server with SP4,
My J2RE is Java SDK and JRE with 1.4.2,
I have also installed Tomcat, but stopped as a service,
I tried the LPS in another PC with WinMe, but got the same results. I guess there is sth. wrong with the procedure I am applying, although there is nothing special.
Again what I did for running were as follows;
Downloaded the LPS DE (complete not the core), (stopped Tomcat), started the LPS, passed the 1st screen and got stuck on the 2nd screen with the message "No request type: media". Added the "lzt" query string to "html","swf","xml"; all giving the same error.
There is for sure sth. wrong with the Servlet, I guess. Because it is not properly responding. And that is basically dependant on the J2RE. I don't know what else!
Hope that helps also..
Burak
bloch
11-16-2003, 12:09 PM
Burak,
Sorry this is taking so long. This is pretty unusual and it's been good of you to be patient. Hopefully we'll get to it soon. FYI, there have been thousands of flawless lps installs.
I suspect something unusual/atypical about your environment that we haven't discovered yet. I wonder if you have TOMCAT_HOME or CATALINA_HOME or related variables defined somewhere that are confusing the embedded copy of tomcat that comes with the lps.
What version of Tomcat do you have installed outside of the LPS? It's possible that that installation of tomcat is confusing ours. We installed the latest tomcat5 on a windows machine here last week (as an nt service) and when we stop it, we're able to run the lps copy of tomcat just fine. So that alone probably wouldn't explain it though...
It looks like the change to the log4j.properties file didn't take since I'm not seeing any DEBUG log statements in the lps-1.0.2.log file.
When you run catalina.bat (with the JAVA_OPTS set) do you see any java debugging sent to your terminal; it should show the java classes being loaded and will be quite verbose. If you don't see this, then the JAVA_OPTS variables is not set correctly before you ran the .bat script.
I need to see that to help figure out what's going on.
Best,
-Eric
bozkeles
11-16-2003, 01:05 PM
Hi Eric,
When I write "catalina.bat run" on the cmd window, it now gives lots of LOADED statements with some CLASSNOTFOUND exceptions during startup. I guess, the problem lies here and I didn't understand anything. Here they are;
----------------------------------------
Exception during startup processing
java.lang.ClassNotFoundException: org.apache.catalina.startup.Catalina
[Loaded java.lang.StackTraceElement from C:\j2sdk1.4.2_02\jre\lib\rt.jar]
at org.apache.catalina.loader.StandardClassLoader.loa dClass(StandardClas
sLoader.java:992)
at org.apache.catalina.loader.StandardClassLoader.loa dClass(StandardClas
sLoader.java:857)
at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:176)
----------------------------------------
Burak
bozkeles
11-16-2003, 01:16 PM
Eric,
By the way, the LPS DE still runs! Doesn't that contradict to the fact that "catalina.bat run" doesn't startup correctly, now??
Burak
bloch
11-16-2003, 06:32 PM
This continues to be pretty strange!
Could you post the entire log from when you startup the lps copy of tomcat via catalina.bat?
Thx,
Eric
bozkeles
11-17-2003, 08:01 AM
Eric,
Sorry for the delay. Attached is the file for the screen after trying to run catalina.bat. FYI.
hope to solve it soon.
Burak
bloch
11-17-2003, 09:25 AM
Hey there,
Could you type
set
at the windows command prompt so I can see all the environment variables you have set.
The log you displayed made it seem as though tomcat couldn't find it's on %TOMCAT_HOME%\server\lib directory.
-Eric
bozkeles
11-17-2003, 12:15 PM
Here it is.
Burak
bloch
11-17-2003, 12:26 PM
Ok, let's try this. Let's unset CATALINA_HOME.
set CATALINA_HOME=""
should do it. Then try
catalina.bat run
again
-Eric
bozkeles
11-17-2003, 12:31 PM
Then it says;
"The CATALINA_HOME environment variable is not defined correctly. This environment variable is needed to run this program."
Burak
bloch
11-17-2003, 12:42 PM
Sorry, my DOS shell programming isn't that good.
set CATALINA_HOME=
(no quotes).
-E
bozkeles
11-17-2003, 12:52 PM
Eric,
The results on the screen are attached after the JAVA verbose set command and request of "hello.lzx" application.
The first statements are not shown but all the last rows are within the file.
Burak
bloch
11-17-2003, 01:18 PM
Can you report back the full contents of
c:\lps-1.0.2\jakarta-tomcat-4.1.12\work\Standalone\localhost\lps-1.0.2\LPS
and any of its subdirectories?
-Eric
bozkeles
11-17-2003, 01:26 PM
Eric,
The directories and contents there, are;
1. cache
- media directory, (full)
- many files with dat and swf extensions.
2. dcache (empty)
3. logs (attached)
4. mcache (empty)
Burak
bloch
11-17-2003, 02:17 PM
Could you send me the contents of
c:\lps-1.0.2\jakarta-tomcat-4.1.12\webapps\lps-1.0.2\WEB-INF\lps\config\log4j.properties
I'm not seeing DEBUG statements I'd expect to see in the lps-1.0.2.log . Please make sure that
the log level is changed from INFO to DEBUG and then restart the server via catalina.bat and then report back the details of the lps-1.0.2.log .
Thanks for sticking with it!
-Eric
bozkeles
11-17-2003, 02:26 PM
Eric,
Attached is the log file after changing to DEBUG. Sorry, I forgot to do that.
Burak
bloch
11-17-2003, 05:47 PM
This one's got me stumped. I going to stick
a copy of the lps.jar on our server
for you to download. This one has some more
debugginig in it for me to help determine
what exception is firing on your systems.
url to come soon...
-Eric
antun
11-18-2003, 08:37 AM
Here's the lps.jar:
http://www.laszlosystems.com/files/forums/lps.jar.zip
[We will be removing this jar soon]
-Antun
bozkeles
11-18-2003, 09:01 AM
Changes after replacing with the old jar are attached.
It formed a new lps-1.0.3 log file but did not write anything in that.
Burak
bozkeles
11-18-2003, 09:05 AM
Contents of log4j, also. Maybe it helps!
Burak
bloch
11-18-2003, 09:13 AM
Could you change the 1.0.2 in log4j.properties to 1.0.3 so more of the logging will work?
My guess is that this still won't show the problem though. But it's worth a shot.
-Eric
I vaguely recall seeing this error when running on Windows and I think it may have had to do with the pathname of the directory where the LPS and tomcat are installed. In particular, are there any spaces (like "Apache Group") in the path down to where tomcat is running?
Can you install apache tomcat in a directory with no spaces anyplace in it's path?
Just to be safe, make sure your LPS_HOME also is in a path with no spaces.
I remember also there was an issue when the config file (lps.properties) could not be read or could not open the log4j server log file to output to. Check that the server log destination exists and is writable with the server user.
bozkeles
11-18-2003, 10:05 AM
1. log4j changed as requested.
2. there is no space on the directories (exceot -,.)
3. LPS_HOME is in the env. system vars.
4. Server log destination exists and is writable by the srv usr.
Atached is also the log file.
Burak
bloch
11-18-2003, 11:32 AM
Hey Burak!
I think we got it. You must be in the Turkish locale. We have a bug in our code that uses the java String.toUpperCase() method, which works in a way we didn't expect in 1.4.2. It turns the string 'media' into 'MED?A'. Well, the workaround should be to hardcode the english locale for now until we have this fixed.
If you edit the catalina.bat script and add the line
set JAVA_OPTS="-Duser.language=en"
to the top, we should be ok.
Please let me know how it goes!
-Eric
bozkeles
11-18-2003, 12:04 PM
Eric,
Good news, 'cause it worked.
Thanks for your efforts since days. We will be partnering with Laszlo in the coming days and that was a good test for me, too!
Kind regards,
Burak Ozkeles
bloch
11-18-2003, 12:09 PM
Also, you should probably go back to using the original log4j.properties and lps.jar files.
Thanks, again, for being patient!
I will probably remove the lps.jar from here since it's not needed.
-Eric
vBulletin® v3.8.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.