You need to set the log4j threshold to DEBUG for
org.jboss.seam.remoting.ExecutionHandler. If you're using JBossAS, it comes
configured by default to log debug messages.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111048#4111048
Reply to the post :
http
Hey so I don't see the exception being propagated to the browser now which is
great. I see the exceptions in the log but I have set the logging in the app.
server to finest and still do not see the debug messages. What is required to
enable the log debugging?
S.D.
View the original post :
htt
Cool and thanks, I'll checkout and build again.
S.D.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110713#4110713
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110713
___
j
I've modified the code a little further to pre-cache the request data before
parsing it as XML. It is also logged as a debug message, so you should be able
to see the exact XML that is being parsed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110703#41107
Hello Shane, latest build from CVS still generates this error periodically.
|
[#|2007-12-05T13:48:50.106-0500|SEVERE|sun-appserver9.1|org.jboss.seam.remoting.Remoting|_ThreadID=20;_ThreadName=httpSSLWorkerThread-38080-1;_RequestID=b24ed108-c908-43e6-81c5-bbf9ccc60b3b;|Error
| org.dom4j.Docum
I lost our demo box again until tomorrow but what happens sometimes is that in
the debug output window it just says empty response immediately followed by the
expected response. Seemed odd.
S.D.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110397#4110397
The request packet looks well-formed and complete, it's not clear why the
exception is being thrown. Just to try something different, I've wrapped the
request's InputStream in an InputStreamReader for the parsing of the xml. You
can try this in the latest CVS version.
"samdoyle" wrote :
|
Anyone?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110351#4110351
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110351
___
jboss-user mailing list
jboss-user@lists.jboss.
The following produced the error, doesn't look unusual. It is the same as the
several succeeding requests before it.
|
| Tue Dec 4 11:01:57 PST 2007: Request packet:
|
41
|
|
|
As a result of this it is generating a error 400 poup dialog which as a result
of the current way re
No JavaScript errors. I'll check it out with debugging enabled.
S.D.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110294#4110294
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110294
_
I haven't seen this before. Are there any Javascript errors when this occurs?
I suggest you turn on debug mode so that you can examine the request packets
that are being sent to the server to confirm that they are complete. Debug
mode is turned on like this:
Seam.Remoting.setDebug(true)
Vie
Anyone see this before?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110063#4110063
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110063
___
jboss-user mailing list
jboss-u
12 matches
Mail list logo
