Hi, this is my jsp page and i just print the exception, it gives me null.
You might be using the error jsp page in your application to catch some of the exceptions which might be thrown inside the jsp pages. But, in my case the exception is being thrown by the ServerDatabaseLoginModule and which is not reaching till the error jsp page. I will check your suggestion of Tomcat Valve. Thanks a lot.
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ page isErrorPage="true" import="java.io.*" %>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
Insert title here
exception object
<%=exception%>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203723#4203723
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203723
Hi,
I'm trying to use a Struts Action as part of the login sequence of the portal.
I've got it all working fine - the Struts libs are in the jboss-portal.sar lib folder, and our portal application ear (has to be) is dependent on them.
Unforunately this means the wars in the ear utilised the Struts i8n properties etc from the jboss-portal.sar config, and not individually as they should.
We don't want to have to copy the properties files over the jboss installation everytime we do a deploy - we expect the properties to be contained within the war (in the ear).
Firstly - why is it that the sar's classpath interfere's with that of the ear's war.
Secondly, is there any way around this problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203716#4203716
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203716
Your "ConnectionTable" logging:
| 09:02:22,093 WARN [ConnectionTable] peer closed connection, trying to re-send msg
| 09:02:22,093 ERROR [ConnectionTable] 2nd attempt to send data failed too
is coming from the JBoss Messaging Data Channel. That channel uses TCP unicast for sending messages, unlike the other channels that use UDP multicast.
Farming doesn't use that channel; it uses a different one, the UDP multicast-based one from cluster-service.xml.
So, two separate channels using different underlying protocols are experiencing problems, which sounds to me like a network or host configuration problem. Hard to say what; if resolving the firewall issues you raise in a separate thread make it go away, there's your answer.
See also http://www.jboss.org/community/docs/DOC-12375
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203715#4203715
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203715