Problems with deploytool

hi,
i have just started with j2ee...i have win98/j2sdk1.4.0/j2sdkee1.2.1...
i get an error message when i start the deploytool...
is the config mentioned above compatible..or is something else wrong..
thanks in advance..

You'll probably want to upgrade to at least J2EE Version 1.3.1 and may be even 1.4 for starters. You'll find detailed instructions on how to do either at
http://groups.msn.com/J2EETools
Good luck!

Similar Messages

  • Problem with deploytool

    I'm using IPlanet 6 SP3 and am using the deploytool to deploy my application.
    The application deploys without errors, but one of my jar files that lives under WEB-INF/lib does
    not get fully unpacked. I have some dtd files which live in the JAR with the names
    com/volantis/mcs/protocols/dtd/wml1_1.dtd
    com/volantis/mcs/protocols/dtd/wml1_2.dtd
    etc.
    These files do not get unpacked in the deployed application. Anyone have any idea why?
    Thanks
    Mat.

    I discovered the same issue. It seems that the deploy utility ONLY unpacks
    class files and ignores all others. The only workaround that I have
    discovered is to place the offending files elsewhere in the web application.
    -jeff
    "Mat Diss" <[email protected]> wrote in message
    news:[email protected]..
    I'm using IPlanet 6 SP3 and am using the deploytool to deploy myapplication.
    >
    The application deploys without errors, but one of my jar files that livesunder WEB-INF/lib does
    not get fully unpacked. I have some dtd files which live in the JAR withthe names
    >
    com/volantis/mcs/protocols/dtd/wml1_1.dtd
    com/volantis/mcs/protocols/dtd/wml1_2.dtd
    etc.
    These files do not get unpacked in the deployed application. Anyone haveany idea why?
    >
    Thanks
    Mat.

  • Have problem with deploytool,help,Tx!!!

    Hi:
    I use deploytool to package ConverterApp followed the J2ee tutorial. But after Compile the file, i New a
    new jar in Converter app , add the 3 classes to the Content,I get a error that deploytool told me "Cannot load the class convert.ConvertHome ...........",Why??? I confushed about it, Who can Help me???

    I really find the Exception in the log file:
    ---------------- (DEBUG) Exception ---------------------------------------------
    [NewEjbWizard.verifyAddedClasses:716]
    Error loading class: converter.Converter
    java.lang.UnsupportedClassVersionError: converter/Converter (Unsupported major.minor version 49.0)
    java.lang.UnsupportedClassVersionError: converter/Converter (Unsupported major.minor version 49.0)
         at java.lang.ClassLoader.defineClass0(Native Method)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
         at com.sun.enterprise.tools.deployment.ui.utils.J2EEClassLoader.findClass(J2EEClassLoader.java:529)
         at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.findClass(DTClassLoader.java:424)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
         at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader._loadClass(DTClassLoader.java:381)
         at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.loadClass(DTClassLoader.java:399)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
         at com.sun.enterprise.tools.deployment.ui.utils.DTClassLoader.loadClass(DTClassLoader.java:345)
         at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.verifyAddedClasses(NewEjbWizard.java:712)
         at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.validateComponent(NewEjbWizard.java:980)
         at com.sun.enterprise.tools.deployment.ui.utils.Wizard._performValidation(Wizard.java:711)
         at com.sun.enterprise.tools.deployment.ui.utils.Wizard._goForward(Wizard.java:724)
         at com.sun.enterprise.tools.deployment.ui.utils.Wizard$1.actionPerformed(Wizard.java:177)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
         at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
         at java.awt.Component.processMouseEvent(Component.java:5100)
         at java.awt.Component.processEvent(Component.java:4897)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
         at java.awt.Container.dispatchEventImpl(Container.java:1613)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at com.sun.enterprise.tools.deployment.ui.utils.UIEventQueue.dispatchEvent(UIEventQueue.java:168)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
         at java.awt.Dialog$1.run(Dialog.java:540)
         at java.awt.Dialog.show(Dialog.java:561)
         at com.sun.enterprise.tools.deployment.ui.utils.UIDialog._showDialog(UIDialog.java:373)
         at com.sun.enterprise.tools.deployment.ui.utils.UIDialog.show(UIDialog.java:432)
         at com.sun.enterprise.tools.deployment.ui.utils.Wizard.show(Wizard.java:621)
         at com.sun.enterprise.tools.deployment.ui.utils.Wizard.show(Wizard.java:584)
         at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.show(NewEjbWizard.java:558)
         at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard._showWizard(NewEjbWizard.java:282)
         at com.sun.enterprise.tools.deployment.ui.ejb.NewEjbWizard.newModule(NewEjbWizard.java:265)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:371)
         at com.sun.enterprise.tools.deployment.ui.shared.ModuleManagerImpl.createNewModule(ModuleManagerImpl.java:229)
         at com.sun.enterprise.tools.deployment.ui.DeployToolWindow.createNewModule(DeployToolWindow.java:1811)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:371)
         at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.invoke(UIActionDispatcher.java:393)
         at com.sun.enterprise.tools.deployment.ui.utils.UIActionDispatcher.actionPerformed(UIActionDispatcher.java:476)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at com.sun.enterprise.tools.deployment.ui.utils.UIMenu$UIMenuItem.fireActionPerformed(UIMenu.java:436)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
         at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
         at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113)
         at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943)
         at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
         at java.awt.Component.processMouseEvent(Component.java:5100)
         at java.awt.Component.processEvent(Component.java:4897)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
         at java.awt.Container.dispatchEventImpl(Container.java:1613)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at com.sun.enterprise.tools.deployment.ui.utils.UIEventQueue.dispatchEvent(UIEventQueue.java:168)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    [Wizard._goForward:727] Validation failed, 'goForward' ignored.

  • Problem with hello2 in the J2ee tutorial

    Hi all:
    I faced this problem when iam running the hello2 application I have followed the tutorial instructions and when i write the url in my browser http://localhost:8080/hello2/greeting but this error occur:
    HTTP Status 500 -
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException: Wrapper cannot find servlet class servlets.GreetingServlet or a class it depends on
         org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
         org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
         com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:272)
         com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
         org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
         org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
         org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
         org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
         java.lang.Thread.run(Thread.java:595)
    root cause
    java.lang.ClassNotFoundException: servlets.GreetingServlet
         org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1437)
         org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
         java.security.AccessController.doPrivileged(Native Method)
         org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
         org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
         com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:272)
         com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
         org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
         org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
         org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
         org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
         java.lang.Thread.run(Thread.java:595)
    note The full stack trace of the root cause is available in the Sun-Java-System/Application-Server-PE-8.0 logs.
    If any one can help i will be pleased..
    Thanks all.

    Hello,
    Are you sure that you performed all of step 5 in the instructions for packaging the example with deploytool?
    Instead of using deploytool, you can also build, package, and deploy the example by running the following commands:
    asant build
    asant create-war
    asant deploy-war
    Try this method and see it works. This will be documented in the next version of the tutorial.
    Jennifer

  • Creating web service client with deploytool

    J2EE 1.4 SDK 2005Q1 Release Candidate
    Windows XP Professional SP1
    I cannot create a web service client from a WSDL file any longer.
    deploytool
    - new
    - web service
    - web service client
    - next (provide the wsdl file): package name is not filled in automatically
    - next: there is no way to continue - next and finish button are both grey
    There are no problems with J2EE 1.4 SDK 2004Q4 Beta

    There is a bug in the processLauncher for deploytool. The workaround is to edit the processLauncher.xml located under <AS_INSTALL>/lib/processLauncher.xml and add
    add xalan.jar and mail.jar to the classpath includes of the s1as-deploytool process:
    includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar, mail.jar"
    The web service wizard should now work.

  • J2EE 1.4 Tutorial - problems with deploying web services

    Hi folks,
    I have a problem with the deployment of the example "MyHelloService" (chapter 8: Building Web Services With JAX-RPC).
    I've installed the application server properly and executed all the necessary steps written down in the tutorial (Packaging the Service and Specifying the Endpoint Address).
    While deploying the service I get the following error message:
    Deploy action running...
    com.sun.enterprise.admin.common.exception.DeploymentException: com.sun.enterprise.config.ConfigException: Failed to load deployment descriptor for: MyHelloService
    cause: Premature end of file.
         at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployWarModuleArchiveOrDirectory(ManagedServerInstance.java:1099)
         at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.deployWarModule(ManagedServerInstance.java:1003)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
         at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
         at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:663)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:223)
         at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.callInvoke(AdminAPIEntryServlet.java:203)
         at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.callMBean(AdminAPIEntryServlet.java:162)
         at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.doGet(AdminAPIEntryServlet.java:103)
         at com.sun.enterprise.admin.server.core.servlet.AdminAPIEntryServlet.doPost(AdminAPIEntryServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at sun.reflect.GeneratedMethodAccessor137.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:202)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:499)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:212)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:149)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:282)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:99)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:206)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2748)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:186)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:512)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:383)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:163)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:561)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1018)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:199)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:630)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:463)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:568)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:631)
         at java.lang.Thread.run(Thread.java:536)
    !!! Operation Failed !!!
    [Completed (time=4.1sec, status=13)]
    I verified the deployment descriptor and unpacked the WAR, but there seems to be no mistake. I don't know what to do...I can't imagine that this is a bug, so maybe I've done something wrong.
    Any help would be appreciated.

    Thank you for your answer, but I encountered the problem with the defect WAR file already in chapter 3 (Getting Started with Web Applications). I searched the forum and found the thread you recommended, made the adjustments in the deploytool.bat file and so fixed the problem.
    Thus your recommendation is unfortunately not the right solution for my problem.
    For verification purposes, here is an extract from my deploytool.bat file:
    set _USER_COUNTRY=US
    set _USER_LANG=en
    set _USER_REGION=US
    set _MAIN=com.sun.enterprise.tools.deployment.ui.Main
    set _CPATH=%LIB%\appserv-assemblytool.jar;%AS_IMQ_LIB%\activation.jar; %AS_JHELP%\jhall.jar;%LIB%\appserv-admin.jar;%LIB%\appserv-cmp.jar; %LIB%\appserv-rt.jar;%LIB%\j2ee.jar; %AS_INSTALL%\share\lib\jaxrpc-impl.jar;%LIB%\appserv-ext.jar; %LIB%\deployhelp.jar
    echo %_JAVACMD% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.endorsed.dirs=%AS_INSTALL%\share\lib\endorsed -Dcom.sun.aas.defaultUserName="%AS_ADMIN_USER%" -Dcom.sun.aas.defaultPassword="%AS_ADMIN_PASSWORD%" -Duser.country="%_USER_COUNTRY%" -Duser.language="%_USER_LANG%" -Duser.region="%_USER_REGION%" -cp %_CPATH% %_MAIN% %1 %2
    %_JAVACMD% -Dcom.sun.aas.installRoot="%AS_INSTALL%" -Djava.endorsed.dirs=%AS_INSTALL%\share\lib\endorsed -Dcom.sun.aas.defaultUserName="%AS_ADMIN_USER%" -Dcom.sun.aas.defaultPassword="%AS_ADMIN_PASSWORD%" -Duser.country="%_USER_COUNTRY%" -Duser.language="%_USER_LANG%" -Duser.region="%_USER_REGION%" -cp %_CPATH% %_MAIN% %1 %2In addition, I used the verification option from the deploytool and checked the deployment descriptor with the following results (only passed tests):
    Test Name : tests.web.ServletLargeIcon
    There are no large-icon elements within the servlet [ helloservice.HelloImpl ].
    Test Name : tests.web.ServletClass
    Servlet class [ helloservice.HelloImpl ] resides in the WEB-INF/classes directory.
    Test Name : tests.web.SessionTimeout
    Servlet session-timeout [ 30 ] element defines the default session timeout interval expressed in whole minutes.
    Test Name : tests.web.ServletInterface
    Not Applicable since, Servlet [ helloservice.HelloImpl ] is a JAXRPC Endpoint.
    Test Name : tests.web.ParamValue
    Test Name : tests.web.ServletSmallIcon
    There are no small-icon elements in the servlet [ helloservice.HelloImpl ].
    Test Name : tests.web.WebName
    Web-App display name is : [ MyHelloService.war ]
    Test Name : tests.web.ServletParamName
    ServletParam name exists in the web application.
    Test Name : tests.web.ResourceAuth
    Test Name : tests.web.ServletParamValue
    Test Name : tests.web.JarContainsXMLFile
    Found deployment descriptor xml file [ WEB-INF/web.xml ]All the other tests were notapplicable (no errors).
    Moreover, I unpacked the WAR file (MyHelloService.war): all necessary XML files were included and well-formed.

  • Problems starting Deploytool of j2sdkee1.3.1

    Hi everybody!!
    I recently installed j2sdkee1.3.1 on Windows 2000(Advanced Server).
    I set up the JAVA_HOME and J2EE_HOME environment variables accordingly. I have j2sdk1.4.1 installed prior to it. So, the J2EE server starts properly and I can see the welcome & congrats page at http://localhost:8000/index.html.
    But, the problem I am facing is that the DEPLOYTOOL just doesn't start.
    I am mentioning below the exact messages that I get on my command prompt
    while trying to start the deploytool after I have started the J2EE server on another command prompt:
    C:\>deploytool
    Starting deploytool, version 1.3.1
    (Type 'deploytool -help for command line options)
    No local string for enterprise.tools.deployment.main.error_creating_ui
    Unable to create UI: java.lang.ExceptionInIntializerError
    I thought that may be there could be a problem in installation so I uninstalled the j2sdkee1.3.1 and then reinstalled it, but still I was facing the same problem.
    So,then I thought that may be there could be some problem with the installation bundle of j2sdkee1.3.1 that I installed. So I got hold of
    another bundle of j2sdkee1.3.1 and installed it. But still I am getting
    the same problem.
    Please help me, I am stuck with this problem for past couple of months.
    Thanking you all!!
    Tariq

    Hi Tariq,
    Can you try the deploytool with jdk1.3,I suspect there the Linkage Error being due to incompatibility of some classes which have been changed in jdk1.4.
    And the classes which make run the deploytool are dependent on those classes(which have been modified in jdk1.4).Check what the Linkage Error means in java docs
    Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class
    So the classes which make the deploytool have some dependencies on the classes which have been modified in jdk1.4 latter class has incompatibly ....
    Got it!!!!
    That is what I can tell you out of my experience.....
    regards
    Vicky

  • Help with deploytool

    Hi all,
    I'm playing around with Oracle9i App Server at the moment. Having a problem with the deploytool. When I try to add my app server it says it can't connect. I've tried various combinations like localhost:7777 or using my ip :7777 all with and without http:// but nothing works.
    Can anybody offer assistance??
    Thank you!

    deploytool only works with the J2EE 1.4 Application Server from Sun.

  • 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 threads and/or memory

    I'm developing an application where there are 3 threads. One of them sends a request to the other, and if the 2nd can't answer it, it sends it to the 3rd (similar to CPU -> CACHE -> MEMORY). When i run the program with 1000-10.000 requests, no problem occurs. When i run it with 300.000-1.000.000 requests, it sometimes hangs. Is this a problem with the garbage collector, or should it be related to the threads mecanism.
    (note: eache thread is in execution using a finite state machine)

    i had been running the program inside Netbeans.
    Running the jar using the command line outside
    Netbeans i have no more problems... Does Netbeans use
    it's own JVM?Depends how you set it up, but look under the options. There are settings for the compiler and jvm that it uses.

Maybe you are looking for

  • TV out problem, rolling back to earlier firmwares

    I went and bought a component video cable from Apple, so I could improve my video output to TV (I've got a composite video cable, as well) Well, get back from the Apple store, hook up my cable to test it and -- nothing plays back, absolutely nothing.

  • Trying to link VC++ and CVI

    I have a VC++ application that uses CVI components. It links fine when VC++ is in debug mode, but when I change to Release mode I get link errors. C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\mbstring.h(117) : error C2375: 'CVI__mbsbtype' :

  • ColorTransform Question

    Hi All, Quick and im sure very easy question, i am new to flex and coding in general.  I have 3 Images that i want to use as a kind of rollover toolbar. I want to use the color transform to highlight as they go along the images.  Using the code below

  • Problem in returns

    Dears, i got one issue now. when i wanna to handle one sales order type of Returns Order ( sample of charges) . then my screen show some message " copying from sales document type ZORA to ZRE1  isn't support " how can i do? PLZ let me know what you t

  • Increasing Weblogic client Socket Readers etc

    How can you increase the number of socket readers on a client application which uses JMS, EJB and talks to multiple WLAS servers. I get the following message Muxer> <There are: '3' active sockets, but the maximum number of socket readers allowed by t