[JBoss Seam] - MultipartFilter - exception redirect missed when maxsize exc
by nwray
Hi, I'm using the file upload tag s:fileUpload and org.jboss.seam.web.MultipartFilter in a seam 2.0.0CR1 project. I have a maxRequestSize configured in components.xml:
| <component class="org.jboss.seam.web.MultipartFilter">
| <property name="createTempFiles">false</property>
| <property name="maxRequestSize">41943040</property>
| </component>
|
and in pages.xml I have the following:
<exception class="org.jboss.seam.web.FileUploadException">
| <redirect view-id="/main.xhtml">
| <message severity="error">File upload failed, probably because the file is too large</message>
| </redirect>
| </exception>
When I upload a file larger than the max size, I see a debug page with the following stack trace:
| 2007-09-28 10:24:40,703 ERROR [org.jboss.seam.web.ExceptionFilter] handling uncaught exception
| org.jboss.seam.web.FileUploadException: Multipart request is larger than allowed size
| at org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:280)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:80)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| [...]
| 2007-09-28 10:24:40,703 ERROR [org.jboss.seam.web.ExceptionFilter] exception root cause
| 2007-09-28 10:24:40,718 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/set].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
| java.lang.NullPointerException
| at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:93)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
|
rather than seeing main.seam with the expected message, as configured in pages.xml. Following the stack trace back it seems that ExceptionFilter at line 93 assumes a Manager will be found in the request. When the Manager comes back null we get the NPE. I created a patch I'm using locally that handles the missing Manager, attached to Jira 1995:
http://jira.jboss.com/jira/browse/JBSEAM-1995
Am I seeing this due to some underlying misconfiguration on my side or is this a bug? I created the Jira last week but no feedback as of yet.
thanks
Nathan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091706#4091706
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091706
18Â years, 6Â months
[Remoting] - Sockets left in CLOSE_WAIT on server
by engluer
I was trying to cleaning close a connection to a JBoss server. I have tried the following on both JBoss 4.2.2 with Messaging and JBoss 5 b2 and in both cases when the client closes the connection a socket is left in the CLOSE_WAIT state on the server. In both cases I was using the BiSocket transport
| import javax.jms.Connection;
| import javax.jms.ConnectionFactory;
| import javax.jms.Destination;
| import javax.jms.JMSException;
| import javax.jms.Message;
| import javax.jms.MessageConsumer;
| import javax.jms.MessageListener;
| import javax.jms.Session;
| import javax.naming.InitialContext;
| import javax.naming.NamingException;
|
| /*
| *
| * Note monitor server connections with
| * watch "/usr/sbin/lsof -p [pid of Jboss server] | grep -c CLOSE_WAIT"
| *
| */
|
| public class SimpleSubscriber implements MessageListener {
|
| private Session subSession;
| private Connection connection;
| private String destName;
|
| private String password;
| private String username;
| private ConnectionFactory conFactory;
| private InitialContext ic;
| private MessageConsumer subscriber;
|
| public SimpleSubscriber(String destName, String username, String password) {
| this.destName = destName;
| this.username = username;
| this.password = password;
| }
|
| private void connect() throws NamingException, JMSException {
| if (ic == null) {
| ic = new InitialContext();
| }
|
| //Look up JMS connection Factory
| conFactory = (ConnectionFactory)ic.lookup("/ConnectionFactory");
|
| //Lookup Destination
| Object obj = ic.lookup(destName);
| Destination topic = (Destination)obj;
|
| //Create JMS connection
| connection = conFactory.createConnection(username, password);
|
| //Create two JMS session objects
| subSession = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
| subscriber = subSession.createConsumer(topic);
| subscriber.setMessageListener(this);
|
| //Start the connection
| connection.start();
| }
|
| public void close() throws JMSException {
| subscriber.close();
| subSession.close();
| connection.close();
| }
|
| public static void main(String [] args) {
| String username = null;
| String password = null;
| String dest= null;
|
| if (args.length != 3) {
| printUsage();
| return;
| }
|
| dest= args[0];
|
| username = args[1];
| password = args[2];
|
| final SimpleSubscriber subscriber = new SimpleSubscriber(dest, username, password);
|
| System.out.println("Connecting to JBoss...");
| try {
| subscriber.connect();
| } catch (NamingException e) {
| e.printStackTrace();
| return;
| } catch (JMSException e) {
| e.printStackTrace();
| return;
| }
|
| System.out.println("Connected");
|
| System.out.println("Sleeping");
|
| try {
| Thread.sleep(5000);
| } catch (InterruptedException e) {}
| System.out.println("Disconnecting");
|
| try {
| subscriber.close();
| } catch (JMSException e) {
| e.printStackTrace();
| }
|
| System.out.println("Closed");
|
| try {
| Thread.sleep(5000);
| } catch (InterruptedException e) {}
|
| System.out.println("Done");
| }
|
| private static void printUsage() {
| System.out.println("Subscriber <topic> [username] [password]"
| + "\ntopic: Name of topic to connect to pings with"
| + "\nusername: Username to connect with"
| + "\npassword: Password to connect with");
| }
|
| public void onMessage(Message arg0) {
| System.out.println("Received Message: " + arg0);
| }
|
| }
|
Th above example connects waits, then disconnects and waits, then shuts down. Am I not closing the connection correctly? I am using the following to check for socket state.
| watch "/usr/sbin/lsof -p [pid of Jboss server] | grep -c CLOSE_WAIT"
|
The server we are using has client connecting and disconnecting quite rapidly and we quickly run out of file descriptors because of all the CLOSE_WAIT sockets left open.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091683#4091683
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091683
18Â years, 6Â months