Failed to start java application server 8
hi every body,
hi every body,
i am getting the famous error:
" failed to start sun java application server 8 possible causes:
-port conflict
-incorrect server configuration(domain.xml need to be corrected manually)
-corrupted deployed application preventing server to start (domain.xml needs to be modified) "
the thing is that i know the cause of error it is the 3rd one since i had some exception while running a project and since on this error was appearing,and i didnt know how to solve this problem i.e how to edit the domain.xml file
so i uninstaled and reinstaled the java cretor a number of times every time i face the problem, but the last time i did so the folder C:\Sun\Creator\SunAppServer8\domain that contains the file domain.xml was not even there and i dont know why did that happen or how to solve it
please help,
regards.
i too have a similar problem - mine seems to be related to MySQL access but I cant find any help on the problem - surely there is a better way than to continually re-install - on the previous version i could work it out without a re-install but not with the update.
i havent found anything in the server logs - they are huge docs - i cant see how it can be a port conflict as its ok 1 minute and not the next.
i just need a pointer to where to look ?
thanks in advance
Similar Messages
-
Deployment failed. Building failed using sun java application server
Hi
am using netbean 6 ,glassfish v2 and sun java application server 9
When am try to run my jsp file am getting Deployment error report with further error given below.
Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
See the server log for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:163)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor256.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Caused by: org.netbeans.modules.j2ee.deployment.impl.ServerException: The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance._start(ServerInstance.java:1270)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:1224)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.startTarget(ServerInstance.java:1035)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.start(ServerInstance.java:912)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.startTargets(TargetServer.java:417)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:140)
... 16 more
BUILD FAILED (total time: 44 seconds)Hi,
I've found that if you remove the j2ee-application element related to the enterprise app you are trying to deploy from Sun\AppServer\domains\domain1\config\domain.xml, and also remove your enterprise j2ee-app directory from Sun\AppServer\domains\domain1\applications\j2ee-apps\, it works.
This is not a permanent solution. I get the same error again, when I try to redeploy the application for the third time. Hope someone can help soon!
Thanks. -
Failing to start any Application : Server.ServerDisabled
Hi,
after a network failure I had to re-join my sgd array (cause the array was automatically split). Now I am getting for every of my 1500 Application Objects the following error message on a users the webtop:
Error
Launch failed.
Application: .../_ens/o=TDS/ou=IT Outsourcing/cn=Standard Applications/cn=Testappl
Fault Code: Server.ServerDisabled
Fault String: Server is disabledI added several additional log entries to find some usefull hints solving this problem. But none of them seems to give me an additional hint to come closer to a solution.
tarantella config list --array-logfilter
array-logfilter: */*/*error:jserver_error.log,*/*/*error:jserver_error.jsl,*/*/fatalerror:.../_beans/com.sco.tta.server.log.ConsoleSink,*/*/warningerror:.../_beans/com.sco.tta.server.log.ConsoleSink,server/login/*:login.log,server/login/*:login.jsl,server/ldap/*:ldap.log,server/ldap/*:ldap.jsl,server/server/*:server.log,server/server/*:server.jsl,server/config/*:config.log,server/config/*:config.jsl,server/csh/*:csh.log,server/csh/*:csh.jsl,server/diskds/*:diskds.log,server/diskds/*:diskds.jsl,server/launch/*:launch.log,server/launch/*:launch.jsl,audit/session/*auditinfo:session.log,audit/session/*auditinfo:session.jslSome of the only informations are something like
2006/07/25 15:08:07.594 (pid 10920) server/csh/error #1153832887594
Sun Secure Global Desktop Software (4.2) ERROR:
Launch of .../_ens/o=TDS/ou=IT Outsourcing/cn=Standard Applications/cn=Testappl
failed for itosgdapp2p.hn.tds.de:1153830588403:4919276303576744687.
Launch will fail.
Retry the launch.or
2006/07/25 15:23:07.521 (pid 24992) server/launch/info #1153833787521
Received request by .../_service/sco/tta/ldapcache/uid=LWeberru,l=Neckarsulm,c=D
E,o=TDS
to launch .../_ens/o=TDS/ou=IT Outsourcing/cn=Standard Applications/cn=Testappl.
Do-not-redirect is false.
2006/07/25 15:23:07.550 (pid 24992) server/launch/info #1153833787550
Applying emulator session load balancing policy
[].I tried to make new applications, detaching and rejoining the array, and so on, bit nothing seems to work.
I am using the following configuration:
Sun Secure Global Desktop Software for SPARC Solaris 2.8+ (4.20.909)
Sun Secure Global Desktop Software Mainframe Connectivity Pack for SPARC Solaris 2.8+ (4.20.909)
Sun Secure Global Desktop Software AS/400 Connectivity Pack for SPARC Solaris 2.8+ (4.20.909)
Sun Secure Global Desktop Software Security Pack for SPARC Solaris 2.8+ (4.20.909)
Architecture code: spso0510
This host: SunOS itosgdapp2p 5.10 Generic_118833-02 sun4u sparc SUNW,Ultra-80Someone has an idea what i can do to get the applications to start again?
Regards
LukasHi,
I tried to test the applications using the native client, where i get the message:
No host supports the application type(scottawindowsapplication) you are trying to launch.Regards
Lukas -
Could not start Sun Java Application Server
Hi ,
I have been using JSC for a while, now and then it reports an error " could not start sun java application server...". Does any one know why it s not able to start java application server..
Before you say anything, I have tried
1. use netstat to find any port conflicts.
2. Tried to start application server manually
3. shut down and start studio creator and then try running the project
4. shut down and start PC
unfortunately none of them helped
Only reinstalling resolved the problem. But I cant keep reinstalling very often.
Does any one know the permanent solution for this problem.
Cheers
kushSometimes it appears this is a timeout issue because it's taking too long to come up. As Jonathan says, undeploy can help with this (along with his other suggestions).
How many deployed projects do you see (in the server navigator you can open up the deployed server and see what's out there)?
I periodically undeploy "junk" projects that I'm not really using because they slow down the server startup (same thing happens I believe for tomcat... when the server starts it has to load them all and it takes awhile). You can undeploy from within the server navigator by drilling into the server nav and right clicking on the deployed app and choosing undeploy... or you can use the server admin tool.
hth,
v -
The Sun Java Application Server 8.1 could not start anymore
Very incredible I was working fine from may days with Stydio Creator 2
but yesterday I run the project and it does not work anymore, please can you suggest something:
The Sun Java Application Server 8.1 could not start.
from the Output console:
C:\Sun\Creator2\SunAppServer8\bin\asadmin.bat start-domain --domaindir C:\Sun\Creator2\SunAppServer8\domains\ creator
Failed to start server localhost:4848
Deployment error: Failed to start server localhost:4848. See the server log file for details.
Exception=Deployment error: Failed to start server localhost:4848. See the server log file for details.
Deployment error: Failed to start server localhost:4848. See the server log file for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:198)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:75)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:234)
at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:242)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:125)
Caused by: Failed to start server localhost:4848
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:152)
... 10 more
and in the log file:
[#|2006-02-24T11:49:51.296+0100|WARNING|sun-appserver-pe8.1_02|
javax.enterprise.system.core|_ThreadID=25;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: [C4073]: A JMS destination limit was reached.
Too many Subscribers/Receivers for Queue :
temporary_destination://queue/192.168.0.159/3376/2 user=admin, broker=127.0.0.1:27676(2403)
at com.sun.enterprise.jms.JmsProviderLifecycle.onTermination(JmsProviderLifecycle.java:476)
at com.sun.enterprise.server.ApplicationServer.onTermination(ApplicationServer.java:454)
at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:42)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:1445)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:1434)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:443)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
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:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
thanksI just had the same problem this morning. I believe the app server starts and if you browser directly to your app you'd get it, but the connection between the appserver and the IDE is somehow lost. An easier solution than completely reinstalling for me was to delete the .Creator folder in my home directory (C;|Documents and Setting\<username>\.Creator) and restart Creator
-
Jump Start Kit application server failed to start
Hi,
My Jump Start Kit Application server is failing to start. The Error is as below
2012-10-22 11:58:18,076 FATAL [com.fatwire.logging.cs.db] - <Exception loading meta data for data sourcecsDataSource>
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (User not found: SA)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.fatwire.cs.core.db.DataSourceBackedPool.acquire(DataSourceBackedPool.java:47)
at COM.FutureTense.Servlet.JDBCConn.getMeta_trans(JDBCConn.java:188)
at COM.FutureTense.Servlet.JDBCConn.getMeta(JDBCConn.java:130)
at COM.FutureTense.Servlet.JDBCTable.<init>(JDBCTable.java:285)
at COM.FutureTense.Servlet.JDBCConn.GetTable(JDBCConn.java:1333)
at COM.FutureTense.Common.ftDBTable.getconn(ftDBTable.java:3899)
at COM.FutureTense.Common.ftDBTable.grab(ftDBTable.java:982)
at COM.FutureTense.Common.ftAppLogic.getEvent(ftAppLogic.java:2010)
at COM.FutureTense.Common.ftAppLogic.initEventEngine(ftAppLogic.java:3453)
at COM.FutureTense.Common.ftAppLogic.init(ftAppLogic.java:1939)
at COM.FutureTense.Common.ftAppLogic.init(ftAppLogic.java:1897)
at COM.FutureTense.Common.CatalogManager.execute(CatalogManager.java:321)
at COM.FutureTense.Servlet.FTServlet.execute(FTServlet.java:129)
at COM.FutureTense.Servlet.FTServlet.doGet(FTServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.cs.core.logging.context.filter.ContextHeaderFilter.doFilterWork(ContextHeaderFilter.java:37)
at com.fatwire.cs.core.logging.context.filter.RunOncePerRequestFilter.doFilter(RunOncePerRequestFilter.java:54)
at com.fatwire.cs.core.logging.context.filter.HttpFilter.doFilter(HttpFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:557)
at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: User not found: SA
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
... 39 more
2012-10-22 11:58:18,076 ERROR [com.fatwire.logging.cs.db] - <Exception getting database connection>
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (User not found: SA)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.fatwire.cs.core.db.DataSourceBackedPool.acquire(DataSourceBackedPool.java:47)
at COM.FutureTense.Servlet.JDBCTable.get_trans(JDBCTable.java:698)
at COM.FutureTense.Servlet.JDBCTable.get(JDBCTable.java:611)
at COM.FutureTense.Servlet.JDBCTable.<init>(JDBCTable.java:288)
at COM.FutureTense.Servlet.JDBCConn.GetTable(JDBCConn.java:1333)
at COM.FutureTense.Common.ftDBTable.getconn(ftDBTable.java:3899)
at COM.FutureTense.Common.ftDBTable.grab(ftDBTable.java:982)
at COM.FutureTense.Common.ftAppLogic.getEvent(ftAppLogic.java:2010)
at COM.FutureTense.Common.ftAppLogic.initEventEngine(ftAppLogic.java:3453)
at COM.FutureTense.Common.ftAppLogic.init(ftAppLogic.java:1939)
at COM.FutureTense.Common.ftAppLogic.init(ftAppLogic.java:1897)
at COM.FutureTense.Common.CatalogManager.execute(CatalogManager.java:321)
at COM.FutureTense.Servlet.FTServlet.execute(FTServlet.java:129)
at COM.FutureTense.Servlet.FTServlet.doGet(FTServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.cs.core.logging.context.filter.ContextHeaderFilter.doFilterWork(ContextHeaderFilter.java:37)
at com.fatwire.cs.core.logging.context.filter.RunOncePerRequestFilter.doFilter(RunOncePerRequestFilter.java:54)
at com.fatwire.cs.core.logging.context.filter.HttpFilter.doFilter(HttpFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:557)
at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: User not found: SA
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
... 39 more
2012-10-22 11:58:18,076 ERROR [com.fatwire.logging.cs] - <Exception processing CatalogManager request>
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (User not found: SA)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.fatwire.cs.core.db.DataSourceBackedPool.acquire(DataSourceBackedPool.java:47)
at COM.FutureTense.Servlet.JDBCConn.Ping_trans(JDBCConn.java:291)
at COM.FutureTense.Servlet.JDBCConn.Ping(JDBCConn.java:274)
at COM.FutureTense.Common.CatalogManager.execute(CatalogManager.java:1122)
at COM.FutureTense.Servlet.FTServlet.execute(FTServlet.java:129)
at COM.FutureTense.Servlet.FTServlet.doGet(FTServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.cs.core.logging.context.filter.ContextHeaderFilter.doFilterWork(ContextHeaderFilter.java:37)
at com.fatwire.cs.core.logging.context.filter.RunOncePerRequestFilter.doFilter(RunOncePerRequestFilter.java:54)
at com.fatwire.cs.core.logging.context.filter.HttpFilter.doFilter(HttpFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:557)
at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: User not found: SA
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
... 31 more
Can you please tell me why this error is coming and how to resolve it.The error got resolved..
The files in
App_Server\apache-tomcat-6.0.32\default\data\hypersonic
were corrupted hence the error.
Replaced them with the ones from a correct installation and voila! -
Sun Java Application Server 9 Start Up Woes
Hi,
I was asked to install the netbeans 5.5 IDE (which comes with Java Application Server 9 bundled with it) and basically learn how to develop using JMS. After installing everything and following the JavaEE tutorial, I began to set everything up. I get hung during the Sun Java Application Server 9 start up.
It attempts to bind to my host name. After a week of research as to the cause, i discovered that the problem is that the server gets my host name from DNS and uses that as its bind location. The software running at my place of business prevents me from making connections such as these with anything but localhost connections.
I descovered this when I read on here from another topic that i should try and start the server after disabling my network card. This method works in that the server starts up, no longer using my host name as the host but rather using localhost. Now this in no way fixes my problem.
I was wondering if there were any workarounds that would force the application server or netbeans or whatever to use localhost isntead of doing a host name lookup?
The error I got was a NoRouteToHostException, and when I disabled my network card that error went away, the error changed to UnknownHostException, but the server started up and I was then able to go to the admin page and deploy applications (but not run)
P.S. I was going to post the output of the server start ups, but the size is crazy long, if you have a way for me to remove the stack trace I would be glad to give it a try.
-SonOfThor
Message was edited by:
SonOfThor
Linux Fedora Core, by the way.I switched to ActiveMQ and it works perfectly.
The issue had to do with Netbeans, no matter how many config files i changed, always used my computername.host.com:8686 instead of localhost:8686.
ActiveMQ starts and runs beautifully because it binds to localhost:8686.
I dont know what the problem was, Ive read lots of solutions saying its firewall or a firewall like process. I'm running bare bones Linux Fedora Core with no extra programs. I insured my firewall was turned off before even posting this. I spoke with my IT guys and they said that the firewall thats set up here at work does not block port binds.
My conclusion: IDEs are more of a pain then they want you to believe, im going back to terminal commands. -
My sun java application server not run and give me error
hi master
sir i use
sun java system with studio creator but when i start deployment server
that give me this error
==================
The sun java system application server 8.2 could not start.
more information about the cause is in the server log file .
possible reasons include:
-Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
-Incorrect server configuration (domain.xml to be corrected muanually)
-Corrupted Deployed Application preventing the server to start.(this can be seen in the server.log file. in the case, domain.xml needs to be modified).
==========
this is my server.log file
=======
[#|2007-10-23T09:43:55.144+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T09:58:09.886+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T10:12:34.768+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T11:10:28.081+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T12:58:46.034+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
please how i start my application server
thank's
aamirPlease see the following FAQ:
Why doesn't application server Start.
http://developers.sun.com/jscreator/reference/faqs/technical/depsrvs/index.jsp -
Error starting the Application Server and Deployment Tool
After installing the iPlanet Aplication Server with sp3 I get the following
errors starting the Application Server and Deployment Tool.
iAS Application Server
================
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:46:49:8] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
error: could not get context
*** Errors in initialization from registry ***
Errors in initialization, exiting ...
iAS Deployment Tool
===============
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:23:40:7] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
Exception in thread "main" java.lang.NullPointerException
at com.kivasoft.util.Util.loadComponent(Unknown Source)
at
com.iplanet.ias.tools.buzz.ui.application.StartBuzz.initGDS(Unknown Source)
at com.iplanet.ias.tools.buzz.ui.application.StartBuzz.main(Unknown
Source)
Can anyone help me please!Hi,
Would be more helpful if you can mention, the O/S. Also, pls mention where
you are getting this error, at kjs or kxs, or, are you able to start the server
and at which specific instance do you encounter this.
Regards
Raj
"Antonio Casqueiro" wrote:
After installing the iPlanet Aplication Server with sp3 I get the following
errors starting the Application Server and Deployment Tool.
iAS Application Server
================
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:46:49:8] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
error: could not get context
*** Errors in initialization from registry ***
Errors in initialization, exiting ...
iAS Deployment Tool
===============
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:23:40:7] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
Exception in thread "main" java.lang.NullPointerException
at com.kivasoft.util.Util.loadComponent(Unknown Source)
at
com.iplanet.ias.tools.buzz.ui.application.StartBuzz.initGDS(Unknown Source)
at com.iplanet.ias.tools.buzz.ui.application.StartBuzz.main(Unknown
Source)
Can anyone help me please! -
Error starting the Application Server and Deployment Tool in Windows 2000
After installing the iPlanet Aplication Server with sp3 in Windows 2000 I
get the following
errors starting the Application Server and Deployment Tool.
iAS Application Server
================
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:46:49:8] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
error: could not get context
*** Errors in initialization from registry ***
Errors in initialization, exiting ...
iAS Deployment Tool
===============
GXBindInit: GXBindBasic failed
GXContextInit: GXBindInit failed 2
[26/Out/2001 17:23:40:7] error: ENGINE-context_init_failed: EngineClassSpace
ContextModule.createContextInit failed:
Exception in thread "main" java.lang.NullPointerException
at com.kivasoft.util.Util.loadComponent(Unknown Source)
at
com.iplanet.ias.tools.buzz.ui.application.StartBuzz.initGDS(Unknown Source)
at com.iplanet.ias.tools.buzz.ui.application.StartBuzz.main(Unknown
Source)
Can anyone help me please!Okay, pls check that you are logged in as administrator and installed and now you are logged in as administrator and registering the iAS server. Did you get any installation failures while installing and are you able to register the server using iASAT ?
-
Fail to search Oracle Application Server while installing EM Grid Control
Fail to search Oracle Application Server while installing EM Grid Control 10.2.0.2 on Windows XP. All the steps are successful except the last step failed.
I uninstalled the previous Oracle 10g database using the stops of the following link:
http://krsethur.wordpress.com/2006/06/13/uninstalling-oracle-10g-manually-from-windows-xp/
Now I install EM Grid Control with a new database.
I don't have any MetaLink account now.
The log massage from G:\OracleHomes\agent10g\cfgtoollogs\configToolFailedCommands
Command: oracle.sysman.emcp.agent.AgentPlugInThe log messages from C:\Program Files\Oracle\Inventory\logs\installActions2009-12-27_12-12-43...
Starting Agent
Command = oracle.sysman.emcp.agent.AgentPlugIn has failed
Exception : java.lang.Exception:
Management Agent Configuration Assistant is failed.
The following failed messages are recorded:
configureAgent: Search on a non-RAC system: Fail to search Oracle Application Server.
Info: Configuration Assistant "Agent Configuration Assistant" is fail.
*** Starting OUICA ***
Info: Created a new file G:\OracleHomes\agent10g\cfgtoollogs\configToolFailedCommands
Info: Since the option is to overwrite the existing G:\OracleHomes\agent10g\cfgtoollogs\
configToolFailedCommands file, backing it up
Info: The backed up file name is G:\OracleHomes\agent10g\cfgtoollogs\configToolFailed
Commands.bak
Warning: OUI-25031: Some Configuration Assistant is failed. We recommend you to retry
Configuration Assistant.
...I check all the related service and I can see all the related service are up except that the status of Application server is not running and the OracleCSService is in the starting status all the time.
G:\OracleHomes\oms10g>cd G:\OracleHomes\agent10g\BIN
G:\OracleHomes\agent10g\BIN>emctl status agent
Oracle Enterprise Manager 10g Release 10.2.0.2.0.
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.2.0
OMS Version : 10.2.0.2.0
Protocol Version : 10.2.0.2.0
Agent Home : G:\OracleHomes\agent10g
Agent binaries : G:\OracleHomes\agent10g
Agent Process ID : 5812
Agent URL : https://host1.localdomain:3872/emd/main/
Repository URL : https://HOST1:1159/em/upload
Started at : 2009-12-27 19:02:04
Started by user : SYSTEM
Last Reload : 2009-12-27 19:02:04
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 4
Size of XML files pending upload(MB) : 0.04
Available disk space on upload filesystem : 41.63%
Last successful heartbeat to OMS : 2009-12-27 19:02:25
Agent is Running and Ready
G:\OracleHomes\oms10g\BIN>emctl status oms
Oracle Enterprise Manager 10g Release 10.2.0.2.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Oracle Management Server is Up.
G:\OracleHomes\oms10g\BIN>emctl status iasconsole
Oracle Enterprise Manager 10g Release 10.2.0.2.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Oracle 10g Application Server Control is not running.Sorry, it's my mistake. what I am installing is Grid Control 10.2.0.2.
G:\OracleHomes\oms10g>cd G:\OracleHomes\agent10g\BIN
G:\OracleHomes\agent10g\BIN>emctl status agent
Oracle Enterprise Manager 10g Release 10.2.0.2.0.
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.2.0
OMS Version : 10.2.0.2.0
Protocol Version : 10.2.0.2.0
Agent Home : G:\OracleHomes\agent10g
Agent binaries : G:\OracleHomes\agent10g
Agent Process ID : 5812
Agent URL : https://host1.localdomain:3872/emd/main/
Repository URL : https://HOST1:1159/em/upload
Started at : 2009-12-27 19:02:04
Started by user : SYSTEM
Last Reload : 2009-12-27 19:02:04
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 4
Size of XML files pending upload(MB) : 0.04
Available disk space on upload filesystem : 41.63%
Last successful heartbeat to OMS : 2009-12-27 19:02:25
Agent is Running and Ready
G:\OracleHomes\oms10g\BIN>emctl status oms
Oracle Enterprise Manager 10g Release 10.2.0.2.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Oracle Management Server is Up.
G:\OracleHomes\oms10g\BIN>emctl status iasconsole
Oracle Enterprise Manager 10g Release 10.2.0.2.0
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Oracle 10g Application Server Control is not running.Edited by: junez on Dec 27, 2009 4:18 PM -
User Role problems in Sun Java Application Server Platform Edition 8
I am having two problems setting up user roles in Sun Java Application Server Platform Edition 8. At first, I thought that it was a problem with the higher level features that I was using, so I created a very simple example using the simplest authentication I can use, but the problem still occurs. I am using the file realm and configuring the users in the App Server Admin Console. I create 2 users in different roles. One user should have access, the other should not.
1) The first problem is that both users can access the page
2) The second problem is that the isUserInRole() method returns false for both users with the role that it should be authenticating against.
Here is a sample of my code:
Users Configured in Console:
username password roles
user1 ********** admin
user2 ********** noaccess
web.xml
<security-role>
<role-name>admin</role-name>
</security-role>
<security-constraint>
<web-resource-collection>
<web-resource-name>My Protected Area</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>admin</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>file</realm-name>
</login-config>
<servlet>
<servlet-name>
TestServlet
</servlet-name>
<servlet-class>
mypackage.TestServlet
</servlet-class>
<security-role-ref>
<role-name>admin</role-name>
<role-link>admin</role-link>
</security-role-ref>
</servlet>
<servlet-mapping>
<servlet-name>
TestServlet
</servlet-name>
<url-pattern>
/TestServlet
</url-pattern>
</servlet-mapping>
TestServlet.java:
out.println("admin role: " + request.isUserInRole("admin") + "<BR/>");
Thanks before hand for any responses.
- BrianHi Jeanfrancois,
Your suggestion has lead me to find my problem. There were actually three problems.
1) First, you suggestion to reorder my xml file did not cause any errors to occur. I got suspicious that my web.xml file was wrong. I looked at some sample web-xml files and found that I was missing the header as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'>
2) When I added this information, the deploy feature failed stating the my web.xml file was out of order. I fixed the ordering. It now deployed, but the security still wasn't working.
3) I then added the sun-web.xml file. This file was missing before hand as I thought it was unnessary. However, this file added the essential mapping from a role to a group. After adding this, it now started to work.
Thanks so much for you time and effort. You really did help me.
- Brian Blank -
ABAP Trial version u2013 starting the application server
Hi,
I have a problem starting the application server via the management console. After choosing action ->start I have to enter user and password. Do I have to create a new user password combination, use the OS password or try bcuser and minisap? None of these three options worked out. I always get the message 'Start failed: 2 Invalid Credentials'. Or went there something wrong during the installation?
Thanks for your help.
BirgitHey Birgit,
In my case I installed ABAP Trial version (also known as MiniSap) on my local machine (Windows).
When I turn on the machine, my Windows(OS) requires a User/Password (It was configured this way but it is possible you configure to not require a User/Password, it uses a default).
When I instaled the ABAP Trial version, I logged on with a User/Password with administrator rights (it is necessary for installation).
When, in the "Management Console", I start the ABAP (the "NSP" node), it asks me the user and password and I use the OS User/Password that I used to install ABAP Trial (above).
If you are doing the same I don't know why the message "Start failed: 2 Invalid Credentials".
Merry Christmas,
Edited by: Walmir Catunda on Dec 15, 2008 11:34 AM -
Java Application Server 8.2 startup problem
Hello,
I have installed j2ee SDK 1.4.03 on Windows. Then I started the Application
Server in the default domain1 by choosing in "Start default server".
Everything seems to be OK as I get message "Domain domain1 is ready to
receive client requests". I have a problem when I try to verify if the server is
running in the browser on http://localhost:8080/, the browser keeps tring
to open it but nothing is displayed. In the log I get this, which seems to me a bit
too short, as I saw the log of properly running server on another computer
(not everything may have been started). BTW I have got the same problem
with the Glassfish server. Can anyone help me please?
[#|2006-02-01T19:57:05.472+0000|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/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
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\jdk\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\Sun\AppServer\bin;;C:\jdk1.5.0_06\bin;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/AppServer/jdk/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2006-02-01T19:57:15.266+0000|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2006-02-01T19:57:15.266+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2006-02-01T19:57:18.390+0000|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-02-01T19:57:18.400+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-02-01T19:57:18.901+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-02-01T19:57:19.992+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2006-02-01T19:57:19.992+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2006-02-01T19:57:22.476+0000|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-02-01T19:57:22.837+0000|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-02-01T19:57:22.837+0000|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-02-01T19:57:24.519+0000|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]Are you sure that HTTP port used by this installation was actually 8080? It is the default value, but if that port is in use at installation time, alternative port will be assigned. Installer will show you the new value, but it is easy to miss if you are not looking very closely.
To find out which ports are actually being used check <installdir>domains/domain1/config/domain.xml file. -
Sun Java Application Server - Domain and Node agent stop automatically
Hi,
We have installed Sun Java Application server 8.1 in a local zone on Solaris 10. The installation was successful.
A default domain (domain1) was created. We have deployed a sample application too.
The problem is that the domain and node-agent stop automatically. And need to be restarted from asadmin start-domain command.
Not sure why this problem is occurring. One solution given in Sun Java System AS 8.1 EE Troubleshooting Guide was to add these 2 lines in the /etc/inittab file to restart the domain and node-agent whenever the system re-boots.
das:3:respawn:/opt/SUNWappserver/bin/asadmin start-domain user admin passwordfile /opt/SUNWappserver/password.txt domain1
das:3:respawn:/opt/SUNWappserver/bin/asadmin start-node-agent user admin passwordfile /opt/SUNWappserver/password.txt node-agent-name
Pls help me if I can change this inittab file from the local zone and if changing this file has any implications on the other zones on Solaris 10.
Else is there any other way to resolve this problem?
Any help would be highly appreciated.
Thankyou.One thing not clear from the post was,
* when it is going down automatically.
* Are you facing the same problem even after starting through the asadmin
* If so, Post the server.log from "domains/logs" during the starup.
If you want to bring it up with system reboot, You need to have a startup script for that in init.d and have the links to rc2/3.d.
Maybe you are looking for
-
I want to change fonts but get message "no available system font"
I am trying to edit a PDF flyer created by another party. Using Acrobat Pro on Mac OSX. I select "edit document text" and then try to delete or change the text and get the message. "all or part of the selection has no available system font You cann
-
Really? Why is this happening. Nothing is working. Keep getting error messages when I log into the app saying: "WARNING: No groups returned from Server. No devices or custom views will be visible" ... been getting this message now for over 2 hours.
-
Numbers crashes when scrolling
Since updating to IOS 8, including all subsequent updates released for IOS 8, Numbers has exhibited crashing when scrolling horizontally or vertically when the spreadsheet exceeds the screen boundaries. I have erased Numbers from the iPad Air (sympt
-
Hi All, I would like to write some code in Calculated KeyFigure Formula, I have checked the forums. pls donot include SAP Help URL's. Pls explain, if it is possible to write the code... Best Regards, Pandu.
-
I checked the value of a gift card and it asked me to redeem. I did so, and now show $10 credit to my acct. But when I go to purchase a $9.99 album, it goes directly to my CC info, and the "Redeem gift card" section at checkout says my card has alr