RSA Certificate Manager with Sun Java Directory Server

Has anyone integrated Sun Java Directory Server with RSA Certificate Manager

we have the Key Managment System in our DSEE 6.3 through a proxy. We had to enable some OIDs for it to work.

Similar Messages

SingleSign on with Sun Java Directory Server

Hi,
I wanted to know if there is any way to integrate the sun java server for the Single sign on of the App Server 10g(10.1.3.1.0).
Any help is appreciated..

Hi,
What exactly do you want? If you want SSO for your oc4j containers see see: [http://download-west.oracle.com/docs/cd/B32110_01/web.1013/b28957/javasso.htm#BABDCCGB]
If you want authentication and authorisation against Sun LDAP you need to configure the separate components of soa suite to use your sun ldap. See [http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28982/service_config.htm#BABHBEGH] on how to configure e.g. bpel.
Kind regards,
Andre

Sun Java Directory Server Linux RHEL 5 Installation

Hello,
As Linux RHEL ES/AS 5 is not officially listed in the operating system requirements.
Has somebody been succesful in the installation ?
- With which Linux RHEL 5 update.
- Are the package depencies the same (compat-C/C++ libraries)
- Which Edition of Sun Java Directory Server (5.2Q6, 6.0, 6.3) and which packages (Native/ZIP)
Tips would be useful as I have been successful in Linux RHEL 4 update 4 with Sun Java Directory Server 5.x
in the past but customer requirements have changed and I did not find any Information and do not have testing Time.
Thanks,
Fab

I just installed a consumer replica on CentOS (same thing as RHEL) 5.2 . It's working fine. Here's my kickstart file so that you can see what packages I installed:
# Kickstart file automatically generated by anaconda.
install
cdrom
lang en_US.UTF-8
keyboard us
xconfig --startxonboot
network --device eth0 --bootproto dhcp
rootpw --iscrypted <removed>
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Chicago
bootloader --location=mbr --driveorder=sda --append="rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
clearpart --linux
part /boot --fstype ext3 --size=128 --asprimary
part swap --size=1024 --asprimary
part pv.100000 --size=100 --grow
volgroup vgmain --pesize=32768 pv.100000
logvol /var --fstype ext3 --name=varlv --vgname=vgmain --size=512
logvol /var/log --fstype ext3 --name=varloglv --vgname=vgmain --size=512
logvol /usr --fstype ext3 --name=usrlv --vgname=vgmain --size=3072
logvol /usr/local --fstype ext3 --name=usrlocallv --vgname=vgmain --size=4096
logvol / --fstype ext3 --name=rootlv --vgname=vgmain --size=512
logvol /home --fstype ext3 --name=homelv --vgname=vgmain --size=1024
logvol /tmp --fstype ext3 --name=tmplv --vgname=vgmain --size=512
%packages
@development-libs
@editors
@system-tools
@text-internet
@legacy-network-server
@gnome-desktop
@core
@base
@legacy-software-development
@base-x
@web-server
@smb-server
@server-cfg
@admin-tools
@development-tools
@graphical-internet
audit
net-snmp-utils
lynx
kexec-tools
device-mapper-multipath
xorg-x11-server-Xnest
xorg-x11-server-Xvfb
system-config-boot
imake
-bluez-hcidump
-bluez-gnome
-slrn
-gnome-user-docs
-gnome-themes
-gedit
-gnome-power-manager
-gnome-backgrounds
-gok
-gnome-audio
-esc
-gnome-user-share
-gimp-print-utils
-desktop-printing
-file-roller
-gnome-screensaver
-gnome-pilot
-krb5-workstation
-ipsec-tools
-sysreport
-irda-utils
-bluez-utils
-synaptics
-krb5-auth-dialog
-linuxwacom
-system-config-nfs
-evolution
-nspluginwrapper
-gnome-themes
-evolution-webcal
-ekiga
-evolution-connectorI installed DSEE 6.3 from the ZIP distribution.

Sun java DIRECTORY SERVER 6.0 WITH SUN OPENSSO 8

Hi all,
I have install the sun java directory server 6.0.
Now I have install the sun openssl ( I could had installed the sun java access manager but i wanna use the sun opensso 8 for SSO).
when created the directory i.e. by using command from directory preparation tool, the directory server stop starting.
It do not start and is asking me the error as follows,
bash-3.00# /var/opt/SUNWdsee/dsins1/start-slapd
[20/Feb/2009:14:44:30 +0500] - ERROR<4131> - Bootstrap config - conn=-1 op=-1 msgId=-1 - System error The entry cn=schema in file /var/opt/SUNWdsee/dsins1/config/schema/99user.ldif is invalid (error 20: Type or value exists) - attribute type sunIdentityServerDiscoEntries: Does not match the OID "1.3.6.1.4.1.42.2.27.9.1.821". Another attribute type is already using the name or OID..
[20/Feb/2009:14:44:30 +0500] - ERROR<4129> - Bootstrap config - conn=-1 op=-1 msgId=-1 - Configuration error Please edit the configuration file to correct the reported problems and then restart the server. Server exiting.
Server not running!! Failed to start ns-slapd process.
Note: while preparing the directory (sun java directory preparation tool) I mentioned the schema 2 i.e. ACCESS MANAGER, because sun opensso 8 is the latest version for Sun java access manager ?
Any help??????????????
Regards
Adeel

Looks like the attribute sunIdentityServerDiscoEntries is defined twice in the schema. Run the following and see where it is defined for the second time.
# cd /var/opt/SUNWdsee/dsins1/config/schema
# grep -w sunIdentityServerDiscoEntries *.ldif | grep -iv objectclasses
Edited by: etst123 on Mar 3, 2009 1:28 PM

Sun java directory server and Active Directory

We are using two different directory servers Sun java directory server and active directory.
My question is how we can have password synchronization between these two directory servers.
I have checked Sun Java[TM] System Identity Synchronization for Windows 1 2004Q3
http://www.sun.com/download/products.xml?id=41537425
It seems that it's supported platforms is only for solaris and windows , but I have installed my Sun java directory server on linux and obviously it doesn't work for me.
I would be grateful if anyone can suggest a solution to work around this situation.
I have checked identity manager , I would like to know that if I can do this using this product.
http://www.sun.com/software/products/identity_mgr/specs.jsp
--regards.
Sara

Yes RHEL 4 is a supported OS with DSEE 6.0.
Identity Synchronization for Windows is a part of DSEE that allows synchronization of users, passwords and groups between Sun Directory Server and Active Directory bi-directionally without altering the users environments, ie it does not require that users change their current habits.
Identity Manager is a complete identity management solution that is targetting enterprise work flow when it comes to user provisioning and de-provisioning, but also allows to build authentication and password change forms that will provision the passwords to many different systems including Sun Directory Server and Active Directory but also IBM mainframes, legacy applications, databases...
If you are implementing a complete identity management solution, then go with Identity Manager. If you need a lightweight and fast solution for just synchronizing users and passwords between Sun DS and MS AD, Identity Synchronization for Windows should be your choice.
Regards,
Ludovic.

Sun Java Directory Server 5.2 x86 download

I'm trying to find a copy of the x86 version of the Sun Java Directory Server compressed archive for Solaris. I'm trying to build out a test system for some old software, and I only have a copy of the Sparc version of ldap. I've tried using the current DSEE version available on the Oracle e-delivery cloud, but the software is too old to work with it...it needs the 5.2 version, specifically. Is anyone aware of where I can find a copy?
Thanks for any assistance.

Nope
This is part of the Oracle Lifetime Support policy:
http://www.oracle.com/us/support/lifetime-support/index.html
'OLD' products can/may still be supported under *SPECIAL* support contracts. So if you're entitled to its support, you can access it. Otherwise, I'm afraid the answer is no.
HTH,
Marco

Synchronization between AD and Sun Java Directory Server

I would like to build an environment as below, kindly let me know whether it is possible or not.
My Enterprise Directory is Active Directory and i have Policy Server which directs the sso users to get authenticated with that server. I would like to synchronize the user data from Active Directory to Sun Java Directory Server (existing version is 5.2 Service Pack 4) including the passwords and i would like to know with which hashing algorithm these passwords are stored in the sun directory server. Because i want to synchronize the same attributes from sun java directory server to Oracle Internet Directory and is it possible to get my sso users to get authenticated at OID even?
Kindly let me know whether this approach is feasible or not?
Any suggestion to this approach is greatly appreciated...
Thanks in advance...
Regards,
Kishore Repakula.

i would like to know with which hashing algorithm these
passwords are stored in the sun directory server.Like most other directory servers, SunDS offers a few choices here.
The most secure is SSHA, which you'd probably want to use unless you have apps with dependencies on other hashes (e.g., CRYPT for backward compatibility with UNIX password field).
I would like to synchronize the user data from Active Directory
to Sun Java Directory Server (existing version is 5.2
Service Pack 4) including the passwords...Sun has a "Identity Synchronization for Windows" product which might work for you.
http://www.sun.com/software/products/directory_srvr_ee/identity_synch/
Unfortunately, the big trick with AD passwords is that they are stored in a proprietary one-way hash, so you can't just sync them directly over to another directory. Likewise, you can't import password hashes from other sources into AD and expect them to work.

Radius server for Sun Java directory Server?

I want to know what products does offer Sun for provide a radius server using the Sun Java Directory Server..
I have only seen Sun Access Manager, but it is a complex/expensive product for use only the radius server
Regards

Nope
This is part of the Oracle Lifetime Support policy:
http://www.oracle.com/us/support/lifetime-support/index.html
'OLD' products can/may still be supported under *SPECIAL* support contracts. So if you're entitled to its support, you can access it. Otherwise, I'm afraid the answer is no.
HTH,
Marco

Sun Java Directory server 6.3.1

Hello,
Anyone with knowledge to configure mail aliases in LDAP especially in Sun java directory server 6.x? I have already created the container ou=aliases
The problem is i get the below error when I install LDAP client on a server:
+Apr 23 18:32:00 Server1 sendmail[10032]: [ID 801593 mail.crit] n3NHW0HC010032: SYSERR(root): ldap_init/ldap_bind failed to localhost in map aliases.ldap: Can't connect to the LDAP server+
I found that I dont have aliases not configured in LDAP, the mail host sits on a different server. Other than this my client works perfectly over SSL
Thanks in advance
sys

Sys
SOrry but this looks to me like you have serveral problems. Most of them are Sendmail related. Maybe it would be a better idea to ask in a sendmail forum instead of a Directory server forum. Since you have not posted any configs I can not more than speculate. Here are my guesses:
Apr 29 11:58:21 server1 sendmail[3138]: [ID 801593 mail.info] n3TAwKaC003138: n3TAwKaD003138: return to sender: Host unknown (Name server: mailhost.xxxx.com: host not found)if mailhost.xxxx.com is an existing host then I guess you have a problem with DNS resolution. Are you able to resolve hosts other than those related to this case or infrastructure (eg. can you resolve www.google.com)? If not then you should have a look at /etc/resolv.conf. There shold be a series of nameserver lines followed by the IP-Addresses of the nameservers (Important: IPs . not names). Another source of error could be found in the "hosts:" line in /etc/nsswitch.conf (it ususally reads "hosts: files dns").
Apr 29 12:04:22 server1 sendmail[3219]: [ID 801593 mail.crit] n3TB4Muk003218: SYSERR(root): ldap_init/ldap_bind failed to localhost in map aliases.ldap: Can't connect to the LDAP serverNow this means your sendmail is trying to connect to an LDAP Directory on the same host to resolve aliases. If the port is correct you might find in the <instance_root>/logs/access file further details about what the sendmail server tried and why it failed. If there is no entry in the access log this would mean that there is no LDAP-Server listening on the port sendmail connects to. Fact is that somewhere you "told" sendmail to connect to the ldap server and it is failing to do so.
Apr 29 12:04:22 server1 sendmail[3219]: [ID 801593 mail.alert] n3TB4Muk003219: Losing ./qfn3TB4Muk003219: savemail panic
Apr 29 12:04:22 server1 sendmail[3219]: [ID 801593 mail.crit] n3TB4Muk003219: SYSERR(root): savemail: cannot save rejected email anywhereNow this errormessage is normal if alias resolution does not work. An errormessage would be generated which is sent by the user MAILER-DEAMON. In sendmail default config MAILER-DEAMON is an alias for postmaster which is again an alias for root. But if teher is no aliases there is no "account" MAILER-DEAMON. This errormessage will most likely disapear as soon as you resolved the alias issue.
So much for the errormessages. Unfortunately you are not very specific on your environment. I try to guess what I have understood and try to formulate queries which might help you to find the problem.
- There is a host A running solaris 10 and an Sun Directory Server 6.3.1
-- On what port is the server listening and what information can you get at its current configuration with an anonymous bind (eg. ldapsearch without username or password)
-- You have setup a suffix on this server and created an ou=aliases
-- Have you inserted the standard aliases (such as MAILER-DEAMON or postmaster)?
- There is a host B which is the mailhost.
-- B i trying to connect to localhost (so host B not A) to get informations from an LDAP. Is LDAP running on localhost yes or no? You are not clear on this topic.
-- what did you (or anyone else) do to get the server to obtain aliases from an LDAP (this is not standard config - You need to modify settings to do this)
-- it is definitely a good idea to define a global bunch of settings in confLDAP_DEFAULT_SPEC (especially the options -d -P -b -h should be set in your case most likely)
If these hints do not solve your problems I definitely recommend posting in an sendmail forum and read the sendmail documentation (eg. https://www.sendmail.org/doc/sendmail-current/cf/README). As far as I know LDAP in sendmail is pretty new in std sendmail and you have to expect that documentation on this topic is still poor.
Regards
Martin

Importing LTPA key in Sun Java Directory Server

hi all,
is it possible to import a LTPA token into Sun Java Directory Server?
havent found any helpful docs on the net regarding the same.
We want the users to get authentication from a Sun Directory when he login from a Domino HTTP server
thanks
Prasad

Sun Directory Server is a generic purpose LDAP based directory server and can certainly contain any data, including LTPA tokens.
Whether these tokens could be used for authentication using LDAP is another story (and the answer is probably no).
Regards,
Ludovic.

Integrating Sun Java Directory Server with Sun Java Application Server 7

Hi,
My basic goal is to implement Single Sign On within the network i,e if the user is inside the company's network and tries to access any application, then he should not be required for Username/password again becuase he is in the network.
My question is Is this possible with Sun Java System DIrectory server. If yes how can we integrate Directory Server with Sun Java System Application Server 7 2004Q2.
Please help.
Thanks

Directory Server in itself doesn't provide any kind of SSO functions. Basically it is a high performing data repository accessible via LDAP and DSML. It is, however, a key component used by SSO applications like Access Manager. If your applications are web applications then take a look at Access Manager for your SSO needs.
Regards,
Scott

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/

Sun Java Directory Server 6.3 supports nCipher HSM?

Hi,
We want to do the replication in Master - Master configuration on SSL. Does anyone has an idea whether it is possible to store the SSL Certificate Keys used for replication in nCipher netHSM.
If yes, can anyone provide us the URL on how can it be done or how to go about it?
Thanks and Regards

Hi,
Thanks for the reply. The URL that you mentioned has "Sun Java System Web Server" integration with nCipher HSM.
We have a requirement where we want to do replication between two "Sun Java Directory Servers" on SSL and the keys used are in HSM. We are not using Web Servers in our setup.
If you have any info on integration with Directory Servers, it would be of great help.
Thanks and Regards.

Oracle JDeveloper 10g with Sun Java App server

I have oracle JDeveloeper 10g and sun App Server 8. I want to find out if JDeveloper can create entity beans that can run on Sun app server.
I know that sun app server uses things like sun-cmp-mapping.xml and sun-ejb-jar.xml. If i create these as normal in JDeveloper would they run on sun app server? if not what configuration do i need to do?

Sun Java App Server 8 doesn't ship with the Apache Tomcat jk/jk2 connector. But you can download Tomcat 5 and install it. Copy ${catalina_home}/server/lib/tomcat-jk2.jar under $s1as_home}/lib
Now Sun Java App Server 8 will have the code required. Then you will need to start the jk connector (this is the most difficult task). Since you don't have any API to start this connector to listen (in Tomcat, the connector is started by default and listen on port 8009), the only way for you to start it is to use JMX. Pick one of the available JMX client ( jmx-ri is a good candidate), and do:
(1) create the connector
(2) start the connector
Then follow the Jakarta Tomcat instruction on how to install Apache and JK2.
I didn't spend the time to find the exact command for JMX, but technically it should work. Once I have time I will take a look (The Tomcat 5 Admin Gui uses JMX, so by browing the code you should find the exact JMX command)
Hope that help.
-- Jeanfrancois

Error in installing sun java directory server

dear ,
i am trying to install sun java directiry server from sun java enterprise server using command line ( ./installer ), but this error reported to me when i issue the installer command .
# ./installer
Error occurred during initialization of VM java/lang/NoClassDefFoundError: java/lang/Object
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
Thanks in Advance,
Basem

Sorry for the delay in response.
It could be a patch issue. Have you read http://docs.sun.com/app/docs/doc/820-2210/gduwe?a=view
Have you checked if the problem exists in Web Server 7.0 update 3 as well?
Can you send more details like :
isainfo -v
file /home/sjws7.0/lib/libadminsecurity.so
ldd /home/sjws7.0/lib/libadminsecurity.so

RSA Certificate Manager with Sun Java Directory Server

Similar Messages

Maybe you are looking for