SUN TEAM: PLEASE GIVE US A DECENT APP SERVER!
Sun Team,
I am still persevering with JSC2 due to functionality. However my patience is really wearing thin with the app server. How many times in a sesion do I have kill it !! at least twice and hour. I have a top end PC and still it doesn't play ball.
Any chance of giving us tomcat or something that works?
I use both Eclipse and JSC2, and Eclipse(with another app server) has never given me a problem.
I am very, very frustrated with JSC2.
Regards,
LOTI
All I want is the ability to do at least one hours piece of work without having to kill the appserver and Creator. I don't think it is asking too much.
Coming from a background over the last 10 years of using GUI RAD tools, I expected too much from JSC when it was launched. Although SUN did hype it as the best thing since sliced bread!! Time has shown a different story.
It was very niave of me to think JSC could achieve the same of ease of use when putting together a web app. I have championed this product up until now and other of my "low level hmtl" colleagues have expressed an interest. They would laugh if they started using JSC. It is simply not commerical or professional standard as compared to Eclipse, etc.
Until the pefromance issues of JSC are sorted out, I will remain unconvinced about the products viability in the "real life" world.
And before anybody gets on a rant, I am trying to write a fairly sized commercial project of which I am getting well paid. Hence the frustration. This is not some novice putting together a hello world.
Regards,
LOTI
Similar Messages
-
Sun Team: Please help me regarding the login action previously i posted
Hi sun team i have posted one thread recently. Please verify my code and guide me whether it is correct or not. And if any changes needed Please help me out regarding this.
http://forum.java.sun.com/thread.jspa?threadID=5118906&tstart=0
Thank You in AdvanceWe do have a sample app that demos this scenario.
Please check out:
http://developers.sun.com/prodtech/javatools/jscreator/reference/code/sampleapps/index.jsp
Databases: Two Page Create, Retrieve, Update, and Delete (CRUD) Database Operations with Table Display
Two Page CRUD with Table Display is an application that demonstrates how to perform create, read, update, and delete operations on a cached rowset data provider. The data provider is bound to a JavaServer Faces table component. Rather than having functionality confined to one page, this application has two additional pages, one for creating a trip and another for updating a trip.
http://developers.sun.com/prodtech/javatools/jscreator/reference/code/sampleapps/2/TwoPageCrudTable.zip
http://developers.sun.com/prodtech/javatools/jscreator/reference/code/sampleapps/2/2update1/TwoPageCrudTable.zip
Hope this helps,
Sakthi -
Problem with Java System Application Server *(Sun one 8 or J2EE 1.4 app server)
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.VeerendraM.S. Veerendra-
This is a known incompatibility, described at:
http://support.solarmetric.com/Ticket/Display.html?id=14082
Can you try the workarounds listed at:
http://forum.java.sun.com/thread.jsp?forum=136&thread=499803&tstart=0&trange=15
and let us know if it works?
In article <[email protected]>, veerendra wrote:
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Application designer connection to App Server
Hii,
I have a very basic level doubt, we all know that App Designer is 2 tier application/editor. But I observed lot of times, if I shutdown App server and try to connect through App designer, I get some debug error.Please can anybody tell me App server process connectivity with App Desigenr
Thanks in AdvanceThanks a lot Ajit and Nicolos.. Please find below error message
"Debugging disabled.Communication failure during rec(): WSAECONNRESET(10054) connection reset by peer
(143,41)"
How I am getting this error:
After login in App designer (in 2 tier mode), when I am shutting down App server (normal mode), I am getting this error only one time.
So my confusion here is how App designer debugging feature depends on App server?
Thanks -
Feature request: please give the ability to close all background apps at once!?
Hello. Please oh please give us the ability to close all open/running apps with one click or swipe. I, like many users, like to close running apps (much like on my computer) to keep my ipad/iPhone running fast. I know you guys say that background apps are put on pause and don't slow things down but that is simply not the case in real world usage. All the time my iPhone or iPad becomes sluggish and if I swipe 30 times to close all the apps the sluggishness goes away. I like the simple and easy to use ios, but a little more control for the user would be very beneficial. This, I would guess, is one of the main reasons one would get an android device instead, because they require for fine tune control. Giving us this feature, amoung a few others, would be a win win. The end user get more what they need, and apple steals away (or keeps) more loyal apple buyers.
Send your suggestion to Apple at http://www.apple.com/feedback/ipad.html
This is a user to user technical help forum. You aren't talking to Apple here. -
how to register a new responsibility in apps through backend. please give me the full details about it
Hi,
From backend you can add a responsibility to a user using FND_USER_PKG package, and there are so many hit in the google. Let me point out 1:
http://manoharbabuapps.blogspot.com/2013/08/how-to-add-responsibility-from-back-end.html
I personally dont know of any API where you can create a responsibility from backend, but from front end you can create. Steps detailed in following link:
Oracle Applications: creating responsibility in oracle apps R12
Thanks &
Best Regards,
Asif -
please give this awsome app more by providing features::
1. thumbnails for pages ,
2. ability to annotaions( highlighter and underliner) to remain enabled once selected ( because many times it becomes hectic to select again and again the same annotaion when selecting multiple words in a single page).
thanks .. hope this will be soon adapted withplease give this awsome app more by providing features::
1. thumbnails for pages ,
2. ability to annotaions( highlighter and underliner) to remain enabled once selected ( because many times it becomes hectic to select again and again the same annotaion when selecting multiple words in a single page).
thanks .. hope this will be soon adapted with -
I couldn't buy app from my credit card...please give me the solution, I couldn't buy app from my credit card...please give me the solution
Accepted forms of payment > http://support.apple.com/kb/HT5552
Changing Account Information > http://support.apple.com/kb/HT1918
Jinnah1951 wrote:
I couldn't buy app from my credit card..
If necessary... Contact iTunes Customer Service and request assistance
Use this Link > Apple Support iTunes Store Contact -
some apps on my macbook pro will not open,,,they bouce a few times and disappear. would someone please give me a straightforward answer on why this might be haappening(started after updates)) please?
Yay! Solved my own question; just did a hard shutdown, worked like a charm! Funny, didn't before. But who am I to question salvation?
-
I am planing to do ORACLE APPS please give me u r suggesions.
Hi,
I am java developer having one year experience and interested in Oracle.
I am planing to do ORACLE APPS please give me u r suggesions.
which one is better oracle apps technical or functional.
venkyCheck the below thread
Which path Do I need to follow in order to learn E-Business?
Sam
http://appstech-sam.blogspot.com -
Can't execute web app from NetBeans 3.6 with Sun Java App Server 8
Hi there,
I'm tyring to execute a java web application called myfirstjsp.
In directory ...\myfirstsjp I've got:
- index.jsp
- WEB-INF dir
- META-INF dir.
I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I checked port conflicts but none found.
The other two options don't give me a place to start (I don't know what to do with domain.xml)
I'm working with:
- Windows XP Pro
- J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
- Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
- Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
My PC has the following environment variables:
PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
By looking at the Sun App Server log file, I discovered that the log outputs of
- Start Default Server (a link in the folder created by the installation of Sun App Server)
- and trying to execute myfirstjsp from NetBeans through Sun App Server
are very similar.
Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are: |#]
[#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.ejb.codegen.JavaCompilerException: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
... 45 more
|#]
[#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
.|#]
[#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
[#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
Many thanks,
MiguelI seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
This is the Exception:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
[#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/ -
Sun 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. ThanksThanks 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 -
Migrating from Iplanet Application Server 6.0 to SUN ONE App Server 7.0
Hi,
I have an Iplanet App Server 6.0 and Iplanet web server 6.0 I would like to migrate to SUN ONE Appserver 7.0 .
If I am migrating,then can I fit the existing web server(Iplanet 6.0) into SUN ONE or not.
Also I want the migrations cost in detail.Please refer to the following url:
http://www.sun.com/migration/sunonetools.html
This should give u a head start on what needs to be done and how,. WIth respect to webserver , i guess you can use it or leave it depending on the architecture you require to deploy your solution.
Hope this helps ! -
Migration of j2ee app from Sun one App Server 6.0 to Sun one 6.5 Server
Hi all,
Currently I am involved in "J2EE" ear (webapps) migration from Sun One 6.0 to Sun One 6.5 Application Server on solaris os.Since the version and functionlity itself is major change in Sun One Server, my team had decided to build the source file and decided to port to Sun one 6.5 App Server.On doing build and compiling all source files, EJB compiler is failing on Sun one server 6.5.
Our findings on migration was as follows:
Sun one server 6.0 and its EJB compiler internally uses "kfcjdk11.jar" which is the base library to generate ejbs for "Enterprise Archive or ear file " of the application.Hence our application is suceessfully getting compiled and built on Sun one server 6.0 and running pretty fine.
However, "kfcjdk11.jar" still present in Sun One 6.5 server but its not been referred by SUN One 6.5 EJB compiler.So any successfully ear file deployed on 6.0 App Server, can be deployed on Sun One server 6.5. But to test applications/product's cycle, ear file deployed on SUN one 6.5 throws runtime errors and white screen is displayed to the user.
I had already included kfcjdk11.jar file into classpath, still its failing to compile the files.
The one of the error description is as follows:
[exec] iPlanet Enterprise Java Beans(tm) Compiler (version 6.5)
[exec]
[exec] Unexpected compilation Error:
[exec]
[exec] ejb_fac_com_server_framework_ejb_ChannelManagerBean.java:9: Superclass com.kivasoft.eb.EBHomeFactoryBase of class com.server.framework.ejb.ejb_fac_com_server_framework_ejb_ChannelManagerBean not found.
[exec] extends com.kivasoft.eb.EBHomeFactoryBase
[exec] ^
[exec] ejb_home_com_server_framework_ejb_ChannelManagerBean.java:8: Superclass com.kivasoft.eb.EBHomeBase of class com.server.framework.ejb.ejb_home_com_server_framework_ejb_ChannelManagerBean not found.
[exec] public class ejb_home_com_server_framework_ejb_ChannelManagerBean extends com.kivasoft.eb.EBHomeBase implements com.server.framework.ejb.IChannelManagerHome
[exec] ^
[exec] ejb_kcp_skel_IChannelManagerHome.java:9: Superclass com.kivasoft.ebfp.EBKCPSkelBase of class com.server.framework.ejb.ejb_kcp_skel_IChannelManagerHome not found.
[exec] extends com.kivasoft.ebfp.EBKCPSkelBase
[exec] ^
[exec] ejb_stub_IChannelManagerHome.java:9: Superclass com.kivasoft.eb.EBStubBase of class com.server.framework.ejb.ejb_stub_IChannelManagerHome not found.
[exec] extends com.kivasoft.eb.EBStubBase
[exec] ^
[exec] ejb_kcp_stub_IChannelManagerHome.java:9: Superclass com.kivasoft.ebfp.EBKCPStubBase of class com.server.framework.ejb.ejb_kcp_stub_IChannelManagerHome not found.
[exec] extends com.kivasoft.ebfp.EBKCPStubBase
[exec] ^
[exec] ejb_stub_IChannelManager.java:9: Superclass com.kivasoft.eb.EBStubBase of class com.server.framework.ejb.ejb_stub_IChannelManager not found.
[exec] extends com.kivasoft.eb.EBStubBase
[exec] ^
[exec] ejb_kcp_stub_IChannelManager.java:9: Superclass com.kivasoft.ebfp.EBKCPStubBase of class com.server.framework.ejb.ejb_kcp_stub_IChannelManager not found.
[exec] extends com.kivasoft.ebfp.EBKCPStubBase
[exec] ^
[exec] ejb_skel_com_server_framework_ejb_ChannelManagerBean.java:7: Package com.iplanet.ias.tools.monitor not found in import.
[exec] import com.iplanet.ias.tools.monitor.*;
[exec] ^
[exec] ejb_skel_com_server_framework_ejb_ChannelManagerBean.java:11: Superclass com.kivasoft.eb.EBSkelDelegate of class com.server.framework.ejb.ejb_skel_com_server_framework_ejb_ChannelManagerBean not found.
[exec] extends com.kivasoft.eb.EBSkelDelegate
[exec] ^
[exec] ejb_kcp_skel_IChannelManager.java:9: Superclass com.kivasoft.ebfp.EBKCPSkelBase of class com.server.framework.ejb.ejb_kcp_skel_IChannelManager not found.
[exec] extends com.kivasoft.ebfp.EBKCPSkelBase
[exec] ^
[exec] 10 errors
[exec]
[exec] Result: 255
Please guide us or suggest us to migrate our application to Sun one 6.5.
Thanks in advance,Hi,
web applciation uses some of platform specific API which are not portable to App server 7.0 like uda.framework etc.
So to streamline process we are migrating applcaition to 6.5 server and also planning to rewrite whole archietecture to port it to another app server.
Thanks, -
Sun One App Server - Oracle Database 10g
Hi to all:
I�m developing a web application that uses an Oracle 10g database and a I want to use Sun One Application Server 7, the problem that I have is when I have been deployed the war file into the server and acces to my application, specifically when I try to acces a JSP that extracts data from database, I don't see anything of the information that I need, that's not the problem, the problem is that in the server console appear a message indicating that an SQLException occour and the message is "No suitable driver".
I test my methods before deploy the war file and the connection and data extraction are correct, I don't know if the version of the JDBC driver for the connection to Oracle Database 10g is incompatible or if it's impossible to use Sun One App Server 7 with a connection with Oracle 10g.
I tried with other web servers like Tomcat 5.0 and Sun Application Server 9 and the connection it's perfect.
Could somebody give some ideas or orientation please?????, im student, all help will be appreciated, thanks!!!Rahul,
Yes there is an Enterprise Edition in the works. It will address the load balancing and fail over needs for deployments. More details are available here: http://wwws.sun.com/software/products/appsrvr_ee/home_appsrvr_ee.html
We will also be releasing more information in the October and November.
Cheers,
Stefan Bolka
Product Line Manager
Sun ONE Application Server Enterprise Edition
Maybe you are looking for
-
Firefox crashes when I try to start it up
<blockquote>Locking duplicate thread.<br> Please continue here: [[/questions/897418]]</blockquote> '''''''OOPS! Sent wrong crash report ID below is the correct one'''. ''''FF 8 was working for a few days after I upgraded to it and then it crashed and
-
How to display the image which in KM folder using url iview
Hi Friends How to display the image, which is under KM folder structur using the url iview. i trying using url iview url as \document\testfolder\abc.jpg as url for the iview. but its now working .. so please help me how to slove this problem If is n
-
HI Everyone, When you try to select item code when invoicing or sales order and when you are in item code selection, it doesn't pop up or load, Any idea regarding this problem P.S. only one usercode account is affected. Thanks
-
Bor Object for a particular transaction.
Hi Experts, I need to desin a WorkFlow when Invoice is Created, How can we find the Object for a Particular transaction. Thanks
-
No music on ipod but memory is almost full
I have a 30gb ipod photo that I recently connected to itunes to transfer music. I specifically had itunes set to NOT sync my ipod b/c I had more music on my ipod than itunes. For some reason it began to sync, I quickly stopped it but all my music was