Failed to stop two components in application server
my operating system is hp-ux 11.1,when iI use the command :opmnctl stopall
to stop all compenents in middle-tier 904,but there are two components can not be stopped because of timeout. how should i do
any help will be appreciated.
Look for a server.log file.
You could have some memory errors, which not necesary means that your server needs more memory but you may need to give more memory to the processes on the configuration files.
Carlos
Similar Messages
-
J2ee server status stopped in one of application server
Short Text
J2ee server status stopped in one of application server
Long Text
Dear supprot,
We have 3 application servers to our production server.
App1 and App3 are working fine. when i am trying to start App2
J2ee server0 for the same server is getting stopped.
at that time "r3trans -d" is also taking lots of time on all the servers but giving RC 000.
when i will stop the app2 application server again "r3trans -d" status is
coming fast with 0000 for remaining servers and at that time everything is working fine.
please kindly help me to resolve this problem.
Regards
NirgunHello,
Refer to the log files in the instance work directory for a clue why the server node does not start. Usually the files you are interested in are:
dev_serverX
std_serverX.out
dev_disp
If you share these files I could help you identify and fix the problem.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA) -
Crystal Reports 2013 Failed to find an Available Report Application Server.
Hi Experts,
I am unable to Publish Crystal Reports 2013 to the BI 4.1 SP2 Enterprise.
I have installed SAP CR 2013 on my Laptop and also on our Citrix machine, from both systems I am getting the following error when try to publish:
Failed to find an Available Report Application Server.
All the ports and firewall are open, when doing some trace with Wireshark, its assigning some random ports starting with 64960.
On the same machine, i have installed Crystal Reports 2008, I could publish reports to Enterprise.
Could you please let me know what might be the issue.
Is Crystal Reports 2013 need any specific port to be assigned?
Thanks,
KrisHello Experts,
In addition to assiging the ports for below servers,
Crystal 2013 Report Application Server
Crystal Processing Server
Input File Repository Server
Outout File Repository Server
I have configured the following setting also: Add Service Account that the
CMS runs under to the server's local admin group.
Still I am getitng the following error when trying to save the report to Enterprise:
" Failed to find an Available Report Application Server "
Please advise .
Thanks,
Kris -
Dcmctl to stop/start cluster -- restart application server "busy"
Hi,
I am running two instances of 9iAS 9.0.2.x and 9.0.3 on two servers with a third being the infrastructure server. The 9.0.3 instances are clustered together.
I'm using dcmctl to stop my cluster and start it again. We take the database offline nightly to reload the data from the customer site and need to stop the cluster while the database is being reloaded (schema user dropped and full import being done).
I use:
dcmctl stop -cl cluster
and
dcmctl start -cl cluster
from one of the server's scripts. However, when we restart, the user's try to hit the web page and get an error stating that the application server is "busy".
Is there a reliable way to stop and start, short of rebooting the servers?
Thanks,
JeffHello,
The following section on the Help Portal has further information about startsap and stopsap (Starting and Stopping SAP Systems and Instances) :
http://help.sap.com/saphelp_nw04/helpdata/en/5d/c4dd9b9d91dd458e9e5c0386edeb86/frameset.htm
Regards, Mark -
Online Backup Failed from DB13, brbackup runs on application server
Hi Everone,
I am getting problem when i am scheduling Online Backup from DB13 t-code.
Backup gets failed because logical command BRBACKUP execute on our Application server host rather than DBCI server host.
I have pest the lob logs below:
Job started
Step 001 started (program RSDBAJOB, variant &0000000000389, user ID BASIS)
Execute logical command BRBACKUP On host xyzapp - (Application server)
Parameters:-u / -jid ALLOG20110824210000 -c force -t online -m all -p initSEP.sap -a -c force -p initSEP.sap -s
d
BR0051I BRBACKUP 7.00 (40)
BR0252E Function fopen() failed for '/oracle/client/10x_64/instantclient/dbs/initSEP.sap' at location BrInitSapRead-1
BR0253E errno 2: No such file or directory
BR0159E Error reading BR*Tools profile /oracle/client/10x_64/instantclient/dbs/initSEP.sap
BR0280I BRBACKUP time stamp: 2011-09-02 21.01.09
BR0301E SQL error -12545 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-12545: Connect failed because target host or object does not exist
BR0310E Connect to database instance SEP failed
BR0056I End of database backup: begroqyn.log 2011-09-02 21.01.09
BR0280I BRBACKUP time stamp: 2011-09-02 21.01.09
BR0054I BRBACKUP terminated with errors
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished
Please help.
Thanks,
OceanHello
The previous contributor is correct, the profile is usually read from ORACLE_HOME. I have never seen this error linking to the Oracle client directory, please double check the following
Ensure that your envirionment variables are correctly set ORACLE_HOME, DIR_LIBRARY
Brtools are always installed on the DB server and can be called from any application server. if you are scheduling from DB13 on the application server, what is the connection setup? RSH, RFC, standalone gateway?
If using a standalone gateway, it must be installed on the DB server, please refer to oss notes #446172, #1025707
Best Regards
Rachel -
Unable to bring up all components of application server after it was down.
Hi,
The application server is running on windows server.
Tried with opmnctl shutdown
and then opmnctl startall
But components are not running.
Tried individual components.
facing error with dcm-daemon and OC4J.
following error is recorded for Dcm-daemon
ADMN-202046
The OracleAS Repository API threw an exception when obtaining the connect string to the Metadata Repository
Resolution:
Check the exception thrown by the Repository API for resolution information.
Some common causes of this problem are as follows:
OID is not running or unavailable
the ias.properties file is misconfigured with incorrect OID connection information
OID permissions are incorrectly defined
Base Exception:
oracle.ias.repository.schema.SchemaException
Unable to establish connection to the Oracle Internet Directory Server ldap://phl01-css-1.na.ikon.net:389/. Base Exception : javax.naming.CommunicationException: phl01-css-1.na.ikon.net:389 [Root exception is java.net.ConnectException: Connection refused: connect]
the current status details are
D:\OraHome_1\opmn\bin>opmnctl status
Processes in Instance: css.phl01-css-1.na.ikon.net
------------------------------------------------+------
ias-component | process-type | pid | statu
------------------------------------------------+------
DSA | DSA | 5684 | Alive
LogLoader | logloaderd | 724 | Alive
dcm-daemon | dcm-daemon | N/A | Down
OC4J | OC4J_SECURITY | N/A | Down
HTTP_Server | HTTP_Server | 4592 | Alive
OID | OID | 5292 | Alive
Please advice.
Thanks,
GuruOID is down by the look of things.
ldap://phl01-css-1.na.ikon.net:389/
not responding. Check oidldapd.exe. -
Starting and stopping 9ias Infrastructure and Application Server
I have Oracle9ias R2 Infrastucture and Application running on one machine (bad idea - I know) on Windows 2000. I had to restart the system and of course all the different instances from Infrastructure and Application Server started in the wrong order and now nothing operates at all. (It was fine yesterday - really, it was).
Could someone please give me a rough guideline on how to start these services, or instances in the right order.
Much obliged
WilliamSir,
Can you help me to do the installation of 9ias rel. 2.
I installaed 9ias infrastructure on separate m/c.
But unable to do single sign-on on 9ias server side.
How to configure it for web applicaions?
regards -
Applications stopped to work after application server restarted
Hi all,
Does anybody face the following problem? Applications which worked properly before application server (WLS Release 11.1.1) restart change their behavior. Particularly, instead label text of arguments of entity objects pages display arguments original names like control hints had not been configured. Only after redeployment the same ear file applications return back to normal. It never happens on local JDeveloper (11.1.1.3) environment. I guess that something wrong in application server application.
Thanks,
SNikiforovFor jdev 11.1.1.3 you need a wls 10.3.3 server. otherwise you run into problems. For more info check http://wp.me/pcBZk-7S
Timo -
"Failed to find an available Report Application Server." - Error
I'm using .net sdk to connect to Crystal report server XI R2 from Visual Studio 2005.
I was able to successfully run reports from .net app until I upgraded my Crystal Report Server from XI R2 to Crystal Report Server 2008.
Now when I try to run the report from .net app it connects fine to Enterprise and retrieves the report fine, but it failing near the code
reportClientDocument = reportAppFactory.OpenDocument(infoObject.ID, 0);
Is there a way to get this working? Any advice is greatly appreciated.
My code is as below:
SessionMgr sessionMgr = new SessionMgr();
EnterpriseSession enterpriseSession;
ReportAppFactory reportAppFactory;
ReportClientDocument reportClientDocument=new ReportClientDocument();
EnterpriseService enterpriseService;
InfoStore infoStore;
InfoObjects infoObjects;
InfoObject infoObject;
try
// set the name of the CR server
String crServerName = ConfigurationManager.AppSettings.Get("CRServerName");
// set userid to logon to CR server
String crUserID = ConfigurationManager.AppSettings.Get("CRUserID");
//set pwd to logon to CR server
String crPwd = ConfigurationManager.AppSettings.Get("CRPwd");
//set userid to logon to database
String dbUserID = ConfigurationManager.AppSettings.Get("DBUserID");
//set pwd to logon to database
String dbPwd = ConfigurationManager.AppSettings.Get("DBPwd");
//set connection Info to logon to database
String dbServerName = ConfigurationManager.AppSettings.Get("DBServerName");
//pass Crystal enterprise logon credentials
enterpriseSession = sessionMgr.Logon(crUserID, crPwd, crServerName, "secEnterprise");
enterpriseService = enterpriseSession.GetService("InfoStore");
infoStore = new InfoStore(enterpriseService);
//pass the report Name to query and pass it to reportClientDocument
infoObjects = infoStore.Query("Select SI_ID From CI_INFOOBJECTS Where SI_NAME='" + reportName + "' And SI_INSTANCE=0");
infoObject = infoObjects[1];
//Connecting to RAS (Report Aplication Server)
EnterpriseService tempService = enterpriseSession.GetService("", "RASReportFactory");
reportAppFactory = (ReportAppFactory)tempService.Interface;
reportClientDocument = reportAppFactory.OpenDocument(infoObject.ID, 0);
// Pass datbase logon credentials
reportClientDocument.DatabaseController.LogonEx(dbServerName, "", dbUserID, dbPwd);So it's failing to connect.
Did you see if there's anything blocking connection to the RAS server? I'm assuming your app is on a different machine than the RAS server.
Firewall config is first thing I'd look at. Network config would be next.
Sincerely,
Ted Ueda -
Deploy to Application Server Failed on a distributed environment
Hi All,
I am trying to configure new Hyperion verion 11.1.2.2 on distributed environment but during configuring calculation manager to application server failed and getting error message like "Deploy to Application Server Failed". I am not sure what is issue and how to fix it. I have tried to read log files but I am not able to undersantd where to look and debug this issue.
My Hyperion Environment over view as a below:-
1- I have used Microsoft VMWARE to build my Hyperion Enviornment
2- I have created 1 window server 2003 domain and made 4 clients of that domain. (All these systems have windows server 2003 installed). I have given name to each client server i.e. System A, System B, System C, System D
3- I have installed SQL 2005 and created databases for all Hyperion components i.e. Shared services, calculation manager, epma on a system A
5- I have installed and configured foundation services and weblogic server on a system B. (In this system I have installed and configured shared services, weblogic, workspace, and able to deploye application server on a same system)
6- On a system A I am able to complete installation for hyperion Performance Management Architect and Calculation Manager and able to finish all type of configuration for these two components but as soon as system trying to configure any related to APPLICATION SERVER services it fails to configure. On a configuration summary page system shows everything is configured but APPLICATION SERVER says FAILED wrtten on a red color letters.
I have explored log files and found that Calculation Manager application server failed to deploy or Deploy to Application server failed.....
Since, I am not sure where to look and how to debug this issue I am requesting to all hyperion friends to help and guide me to debug as I have been trying to install this product since last friday and still no out put....
I will be really thankful if someone share his or her wisdom to help me....
Thank you to all in Advance.....
Thanks,
SafiDid you install all the WebLogic web applications on the foundation machine as well as the machine they are going to be deployed to.
"On the machine on which you plan to administer the WebLogic Server, you must install all Web applications for all applications you plan to deploy on any machine in the environment. (The WebLogic Administration Server is installed and deployed on the Foundation Services machine.)"
Cheers
John
http://john-goodwin.blogspot.com/ -
OEPM 11.1.1.3 Planning Deploy Application Server Failed
Hi All,
We are using two machines: M-A for OEPM 11.1.1.3 & Weblogic Application Server 9.3, M-B for Oracle Repository
Recently We did manual cleanup process from machine A had old version 11.1.1.1 -No SSL <stopped the services, Restarted the server, cleared\deleted folders and Removed Register entry by Searching Key -> Hyperion...& restarted the Server before Re-install>
Installed the products <EMP 11.1.1.3 - 2003 sp2 64bit, SSL enabled> and successfully configured SS, but Planning configuration failed with following Error: Deploy to Application server & Register with SS failed
Configtool.Log
com.hyperion.cis.config.wizard.RunAllTasksWizardAction, ERROR, Shared Services Registration task can not be executed because Shared
Services instance is not available in Registry
com.hyperion.cis.config.wizard.RunAllTasksWizardAction, ERROR, Error:
java.lang.NullPointerException
at com.hyperion.cis.config.wizard.RunAllTasksWizardAction.executeDbConfigTask(RunAllTasksWizardAction.java:666)
at com.hyperion.cis.config.wizard.RunAllTasksWizardAction.execute(RunAllTasksWizardAction.java:202)
at com.installshield.wizard.RunnableWizardBeanContext.run(Unknown Source)
com.hyperion.cis.config.Configurator, DEBUG, Loading AppServerDeployer class for product: Planning_1_9.5.0.0
com.hyperion.planning.HspWebAppDeployer, DEBUG, In HspWebAppDeployer constructor.
com.hyperion.cis.config.ConfigRegistryUtils, DEBUG, Looking for product component in the registry: component type = SHARED_SERVICES_PRODUCT
com.hyperion.cis.config.AppServerDeployer, DEBUG, Value of "enable_windows_services" property: false
(Nov 18, 2009, 09:48:50 AM), com.hyperion.cis.config.AppServerDeployer, DEBUG, Starting WebLogic 9 deployment...
I have checked the windows services <OpenLDAP, SS Web, RMI> are up and running fine.
We are struggling with this issue for more than 2 days, anybody can help us please.
Thanks.Did this issue resolved ..? appreciate if you could post the solution and steps that you followed
Thanks -
Application server diesn't start
Hi there, I just installed Studio Creator on my Suse 10.1 - I made two attempts always to solve the same problem; one as root and the other as user, but it didn't work.
The application server bundled in doesn't start.
Here the stack trace from the server log.
I hope that someone will be able to help me. Thanks in advance
[#|2006-09-22T00:55:37.883+0200|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]6 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://hydra.localdomain:29686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: hydra.localdomain; nested exception is:
java.net.ConnectException: Connection timed out]|#]
[#|2006-09-22T00:55:37.883+0200|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://hydra.localdomain:29686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: hydra.localdomain; nested exception is:
java.net.ConnectException: Connection timed out]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
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)
at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
Caused by: java.io.IOException: Cannot bind to URL [rmi://hydra.localdomain:29686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: hydra.localdomain; nested exception is:
java.net.ConnectException: Connection timed out]
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:177)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
... 4 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: hydra.localdomain; nested exception is:
java.net.ConnectException: Connection timed out]
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)
... 6 more
Caused by: java.rmi.ConnectException: Connection refused to host: hydra.localdomain; nested exception is:
java.net.ConnectException: Connection timed out
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)
... 10 more
Caused by: java.net.ConnectException: Connection timed out
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:181)
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)
... 15 more
|#]
[#|2006-09-22T00:55:37.887+0200|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2006-09-22T00:55:37.888+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2006-09-22T00:55:37.889+0200|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
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)
at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
|#]
[#|2006-09-22T00:55:37.890+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2006-09-22T00:55:37.898+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
[#|2006-09-22T00:55:37.908+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
[#|2006-09-22T00:55:37.915+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
[#|2006-09-22T00:55:38.557+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-09-22T00:55:38.559+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/09/22 00:55:38]|#]
[#|2006-09-22T00:55:38.559+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2006-09-22T00:55:38.561+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2006-09-22T00:55:38.561+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2006-09-22T00:55:38.561+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2006-09-22T00:55:38.811+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2006-09-22T00:55:39.014+0200|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2006-09-22T00:55:39.015+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2006-09-22T00:55:39.016+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]Please check your DNS address. Also, see the following FAQ. might help debug ythe issue
Why doesn't Application Server start up?
http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/depsrvs/index.jsp -
Startup Problems Application Server on Fedora Core 5
Greetings All;
Little background information
router ip address: 192.168.1.1
web server ip address: 192.168.1.101 (outside: dcrumb.homeip.net)
installed from ip address: 192.168.1.100
using jdk-1.5.0_07
here are my applicable firewall rules:
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 4848 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8080 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8181 -j ACCEPT
-A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8686 -j ACCEPT
I've also forwarded these ports in my Linksys router
Here are my error messages:
[#|2006-06-14T22:30:13.251-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
/usr/share/jdk1.5.0_07/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
-Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
-Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
-Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/SUNWappserver/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/SUNWappserver/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=/usr/share/jdk1.5.0_07/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/derby/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.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-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=/opt/SUNWappserver/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=/opt/SUNWappserver/config
-Djava.library.path=/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/usr/lib/lwp:/opt/SUNWappserver/lib:/usr/lib/lwp:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/usr/share/jdk1.5.0_07/lib/tools.jar:/opt/SUNWappserver/lib/appserv-rt.jar:/opt/SUNWappserver/lib/admin-cli.jar:/opt/SUNWappserver/lib/jax-qname.jar:/opt/SUNWappserver/lib/appserv-cmp.jar:/opt/SUNWappserver/lib/jaxrpc-impl.jar:/opt/SUNWappserver/lib/commons-launcher.jar:/opt/SUNWappserver/lib/jmxremote_optional.jar:/opt/SUNWappserver/lib/j2ee-svc.jar:/opt/SUNWappserver/lib/commons-logging.jar:/opt/SUNWappserver/lib/mail.jar:/opt/SUNWappserver/lib/dom.jar:/opt/SUNWappserver/lib/appserv-jstl.jar:/opt/SUNWappserver/lib/jaxr-impl.jar:/opt/SUNWappserver/lib/j2ee.jar:/opt/SUNWappserver/lib/jsf-api.jar:/opt/SUNWappserver/lib/jsf-impl.jar:/opt/SUNWappserver/lib/saaj-api.jar:/opt/SUNWappserver/lib/appserv-upgrade.jar:/opt/SUNWappserver/lib/jaxr-api.jar:/opt/SUNWappserver/lib/xsdlib.jar:/opt/SUNWappserver/lib/saaj-impl.jar:/opt/SUNWappserver/lib/rmissl.jar:/opt/SUNWappserver/lib/relaxngDatatype.jar:/opt/SUNWappserver/lib/xercesImpl.jar:/opt/SUNWappserver/lib/xalan.jar:/opt/SUNWappserver/lib/appserv-admin.jar:/opt/SUNWappserver/lib/appserv-ext.jar:/opt/SUNWappserver/lib/jaxrpc-api.jar:/opt/SUNWappserver/lib/activation.jar:/opt/SUNWappserver/lib/jmxremote.jar:/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar:/opt/SUNWappserver/imq/lib/jaxm-api.jar:/opt/SUNWappserver/imq/lib/fscontext.jar:/opt/SUNWappserver/lib/ant/lib/ant.jar
com.sun.enterprise.server.PEMain
start
display|#]
[#|2006-06-14T22:30:29.526-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
[#|2006-06-14T22:30:29.537-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2006-06-14T22:30:33.433-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
[#|2006-06-14T22:30:33.461-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-06-14T22:30:34.381-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-06-14T22:30:37.708-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2006-06-14T22:30:37.769-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2006-06-14T22:30:41.921-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2006-06-14T22:30:44.285-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2006-06-14T22:30:44.322-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2006-06-14T22:30:49.383-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2006-06-14T22:31:15.145-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2006-06-14T22:31:17.679-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75388332422004736|#]
[#|2006-06-14T22:31:19.824-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-06-14T22:31:19.826-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-06-14T22:31:20.540-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75388332902776832|#]
[#|2006-06-14T22:31:21.303-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-06-14T22:31:21.542-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2006-06-14T22:31:21.995-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2006-06-14T22:31:22.758-0400|WARNING|sun-appserver-pe8.2|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|#]
[#|2006-06-14T22:31:23.256-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2006-06-14T22:31:23.306-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2006-06-14T22:31:23.320-0400|WARNING|sun-appserver-pe8.2|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|#]
[#|2006-06-14T22:31:23.350-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2006-06-14T22:31:23.931-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2006-06-14T22:31:33.650-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-06-14T22:31:33.651-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:33.720-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:34.266-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
[#|2006-06-14T22:31:34.268-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:34.290-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:34.523-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-06-14T22:31:34.524-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:34.546-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:35.616-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]3 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]|#]
[#|2006-06-14T22:31:35.619-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
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://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
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:177)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
... 3 more
Caused by: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
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.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
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.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
|#]
[#|2006-06-14T22:31:35.629-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2006-06-14T22:31:35.630-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2006-06-14T22:31:35.639-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
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)
|#]
|#]
[#|2006-06-14T22:31:35.642-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2006-06-14T22:31:35.665-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-06-14T22:31:35.708-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-06-14T22:31:35.728-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-06-14T22:31:36.657-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-06-14T22:31:36.675-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/06/14 22:31:36]|#]
[#|2006-06-14T22:31:36.676-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2006-06-14T22:31:36.686-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2006-06-14T22:31:36.687-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2006-06-14T22:31:36.688-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2006-06-14T22:31:38.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2006-06-14T22:31:39.375-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2006-06-14T22:31:39.376-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2006-06-14T22:31:39.452-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2006-06-14T22:31:39.482-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
Does anybody have any suggestions?
Many thanks,
Best,
--Dave
Message was edited by CrumbDav
I did some more research and looked in my domain.xml file and came across this. Not sure if it helps any:
- <configs>
- <config dynamic-reconfiguration-enabled="true" name="server-config">
- <http-service>
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="8080" security-enabled="false" server-name="" xpowered-by="true" />
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true" />
<http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true" />
- <virtual-server hosts="${com.sun.aas.hostName}" http-listeners="http-listener-1,http-listener-2" id="server" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
</virtual-server>
- <virtual-server default-web-module="admingui" hosts="${com.sun.aas.hostName}" http-listeners="admin-listener" id="__asadmin" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
</virtual-server>
</http-service>
- <iiop-service client-authentication-required="false">
<orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1" />
<iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="3700" security-enabled="false" />
- <iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="3820" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
</iiop-listener>
- <iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="3920" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
</iiop-listener>
</iiop-service>Nope - it's not supported. It is useable though ...
The problem is that the Fedora series uses cutting edge technology. The Fedora technology cycles every 6-9 months.
Oracle likes things very stable. So Oracle builds a clean copy using a specific set of APIs at a specific release of the kernel, the glibc and so on. They chose the commercial releases which cycle every 18-24 months - in part so they can get people trained to provide support.
Due to the nature of Linux, you CAN install the correct APIs and get it to work and many of the free distros. Just don't expect Oracle to provide assistance or support. (After all, where do they stop - there are hundreds of free distros, and even more when you count the 'objsolete but still running' ones.)
If you really want to proceed, then you need to read up the cookbook sites from experts such as Ivan Kartik (http://ivan.kartik.sk/) or Werner Puschitz (http://www.puschitz.com) As long as you realize that the install is NOT recommended for production. -
Eclipse/Sun Java Application Server
Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#]Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#] -
Application Server couldn�t start
Dear All,
I'm facing some problems on starting Application Server 8 on Win XP SP2.
When I start Default server it apperars a window console saying:
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 bein
g started in background.
but when i start localhost:8080 the page couldn't not be found.
I've already checked the log file and it appears the following error:
[#|2005-08-19T14:47:33.843+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://172.16.3.211:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.16.3.211; 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://172.16.3.211:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.16.3.211; 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: 172.16.3.211; 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: 172.16.3.211; 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-08-19T14:47:33.843+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-08-19T14:47:33.843+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-08-19T14:47:33.843+0100|WARNING|sun-appserver-pe8.1_02|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-08-19T14:47:33.843+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-08-19T14:47:33.843+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-08-19T14:47:33.859+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-08-19T14:47:33.859+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-08-19T14:47:34.109+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-08-19T14:47:34.109+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/08/19 14:47:34]|#]
[#|2005-08-19T14:47:34.109+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-08-19T14:47:34.125+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-08-19T14:47:34.125+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-08-19T14:47:34.125+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-08-19T14:47:34.125+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-08-19T14:47:34.343+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-08-19T14:47:34.343+0100|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Any help from you, I would be very apreciated...
Thank youAccording to the log file, the server startup is failing and therefore you can not access localhost:8080.
The reason for startup failure is that JMX Connector service within application server could not bind to the address 172.16.3.211:8686. This could be caused by several things, one of them being firewall not allowing it.
A workaround would be to open up application server configuration file INSTALL_DIR/domains/domain1/config/domain.xml and add an entry of the form
<jvm-options>-Djava.rmi.server.hostname=localhost</jvm-options>
The entry will have to added under the java-config element.
This will make Java RMI use "localhost" for binding remote server side objects(this assumes that your firewall allows creation of localhost connections)
Maybe you are looking for
-
Hi All, I have a problem with automatic dunning. I want to have interest calculation and charge in dunning letter but SAP have a problem "interest indicator xxx and currency xxx are missing in T506Z. Pls help me. Thanks,
-
If I notice this problem (eg. someone calls me on another phone) and I make a call from my phone to someone else (which DOES work) then all the missed calls and SMS will come through. Almost as if the phone put the cellular radio to sleep and only wa
-
Earning cash back rewards on child support!
My DBF recently lost his job, so he will start making child support payments manually instead of having them withdrawn from his paycheck. I have read on here that credit cards can't be used for child support payments; at least not without fees that w
-
Is it mandatory to send both old and new entity type in case of update procedure?
Hi, While updating an entity, is it mandatory to send both the new entity and the old entity from the exit to the procedure? In that case we would have to create 2 temporary tables, insert values into them and then pass the tables to the procedure? O
-
Please, if you have ever used schemas with JDOM !!!!!!
How can we validate a document which refers to a schema rather than a DTD with JDOM ? I tried to do that but an error occured, telling to me that my root element isn't declared. Can someone help me ?