App server 8.1 could not start

Encounter App server 8.1 could not start
Reason by bugger :
Port Conflict
Incorrect server config.
Corrupt depoly app.
Anyone could make to varify the actual cause. I using MS XP SP2, Norton Interent security and connect to internet while depoly to run program encountered such error.
Thing being try :
use netstat has a list of port been use, which is the cause ?
domain.xml server config. file need to be change but which one ?
or could it be corrupted depoly appl. prevent start up ?? clean and redepoly has done.
Thks
ctbeans

Hi,
Please go through the FAQ titled "Why doesn't Application Server start up" which is at :http://developers.sun.com/prodtech/javatools/jscreator/reference/faqs/technical/depsrvs/
Hope thsi helps.
RK.

Similar Messages

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)
thanks

I 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

Portal EHP1 SP07 Patch causes app server jcontrol.exe to not start.....

I just finished patching our test portal system.
The database\message server which also has an app server on it starts up and runs just fine. The problem we are having is the second app server which is on a different windows host will not start (jcontrol.exe stays in a gray status).
Here is the developer trace errors for the second app server:
[Thr 5136] Wed Dec 08 06:56:19 2010
[Thr 5136] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c   1642]
[Thr 5136] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
[Thr 5136] JControlCloseProgram: started (exitcode = 66)
[Thr 5136] JControlCloseProgram: good bye... (exitcode = 66)
Here is jvm_bootstrap.out log file located at \usr\sap\xxx\j00\work:
Bootstrap MODE:
<INSTANCE GLOBALS>
determined by parameter [ID0067689].
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
     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:331)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
     at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:60)
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
     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:331)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.microsoft.sqlserver.jdbc.SQLServerDriver.
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)
     ... 14 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
     at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:303)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
     ... 17 more
[Bootstrap module]> Problem occurred while performing synchronization.
Any ideas?
Thank you,
Neil

Neil,
Thanks for your persistence and for reporting how you eventually solved it. I had precisely the same problem after upgrading our production Portal from 7.00 to 7.01. I didn't have problems in dev or test, because we don't have multiple app servers in those environments, just a central instance. Now it's GoLive weekend and I've been pulling out my hair trying to get the app servers to work after the EHPI process is done. I had to do just what you suggested, about editing the bootstrap configuration manually, as changes in the config tool didn't seem to have any effect on jcontrol. I got that solved using your solution, but that led to nearly the same problem occurring for the individual dispatcher and server nodes, once jcontrol was started. It took a while and lot of experimenting, but eventually I figured out that they were pulling the wrong jdbc driver from their individual configuration.manager properties (accessed via config tool). The central instance was correctly updated by the EHPI program, but not the app servers. Annoying!
Makes me wonder if I was supposed to leave the app servers running during the 'downtime' phase of the EHPI. The manual, and the EHPI program, tell you at the start of the phase "shut down all dialog instances now", but then there's no indication of how these significant changes are supposed to be replicated to the app servers. Several times I nearly escalated to a Very High priority Customer Message, but I kept unraveling the thread until I solved it, and your message here was the clue that put me on the right track.
Thanks,
Matt

Could not start Service Broker for database id

I am getting this message in the SQL Server error log:
Could not start Service Broker for database id: 10. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
It appears even when the broker is disabled on the database. How can I eliminate this error?
Thanks!

In that case you're gonna have to contact Microsoft support, perhaps provide a copy of the database.
Typical reason why a broker cannot be started is that another database with the same service_broker_guid already exists in the instance (result of a file copy/attach or a double restore). However, in that case a message is given that states the reason.

Sun App Server 8.1 and 8.2 could not start

Hi friends, thank for various suggestions. pls i'm having problem with Sun App Server 8.1 and 8.2. I installed Portal 7 on Red Hat Enterprise Linux 3 and also Sun Portal 6 on Suse Linux 9. The problem is that App server keep giving Login exception after using them for a while. The details is given below:
after typing ./asadmin start-domain --user admin domain1. Instead of it to give me the password prompt, it threw the following exception:
INFO: SEC5046: Audit: Authentication refused for [admin]
Login Failed javax.security. auth.login.LoginException: Failed file for login admin
CL1156 could not start the domain domain1.
I always login to the O/S as root.
Any suggestion will be highly appreciated. Thanks

Thanks very much kedar.mhaswade for your suggestions.
I do not have a regular access to the Internet, I
would have gotten back earlier than this, so i'm
sorry. Anyway, i checked the content of
~/.asadminprefs and the password is not the same with
the one i'm using. I found the default password
supplied by Sun but I don't think this could be the
problem. I'm actually using the App server that is
bundled with Sun Portal 6 and 7 and so i supplied my
own password during installation and i've logged in
several times after installation. It just failed in
one of those logins and had stopped working since. I
always encountered the same problem either when using
Sun Portal 7 or 6 on Red Hat ES 3 and Suse 9
respectively.
I'm posting the content of admin-keyfile as you
requested:
admin;{SSHA}Qf/m4KEBDPojsP1mkjywE5XZA6SPh7i8WQmV/A==;a
sadmin
# Domain User and Password - Do Not Delete Entry
Above
So i will so much appreciate your help and i wouldn't
mind if you could send me your phone number. Thanks.Hi tolulike,
Even if you supplied your own password, we have this developer friendly
feature that has side effects that are at times hard to diagnose. Can you
please
- rename the .asadminprefs file and make sure that there is no .asadminprefs file in your home directory?
- attempt to start the domain.
You should be prompted for the password.
The idea is that when you've got that file and that entry AS_ADMIN_PASSWORD in your home directory, asadmin will read it
from there and you land in this (unfortunate) situation.
Obviously doing this might have some side effects with other domains. This
is because for all domains, asadmin reads this file as a last resort. So,
it might so happen that this file is actually required for functioning of your
other domains.
But now you know when this file is used, so there is no mystery (hopefully).
Let me know if this works.
Thank you.
Kedar

Could not start the app due to a configuration problem - Launchpad issue

Hi,
When I try to launch a custom app from Fiori Launchpad I get an error could not start app due to configuration problem. Error 500- Internal Server Error.
App works correctly when I try to execute via URL http://XXX/sap/bc/ui5_ui5/sap/zmyfioriui5_v11.
Screenshot of Chrome debugging and lpd_cust attached.
It seems problem with ResolveLink but unable to conclude.
Any Suggestion how to proceed.
Thanks,
Mayank

Hi Mayank,
Few modifications :
For additional information field : ".component" at the end is not required.
Only keep : SAPUI5.Component=sap.ui.demo.myFiori
Check this screenshot :
Also, please don't keep Semantic object name and application alias as same name i.e. ymyfioriui5_v11. Its very confusing.
If above doesn't solve, please confirm below :
ZXXXLPD is your launchpad role in LPD_CUST tcode.
Please use TRANSACTIONAL instead of transactional (might be case sensitive)
Show your semantic object "ymyfioriui5_v11" created in /UI2/SEMOBJ
Regards,
Tejas

Error in Fiori Launchpad "could not start the app due..."

Hello everyone,
I am having a previously unseen (well, at least for me) error which raises on a click on the tile "Track Purchase Orders" on the SAP Fiori Launchpad:
"Could not start the app due to an internal error" (see the screenshot attached)
I haven't found any help on this error on Google and SAP portals.
The other applications work fine. So did this one before the implementation of SAP_UI 740 SP09 (before that it was SAP_UI 740 SP08). We applied all the notes specified in this post http://scn.sap.com/docs/DOC-56967
Components needed for Track Purchase Orders are patched to their maximum levels (UIX01EAP 100 SP03 and SRA020 600 SP05). OData and UI5 services are activated.
Plus, this error doesn't appear in the Gateway error logs (transaction /iwfnd/error_log) so troubleshooting is difficult.
The issue is systematically reproducible and has been reproduced on several computers.
Thanks a lot if you have any insight about this issue!
Best regards,
Guillaume

Thank you for replying.
I have inspected the element and clicked on the tile. The network tab is below:
The status seems OK.
The response for ResolveLink:
{"d":{"results":[{"__metadata":{"id":"http://<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","uri":"<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","type":"INTEROP.NavTarget"},"id":"PurchaseOrder-track~68","shellType":"FLP","postParameters":"","text":"Track Purchase Order","applicationData":"SAPUI5.Component=ui.s2p.mm.purord.tracking","applicationAlias":"TrackPurchaseOrder","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_purord_tpo"}]}}
I'm surprised that gbapp_poapproval and sra001 OData services are called here (with an intriguing ";mo")... We have found these errors in our /iwfnd/error_log screen after the SAP_UI 740 SP09 patch. Seeing this, we have installed GBAPP002 600 SP6 and SRA001 600 SP4 and activated the OData services but have not tried to use the corresponding apps (meaning that we have not done any other app implementation tasks because we don't really intend to for the moment).
In case the two problems are related, these are the responses to these requests:
For gbapp_poapproval request
{"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB173F121613F0E1008000A87C135A","timestamp":"20140814124456.5404250","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
For gbapp_prapproval request
{"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0B1112160FA0E1008000A87C135A","timestamp":"20140814124456.4449070","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
For sra001_pcapproval request
{"error":{"code":"SRA001_CMN_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0E4512161140E1008000A87C135A","timestamp":"20140814124456.3244590","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"SRA001_CMN_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
Regards,
Guillaume

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
kush

Sometimes 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

CLI156 Could not start the domain domain1. in Application Server 8

Hi everybody!
Sorry to post this message here at Application Server 7. But I'm using the Application Server 8 along with NetBeans 4.1 early access. Suddenly, the application server stop working on my computer and now, every time I try to start the default server, I get this error message:
CLI156 Could not start the domain domain1.
With the following log:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-12-28T22:46:39.359+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2004-12-28T22:46:42.296+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-12-28T22:46:42.625+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded).|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
log4j:WARN Please initialize the log4j system properly.|#]
[#|2004-12-28T22:46:47.687+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-12-28T22:46:47.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-12-28T22:46:47.750+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-12-28T22:46:53.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-12-28T22:46:56.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-12-28T22:46:57.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-12-28T22:46:59.328+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-12-28T22:47:00.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-12-28T22:47:02.390+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-12-28T22:47:04.640+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
CharScanner; panic: ClassNotFoundException: com.sun.jdo.spi.persistence.support.ejb.ejbqlc.EJBQLLexer$EJBQLToken|#]
I'm running this application server on Windows XP, like I said, I was working with NetBeans and suddenly, the AS stop working.. I did not delete anything, I did not move anything either.
Please, does any of you have any ideas of how can I fix this issue?
Best regards!

You may try this soultion. I fixed this in my Window 2000 machine(Application Server 8) by:
1. Edit domain.xml($DEFAULT_DOAMIN/config)
2. Update the port="4702" for http-listener tag, and change to something else(e.g. 4802).
3. Save it
4. Make sure the Application Server is shut down.
5. Start the Application Server.
Hope it helps!
Ming-wei

Jdeveloper :Server Instance IntegratedWebLogicServer could not be started

hi ...
i used jdeveloper 11.1.1.3.0. i built a adf web application and when i run JSF pages i faced the following error:
starting weblogic with Java version:
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Duser.timezone="+06:00" -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\IABUZA~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<Jul 31, 2010 10:46:58 AM GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
<Jul 31, 2010 10:46:59 AM GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Jul 31, 2010 10:46:59 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 31, 2010 10:46:59 AM GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jul 31, 2010 10:46:59 AM GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Documents and Settings\iabuzayed\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jul 31, 2010 10:46:59 AM GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Documents and Settings\iabuzayed\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00057. Log messages will continue to be logged in C:\Documents and Settings\iabuzayed\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<Jul 31, 2010 10:46:59 AM GMT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Documents and Settings\iabuzayed\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<Jul 31, 2010 10:47:02 AM GMT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jul 31, 2010 10:47:10 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jul 31, 2010 10:47:10 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 31, 2010 10:47:28 AM GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
*weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected.*
     at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:107)
     at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
     at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
     at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:118)
     at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:91)
     at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:128)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Jul 31, 2010 10:47:28 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 31, 2010 10:47:28 AM GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 31, 2010 10:47:29 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Process exited.
and in masseage window:
[Starting Server Instance IntegratedWebLogicServer]
#### Server Instance IntegratedWebLogicServer could not be started: Server Instance was terminated

Found the issue.... I have different root cause for this issue..... I have installed 2 Jdev softwarres (9G & 11G) in my machine and I have set the JDEV_USER_HOME as environment variable for 9G version. When I remove this environment variable then the page executed perfectly with no issues.
-

WLS 9.2: MigrationException: Could not start JTAMT on local server

I have configured a two machine WLS 9.2 Cluster with two Managed Servers.
          When I try to start the Managed Server through the Node Manager from Admin
          Server's WLS Console, it fails with the following error (
          actually both Managed Servers fail with the same error):
          weblogic.cluster.migration.MigrationException: Could not start JTAMT on
          local server because it could not be deactivated on the current host.
          at
          weblogic.transaction.internal.TransactionRecoveryService.deployAllTransactionRecoveryServices(TransactionRecoveryService.java:400)
          at
          weblogic.transaction.internal.TransactionRecoveryService.resume(TransactionRecoveryService.java:170)
          at
          weblogic.transaction.internal.TransactionRecoveryService.start(TransactionRecoveryService.java:181)
          at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
          This message resides in file:
          bea920\weblogic92\common\nodemanager\servers\MANAGED-SERVER1\logs\MANAGED-SERVER1.log
          The WLS installation was done including the Node Manager Service.
          Is this error message familiar at all and what could be done to fix it?
          These Managed Servers run on Win2000 and Win2003 respectively. Should I do
          something to the OS (Enable XA Txs in Control Panel/MSDTC)?

Did you start AdminServer before try to start MANAGED-SERVER1?
          Did you ever migrate Transaction Recovery Service of MANAGED-SERVER1 to other servers?
          If the problem still exist, you can enable the debug option "DebugJTAMigration" and post the stack trace.

The Sun Java System Application Server could not start

Hello All,
I downloaded the Java Pet Store example from sun's website and followed the instructions for installation. After successful installation, I tried to deploy the project and gave the following error
C:\Documents and Settings\sina\My Documents\Projects\services\nbproject\build-impl.xml:194: 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.
BUILD FAILED (total time: 5 minutes 20 seconds)
The link above points to the following line in the build-impl.xml file
<nbdeploy debugmode="false" forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" clientModuleUri="${client.module.uri}"/>
Can any one help whats wrong.An early response will be highly appreciated.
Kind Regards.
Hasnain Javed.

Hi,
Maybe you already got this fix but here is a suggestion, a snippet from the readme index,html of the petstore download
# Start the Sun Java System Application Server and the JavaDB database. To do so, open a command prompt and change directory to <javaeesdk.home>/bin and issue the following commands:
asadmin start-database
asadmin start-domain
# Change directory to <petstore.home> and enter the following commands
ant setup
ant run
This will setup, build and deploy the petstore on the application server, and then launch the application homepage in your default browser.
The "ant setup" that you run from <petstore.home> (petstore.home is the directory where petstore is installed or where you unzipped it) will populate the database wth data and setup the proper database tables etc that are used by the application.
hth,
Sean

Sun Java System Application Server could not start

Hi
I have installed JDK1.5 Update1 + netbeans 5.5 with the JBOSS bundle and added the Sun Java System Application Server 9.1.02.
I am creating the EJB-JMS application described at
http://www.netbeans.org/kb/55/ejb30.html
All the steps are followed properly, but while running the project i get the 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.
D:\MyNBProjects\EJBAPP1\nbproject\build-impl.xml:183: 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.
BUILD FAILED (total time: 5 minutes 3 seconds)

Hi Roman,
Sorry for the long wait....
In the mean time I have downloaded NB6.1 (final Release) and JDK 1.6.0_04,added the sjsas-9_1_02 to NB6.1, all are in D:\javak (where previous setup of NB5.5 and jdk1.5 and SJSAS-9_1_02 is AS IS in D:\java)
Current Scenario:
Product Version: NetBeans IDE 6.1 (Build 200805300101)
Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: D:\Documents and Settings\kedar\.netbeans\6.1
Now, when i try to Run the SAME code i get the following error:
Created dir: D:\ProjectsNB\EJBAPP1\dist
Building jar: D:\ProjectsNB\EJBAPP1\dist\EJBAPP1.ear
post-dist:
dist:
pre-run-deploy:
Initial deploying EJBAPP1 to D:\ProjectsNB\EJBAPP1\dist\gfdeploy
Error during incremental deploy: java.lang.NullPointerException
Start registering the project's server resources
Finished registering server resources
java.lang.NullPointerException
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.getFileArchive(DirectoryDeploymentFacility.java:264)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:168)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.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)
java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.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)
Deployment error:
cannot find FileArchive class...
See the server log for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:166)
at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor112.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: java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:194)
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
... 16 more
Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
... 20 more
BUILD FAILED (total time: 9 seconds)
Thanks,
Kedar.

Oracle APP'S Installations Context Value Management Could not started

oracle APP'S Installations Context Value Management Could not started
how it is started

Fadi, Context Value Management runs during Rapid Install or AutoConfig to make sure the context file is in good order. If it fails at the time of the installation, then most probably you have missing components at the OS level.

Wndows could not start the SQL Server (MSSQLSERVER) service on Local computer

I have 2 instance of SQL Server in same server. A is installed first and B next.
Somehow A cannot start at all when I try to start from Windows Services.
B can be started normally.
A worked normally week ago. There has been only one thing what I may have to server since that.
I have installed MondoDB. Currently MondoDB it is stopped.
windows could not start the SQL Server (MSSQLSERVER) service on Local computer
Error 31: A device attached to the system is not functioning.
Kenny_I

I don't see anything special in event logs.
Data file of both SQL Server instance are located on same C drive of same server.
Kenny_I
Hello Kenny,
The main issue is not related to SQL server .SQL is at receiving end its hardware or the cables ( not sure which one) are the one causing issue.
I serached
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/111da2ae-0a86-41a5-ba03-7d1c0cc91ea9/windows-error-code-31a-device-attached-to-the-system-is-not-functioning-properly?forum=wdk
http://www.chicagotech.net/netforums/viewtopic.php?f=1&t=6467
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

App server 8.1 could not start

Similar Messages

Maybe you are looking for