Sun AppServer can't start

Hi everybody.
I hope this is the right forum to post this question. If not, I'm sorry. My problem is: I've just downloaded and installed J2EE SDK and when I try to run Sun AppServer, I get this error message from Java Virtual Machine Launcher saying "Can not find the main class".
Has anybody encountered this kind of problem? I would be greatfull for any hint, since this is very frustrating.
TIA
P.S. I'm running windowsXP, if that might be relevant.

I seem to have exactly the same problem. Also running XP professional.
Just downloaded and installed J2EE 1.4
< j2eesdk-1_4-dr-windows-eval.exe >
and when I try to start < Start Default Domain > I get the message "Could not find the main class. Program will exit" from the Java Virtual Machine Launcher.
The command prompt window shows the following text
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1.
Press any key to continue . . .
and the log files shows a zero length, and appears blank/empty when you examin it.
Any comments welcome, thanks Joe Cullity

Similar Messages

Sun App server can't start

Hello,
I've got Sun One Studio and I can't start the Application Server. I have created a domain like this int the command prompt :
asadmin> create-domain path /global/appserver adminport=4848 adminuser xxx adminpassword xxx scdomain
Domain scdomain successfully
But when I start the server, I've got a message :
Le service Sun App Server 7 Admin Server (domain1:admin-server) d�marre.....
Le service Sun App Server 7 Admin Server (domain1:admin-server) n'a pas pu �tre
lanc�.
Le service n'a pas signal� d'erreur.
Vous obtiendrez une aide suppl�mentaire en entrant NET HELPMSG 3534.
C:\Sun\jstudio\AppServer7\domains\domain1\admin-server\bin>net helpmsg 3534
Le service n'a pas signal� d'erreur.
In english, it is said that the server can't have been started. And there isn't any error ...
Whith Sun Studio one, I've got this message :
Could not start the instance
server failed to start: abnormal subprocess termination
Can somenone help me please ?
Thanks in advance.

OK thanks caseylou. The server.log file contains that :
[12/Oct/2004:14:29:02] INFO ( 2612): CORE1116: Sun ONE Application Server
[12/Oct/2004:14:29:03] FATAL ( 2612): CORE4005: Internal error: unable to create JVM
[12/Oct/2004:14:29:03] SEVERE ( 2612): CORE4009: Failed to load JVM (check your JRE)
[12/Oct/2004:14:29:03] SEVERE ( 2612): CORE3187: Late initialization failed: Error running init function(late) init-j2ee: unknown error
Sorry, I have created two topics in the forum (J2SE and J2EE) because on the J2SE I have been recommended this forum.
Maybe it is better to continue on the first topic ?
http://forum.java.sun.com/thread.jsp?forum=17&thread=561619&tstart=0&trange=15
Sorry for "flooding".

Can not start Messaging server in Sun Java System Messaging Server 6 2005Q1

Hi all,
I installed Sun Java System Messaging Server 6 2005Q1 from Solaris 10 DVD on Solaris 10.
After the installation, I got directory server, admin server running but messaging server not running. I can not start Messaging server (start smtp, http, pop, imap). I found in directory which I installed messaging server but I could not see script "start-msg" and "stop-msg".
# pwd
/opt/SUNWmsgsr/sbin
# ls
MoveUser ha_ip_config imquotacheck imsdirmig mkbackupdir
UpgradeMsg5toMsg6.pl hashdir imsbackup imsexport readership
configure imexpire imsconnutil imsimport reconstruct
control-params.txt iminitquota imscripter imsrestore relinker
deliver immonitor-access imsdaaci mboxutil useconfig
Any idea what might have gone wrong?
Thanks.

Thanks.
I have a problem when I configure the Messaging Server (by running the /opt/SUNWmsgsr/sbin/configure script):
Hostname mailtest for this machine is not a fully qualified domain name. Please
correct this before attempting to configure Messaging Server. Please make sure
that your DNS is working properly.
<Press ENTER to continue> {"<" goes back, "!" exits}
Can you help me fix this problem?
Thanks.

Can't PING a Datasource from Sun AppServer 1.4

posted February 25, 2004 06:49 PM
Hi all!
I am trying to create a datasoure in Sun AppServer 1.4 Developer Release. To connect to MySQL
After download and installed the mysql-connector, I created a connection pool in the appserver called mySQLconPool with the following settings:
Datasource Classname: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
Additional Properties
serverName: 127.0.0.1
databaseName:test
port:3306
user:Admin
password:admin
I added the mysql-connector jar file path to the app server> JVM Settings> Classpath sufix.
The problem is that if I try to PING the connection I get the following error:
quote:
An error has occurred.
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Error getting connection from the EIS
What am I doing wrong? Am I missing something?
Please if any of you can help me I will appreciate!!!!!!
Thanks in advance,
JOSEL

Hi aagore:
First thank you for replying. Here you have a snippet you domain.xml:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="mySQLconPool" pool-resize-quantity="2" steady-pool-size="8">
<property name="url" value="jdbc:mysql://127.0.0.1:3306/sss"/>
<property name="user" value="Admin"/>
<property name="port" value="3306"/>
<property name="databaseName" value="sss"/>
<property name="password" value="admin"/>
<property name="serverName" value="127.0.0.1"/>
</jdbc-connection-pool>
</resources>
JOSEL

Sun Appserver V9.0 Facing following error while starting server

C:/Sun/AppServer/jdk\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:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/javadb/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-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.DocumentBuilderFactory=com.sun.org.apache.xerces. \internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Sun/AppServer/jdk/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/imq/lib/imqxm.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
-Dcom.sun.aas.classloader.serverClassPath=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/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\SYSROOT\system32;C:\SYSROOT;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\PROGRA~1\CA\ETRUST~1;D:\j2sdk1.4.2_05\bin;D:\Program Files\python;C:\PROGRA~1\ABSOLU~1;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;C:\Sun142\AppServer\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/Sun/AppServer
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=;C:\Sun\AppServer\addons\amserver\amclientsdk.jar;C:\Sun\AppServer\addons\amserver\amwebServiceProvider.jar;C:\Sun\AppServer\addons\amserver
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/Sun/AppServer/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]
[#|2006-09-15T11:02:35.125+0530|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...|#]
[#|2006-09-15T11:02:35.390+0530|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;|java.lang.reflect.InvocationTargetException
     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:585)
     at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.xml.parsers.FactoryConfigurationError: Provider com.sun.org.apache.xerces. \internal.jaxp.DocumentBuilderFactoryImpl could not be instantiated: java.lang.NullPointerException
     at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
     at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:404)
     at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2172)
     at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:363)
     at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:468)
     at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:259)
     at com.sun.enterprise.config.ConfigBeansFactory.getConfigBeanByXPath(ConfigBeansFactory.java:85)
     at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getServerBean(ServerBeansFactory.java:104)
     at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:77)
     at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:115)
     at com.sun.enterprise.server.logging.ModuleToLoggerNameMapper.getMatchedModuleLoggerName(ModuleToLoggerNameMapper.java:191)
     at com.sun.enterprise.server.logging.BaseLogManager.addLogger(BaseLogManager.java:156)
     at java.util.logging.Logger.getLogger(Logger.java:232)
     at sun.rmi.runtime.Log$LoggerLogFactory.createLog(Log.java:154)
     at sun.rmi.runtime.Log.getLog(Log.java:121)
     at sun.rmi.server.Util.<clinit>(Util.java:51)
     at sun.rmi.server.UnicastRef.<clinit>(UnicastRef.java:33)
     at java.rmi.server.RemoteServer.<clinit>(RemoteServer.java:97)
     at com.sun.enterprise.admin.server.core.channel.AdminChannel.createServerObject(AdminChannel.java:234)
     at com.sun.enterprise.admin.server.core.channel.AdminChannel.createRMIChannel(AdminChannel.java:92)
     at com.sun.enterprise.admin.server.core.AdminChannelLifecycle.onInitialization(AdminChannelLifecycle.java:61)
     at com.sun.enterprise.server.ss.ASLazyKernel.initializeAdminService(ASLazyKernel.java:181)
     at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:80)
     at com.sun.enterprise.server.ondemand.OnDemandServer.onInitialization(OnDemandServer.java:84)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:316)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
     ... 5 more
|#]
recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecall
     at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:346)
     at java.io.PrintStream.write(PrintStream.java:414)
     at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:280)
     at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
     at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
     at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:115)
     at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:169)
     at java.io.PrintStream.write(PrintStream.java:459)
     at java.io.PrintStream.print(PrintStream.java:602)
     at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.print(SystemOutandErrHandler.java:192)
     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:985)
     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:978)
     at java.lang.Thread.dispatchUncaughtException(Thread.java:1778)

By Sun Appserver v9.0, you mean GlassFish. I did not have any problem is deploying Creator 2U1 project to Glass Fish. See my blog on this
http://blogs.sun.com/winston/entry/deploying_to_glassfish
- Winston

How I can to do get a data sources on sun appserver 8 like this?

jsc GUI develop jsf pages ,I want to get a data sources by Context lookup jndi have binding data sources.
I know weblogic to get this.
such as :
Context ctx = null;
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
p.put( Context.PROVIDER_URL, "t3://localhost:7001" );
p.put("java.naming.security.principal", user);
p.put("java.naming.security.credentials", pwd);
ctx = new InitialContext(p);
ds = (DataSource)ctx.lookup( "myds" );
do you tell me sun appserver 8 how to implements this?thx.

HI
I am not clear what you are looking for but let me try to give you something. Yes it is possible to get DataSources on apserver 8 by registering JDBC Connection Pool and JDBC DataSource in the admin gui. You can use the regisred datasource in your code like this
InitialContext ctx = new InitialContext();
dataSource ds = (DataSource)ctx.lookup( "jdbc/myds" );
OR
if you are looking for the Creator do all these, here is the way.
Create a datasource in the server navigator to point to any of your database. Drag and drop a table to any of your pages in the application (This is not neccessary if any of your application pages have a rowset/datatable already).
Deploy the application then the datasource will be registered into application server 8. You can use the same code now to access the datasource
InitialContext ctx = new InitialContext();
dataSource ds = (DataSource)ctx.lookup( "jdbc/myds" );
Please let me know if you are not looking for above .
Thanks
Srinivas

Pls help! problem to start my sun AppServer

I am a new learner to Sun Microsystem's application server.
Yesterday i start the default server from clicking the icon "start default server" under all programs, it worked fine. But today when i did the same thing, it got problem. it gave the message: CLI156 could not start the domin domin1, check the server log
I tried to start it from commond line by key in "j2ee -verbose", the system says it cannot recognize the command.
I have set the J2EE_HOME to the path of j2ee sdk installations, and also set the bin of j2ee sdk installation to the system enviroment PATH. why it still cannot recognize j2ee command?
i did not do any special things to the application server. the only fault is that i switched off my pc without stop the default server last night.
how can i start the server again?

very strange!!!! The server can be started again, however i did not do anything.
is that the server also has temper sometimes?

Sun AppServer 9.0 Update 1 on Solaris not supporting form-based auth

Ok, I installed Appserver 9 on a Solaris box and then started up the default domain1. When I point the browser to http://localhost:4848 I am not pointed to the login page for the admingui, it just bypasses the authentication and I am allowed to perform all admin actions without logging in. I then deployed a custom web application that uses form-based authentication that works correctly on Sun Appserver 8.1. However it behaves the same way as the admingui application (I am not presented with a login page). After setting some of the log levels to FINEST and looking at the logs it appears that when these requests are coming in they are not matching any constraint (but the constraints are defined in the web.xml). Installing Appserver 9 on a win2k box does not have this issue. Has anyone else seen this problem? Is there some security setting that is not turned on by default from the solaris install????

Ok if anyone is interested I was able to fix my problem. It looks like the issue is the version of java used with Appserver 9 on Solaris. The latest version of java i have on the machine is Java 1.5.0_06, but everytime I try to install the Appserver with this version it hangs at 39% into the installation. The next latest version of Java i have on the machine is 1.5.0_02, so that is the version I was using to install and the install works perfectly. However, after the install the form-based authentication does not work with this version of Java on Solaris.
They way I fixed this was to modify the asenv.conf file in the Appserver_Install dirrectory to point to the Java 1.5.0_06 installation and started the domain, now the form-based authentication is working as expected.
I guess my question now is does anyone know why I can't install the server with Java 1.5.0_06? But it looks like I need that version to actually run things correctly.

New install of SJS Ent 8 on Solaris, can't start Application Server 8.1

Hello,
Appreciate in advance your help.
Just downloaded and installed SJS 8.1 on a new Sun Solaris 10 box. I'm able to run the IDE and have started the Tomcat server, but when attempting to start the SJS 8.1 application server, I get:
The Sun Java System Application Server 8.1 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)
- Incorrect server configuration
- Corrupted Deployed Applications
The problems are:
- There is no server.log file in the expected directory at /opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs
- I ran netstat -a, but could glean no useful information
- I have not modified the server configuration since the new install
- I have not deployed my application (since I can't start the server).
Forgive my ignorance since I'm not a Solaris expert. I would greatly appreciate your assistance.

No difference in server.log after setting level="FINEST".
Don't know if it would help, but the contents of my server.log file follow:
[#|2006-09-25T15:39:46.485-0400|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
/opt/sun/jstudio_ent8/jdk1.5.0_04/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs/server.log
-Djava.endorsed.dirs=/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/endorsed
-Djava.security.policy=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/server.policy
-Djava.security.auth.login.config=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/cacerts.jks
-Djava.ext.dirs=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/ext:/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/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=myDomain1
-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=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=myDomain1
-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=/opt/sun/jstudio_ent8/AppServ8.1UR2/config
-Djava.library.path=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386/client:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/../lib/i386:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib:/usr/lib/lwp::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/opt/sun/jstudio_ent8/jdk1.5.0_04/lib/tools.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/activation.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/mail.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/admin-cli.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-admin.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-jstl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-logging.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee-svc.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jax-qname.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/dom.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/relaxngDatatype.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xsdlib.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote_optional.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/rmissl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xalan.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xercesImpl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-upgrade.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-ext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/install/applications/jmsra/imqjmsra.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/jaxm-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/fscontext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/ant/lib/ant.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbclient.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start|#]
I do notice that the class path references jdk1.5.0_04. When installing SJS I selected the separately installed jdk1.5.0_07. Could that be causing the problem?
You have great patience.

Sun AppServ Problem

Hi
I have a problem when I started the admin server, the error is:
......C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
*** EXITING ERROR:
Can't create Java VM
How I can repair it?
Thanks

Looks like a horribly failed install - one that didn't load any of the J2EE SDK libraries in the runtime classpath.

Sun AppServer 8-Startup failed

Hello All,
Can anyone please, please help me out?!!!
I cannot get appServer8 up and running without a "server startup failed" error. I am running WinDozeXP Pro.
I tried re-installing, seperate bundle and full bundle downloads, checking system/global variables, path/classpath for spaces and quotes, followed all troubleshooting docs, checked the <http-listener> default ports in the domain1/config/domain1.xml
Startup shows: Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Press any key to continue . . .
Shut down shows: The domain (domain1) isn't running.
CLI157 Could not stop the domain domain1.
Press any key to continue . . .
Server log shows:
[#|2005-06-05T13:28:06.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/jdk1.5.0_03\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:/jdk1.5.0_03/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:\jdk1.5.0_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\jdk1.5.0_03\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:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\System32;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/jdk1.5.0_03/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.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\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\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.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-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-06-05T13:28:12.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-06-05T13:28:13.625-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-06-05T13:28:15.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-06-05T13:28:16.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-06-05T13:28:19.937-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-06-05T13:28:20.312-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2005-06-05T13:28:22.187-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:22.218-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1375 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:22.906-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-06-05T13:28:23.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2005-06-05T13:28:23.140-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.171-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-06-05T13:28:23.328-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 73269464414158848|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2005-06-05T13:28:23.859-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4438 msec, Total EJB Compiler Module Time: 4016 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 4016 msec, CMP Generation: 641 msec (15%), Java Compilation: 3297 msec (82%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:28.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-06-05T13:28:28.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:28.265-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.406-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 73269464784896000|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-06-05T13:28:29.109-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:29.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-06-05T13:28:29.281-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.421-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-06-05T13:28:29.453-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-06-05T13:28:29.453-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.484-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-06-05T13:28:29.578-0700|INFO|sun-appserver-pe8.1_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-06-05T13:28:31.046-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
     java.net.ConnectException: Connection timed out: no further information]|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
     java.net.ConnectException: Connection timed out: no further information]
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:101)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: java.io.IOException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
     java.net.ConnectException: Connection timed out: no further information]
     at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
     at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
     at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:173)
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:93)
     ... 3 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
     java.net.ConnectException: Connection timed out: no further information]
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
     at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
     at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
     ... 5 more
Caused by: java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
     java.net.ConnectException: Connection timed out: no further information
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
     at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
     ... 9 more
Caused by: java.net.ConnectException: Connection timed out: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
     at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
     at java.net.Socket.connect(Socket.java:507)
     at java.net.Socket.connect(Socket.java:457)
     at java.net.Socket.<init>(Socket.java:365)
     at java.net.Socket.<init>(Socket.java:178)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
     ... 14 more
|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-06-05T13:28:52.546-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:118)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:52.562-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/06/05 13:28:52]|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-06-05T13:28:53.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-06-05T13:28:53.015-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Thanks in Advance,
~Stacy

[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
is the start of your problem, but I expect you've guessed that.. Have you googled for the messages? is host romeo available on that port???

Can't start Appserver7 on RedHat7.2

After installing appserver, I get this:
#/opt/SUNWappserver7/bin/asadmin start-domain
Could not start the instance: domain1:admin-server
server failed to start: abnormal subprocess termination
Could not start the instance: domain1:server1
server failed to start: abnormal subprocess termination
Could not start the domain.
Could not start one or more instances in the domain : domain1
#more /var/opt/SUNWappserver7/domains/domain1/admin-server/logs/server.log
[06/Nov/2003:05:18:13] INFO ( 8441): CORE1116: Sun ONE Application Server 7.0.0_00
[06/Nov/2003:05:18:15] INFO ( 8443): CORE3016: daemon is running as super-user
[06/Nov/2003:05:18:17] INFO ( 8443): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_02] fr
om [Sun Microsystems Inc.]
[06/Nov/2003:05:18:18] WARNING ( 8443): CORE5061: Exception :
java.lang.NoClassDefFoundError: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.config.ConfigBean.getAttributeValue(ConfigBean.java:488)
     at com.iplanet.ias.config.serverbeans.Server.getApplicationRoot(Server.java:1057)
     at com.iplanet.ias.instance.InstanceEnvironment.createApplicationRootPath(InstanceEnvironment.
java:1297)
     at com.iplanet.ias.instance.InstanceEnvironment.init(InstanceEnvironment.java:285)
     at com.iplanet.ias.instance.InstanceEnvironment.getLibClassesPath(InstanceEnvironment.java:175
4)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:141)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): ADM0003:MBeanServer initialization failed
java.lang.NoClassDefFoundError: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.admin.common.ObjectNames.getObjectName(ObjectNames.java:802)
     at com.iplanet.ias.admin.common.ObjectNames.getControllerObjectName(ObjectNames.java:140)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.initialize(ASMBeanServerImpl.java:144)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.<init>(ASMBeanServerImpl.java:96)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.<init>(ASMBeanServerImpl.java:110)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.getMBeanServerInstance(ASMBeanServerImpl.java:125)
     at com.iplanet.ias.admin.server.core.AdminService.init(AdminService.java:125)
     at com.iplanet.ias.admin.server.core.AdminServiceLifeCycle.onInitialization(AdminServiceLifeCycle.java:82)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.admin.server.core.AdminService.init(AdminService.java:152)
     at com.iplanet.ias.admin.server.core.AdminServiceLifeCycle.onInitialization(AdminServiceLifeCycle.java:82)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): CORE3186: Failed to set configuration
Can anyone help me how to fix this?

After installing appserver, I get this:
#/opt/SUNWappserver7/bin/asadmin start-domain
Could not start the instance: domain1:admin-server
server failed to start: abnormal subprocess termination
Could not start the instance: domain1:server1
server failed to start: abnormal subprocess termination
Could not start the domain.
Could not start one or more instances in the domain : domain1
#more /var/opt/SUNWappserver7/domains/domain1/admin-server/logs/server.log
[06/Nov/2003:05:18:13] INFO ( 8441): CORE1116: Sun ONE Application Server 7.0.0_00
[06/Nov/2003:05:18:15] INFO ( 8443): CORE3016: daemon is running as super-user
[06/Nov/2003:05:18:17] INFO ( 8443): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_02] fr
om [Sun Microsystems Inc.]
[06/Nov/2003:05:18:18] WARNING ( 8443): CORE5061: Exception :
java.lang.NoClassDefFoundError: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.config.ConfigBean.getAttributeValue(ConfigBean.java:488)
     at com.iplanet.ias.config.serverbeans.Server.getApplicationRoot(Server.java:1057)
     at com.iplanet.ias.instance.InstanceEnvironment.createApplicationRootPath(InstanceEnvironment.
java:1297)
     at com.iplanet.ias.instance.InstanceEnvironment.init(InstanceEnvironment.java:285)
     at com.iplanet.ias.instance.InstanceEnvironment.getLibClassesPath(InstanceEnvironment.java:175
4)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:141)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): ADM0003:MBeanServer initialization failed
java.lang.NoClassDefFoundError: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.admin.common.ObjectNames.getObjectName(ObjectNames.java:802)
     at com.iplanet.ias.admin.common.ObjectNames.getControllerObjectName(ObjectNames.java:140)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.initialize(ASMBeanServerImpl.java:144)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.<init>(ASMBeanServerImpl.java:96)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.<init>(ASMBeanServerImpl.java:110)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.getMBeanServerInstance(ASMBeanServerImpl.java:125)
     at com.iplanet.ias.admin.server.core.AdminService.init(AdminService.java:125)
     at com.iplanet.ias.admin.server.core.AdminServiceLifeCycle.onInitialization(AdminServiceLifeCycle.java:82)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com/sun/jmx/mbeanserver/GetPropertyAction
     at com.iplanet.ias.admin.server.core.AdminService.init(AdminService.java:152)
     at com.iplanet.ias.admin.server.core.AdminServiceLifeCycle.onInitialization(AdminServiceLifeCycle.java:82)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[06/Nov/2003:05:18:19] SEVERE ( 8443): CORE3186: Failed to set configuration
Can anyone help me how to fix this?

How to create Seperate Containers in Sun AppServer 8.1 2005Q2?

Hi !
We are currently in the middle of a server migration - from Oracle AppServer to the Sun AppServer 8.1. In Oracle it was possible to create seperate containers which had the same i-net address and same port(Called OC4J Instances). These containers were able to start and stop seperatly.(The reason for this is that we have many applications running and if some problems arise we don't need to stop the whole Container/Server)
I tried different solutions:
- create a new domain --> Port has to be not the same
- create an instance --> Port has to be not the same
- create a virtual server --> domain name has to change
i also thought about a special config for http listners
but didn't get to a point jet.
pls help me -- i'm sure it is possible
greetings
maty

Hi Maty,
To anwer you questions from previous posting:
1. Yes you have to deploy all of your apps on all instances known to the loadbalancer. This is becasue all of the request comming to the load balancer can be routed to any of these instances.
2. To insure that you don't run two different versions of you application in the cluster you can quiese single appserver instance or any given application before update. See following doc for more info.
http://docs.sun.com/source/819-0216/ha_as_overview.html#wp1046921
One additional note: To upgrade you application in Sun AS8.1 you don't need to shut it down as it supporst dynamic application deployment. This may be all you need... that is If you don't want any of the High availability features that LB gives you .
Regards,
/Oleg

ClassCastException on Deploy to Sun Appserver 8.1 from Netbeans 4.1

I am working with an academic group that has chosen to use the Netbeans 4.1/Sun Appserver 8.1 integrated combo. We are running a standard ejb app and a standard web app (java servlets, Struts flavor) that talks to the ejb app.
But the Sun Appserver is incredibly unstable with regard to the web container. If the problem is really Sun's, I can't believe
that they released something such as this. We get a ClassCastException related to jsp configuration everytime we
'deploy' from Netbeans to the web container.
And sometimes, the ejb container seems to just "disappear" from our runtime execution. In this situation, the web container gets no data from the ejb container, so that the form fields in the result html show up empty. Could the ClassCastException at deployment time be the problem? If not, what can we do to stabilize our deployment?
I've posted the error with system info below. Any help or ideas would be much appreciated. Thank you in advance!
[ o/s: Windows XP sp2 ]
[ jdk: 1.4.02 ]
[ Sun Appserver 8.1 ]
[ Netbeans 4.1 with 'deploy' command running ]
[ Netbeans deploying a standard ejb app and a standard web app, Struts
1.2 flavor ]
[ Error message: ]
Redeploying
C:\CMU\AdvancedProject\Develop�ment\se-2004-spring-pt-advance�d-team2\PETv3_Struts\dist\PETv�3_Struts.war
java.lang.ClassCastException
at
org.netbeans.modules.j2ee.sun.�dd.impl.web.model_2_4_1.SunWeb�App.setJspConfig(SunWebApp.jav�a:850)
at
org.netbeans.modules.j2ee.sun.�dd.impl.web.SunWebAppProxy.set�JspConfig(SunWebAppProxy.java:�342)
at
org.netbeans.modules.j2ee.sun.�share.configBean.WebAppRoot$1.�getDDSnippet(WebAppRoot.java:3�01)
at
org.netbeans.modules.j2ee.sun.�share.configBean.Base.addToGra�phs(Base.java:625)
at
org.netbeans.modules.j2ee.sun.�share.configBean.SunONEDeploym�entConfiguration.saveDConfigBe�an(SunONEDeploymentConfigurati�on.java:349)
at
org.netbeans.modules.j2ee.sun.�share.configBean.SunONEDeploym�entConfiguration.save(SunONEDe�ploymentConfiguration.java:317�)
at
org.netbeans.modules.j2ee.depl�oyment.config.ConfigSupportImp�l.getDeploymentPlanFileForDist�ribution(ConfigSupportImpl.jav�a:248)
at
org.netbeans.modules.j2ee.depl�oyment.config.ConfigSupportImp�l.getConfigurationFile(ConfigS�upportImpl.java:224)
at
org.netbeans.modules.j2ee.depl�oyment.impl.projects.Deploymen�tTargetImpl.getConfigurationFi�le(DeploymentTargetImpl.java:1�80)
at
org.netbeans.modules.j2ee.depl�oyment.impl.TargetServer.deplo�y(TargetServer.java:615)
at
org.netbeans.modules.j2ee.depl�oyment.devmodules.api.Deployme�nt.deploy(Deployment.java:129)
at org.netbeans.modules.j2ee.ant.�Deploy.execute(Deploy.java:62)
at org.apache.tools.ant.UnknownEl�ement.execute(UnknownElement.j�ava:275)
at org.apache.tools.ant.Task.perf�orm(Task.java:364)
at org.apache.tools.ant.Target.ex�ecute(Target.java:341)
at org.apache.tools.ant.Target.pe�rformTasks(Target.java:369)
at org.apache.tools.ant.Project.e�xecuteTarget(Project.java:1214�)
at org.apache.tools.ant.Project.e�xecuteTargets(Project.java:106�2)
at
org.apache.tools.ant.module.br�idge.impl.BridgeImpl.run(Bridg�eImpl.java:234)
at
org.apache.tools.ant.module.ru�n.TargetExecutor.run(TargetExe�cutor.java:242)
at
org.netbeans.core.execution.Ru�nClassThread.run(RunClassThrea�d.java:125)
Start registering the project's server resources
Finished registering server resources

Thanks for your post!
I have been meaning to reply to this for so long that I have forgotten the exact details of how we fixed this. However, the issue with the ejb container 'disappearing' at random times during application operation was resolved by doing something different in the ejb container. As I recall, the ejb code that we had when the problem existed should not have caused this kind of problem, but we found a work-around.
The 'ClassCastException' on deploy was apparently due to a problem with the portability of Netbeans Java code. Space characters in file paths appear to have caused this problem.

Programmatically access DMQ in Sun AppServer

Hi,
I'm trying to write an automatic recovery tool to recover messages from the DMQ in Sun AppServer (mq.sys.dmq).
I was able to connect to the queue and browse (QueueBrowser) the messages present. I even can reuse the messages to re-post them to the correct queue, but I can't find a way to remove messages from the queue. I want to remove them programmatically, if possible one by one.
Adding a QueueReceiver seemed to work, but it would not receive any of the message already present on the DMQ.
Can anyone help me out with this issue?
Regards,
Bart

I know this is an old post, but this could help :
There is no problem to receive messages already in the DMQ.
Just don't forget to do a jmsConnection.start(); before to dmqConsumer.receive(...);

Sun AppServer can't start

Similar Messages

Maybe you are looking for