Problem with hx:fileupload

Hello!
I have a new problem. I'm using a hx:fileupload tag, but when I write in this input text intead of selecting the browse button I get a javascript error. I have read that is a problem only with IE, so I need to make readonly this field.
I have also read that a readonly is not easy for an input type file, I have found a solution here
http://www.codeguru.com/forum/archive/index.php/t-197501.html
but when I have tried the solution I find a new error, when I click over a submit file my hx:fileuploadis clear and a submit is not executed.
I don�t know why my file is clear.
Can someone help me again
thanks

Sorry, I have no solution for you but I do have the same problem. I have been searching every java site/forum I could found for a solution but no luck so far.
As soon as the �DiskFileUpload upload = new DiskFileUpload()� line is executed the program crash with a NoClassDefFoundError: javax/servlet/ServletInputStream. There is no problem creating a ServletInputStream object though. I would also appreciate it very much if anyone could give us any ideas on what might cause this error.

Similar Messages

Problem with commons-fileupload library.

Hello,
I'm using the following code to try and upload files to my Tomcat server from HTTP clients. The code is inside a JSP page. When I submit the form to this jsp page, I get no errors but the file is not being uploaded and the only out.println statement that is printing is the first one that tests if the form is multi-part. It prints true.
     boolean isMultipart = FileUpload.isMultipartContent(request);
     out.println("" + isMultipart);
     if (isMultipart) {
          DiskFileUpload upload = new DiskFileUpload();
          upload.setSizeThreshold(2000000);
          upload.setSizeMax(5000000);
          int sizeThresh = 2000000, sizeMax = 5000000;
          String dir = "c:/temp";
          List items = upload.parseRequest(request, sizeThresh, sizeMax, dir);
          Iterator iter = items.iterator();
          while (iter.hasNext()) {
               FileItem item = (FileItem) iter.next();
               out.println(item.getFieldName());
               if (item.isFormField()) {
                    continue;
               else {
                    String fieldName = item.getFieldName();
                    String fileName = item.getName();
                    String contentType = item.getContentType();
                    boolean isInMemory = item.isInMemory();
                    long sizeInBytes = item.getSize();
                    out.println("Info: " + sizeInBytes + " " + contentType + " " + fileName + " " + fieldName);
                    File uploadedFile = new File("test.txt");
                    item.write(uploadedFile);
     } Any idea what my problem is?
Thanks.

Sorry to keep posting but this gets more complex. Here's the deal.
The UploadBean works on both Tomcat 4 and Tomcat 5 as long as the code below has not been called yet for the user's session. It is code that asks the browser for authentication. Once this code has been called for the current session, the Upload Bean no longer works.
Any idea what would cause this?
package com.biscuit.servlets;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
* NTLM authorization (Challenge-Response) test servlet.
* Requires IE on the client side.
* In order to avoid browser log on dialog box User Authentication/Logon
* settings should be set to:
* <ol>
* <li>Automatic logon in Intranet zone or</li>
* <li>Automatic logon with current username and password</li>
* </ol>
* Based on information found on jGuru WEB site:
* http://www.jguru.com/faq/viewquestion.jsp?EID=393110
* @author Leonidius
* @version 1.0 2002/06/17
public class NTLMTest extends HttpServlet{
     // Step 2: Challenge message
     final private static byte[] CHALLENGE_MESSAGE =
          {(byte)'N', (byte)'T', (byte)'L', (byte)'M', (byte)'S', (byte)'S', (byte)'P', 0,
          2, 0, 0, 0, 0, 0, 0, 0,
          40, 0, 0, 0, 1, (byte)130, 0, 0,
          0, 2, 2, 2, 0, 0, 0, 0, // nonce
          0, 0, 0, 0, 0, 0, 0, 0};
     * HTTP request processing
     protected synchronized void service(HttpServletRequest request,
          HttpServletResponse response)
          throws IOException, ServletException{
          PrintWriter out = response.getWriter();
          try{
               String auth = request.getHeader("Authorization");
               if (auth == null) {
                    response.setContentLength(0);
                    response.setStatus(HttpServletResponse.SC_UNAUTHORIZED);
                    response.setHeader("WWW-Authenticate", "NTLM");
                    response.flushBuffer();
                    return;
               if (!auth.startsWith("NTLM ")) return;
               byte[] msg = new sun.misc.BASE64Decoder().decodeBuffer(auth.substring(5));
               // Step 1: Negotiation message received
               if (msg[8] == 1) {
                    // Send challenge message (Step 2)
                    response.setContentLength(2);
                    response.setStatus(HttpServletResponse.SC_UNAUTHORIZED);
                    response.setHeader("WWW-Authenticate",
                    "NTLM " + new sun.misc.BASE64Encoder().encodeBuffer(CHALLENGE_MESSAGE));
                    out.println(" ");
                    response.flushBuffer();
                    return;
               // Step 3: Authentication message received
               if (msg[8] == 3) {
                    int off = 30;
                    int length, offset;
                    length = (msg[off+1]<<8) + msg[off];
                    offset = (msg[off+3]<<8) + msg[off+2];
                    String domain = new String(msg, offset, length);
                    domain = removeBlanks(domain).toUpperCase();
                    length = (msg[off+9]<<8) + msg[off+8];
                    offset = (msg[off+11]<<8) + msg[off+10];
                    String user = new String(msg, offset, length);
                    user = domain + "\\" + removeBlanks(user).toUpperCase();
                    HttpSession session = request.getSession(true);
                    session.setAttribute("userID", user);
                    String forwardAddress = "home";
                    RequestDispatcher dispatcher = request.getRequestDispatcher(forwardAddress);
                    dispatcher.forward(request, response);
//                    length = (msg[off+17]<<8) + msg[off+16];
//                    offset = (msg[off+19]<<8) + msg[off+18];
//                    String ws = new String(msg, offset, length);
//                    ws = removeBlanks(ws);
//                    response.setContentType("text/html");
//                    out.println("<html>");
//                    out.println("<head>");
//                    out.println("<title>NT User Login Info</title>");
//                    out.println("</head>");
//                    out.println("<body>");
//                    out.println(new java.util.Date() + "<br>");
//                    out.println("Server: " + request.getServerName() + "<br><br>");
//                    out.println("Domain: " + removeBlanks(domain) + "<br>");
//                    out.println("Username: " + removeBlanks(user) + "<br>");
//                    out.println("Workstation: " + removeBlanks(ws) + "<br>");
//                    out.println("</body>");
//                    out.println("</html>");
          catch (Throwable ex){
               ex.printStackTrace();
     }//service
     * Removes non-printable characters from a string
     private synchronized String removeBlanks(String s){
          StringBuffer sb = new StringBuffer();
          for (int i = 0; i < s.length(); i++) {
               char c = s.charAt(i);
               if (c > ' ')
               sb.append(c);
          return sb.toString();
}//class NTLMTest

Problems with htmlb:fileUpload

Hi, I am trying to implement a JSPDynPage which uses the
fileUpload-Tag. In most cases it works fine but sometimes I can select a file but the next button click (onWork) event is not send to the server.
<hbj:form id="myForm" encodingType="multipart/form-data">
<hbj:formLayoutCell id="cf_fimport_2" align="center" valign="TOP" width="175">
<hbj:fileUpload id="upload" size="30" accept="plain/text"/>
</hbj:formLayoutCell>
and the button is defined
<hbj:formLayoutCell id="cf_fimport_5" align="right" paddingRight="7">
<hbj:button id="bpreview" text='doWork' design="STANDARD" disabled="false"
onClick="work"/>
</hbj:formLayoutCell>
The page is refreshed but no action is done.
Any idea?
Is there a bit more documentation about the fileUpload-Tag ?
Environment:
Windows XP
SAP EP6 SP4 Sneak Preview
IE 6.0
Regards
Edmund

Dear Edmund.
I've exactly the same problem.
In details:
Prerequisites:
1) there is <hbj:fileUpload ...> tag on the jsp.
2) The form is declared as <hbj:form id="....." encodingType="multipart/form-data">
3) There is defined button with handled event e.g. "onButtonClicked"
4) The user will insert any file to the tag
Behavior:
1) The request does NOT consist ANY components. ( I can see in the log )
2) The method "onButtonClicked" is NOT called.
3) Randomly - there is onInitialization() method called.
As it was mentioned by You, the older versions of portal works with the hbj:fileUpload correctly.
I will be very pleased with someone explaining the problem.
Regards Best
Marek
P.S.Very interesting fact: when <the hbj:fileUpload> is empty the request is sent properly - with all the components.

Problem with Commons FileUpload and ssl

Hi,
i want to send to servlet mulipart form data using ssl:
this is my html page:
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>simple form page</title>
    </head>
    <body>
        <form method="POST" enctype="multipart/form-data" action="SimpleResponseServlet">
            <br><input type=file name=upfile></input></br>
            <br><input type=text name=note></input></br>
            <br><input type=submit value=Press></input></br>
         </form>
     </body>
</html>This is code from SimpleResponseServlet:
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException {
   response.setContentType("text/plain;");
   PrintWriter out = response.getWriter();
   boolean isMultipart = ServletFileUpload.isMultipartContent(request);
   System.err.println(isMultipart);
   try{
            FileItemFactory factory = new DiskFileItemFactory();
            ServletFileUpload upload = new ServletFileUpload(factory);
            List items = upload.parseRequest(request);
         Iterator iter = items.iterator();
            while(iter.hasNext())
                 FileItem item = (FileItem) iter.next();
                 System.out.println(item.getContentType());
                 System.out.println(item.getFieldName());
                 System.out.println(item.getName());
                 System.out.println(item.isFormField());
       out.println("ok");
catch(Exception ex){
   System.out.println(ex.toString());
finally{
    out.close();
        this is what Tomcat 6.0 console show using https to call servlet:
false
org.apache.commons.fileupload.FileUploadBase$InvalidContentTypeException:the request doesn't contain a multipart/form-data or multipart/mixed-stream, content type header is null.if i use normal http servlet works fine.
Help me, please.
Thank you,
David.

I have replaced in html page this attribute:
action="SimpleResponseServlet"with this:
action="https://localhost:8443/ProvaImageReaderServlet/SimpleResponseServlet"and servlet can read items because there's not redirecting.
But is it a clear way call directly servlet with https???
Thank you....

Problem with commons.fileupload

I'm using Tomcat 4.1 and before I couldn't get the compiler to find the package until I put it in my %JAVA-HOME%\jre\lib\ext folder. After I did that I could compile just fine. Now when I try uploading a file I get 'NoClassDefFoundError'. I read that this is because I have the jar file in both the %JAVA-HOME% and WEB-INF\lib . I tried running it without having it in %JAVA-HOME% and it made no difference. If anyone can help I would really appreciate it. Thanks.

I suggest taking a look at the user guide, they do some things differently than you do:
http://jakarta.apache.org/commons/fileupload/using.html

Problems with FileUpload Demo

Hi!, i have a problem with the File Upload Demo when it calls this line:
hDirectoryObject := JFile.new(directory);
and the error is: error 6508 "PL/SQL: could not find program unit being called"
That's ok, but anybody knows why should the program couldnt find the routine ?
And just one more thing...where can i look for JFile method description ??
Thanks a lot :) !!
Cristian.

Hi!, i have a problem with the File Upload Demo when it calls this line:
hDirectoryObject := JFile.new(directory);
and the error is: error 6508 "PL/SQL: could not find program unit being called"
That's ok, but anybody knows why should the program couldnt find the routine ?
And just one more thing...where can i look for JFile method description ??
Thanks a lot :) !!
Cristian.

Problem with deploying SPLService (CC&B2.2.0) on OAS

Hi,
I have a problem with installation CC&B 2.2.0.
I have this error during the deploying it on Oracle Application Server:
09/01/28 08:23:22 Start process
09/01/28 08:23:30 Oracle Containers for J2EE 10g (10.1.3.1.0) initialized
- 08:25:46,009 [DeployerRunnable Thread for SPLService] INFO (service.impl.ServiceBeanContext) Initializing Service Bean
- 08:25:46,025 [DeployerRunnable Thread for SPLService] INFO (shared.environ.ApplicationProperties) loaded properties from resource spl.properties: {spl.runtime.service.extraInstallationServices=CILTINCP, spl.runtime.cobol.remote.jvmcommand=C:/PFiles/Java/jdk1.5.0_09/bin/java.exe, spl.tools.loaded.applications=base,ccb,cm, spl.runtime.cobol.remote.jvmcount=2, spl.runtime.socket.file.dir=C:/spl/ccb/runtime, spl.runtime.cobol.sql.fetchSize=50, spl.runtime.cobol.cobrcall=false, spl.runtime.cobol.encoding=UTF8, spl.runtime.cobol.sql.disableQueryCache=false, com.splwg.grid.online.enabled=true, spl.runtime.utf8Database=true, spl.runtime.cobol.remote.jvmoptions=-Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar, spl.runtime.environ.init.dir=C:/spl/ccb/etc, com.splwg.grid.distThreadPool.threads.DEFAULT=5, spl.runtime.cobol.sql.cache.maxTotalEntries=1000, spl.runtime.oracle.statementCacheSize=300, spl.runtime.cobol.remote.rmiStartPort=6503, spl.runtime.cobol.sql.cursoredCache.maxRows=10, spl.runtime.cobol.remote.jvm=true, com.splwg.batch.scheduler.daemon=true, spl.runtime.sql.highValue=}
- 08:25:46,025 [DeployerRunnable Thread for SPLService] INFO (shared.context.ApplicationMode) Application set to production mode
- 08:25:46,041 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Creating default context
- 08:25:47,697 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Loading lookups for runtime discovery of implemented lookups in application
- 08:25:48,228 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Done loading lookups for discovery, time 526,639 ms
- 08:25:51,259 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Discovering lookups for base
- 08:25:51,525 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Done discovering base lookups (generated=203, manual=23), time 263,781 ms
- 08:25:54,869 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Discovering lookups for ccb
- 08:25:55,134 [DeployerRunnable Thread for SPLService] INFO (shared.context.ContextLoader) Done discovering ccb lookups (generated=439, manual=81), time 257,230 ms
- 08:25:55,197 [DeployerRunnable Thread for SPLService] WARN (shared.environ.ContextManagedObjectSet) Could not load resource com/splwg/cm/domain/contextManagedObjects.xml on classpath. This may be harmless but could mean a problem with the classpath. Please verify that the classpath for application cm is correctly configured.
- 08:26:07,415 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering lookups
- 08:26:07,900 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 613 lookups registered, time 483,437 ms
- 08:26:07,900 [DeployerRunnable Thread for SPLService] INFO (support.context.ComponentContainerLookupHelper) Initializing constants on 642 lookup interface classes
- 08:26:08,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ComponentContainerLookupHelper) Done initializing lookup constants, time 862,978 ms
- 08:26:08,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Entities
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 857 entities registered, time 2 621,264 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Code Description queries
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 50 code/description queries registered, time 0,085 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering algorithm spots
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 183 algorithm spots registered, time 0,382 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering algorithm components
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 68 algorithm components registered, time 0,087 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering batch jobs
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 21 batch jobs registered, time 0,052 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Components
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 489 components registered, time 4,287 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Change Handlers
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 237 handlers registered, time 0,913 ms
- 08:26:11,384 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering Services
- 08:26:11,399 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 460 services registered, time 13,970 ms
- 08:26:11,399 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering cobol programs
- 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 351 cobol copybooks registered, time 293,026 ms
- 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) Registering cobol programs
- 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ContextFactory) 105 cobol programs registered, time 0,094 ms
- 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Building hibernate configuration
- 08:26:11,696 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Adding 857 hibernate mappings
- 08:26:13,603 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 100 mappings
- 08:26:14,321 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 200 mappings
- 08:26:15,056 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 300 mappings
- 08:26:15,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 400 mappings
- 08:26:16,462 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 500 mappings
- 08:26:17,118 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 600 mappings
- 08:26:17,759 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 700 mappings
- 08:26:18,415 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 800 mappings
- 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Added 857 mappings
- 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Done building hibernate configuration, time 7 095,676 ms
- 08:26:18,790 [DeployerRunnable Thread for SPLService] INFO (support.context.ApplicationContext) Building hibernate session factory
- 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.ConnectionProviderFactory) Initializing connection provider: org.hibernate.connection.C3P0ConnectionProvider
- 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) C3P0 using driver: oracle.jdbc.driver.OracleDriver at URL: jdbc:oracle:thin:@localhost:1521:ccb
- 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) Connection properties: {user=cisuser, password=****}
- 08:26:20,165 [DeployerRunnable Thread for SPLService] INFO (hibernate.connection.C3P0ConnectionProvider) autocommit mode: false
- 08:26:20,181 [DeployerRunnable Thread for SPLService] INFO (v2.log.MLog) MLog clients using log4j logging.
- 08:26:20,259 [DeployerRunnable Thread for SPLService] INFO (v2.c3p0.C3P0Registry) jdk1.5 management interfaces unavailable... JMX support disabled.
java.lang.SecurityException: Unauthorized access from application: SPLService to MBean: java.lang:type=ClassLoading
     at oracle.oc4j.admin.jmx.shared.UserMBeanServer.checkRegisterAccess(UserMBeanServer.java:873)
     at oracle.oc4j.admin.jmx.shared.UserMBeanServer.registerMBean(UserMBeanServer.java:400)
     at oracle.oc4j.admin.jmx.server.state.LocalizationFilterMBeanServer.registerMBean(LocalizationFilterMBeanServer.java:348)
     at sun.management.ManagementFactory$1.run(ManagementFactory.java:240)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.management.ManagementFactory.addMBean(ManagementFactory.java:235)
     at sun.management.ManagementFactory.addMBean(ManagementFactory.java:223)
     at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:266)
     at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:512)
     at com.mchange.v2.c3p0.management.ActiveManagementCoordinator.<init>(ActiveManagementCoordinator.java:42)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
     at java.lang.Class.newInstance0(Class.java:350)
     at java.lang.Class.newInstance(Class.java:303)
     at com.mchange.v2.c3p0.C3P0Registry.<clinit>(C3P0Registry.java:134)
     at com.mchange.v2.c3p0.impl.DriverManagerDataSourceBase.<init>(DriverManagerDataSourceBase.java:206)
     at com.mchange.v2.c3p0.DriverManagerDataSource.<init>(DriverManagerDataSource.java:60)
     at com.mchange.v2.c3p0.DriverManagerDataSource.<init>(DriverManagerDataSource.java:56)
     at com.mchange.v2.c3p0.DataSources.unpooledDataSource(DataSources.java:152)
     at org.hibernate.connection.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:154)
     at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
     at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
     at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:414)
     at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62)
     at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
     at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
     at com.splwg.base.support.context.ApplicationContext.buildSessionFactory(ApplicationContext.java:152)
     at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:114)
     at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:88)
     at com.splwg.base.support.context.ContextFactory.createDefaultContext(ContextFactory.java:497)
     at com.splwg.ejb.service.impl.ServiceBeanContext.initializeApplicationContext(ServiceBeanContext.java:79)
     at com.splwg.ejb.service.impl.ServiceBeanContext.initialize(ServiceBeanContext.java:27)
     at com.splwg.ejb.service.impl.ServiceBean.<clinit>(ServiceBean.java:43)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:242)
     at com.evermind.server.ejb.deployment.BeanDescriptor.initialize(BeanDescriptor.java:288)
     at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.initialize(ExposableBeanDescriptor.java:173)
     at com.evermind.server.ejb.deployment.SessionBeanDescriptor.initialize(SessionBeanDescriptor.java:225)
     at com.evermind.server.ejb.deployment.EJBPackage.initialize(EJBPackage.java:999)
     at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:852)
     at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
     at com.evermind.server.Application.setConfig(Application.java:413)
     at com.evermind.server.Application.setConfig(Application.java:314)
     at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
     at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
     at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
     at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
     at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
Can anyone help me to resolve this?
Thanks - Michael

Yes, SYSUSER is defined and it is a member of cisusers group.
on another forum I found a solution for "Unauthorized access exc...". I added "-Doc4j.jmx.security.proxy.off=true" to "Start-parameters: Java Options". Now I don't have this error, but I have another:
- 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using provided java command for remote cobol execution: C:/PFiles/Java/jdk1.5.0_09/bin/java.exe
- 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using provided java command options for remote cobol execution: -Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar
- 09:17:53,725 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using starting port number 6503 for remote cobol execution.
- 09:17:53,740 [DeployerRunnable Thread for SPLService] INFO (cobol.host.SocketStrategy) Socket strategy set to com.splwg.base.support.cobol.host.sockets.WindowsPipeSocketStrategy
- 09:17:53,756 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6504
- 09:17:53,787 [JVM Socket Listener] DEBUG (support.context.ThreadlocalStorage) Added entry to ThreadlocalStorage global map, current size: 3
- 09:17:53,787 [JVM Socket Listener] DEBUG (host.sockets.WindowsPipeSocket) Creating server socket for named pipe remoteJvmPipe6504
- 09:17:53,787 [DeployerRunnable Thread for SPLService] INFO (cobol.host.CobolHostStartup) Using active JVM count of 2 for remote cobol execution.
- 09:17:53,803 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6506
- 09:17:53,803 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteJVMFactoryImpl) Command line used to launch child JVM: C:/PFiles/Java/jdk1.5.0_09/bin/java.exe -Xmx512m -server -Dfile.encoding=ISO8859_1 -cp C:/spl/ccb/splapp/standalone/config;C:/spl/ccb/splapp/standalone/lib/activation_api-1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-beanutils-core-1.7.0.jar;C:/spl/ccb/splapp/standalone/lib/commons-codec-1.3.jar;C:/spl/ccb/splapp/standalone/lib/commons-collections-2.1.1.jar;C:/spl/ccb/splapp/standalone/lib/commons-fileupload-1.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-httpclient-2.0.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-io-1.3.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-lang-2.2.jar;C:/spl/ccb/splapp/standalone/lib/commons-logging-1.0.4.jar;C:/spl/ccb/splapp/standalone/lib/concurrent-1.3.4.jar;C:/spl/ccb/splapp/standalone/lib/dom4j-1.6.1.jar;C:/spl/ccb/splapp/standalone/lib/hibernate-3.2.5.ga.jar;C:/spl/ccb/splapp/standalone/lib/icu4j-3.6.1.jar;C:/spl/ccb/splapp/standalone/lib/jaxen-1.1.1.jar;C:/spl/ccb/splapp/standalone/lib/jcip-annotations.jar;C:/spl/ccb/splapp/standalone/lib/jta.jar;C:/spl/ccb/splapp/standalone/lib/jtds-1.2.jar;C:/spl/ccb/splapp/standalone/lib/log4j-1.2.15.jar;C:/spl/ccb/splapp/standalone/lib/mail_api-1.4.jar;C:/spl/ccb/splapp/standalone/lib/mfcobol.jar;C:/spl/ccb/splapp/standalone/lib/ojdbc5-11.1.0.6.0.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-collation.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-mapping.jar;C:/spl/ccb/splapp/standalone/lib/orai18n-utility.jar;C:/spl/ccb/splapp/standalone/lib/orai18n.jar;C:/spl/ccb/splapp/standalone/lib/serializer-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-base-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-ccb-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-servicebeaninterface-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-serviceclient-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-shared-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-web-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/spl-xai-2.2.0.jar;C:/spl/ccb/splapp/standalone/lib/xalan-2.7.0.jar;C:/spl/ccb/splapp/standalone/lib/xmlparserv2.jar;C:/spl/ccb/splapp/standalone/lib/xquery.jar;C:/spl/ccb/splapp/standalone/lib/xstream-1.2.1.jar;C:/spl/ccb/splapp/standalone/lib/yjp-controller-api-redist.jar com.splwg.base.support.cobol.host.RemoteJVM 1 6505 6506 2
- 09:17:53,834 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteRequestTimer) Request made:RegisterServerExecuterCommand for connection 5040264954652086151
- 09:17:53,834 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.RemoteRunnerImpl) Invoking command: RegisterServerExecuterCommand
- 09:17:53,850 [DeployerRunnable Thread for SPLService] DEBUG (cobol.host.SocketStrategy) Attempting to create socket on port 6506
- 09:17:53,850 [DeployerRunnable Thread for SPLService] DEBUG (host.sockets.WindowsPipeSocket) Creating client socket for named pipe remoteJvmPipe6506
- 09:17:53,850 [DeployerRunnable Thread for SPLService] WARN (cobol.host.SocketStrategy) Unable to create socket on port 6506
java.net.ConnectException: Error: Could not open pipe
caused by system error: cannot find the file specified.
     at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.connectToPipe(Native Method)
     at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.<init>(WindowsPipeSocket.java:64)
     at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.createSocket(WindowsPipeSocket.java:100)
     at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocket.connect(WindowsPipeSocket.java:96)
     at com.splwg.base.support.cobol.host.sockets.WindowsPipeSocketStrategy.openSocket(WindowsPipeSocketStrategy.java:32)
     at com.splwg.base.support.cobol.host.SocketStrategy.unsafeOpen(SocketStrategy.java:119)
     at com.splwg.base.support.cobol.host.SocketStrategy.open(SocketStrategy.java:104)
     at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.createNewHolder(OptimizedRemoteExecuterStub.java:162)
     at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.getStreamHolder(OptimizedRemoteExecuterStub.java:125)
     at com.splwg.base.support.cobol.host.OptimizedRemoteExecuterStub.invoke(OptimizedRemoteExecuterStub.java:46)
     at com.splwg.base.support.cobol.host.RemoteRunnerImpl.invoke(RemoteRunnerImpl.java:89)
     at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.createRemoteRunner(RemoteJVMConnectionImpl.java:148)
     at com.splwg.base.support.cobol.host.RemoteJVMConnectionImpl.<init>(RemoteJVMConnectionImpl.java:67)
     at com.splwg.base.support.cobol.host.RemoteJVMFactoryImpl.addConnection(RemoteJVMFactoryImpl.java:92)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.addNewConnection(RotatingCommandRunnerProvider.java:135)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.addNecessaryConnections(RotatingCommandRunnerProvider.java:121)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider.access$800(RotatingCommandRunnerProvider.java:30)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.performPollingActions(RotatingCommandRunnerProvider.java:257)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.performRunLoop(RotatingCommandRunnerProvider.java:239)
     at com.splwg.base.support.cobol.host.RotatingCommandRunnerProvider$ConnectionMonitor.run(RotatingCommandRunnerProvider.java:230)
     at java.lang.Thread.run(Thread.java:595)
other processes don't use port 6506, java.exe opens this port few secounds after starting genoasdeploy.cmd
Edited by: user4630304 on 2009-02-03 02:29

Problem with File Uploading.

Hi,
I have one problem with File Upload component.
JSP
<ui:upload binding="#{NewProblem.fileUpload1}" columns="#{SessionBean1.uploadedFile}" id="fileUpload1" labelLevel="3"
style="left: 24px; top: 24px; position: absolute" validator="#{NewProblem.fileUpload1_validate}"/>
Java
UploadedFile uploadedFile = getSessionBean1().getUploadedFile();
Variable uploadedFile is NULL :(((((((((((
web.xml
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>
<filter>
<filter-name>UploadFilter</filter-name>
<filter-class>com.sun.web.ui.util.UploadFilter</filter-class>
<init-param>
<param-name>maxSize</param-name>
<param-value>10000000</param-value>
</init-param>
<init-param>
<param-name>sizeThreshold</param-name>
<param-value>10024</param-value>
</init-param>
</filter>
Thanks.

check out the fileUpload article
Using the File Upload Component
http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/file_upload.html

Newbie : memory problem with file uploading

Hello
I'm exdending a web app based on jsf and , being new to it and java in general, i'm having a problem with file uploading.
The customer needs to upload large file (more than 30 MB). The application accomplish this using a fileupload component, to let the user select the file, and passing the array of bytes to a web service method.
I'm using netbeans 6, tomcat 5.5.
When i try to upload a file too large i got an outofmemory on the local tomcat. So i've rised jvm memory and going on with tests i've found that growing the size i got an http 500 error from the service (the developer of the service has found an out of memory too ).
I think the service is not modifiable, so i were asking if threre were a way to optimize the file uploading process (a component, a library, a pattern ...) or my only chioice is to rise available memory on both sides.
I've notice the wsdl declares as base64binary type the data parameter , while netbeans 6 generates a client proxy with a byte[] parameter. Is correct or is a netbeans problem?
searching with google i've found few thing i haven't fully understood due to my lack of experience:
the mtom , how can evaluate if it's suitable to help in my problem (i suppose it involves more the web service rather than the client)
something about the size of a soap body.
thank you in advance
Stefano

Which component exactly are you using? Declaring the stream as a raw byte[] is certainly not efficient. Write code yourself, don't let it autogenerate.
I can highly recommend you the Tomahawk t:inputFileUpload component. It is easy to integrate in Mojarra. You can find here an useful article: [http://balusc.blogspot.com/2008/02/uploading-files-with-jsf.html].

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with threads and camera.

Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while((!performing.isShown()) && (backgroundCamera.isShown())){
                    Thread.yield();
                notifyAll();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    this.wait();
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?

Hi,
I've finally managed to work this fine.
The code:
       Object o = new Object();
       display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while(!performing.isShown()){
                    Thread.yield();
               synchronized(o) {
                  o.notify();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    synchronized(o) {
                       o.wait(1);
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();

Problem with threads hanging

We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
=============================================================================================
"ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
at java.lang.String.substring(String.java:1446)
at java.lang.String.substring(String.java:1411)
at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
=============================================================================================
String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
=============================================================================================
----------------- lwp# 44 / thread# 44 --------------------
ff31f364 lwp_mutex_lock (e3d70)
fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
0) + 78
fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
From the thread dump:
"VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
From the first pstack:
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Second pstack
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there. Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this.
We're using the following memory options:
-ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
-verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
Thanks!
--Andy

Problem with threads and ProgressMonitor

Dear Friends:
I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
But I need deactivate the main class(the main class is the user interface) until the thread ends.
I use something like this:
LongTask myTask=new LongTask();
myTask.start();
myTask.join();
Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
What's wrong?

Is the dialog a modal dialog? This can block other UI updates.
In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

Problem with hx:fileupload

Similar Messages

Maybe you are looking for