Assertion in linking with Sun C++ 5.0 on Solaris 7

I have a program using a few libraries and object files which i was able to compile and link fine. Then suddenly one day it started giving me and assertion message (as below) and since then i have not been able to link this program again.
-I do not get any compile time errors
- I am using the same version of compiler to compile all the objects and link them (C++ 5.0)
- I have tried removing the SunWS_Cache directory
- Some of the objects (in a separate directory) with which i am linking this program are being used by some other executables. However, each executabel is being generated in a separate directory. (Could this create trouble?).
- I do not get any problem making the other executables
Please Help? The earlier post on the above matter does not help.
/usr/SUNWspro/bin/CC -DOS_SOLARIS_2_7 -DOS_NEW_CHECK -DOS_STL_ASSERT -DOS_NO
WSTRING -DOSUSE_STD_IOSTREAMS -DOS_USE_ALTERNATE_STL -DOS_USE_ALTERNATE_ST
D -DOS_NON_STD_COUNT -DOS_RW_ALLOCATORS -DOS_MULTI_THREADED -DOS_SOLARIS_PTH
READS -DOS_REALTIME -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -mt -DOS_NO_TY
PEID -R/usr/toolkit/lib -DSOLARIS /home/mosys/app/event_c.o /home/mosys/a
pp/event_s.o /home/mosys/common/Util.o /home/mosys/app/AllMessage.o /home
/mosys/common/MesgQueue.o /home/mosys/common/Timer.o /home/mosys/common/Co
nsumer.o /home/mosys/common/Supplier.o /home/mosys/common/NameService.o /h
ome/mosys/app/Manager.o std/ConvMgr.o std1/ExchangeConvInfo.o std2/ConvInfoL
ist.o std3/FileConvInfo.o std4/Routines.o -o convmgr -verbose=diags +w -L/us
r/inprise/vbroker/lib -L/usr/toolkit/lib -lorb_r -lvport_r -lcosnm_r -lcosev
r -losstd -los_helper -los_time -los_thread -los_io -los_security -los_pip
e -los_file -los_stream -los_network -los_unix -los_uss_file -los_u
ss_network -los_uss_security -los_uss_std -los_uss_helper -los_uss_time -los
ussunix -ldl -lnsl -lsocket -lposix4
** Assertion ** : which_cache != 0 (/set/taz/builds/patchz0711/sparc-S2/lang
/cafe/resources/cdr/src/c_filecache.cc: 84)
*** Error code 84
make: Fatal error: Command failed for target `convmgr'

I have found the patch for this problem
(Patch Id: 109490-01), but, it requries you to upgrade to Forte 6.0. If you found a patch for Workshop 5.0 then please let me know. I don't want to do an upgrade just because of one bug.

Similar Messages

  • Upgrade from Solaris 8 SPARC with Sun cluster 3.1u3 to Solaris 10 SPARC

    Dear All,
    We are planning an upgrade of the OS from Solaris 8 SPARC to Solaris 10 SPARC on a two-node active-standby clustered system.
    The current major software we have on the Solaris 8 system are:
    1: Sun Cluster 3.1u3
    2: Oracle 9i 9.2.0.8
    3: Veritas File System Vxfs v4.0
    4: Sun Solaris 8 2/04 SPARC
    Any pointers as to what sequence and how the upgrade should be done?
    Thanks in advance.
    Regards,
    Ray

    yes I know it can be quite complicated and complex, but Sun provided us with a detailed documentation, at least in our case Solaris 9 to 10 it was very helpful.
    You might get better help in the cluster forum http://forums.sun.com/forum.jspa?forumID=842
    -- Nick

  • Can't execute web app from NetBeans 3.6 with Sun Java App Server 8

    Hi there,
    I'm tyring to execute a java web application called myfirstjsp.
    In directory ...\myfirstsjp I've got:
    - index.jsp
    - WEB-INF dir
    - META-INF dir.
    I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
    However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
    The Sun Java System Application Server 8 could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    I checked port conflicts but none found.
    The other two options don't give me a place to start (I don't know what to do with domain.xml)
    I'm working with:
    - Windows XP Pro
    - J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
    - Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
    - Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
    My PC has the following environment variables:
    PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
    PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
    CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
    By looking at the Sun App Server log file, I discovered that the log outputs of
    - Start Default Server (a link in the folder created by the installation of Sun App Server)
    - and trying to execute myfirstjsp from NetBeans through Sun App Server
    are very similar.
    Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
    Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
    [#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
    [#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
    [#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
    [#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
    [#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
    [#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
    [#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
    [#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
    [#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
    [#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
    [#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
    [#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
    Error messages are: |#]
    [#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
    Error messages are:
         at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
         at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
         at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
         at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
         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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
         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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
         at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
         at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
         at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
         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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.ejb.codegen.JavaCompilerException: Native compiler returned an error: 2
    Error messages are:
         at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
         at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
         at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
         at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
         ... 45 more
    |#]
    [#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
    Error messages are:
         at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
         at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
         at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
         at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
         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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
         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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
         at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
         at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
         at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
         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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    |#]
    [#|2004-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
    [#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
    Error messages are:
         at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
         at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
         at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
         at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
         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.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
         at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
         at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
         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.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
         at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
         at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
         at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
         at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
         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 org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    |#]
    [#|2004-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
    Error messages are:
    .|#]
    [#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
    [#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
    [#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
    [#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
    [#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
    [#|2004-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
    [#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
    [#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
    [#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
    [#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
    [#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
    [#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
    [#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
    [#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
    [#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
    [#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
    [#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
    [#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
    [#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
    [#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
    [#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
    [#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
    Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
    I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
    If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
    Many thanks,
    Miguel

    I seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
    The Sun Java System Application Server 8 could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
    This is the Exception:
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
    [#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
    [#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
    at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
    at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
    ... 5 more
    Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
    at java.lang.ProcessImpl.start(ProcessImpl.java:30)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
    at java.lang.Runtime.exec(Runtime.java:591)
    at java.lang.Runtime.exec(Runtime.java:464)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
    ... 5 more
    |#]
    [#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
    java.lang.NullPointerException
    at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
    at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]
    [#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0_04\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
    -Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=domain1
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
    [#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
    [#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
    at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
    at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
    ... 5 more
    Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
    at java.lang.ProcessImpl.start(ProcessImpl.java:30)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
    at java.lang.Runtime.exec(Runtime.java:591)
    at java.lang.Runtime.exec(Runtime.java:464)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
    ... 5 more
    |#]
    [#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
    java.lang.NullPointerException
    at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
    at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]
    [#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
    [#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
    [#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0_04\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
    -Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=domain1
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
    [#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
    [#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
    com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
    at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
    at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
    ... 5 more
    Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
    at java.lang.ProcessImpl.create(Native Method)
    at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
    at java.lang.ProcessImpl.start(ProcessImpl.java:30)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
    at java.lang.Runtime.exec(Runtime.java:591)
    at java.lang.Runtime.exec(Runtime.java:464)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
    ... 5 more
    |#]
    [#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
    java.lang.NullPointerException
    at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
    at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
    at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]
    [#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
    [#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0_04\bin\java
    -client
    -Xdebug
    -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
    -Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
    -Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
    -Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/

  • Integrating WebSphere Portal Server with Sun Java System Access Manager

    Hi All,
    Is it possible to Integrate WebSphere Portal Server with Sun java System Access Manager?. If so plz send me any doc or web site link for the same.
    Thanks in Advance
    Rgds,
    Lessly J

    Rushi-Reliance wrote:
    Kindly let us know how to proceed further as we are waiiting some reply from your team.As I already advised in your previous posting (http://forums.sun.com/thread.jspa?threadID=5359095), you are best off re-installing solaris from scratch and installing Communication Suite 6 update 1 if you cannot get Access Manager 7.1 configured.
    Regards
    Shane.

  • How to setup Glashfish 2.1 with sun crypto hardware inside T2 processor

    Dear Expert,
    I had setup comm 7 at guest os (ldom guest) on sun fire t5240 , All running well (mail,calender,im) , I also read
    http://wikis.sun.com/display/BluePrints/Taking%20Advantage%20of%20Wire-Speed%20Cryptography
    Does any body have guide step by step How to integrated glasshfish with sun    Cryptography hardware ?
    thanks
    Hadi

    singautara,
    SLIM is trying to tell you that SUSE 9.x will just not work.
    Period.
    SUSE 9.x is for Intel and AMD chips and the computers that use them. Your Ultra-60 does not have x86 compatible components in it.
    It does not have a BIOS. It has an OpenBootProm .
    The last distribution ever ported by SUSE to Sun's SPARC cpu architecture was something like version 7.3. That is from 5 years ago !
    What's wrong with the Operating Environment that was developed by the same company that manufactured your computer?
    Use the SunOS on the Sun system !
    http://sunsolve.sun.com/handbook_pub/Software/
    Tell you what ...
    Find the "Related Documentation" link at this page in the Sun System Handbook and research what sort of system you have.
    http://sunsolve.sun.com/handbook_pub/Systems/U60/U60.html

  • Veritas Volume manager 4.0 with Sun StorEdge 3310 D

    I am running into a problem. The vxconfigd deamon always dump core when rebooting.
    Our environment is listed below.
    OS environemt.
         SunOS server1 5.8 Generic_117350-43 sun4u sparc SUNW,Sun-Fire-V240
    Software installed.
         Sun Cluster 3.0
         Veritas Volume Manager 4.0 MP2.
    Disk Array associated.
         Sun StorEdge 3310 D.
    I looked up veritas.com and find Array Support Library (ASL) for Sun StorEdge 3xxx Series is recommended. But I didn't find this library is running on this server.
    Please refer to this following link
    http://support.veritas.com/docs/277923
    As our system is one of critical systems and I'd like to confirm that I can follow up this procedure without doing harm things to our system.
    Jeff

    No problem Jeff :)
    I took a look at the Veritas doc and you're right it does seem to cover everthing.
    Has the vxconfigd core dumped since the start? ie from the moment it was installed?
    I have installed VXVM 4.0 with Solaris 8 but without the ASL and this worked ok, I know that's not much help to you but I am not sure the ASL will help. Mind you I have not installed it with Sun Cluster 3.0.

  • [svn:fx-trunk] 11488: Resubmitting binary distribution of xercesPatch. jar from the third party module in the SDK and compiled it with Sun JDK 1.4 .2_12.

    Revision: 11488
    Author:   [email protected]
    Date:     2009-11-05 17:10:10 -0800 (Thu, 05 Nov 2009)
    Log Message:
    Resubmitting binary distribution of xercesPatch.jar from the third party module in the SDK and compiled it with Sun JDK 1.4.2_12.
    QE notes: N/A
    Doc notes: N/A
    Bugs:
    SDK-16818 - Must open-source the code for xercesPatch.jar.
    Reviewer: Discussed with Gordon
    Tests run: Checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-16818
    Modified Paths:
        flex/sdk/trunk/lib/xercesPatch.jar
        flex/sdk/trunk/modules/thirdparty/xerces-patch/build.xml

    Did you try this:
    http://forum.java.sun.com/thread.jsp?thread=434718&forum=60&message=1964421

  • Comaptibility of Discoverer with Sun Solaris(5.10) Operating system

    Please tell me which version of Oracle Discoverer is compatible with Sun Solaris(5.10).
    Thanks&Regards
    Pooja

    Cross-posted
    Sun Solaris 5.10 - SSH 1.1.3-Not able to connect to server with ssh -Urgent
    @O.P.
    Don't do that.
    In the future, pick the most appropriate forum and make your post.
    Cross-posting is considered to be the same as rude spamming.
    I'm not aware of any forum web-site-of-value that would encourage cross-posting in its etiquette guidelines.
    ... and as far as "Urgent" goes?
    This web site is for the end-user community to gather and discuss various topics in general conversations. Your self-imposed time pressures are irrelevant. If you need actual technical support for something, then log a support case and pay for a speedy answer.
    See the FAQ link at the top of the page.

  • Linking with gnu libstdc++ using no%Cstd option

    Has anybody had success using (compiling and linking with) the GNU libstdc++ C++ standard library? This would be excluding the use of the Sun supplied Cstd library by using the compile option -library="no%Cstd".
    If so please provide any key details.
    I'm just trying a very simple test program:
    #include <string>
    int main(int argc, char** argv) {
    string s = "Hello";
    The command line to compile is: CC -library="no%Cstd" -lstdc++ test.cc
    Many many compile errors follow. Curiously enough it doesn't seem to find the standard includes at /usr/include, even if I explicity specify in the compiler options.
    Thanks.

    This isnt going to happen. You would have to use -I to point CC at the gcc std header files. They are not going to compile with CC. Furthermore, CC and g++ use different mangling algorithms, so even if you got it to compile, the mangled names that CC emitted would not match the symtab entries in the gcc standard library shared object. And if you managed even more magic to get past this, you would discover that nothing ran, because CC and g++ use different ABI's, i.e. the mechanism by which g++ would propogate an exception would be incomprehensible to code generated by CC, etc. This is actually the underlying reason why the mangling algorithms differ - to explicitly prevent mixing compilers and libraries. Its a sad fact about C++, but you've got to use the same compiler all around, unless you limit yourself to a strict subset at the .so boundry, which is how COM gets around this.

  • Unable to link to sun performance library

    I am using SS12 with nevada build 70. When trying to link to sun performance library routine from F90 code, I am getting errors. See the code and output below,
    PROGRAM DeepWell
         USE SUNPERF
         IMPLICIT NONE
         INTEGER, PARAMETER :: N=5          ! No. of nucleons in consideration
         INTEGER :: i,j,k,ios
         DOUBLE PRECISION,DIMENSION(N,N) :: S,H
         DOUBLE PRECISION,DIMENSION(N) :: eig
         DOUBLE PRECISION :: tmp
         DO i=1,N
              DO j=i,N
                   k = i+j
                   IF (MOD(k,2) == 0) THEN
                        S(i,j) = 2.0/(k+5.0) - 4.0/(k+3.0) + 2.0/(k+1.0)
                        H(i,j) = 8*(k+2.0*i*j-1)/(k+3.0)/(k+1.0)/(k-1.0)
                   ELSE
                        S(i,j) = 0.0
                        H(i,j) = 0.0
                   ENDIF
    ENDDO
         ENDDO
         call sygy(1,'V','U','N',H,B=S,W=eig)
    END PROGRAM DeepWell
    Output:
    Running "/usr/bin/dmake -f Makefile CONF=Release" in /export/home/mbkumar/Thissjen/C3/This_C3_P1_VC
    dmake: defaulting to parallel mode.
    See the man page dmake(1) for more information on setting up the .dmakerc file.
    bharat1 --> 1 job
    /usr/bin/dmake -f nbproject/Makefile-Release.mk SUBPROJECTS= .build-conf
    bharat1 --> 1 job
    mkdir -p build/Release/Sun12-Solaris-x86
    f90 -xtarget=opteron -m64 -dalign -xlic_lib=sunperf -c -O3 -w1 -o build/Release/Sun12-Solaris-x86/VC.o VC.f90
    bharat1 --> Job output
    mkdir -p build/Release/Sun12-Solaris-x86
    f90 -xtarget=opteron -m64 -dalign -xlic_lib=sunperf -c -O3 -w1 -o build/Release/Sun12-Solaris-x86/VC.o VC.f90
    (/export/home/mbkumar/Thissjen/C3/This_C3_P1_VC)VC.f90:
    call ssygy(1,'V','U','N',H,B=S,W=eig)
    ^
    "VC.f90", Line = 41, Column = 30: ERROR: An actual argument keyword is being used when an explicit interface is not known.
    ^
    "VC.f90", Line = 41, Column = 34: ERROR: An actual argument keyword is being used when an explicit interface is not known.
    f90comp: 44 SOURCE LINES
    f90comp: 2 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
    :(/export/home/mbkumar/Thissjen/C3/This_C3_P1_VC)VC.f90
    *** Error code 1
    dmake: Fatal error: Command failed for target `build/Release/Sun12-Solaris-x86/VC.o'
    Current working directory /export/home/mbkumar/Thissjen/C3/This_C3_P1_VC
    *** Error code 1
    dmake: Fatal error: Command failed for target `.build-impl'
    Build failed. Exit value 1.

    please ignore the above question. I called non-existing routine.

  • Problems linking with log4cpp..

    Hi all,
    working on a T200 with solaris 10 and sunstudio 11,
    I have a program that I have to compile with -library=stlport4 since it's being ported from gcc where it was using <hash_map>.
    I succeeded building log4cpp-0.3.5-rc3 with SUN compiler both with standard STL and with stlport, but now it seems I cannot use neither one of these two version of liblog4cpp.so with my program, because when it comes to linking in sunstudio, it fails with a lot of messages like
    undefined symbol first referenced in file
    std::ostream &std::operator<<(...) liblog4cpp.so
    std::ios::operator void *() const liblog4cpp.so
    The test application included in the log4cpp source distribution has been built and runs with no problems...
    So I have no clue of what this could be, it seems like liblog4cpp.so itself is missing some external library when it comes to linking with my app...
    If I remove -library=stlport4 everything is ok, but then I cannot use hash_map in my program....
    Any idea? Am I missing something particularly stupid?...
    Thanks in advance.
    Andrea.

    Yes,
    I've checked that liblog4cpp.so has been built with -library=stlport4 both on the compile and on the linker command line.
    And here I'm showing you the full output during the compile and linking stage:
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/cmd.o source/cmd.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/dbmgr.o source/dbmgr.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/Feeder.o source/Feeder.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/IndexedMap.o source/IndexedMap.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/main.o source/main.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/Monitor.o source/Monitor.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/mspp_config.o source/mspp_config.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/mspp_utils.o source/mspp_utils.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/NSMapper.o source/NSMapper.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/patterns.o source/patterns.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/PDUSequencer.o source/PDUSequencer.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/processor.o source/processor.cpp
    CC -g   -c  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/Status.o source/Status.cpp
    CC -g   -filt=%none  -library=stlport4  -I./include  -I/usr/sfw/include/mysql  -I/usr/local/include  -I../rps/mc_receive/source  -I../rps/common/include  -I../common/include  -L.  -Lbuild/solaris  -L/usr/local/mysql/lib  -L/usr/local/lib -o build/solaris/mspp build/solaris/cmd.o  build/solaris/dbmgr.o  build/solaris/Feeder.o  build/solaris/IndexedMap.o  build/solaris/main.o  build/solaris/Monitor.o  build/solaris/mspp_config.o  build/solaris/mspp_utils.o  build/solaris/NSMapper.o  build/solaris/patterns.o  build/solaris/PDUSequencer.o  build/solaris/processor.o  build/solaris/Status.o -lmc_receive -llog4cpp_stlport -lmysqlclient_r -lsocket
    Undefined                       first referenced
    symbol                             in file
    __1cDstdGsmanip4Ci_2t6MpFrn0AIios_base_i_3i_v_ ./liblog4cpp_stlport.so
    __1cDstdJbasic_ios4Ccn0ALchar_traits4Cc___2C6kM_b_ ./liblog4cpp_stlport.so
    __1cDstdHgetline4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___6Frn0ANbasic_istream3CTACTB__rn0AMbasic_string3C1C2CTC__1_4_ ./liblog4cpp_stlport.so
    __1cDstdJbasic_ios4Ccn0ALchar_traits4Cc___2v6kM_pv_ ./liblog4cpp_stlport.so
    __1cDstdLsmanip_fill4Ccn0ALchar_traits4Cc___2t6MpFrn0AJbasic_ios4Ccn0B___c_3c_v_ ./liblog4cpp_stlport.so
    __1cDstdLchar_traits4Cc_Deof6F_i_   ./liblog4cpp_stlport.so
    __1cDstdCws4Ccn0ALchar_traits4Cc___6Frn0ANbasic_istream3CTACTB___4_ ./liblog4cpp_stlport.so
    __1cDstdM__initialize4CI_6FrTA1_v_  ./liblog4cpp_stlport.so
    __1cDstd2l6Frn0ANbasic_ostream4Ccn0ALchar_traits4Cc____pkc_2_ ./liblog4cpp_stlport.so
    __1cDstd2E4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___6Frkn0AMbasic_string3CTACTBCTC__pk1_b_ ./liblog4cpp_stlport.so
    __1cDstdLchar_traits4Cc_Emove6FpcpkcI_2_ ./liblog4cpp_stlport.so
    __1cDstdJuse_facet4n0AFctype4Cc___6Frkn0AGlocale_pTA_rk4_ ./liblog4cpp_stlport.so
    __1cDstdNbasic_istream4Ccn0ALchar_traits4Cc___Hgetline6Mpcl_r1_ ./liblog4cpp_stlport.so
    __1cDstd2s4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___6Frkn0AMbasic_string3CTACTBCTC__1_4_ ./liblog4cpp_stlport.so
    __1cDstdLlogic_error2t5B6Mrkn0AMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc_____v_ ./liblog4cpp_stlport.so
    __1cDstd2l6Frn0ANbasic_ostream4Ccn0ALchar_traits4Cc____c_2_ ./liblog4cpp_stlport.so
    __1cDstdLchar_traits4Cc_Leq_int_type6Frkir2_b_ ./liblog4cpp_stlport.so
    __1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___M__sun_concat6kMrk1_1_ ./liblog4cpp_stlport.so
    __1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___M__sun_concat6kMpkc_1_ ./liblog4cpp_stlport.so
    __1cDstdJbasic_ios4Ccn0ALchar_traits4Cc___Egood6kM_b_ ./liblog4cpp_stlport.so
    __1cDstdNbasic_istream4Ccn0ALchar_traits4Cc___Gsentry2v6M_b_ ./liblog4cpp_stlport.so
    ld: fatal: Symbol referencing errors. No output written to build/solaris/mspp
    *** Error code 1
    dmake: Fatal error: Command failed for target `build/solaris/mspp'I wonder how I'm going to bring all my code base (actually built with gcc) under sunstudio 11, if I can't even get my feet out of this first project, that is the simplest I have to deal with...
    In any case, even if I have to give up, I'd really like at least to understand what's really going on under the hood and why does liblog4cpp_stlport cause all of this...
    Andrea.

  • GUI tools availabe with sun studio 11

    I have used sun workshop v5 for a good number of years and am happy with the GUI based tools I use for debugging C, Fortan and soon Ada code whcih link with dbx and emacs.
    I have had a trawl through the website but haven't found what I;m looking for.
    so the question is : what are the GUI based tools which I could use with sunstudio 11 which will give similar capability to that availabe with sun workshop v5 ?
    regards
    bladerunner

    I guess the base tools in Workshop 5 you mentioned are IDE, dbx. Sun Studio 11 has all of those functions which are much more far better than Workshop 5. The only missing from Sun Studio 11 IDE is project function. It will be back in next release. Take a look at Sun Studio matrix page to see which function is included in Sun Studio 11. The matrix page does not include WS 5 because this version is 5 years old. Here is the URL
    http://developers.sun.com/prodtech/cc/support/support_matrix.jsp
    -Ngoc

  • Compiling MySQL 5.1.26-rc with Sun Studio Express on Linux?

    I managed to compile MySQL 5.1.26-rc with Sun Studio Express on Linux (OpenSuse 10.2 on x64), but I get unexpected crashes every time a connection thread exits:
    (gdb) where
    #0  0x00002b2ce0649535 in raise () from /lib64/libc.so.6
    #1  0x00002b2ce064a990 in abort () from /lib64/libc.so.6
    #2  0x00002b2cdf949795 in __pthread_unwind () from /lib64/libpthread.so.0
    #3  0x00002b2cdf944425 in pthread_exit () from /lib64/libpthread.so.0
    #4  0x00000000005048b2 in one_thread_per_connection_end (thd=0x16d88f0, put_in_cache=false)
    at /home/mysql/debug/sql//mysqld.cc:1893
    #5  0x0000000000513b75 in handle_one_connection (arg=0x16d88f0) at /home/mysql/mysql-5.1.26-rc/sql//sql_connect.cc:1122
    #6  0x00002b2cdf94309e in start_thread () from /lib64/libpthread.so.0
    #7  0x00002b2ce06da4cd in clone () from /lib64/libc.so.6
    #8  0x0000000000000000 in ?? ()If I compile with gcc using e.g. BUILD/compile-amd64-debug-max, I have no issue! But I want to use Sun Studio in order to be consistent with the Solaris version, and also because Sun Studio is likely to produce better code.
    Here is the compilation script, it downloads and extracts the source tree and builds it (it assumes Sun Studio Express is installed in /opt/sun):
    #!/bin/bash
    export PATH=/opt/sun/sunstudioceres/bin:$PATH
    wget -q http://mir2.ovh.net/ftp.mysql.com/Downloads/MySQL-5.1/mysql-5.1.26-rc.tar.gz
    tar xpf mysql-5.1.26-rc.tar.gz
    cd mysql-5.1.26-rc
    # Explicitly specify libs to avoid linking with the STL.
    export LIBS="-xnolib -lCrun -lm -lc -lrt"
    autoreconf --force --install > autoreconf.log 2>&1
    export MY_FLAGS="-g -mt -xtarget=generic -m64"
    CC=cc CXX=CC CFLAGS=$MY_FLAGS CXXFLAGS=$MY_FLAGS ./configure --with-big-tables --without-embedded-server --disable-shared --with-pthread --with-ssl -with-plugins=max > configure.log 2>&1
    gmake -j > build.log 2>&1Any idea about what is going wrong?
    Thanks.

    Possibly the actual CC (or cc) command lines are not correct. The proper way to say not to link libCstd is the command-line option -library=no%Cstd. Then you don't need to add the default system libraries like -lc to the command line.
    Can you show the actual CC command lines that are generated by the makefile? They should be in the compilation log. I'd also like to see the command line(s) used to create dynamic libraries, if any, and the final executable.

  • Linking secure html link with JSF?

    Hey all,
    I do have a previous post regarding j_security_check and using container based security, but since this problem could be answered without it, checking to see how (j_security_check: http://swforum.sun.com/jive/thread.jspa?threadID=54464&tstart=0).
    I want to be able to e-mail links with pre-populated attributes (identifiers, dates, what have you) but still have the link secure and require auth. But, I do want to automatically go to that linked page after auth. How does one do this with JSF?
    thanks,
    -D

    Hi,
    Please go through the below thread:
    http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=50520
    Hope this helps.
    Thanks,
    RK.

  • How do I add URI web link with custom tooltip like "CLICK HERE TO UPDATE" instead of URI web link in tooltip.

    How do I add URI web link with custom tooltip like "CLICK HERE TO UPDATE" instead of URI web link in tooltip.

    You've probably found an answer to this by now, but I think this has been addressed in another forum -- The link below suggested using a button and adding the tooltip to the button. 
    https://forums.adobe.com/thread/304974?start=0&tstart=0
    Sounds like it would work but I haven't actually tried it. 
    Good luck~!

Maybe you are looking for

  • IPhone 4S skipping songs/won't play some

    I recently updated my iPhone 4S, in doing so, I had to reset it and restore it from my back up. Now that I've done that, when I'm playing music from my iTunes, it wil skip the most recently added songs and won't play them at all if you try and click

  • Is there actually a way to back up attached drives and have it work?

    I have 2 identical 500GB drives attached to my Mac Mini (media computer). One of them contains nothing but my iTunes library (a little over 120GB) and I was just manually copying that to the other once a week or so. After reading up on Time Machine i

  • How to setup the security based on roles in Organization.

    Hi, How to setup the security based on roles in Organization. For example:Few users are Manager and a few user are Non Manager .Manager should have access to all work data including Non Manager and Non Manager should access based role.How to setup th

  • Safari hangs then quits

    There is the scenario: Opened Mail, opened Safari, read mail looked on web, kept both open then opened a game (ZUMA). After playing game for a period of time, I put game in pause mode, wife wanted me to take her to gym. When I returned about 2 hours

  • ICal freezes while saving backup file

    I want to migrate from my iTunes account to my MobileMe/iCloud account. But before I can do that, I need to create a backup of my calendars. My problem is though, that iCal constantly freezes when I'm saving the backup file (via File > Export > iCal