Unable to initialize Graphing service in Solaris 9 using ColdFusion MX 7

Upgraded from CMFX 6,1,0,63958 to CMFX 7.0.2 on Solaris 2.9
No errors during upgrades. Upon starting the CMFX 7, I am
seeing this in the cfserver.log. I cannot reach the CFMX
administrator page.
07/07 15:55:44 Information [main] - Starting graphing...
07/07 15:55:44 Error [main] - Unable to initialize Graphing
service: java.lang.InstantiationError: com.gp.image.server.IcMap
I have tried different work-arounds but have not been
successful...
http://www.adobe.com/go/ceb0e519
http://www.adobe.com/go/tn_18747
Here is my jvm.config:
# Arguments to VM
java.args=-server -Xmx512m -Dsun.io.useCanonCaches=false
-XX:MaxPermSize=128m -XX:+UseParallelGC -Djava.awt.headless=true
-Dco
ldfusion.rootDir={application.home}/
-Dcoldfusion.classPath={application.home}/lib/updates,{application.home}/lib,{application
.home}/gateway/lib/,{application.home}/wwwroot/WEB-INF/cfform/jars
-Dcoldfusion.libPath={application.home}/lib

Similar Messages

Unable to start workspace service on Solaris

Hi,
We are having some issues starting workspace services on solaris evviroment, when we start the workspace using the command "/app/hyperion/common/workspacert/9.5.0.0/bin/startAgent.sh" it starts only workspace agent, i see only the below process running on my server..
/app/hyperion/common/JRE-64/Sun/1.5.0/bin/java -DSname=wksagent -DCMC_AGENT=true
Actually there should be another service for workspace as below..
/app/hyperion/common/JRE-64/Sun/1.5.0/bin/java -DSname=workspace -DAGENT_TASK=0
My shared services is up and running fine, please direct me how to troubleshoot this issue. there are no log files which i can see what is the issue.
Aslo note we are starting all the services in a prefered order
Please let me know if you need further details.
Thanks

Set the Number of File Descriptors to unlimited. Under heavy load, WebLogic
Server may use up all available file descriptors. You can raise the file
descriptor limit permanently by setting rlim_fd_max and rlim_fd_cur in the
/etc/system file and rebooting. Set rlim_fd_cur=256 (soft limit),
rlim_fd_max=1024 (hard limit).
see http://www.weblogic.com/platforms/sun/index.html
"Satya Chauhan" <[email protected]> wrote in message
news:3a679edf$[email protected]..
I get the following error while starting Weblogic--------d.so.1:/usr/java/bin/sparc/native_threads/java: fatal: /dev/zero: open failed: Too
many open files (/usr/java/lib/sparc/native_threads/libnet.so)ld.so.1:
/usr/java/bin/sparc/native_threads/java: fatal: /usr/java/lib/libnet.so:
open failed: Too many open files
(/usr/java/lib/libnet.so)***************************************************
************************The WebLogic Server did not start up
properly.Exception raised: java.lang.UnsatisfiedLinkError: no net in shared
library pathjava.lang.UnsatisfiedLinkError: no net in shared library path
at java.lang.Throwable.<init>(Compiled Code) at
java.lang.Error.<init>(Compiled Code) at
java.lang.LinkageError.<init>(Compiled Code) at
java.lang.UnsatisfiedLinkError.<init>(Compiled Code) at
java.lang.Runtime.loadLibrary(Compiled Code) at
java.lang.System.loadLibrary(Compiled Code) at at at
weblogic.t3.srvr.T3Srvr.checkAccess(Compiled Code) at
weblogic.t3.srvr.T3Srvr.main(Compiled Code) at
weblogic.Server.startServerStatically(Compiled Code) at
weblogic.Server.main(Compiled Code) at weblogic.Server.main(Compiled
Code)***********************************************************************

Allow a user access to start and stop a particular service in Solaris 11 using RBAC controls

So, using svcbundle I created a service called "oracle" that starts and shutdown a db. I'm aware of how to grant RBAC access to be a "service operator" to be able to control start/stop ALL services. But I'd like to grant a user access to start and stop JUST this service.
in this document on page 15, it states that it's possible to do this kind of granularity but doesn't explain how to do it step by step.
how does one achieve this?
thanks.

You need to add a property group such as
<property_group name='general' type='framework'>

<propval name='action_authorization' type='astring'
value='solaris.smf.manage.oracle' />
</property_group>
Then add the solaris.smf.manage.oracle authorization to the user profile.
As an example, see Less known Solaris features: RBAC and Privileges - Part 2: Role based access control - c0t0d0s0.org

Unable to Initialize video deck, you may still use capture now. ??

Im trying to capture footage off my sony DCR-TRV900. Ive been able to do it before, but all of a sudden i cant. Ive tried all sorts of crap like switching cables, even sending the camera in. I dont know if settings got messed up or crap like that, but now my FCE is just acting weird with the camera plugged in. If i try to start it with my camera plugged in with VTR on, it will just crash. Ive been using FCE for 2 years now, and i really don't think i changed anything preference-wise. The only MAJOR change to my computer has been leopard, and if that somehow screwed it up, i will be ******. I can capture using a different camera, by putting the tape that i used in my 900 into a DCR TRV9. however, it always fails to capture correctly, screwing up the audio and leaving it un-synced. If someone could help me, it would be a life saver, thanks. Also, i wouldn't consider myself a beginner, but i taught myself how to use this program from the ground up, so i might be missing a crucial step.
Comp specsM
IMAC
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Message was edited by: alex2928

Let's start over.
I confused myself by invoking the Capture window. Of course that didn't work.
This was a completely different problem. My apologies.
The real problem was that the Log and Transfer window displayed ONLY the Logging pane. The clip list and queue pane were hidden and I couldn't get them back. I eventually found that resizing the entire window - even a small nudge - restored the missing panes. I expected the pane divider bar to not reveal the clip list, but this doesn't happen until the bar gets at least halfway across the window at which point the pane suddenly pops into view. This also confused me.
For the record, I'm using a MacBook core solo running Leopard. My Panasonic SD1 camera is not connected. The files from dozens of camera cards are stored on an external USB drive. I copy selected AVCHD folders from the USB drive to the root directory of the MacBook boot drive so that FCE will recognize them. The scratch disk is a large Firewire 400 drive also connected to the MacBook.

Elements 8 will not initialize online services

I have just upgraded and installed Elements 8 I am running Windows 7. When I start the organizer it will not initialize online services preventing me from using Photomail. I have attempted using Adobe Email Client and also sending as an attachment, neither has been successful.
Please help.
Thank you!
[email protected]

Can you describe more about what you mean by it not initializing online services?
Are you getting any kind of error message?

Coldfusion service hangs when logging into coldfusion administrator

Hi,
After changing the maximum number of connections to 1, I can
no longer enter the coldfusion administrator.
He allows me to enter the password, and then continues, but
after showing only the top frame on the left, the coldfusion
service hangs.
I use coldfusion mx 6.1 on windows 2003 server and IIS.
Kind regards,
Thomas

If you mean the "Maximum number of simultaneous requests",
this setting can be changed by making an edit to jrun.xml found in
\CFusionMX\runtime\servers\default\SERVER-INF\.
The argument is:<attribute
name="activeHandlerThreads">8</attribute> in the
ProxyService section.
Yours should show <attribute
name="activeHandlerThreads">1</attribute>.
Be sure to make a backup copy of the jrun.xml file before
making any edits.
You will need to restart ColdFusion after the change.

Error while installing exchange2007 : Unable to initialize the Microsoft Exchange Information Store service. Failed to find the

Hi,
I am trying fresh install of exchange2007, everything gone well but, finally it thrown a error saying :
Unable to initialize the Microsoft Exchange Information Store service. Failed to find the working directory parameter from the registry - Error 0x80004005.
the installation log says
6/5/2007 3:14:05 PM] [1] Processing component 'Mailbox Service Control (Last)' (Starting mailbox services).
[6/5/2007 3:14:05 PM] [1] Executing 'start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"', handleError = False
[6/5/2007 3:14:05 PM] [2] Launching sub-task '$error.Clear(); start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"'.
[6/5/2007 3:14:05 PM] [2] Beginning processing.
[6/5/2007 3:14:05 PM] [2] The maximum wait for the operation is set to 'unlimited'.
[6/5/2007 3:14:05 PM] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[6/5/2007 3:14:05 PM] [2] Will wait '10000' milliseconds for the service 'MSExchangeIS' to reach status 'Running'.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to reach status 'Running' on this server after waiting for '10000' milliseconds.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] [ERROR] Unexpected Error
[6/5/2007 3:14:15 PM] [2] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] Ending processing.
[6/5/2007 3:14:15 PM] [1] The following 1 error(s) occurred during task execution:
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[6/5/2007 3:14:15 PM] [1] Finished executing component tasks.
[6/5/2007 3:14:15 PM] [1] Ending processing.
[6/5/2007 3:14:18 PM] [0] End of Setup
[6/5/2007 3:14:18 PM] [0] **********************************************
this I am trying on my test system please help me out in resolving the issue
thanks in advance,

Gary,
Open Registry Editor.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Create the following value (REG_SZ): Working Directory and give it a value that points to the new database folder.
Make sure you back up the registry before you do any changes on it.
Raj

Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed

Each time I restart this exchange server, the Information Store and System Attendant don't start. If It try to manually start the services, I get the follow errors:
Event ID 5003:
Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
Event ID 1005:
Unexpected error The clocks on the client and server machines are skewed. ID no: 80090324 Microsoft Exchange System Attendant occurred.
The clocks on the domain controllers and the exchange server are set to the same time zones. As well, all three clocks are in sync down to the second. Any ideas on what's causing this and how to fix it?

Run this Command from the Exchange Server
Net time \\ADServerName /Set
and confirm the action,
and then you need to restart the service
Microsoft Exchange Active Directory Topology Service
and confirm you are not getting the Error 4001 in the event Viewer.
Thank you, it resolved my issue after being sweating looking for solution.
How can I prevent this from happening? I cannot restart services on each server reboot nor lose 5 years of my life!!!
Sokratis Laskaridis MCP, MCTS, MCITP, Small Business Specialist Netapp ASAP, Symantec STS

Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f.

PLease help, I've rstored from backup three times with no success I'm getting the following error
"Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f. "
It's LDap related but i have no idea why :-(
Best Regards Bernhard

IPv6 had been disabled for months on my SBS 2008 Server running Exchange 2007 SP1. I ran 40 or so Windows Updates; subsequently, the next morning Exchange was no longer running; topology issues, event ID 2604, 2114 and 2601 were all over my Application
Log. After 12 hours of research I found this post; figured it was worth a shot and instantly all my services for Exchange fired up. Thanks for the tip; I have no idea which update changed what in regards to needing IPv6 enabled, but that silly
little check mark fixed it.
Thank you for sharing your solution!
Dan

Unable to initialize service 'RemoveComponentServiceInterface'

Hi everyone!
I'm trying to use the api's RemoveComponentServiceInterface by doing the following:
RemoveComponentServiceInterface removeService = (RemoveComponentServiceInterface) Services.getService(
"com.sap.me.production", "RemoveComponentServiceInterface");
On runtime I get the following exception: Unable to initialize service 'RemoveComponentServiceInterface'
I can't figure out where my mistake may be. Any hints?
Thanks a lot!

See Re: When I create SFC By Using API, Exception Happened!

Manged servers is not getting started (Unable to initialize the server)

Hi,
I have weblogic 7.0 is installed in solaris . I configured one of my managed servers on port 80 , while starting the managed server it's giving me the following error:
<May 27, 2009 12:20:05 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to create a server socket on Channel Default for: 172.16.42.16, port: 80. java.net.BindException: Permission denied Perhaps the address 10.16.39.16 is incorrect or another process is using port 80.>
<May 27, 2009 12:20:06 PM IST> <Emergency> <Security> <090085> <Server failed to bind to any port such that it is not reachable from the console.>
<May 27, 2009 12:20:06 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to initialize the server: Fatal initialization exception>
ontext.java:2727)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:2700)
at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:563)
at weblogic.servlet.internal.WebService.preloadResources(WebService.java:476)
at weblogic.t3.srvr.ServletInitRunner$1.run(ServletInitRunner.java:50)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
at weblogic.t3.srvr.ServletInitRunner.run(ServletInitRunner.java:46)
at java.lang.Thread.run(Thread.java:479)
<May 27, 2009 12:22:38 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to create a server socket on Channel Default for: 172.16.42.16, port: 80. java.net.BindException: Permission denied Perhaps the address 172.16.42.16 is incorrect or another process is using port 80.>
<May 27, 2009 12:22:39 PM IST> <Emergency> <Security> <090085> <Server failed to bind to any port such that it is not reachable from the console.>
<May 27, 2009 12:22:39 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to initialize the server: Fatal initialization exception>
Please do needful to reslove the problem.
Rgds,
Krikar.

Hi Krikar,
Make sure -
1. IP is correct.
2. Specified port is not in use
For getting the ports-in-use list, follow below link -
http://www.unix.com/sun-solaris/87330-list-tcp-ports-process.html
Regards,
Anuj

Messaging 3.x fails to start with "Unable to initialize" error

Messaging Server fails to start from the Admin Server or by using the "start" command.

# /etc/NscpMail start
Startup Problem:
Unable to initialize the environment from (/etc/netscape.mail.conf)
Netscape Messaging Server Exiting!

The Messaging Server log file will not show any entries.

The problem is most likely due to a missing dbswtich.conf
file or a zero byte file.

The default dbswitch.conf
file contains a single line:

directory default ldapdb:///usr/netscape/suitespot/userdb/ldap/config/lcache.conf/

Restore this file from a backup if possible.

Unlike Admin Server, Messaging Server will require the correct file to be
restored because it immediately looks for its postmaster entries in the LDAP
directory. If you cannot restore the file:
<OL>
<LI>Place a temporary entry into the
file.
<LI>Start the admin server.
<LI>Enter the correct values into Global Settings,
Configure Directory Service.
<LI>Attempt to start the Messaging Server again.
</OL>

Tracing utilities (e.g. truss in Solaris) can
help analyze problems where servers fail to start and return little or no
useful errors.

truss -f -o <trussfile> /etc/NscpMail start

grep dbswitch.conf <trussfile>.

This would usually show admin returning a ENOENT error or reading zero bytes of
data.

I assume when you say "mentioned solutions", those include:
- Generating xorg.conf with aticonfig --initial
- Blacklisting the radeon module
- Generating the fresh fglrx modules with catalyst_build_module all
Also, how've you set it up? AUR, graysky's repository or directly from AMD's website?
Last edited by clfarron4 (2014-09-15 12:16:09)

Unable to open web service tester page

Hi
I'm three days trying to resolve this problem. I 'dont find a solution. I'm using ejb3.0 and web service. When I test the the application show me the messages Unable to open web service tester page. The application server is start up.
I'm trying this example. http://www.netbeans.org/download/flash/platform_55/platform_ws/
When I try to deploy the application show me this error.
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/javadb/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Sun/AppServer/jdk/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/imq/lib/imqxm.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
-Dcom.sun.aas.classloader.serverClassPath=C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;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:\Archivos de programa\Microsoft SQL Server\80\Tools\Binn\;C:\Archivos de programa\subversion-1.3.2\;C:\Archivos de programa\Subversion\bin;C:\Archivos de programa\QuickTime\QTSystem\;;;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/Sun/AppServer
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/Sun/AppServer/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]
Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_06] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://dani:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
autoDeployment status dir missing, creating a new one
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.
deployed with moduleid = MEjbApp
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.
deployed with moduleid = __ejb_container_timer_app
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.
[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__JWSappclients.ear for autodeployment.
deployed with moduleid = __JWSappclients
[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__JWSappclients.ear.
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
sending notification to server...server
CORE5051: Shutting down all J2EE applications ...
CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...
CORE 5061 : Resource adapters Stop() Complete
CORE5052: Application shutdown complete.
[AutoDeploy] Disabling AutoDeployment service.
WEB0303: Stopping Sun-Java-System/Application-Server.
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0713: Stopping Sun-Java-System/Application-Server HTTP/1.1 on 4848
Waiting for 1 instance(s) to be deallocated
Waiting for 1 instance(s) to be deallocated
Waiting for 1 instance(s) to be deallocated
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext;C:/Sun/AppServer/javadb/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.configName=server-config
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Sun/AppServer/jdk/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/imq/lib/imqxm.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServer/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
-Dcom.sun.aas.classloader.serverClassPath=C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar,C:/Sun/AppServer/imq/lib/jaxm-api.jar,C:/Sun/AppServer/imq/lib/fscontext.jar,C:/Sun/AppServer/imq/lib/imqbroker.jar,C:/Sun/AppServer/imq/lib/imqjmx.jar,C:/Sun/AppServer/lib/ant/lib/ant.jar,C:/Sun/AppServer/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;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:\Archivos de programa\Microsoft SQL Server\80\Tools\Binn\;C:\Archivos de programa\subversion-1.3.2\;C:\Archivos de programa\Subversion\bin;C:\Archivos de programa\QuickTime\QTSystem\;;;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.installRoot=C:/Sun/AppServer
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=C:\Sun\AppServer\domains\domain1\lib\mysql-connector-java-3.1.12-bin.jar
-Dcom.sun.aas.ServerClassPath=
-cp
;C:/Sun/AppServer/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start|#]
Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_06] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://dani:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/asadmin'
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context ''
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
ADM1041:Sent the event to instance:[ResourceDeployEvent -- reference-added jdbc/aae]
CORE5004: Resource Deployed: [jdbc:aae].
wsgen successful
DPL5306:Servlet Web Service Endpoint [AAEWebService] listening at address [http://dani:8080/WebAAEstates/AAEWebServiceService]
deployed with moduleid = WebAAEstates
WEB0100: Loading web module [WebAAEstates] in virtual server [server] at [/WebAAEstates]
naming.bind
topLink_version
application_server_name_and_version
login_successful
Initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/WebAAEstates'
Completed initializing Sun's JavaServer Faces implementation (1.2-b20-FCS) for context '/WebAAEstates'
exception caught
javax.naming.NameNotFoundException
 at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
 at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
 at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
 at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
 at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
 at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
 at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
|#]
Servlet web service endpoint 'AAEWebService' failure
java.lang.RuntimeException: javax.naming.NameNotFoundException
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
 at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
 at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.naming.NameNotFoundException
 at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
 at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
 at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
 at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
 at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
 ... 34 more
|#]
StandardWrapperValve[AAEWebService]: Allocate exception for servlet AAEWebService
javax.servlet.ServletException
 at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:273)
 at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: java.lang.RuntimeException: javax.naming.NameNotFoundException
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
 at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
 ... 26 more
Caused by: javax.naming.NameNotFoundException
 at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
 at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
 at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
 at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
 at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
 ... 34 more
|#]
exception caught
javax.naming.NameNotFoundException
 at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
 at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
 at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
 at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
 at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:43)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at com.sun.enterprise.webservice.JAXWSServlet.registerEndpoint(JAXWSServlet.java:291)
 at com.sun.enterprise.webservice.JAXWSServlet.doInit(JAXWSServlet.java:265)
 at com.sun.enterprise.webservice.JAXWSServlet.init(JAXWSServlet.java:108)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1133)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:787)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:183)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
 at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
 at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
|#]
Servlet web service endpoint 'AAEWebService' failure
java.lang.RuntimeException: javax.naming.NameNotFoundException
 at org.aae.jose.bd.AAEWebService.<init>(AAEWebService.java:50)
 at sun.reflect.NativeConstructorAccessorImpl.newIn

Hello,
you can check it at GlassFish Admin console (usually running on port 4848).
You need to log on to Admin console with the (default) or changed password (depends if you changed it during installation).
There you could see your web service deployed (usually in the "folder" Web services).
If you can see it you should see also wsdl - for your web service.
link:
http://developers.sun.com/appserver/reference/techart/ws_mgmt.html
Regards,
Miro

Unable to initialize the server: Server failed to bind to the requested por

I am facing the error while starting the server. I see the following error.
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 162.86.20.87, port: 8101. java.net.BindException: Address already in use Perhaps the address 162.86.20.87 is incorrect or another process is using port 8101.>
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
Reason: Server failed to bind to the requested port. See preceeding log message for details.
If the port is already in use how to find which server is running on that port, how to find the process and kill it. I am using weblogic 8.1 sp4 in Solaris 8.

Bruce:
It sounds like (as you already note) failed to shutdown WLS, that is why the
.loc file was held and why the port is in use, WLS process was still
running. To see why it failed to shut down, I would examine the
weblogic.log, aslo the servers std out and err. Additionally taking a
thread dump (if possible) on the "it wont shut down" wls java process should
show (maybe unless the VM is hosed), where/what is hanging on/around. Do
you happen to have native code running with wls, say a type 2 JDBC driver?
Otherwise it sounds like a VM bug. But more data is needed to be sure.
Cheers
mbg
"Bruce Bryan" <[email protected]> wrote in message
news:3ef08499$[email protected]..
I was shutting down the WLS server using the console shutdown and itfailed to shutdown completely. I then attempted to use the kill command on
the process which usually works. This time I was unable to kill the process
without using the kill -9 command. When I attempted to bring the server
back up I got a failure to get a lock on the embedded ldap. I removed the
.loc file and came further up but was unable to get further than the
listener ports which were still locked to the old process. Do you know of
anything I can do the get the WLS server back up without rebooting my
Solaris server????
netstat -an shows the port is in use but the only process that is alloweduse that port is WLS.

Unable to initialize SCI Page.

I've written a ton of crawlers and have never come across this issue before.
I'm in the process of implementing a java crawler however when Im trying to create the content source I recieve the following in PTSpy.
Calling Initialize method for SCI editor.....
Initialize method failed.
org.xml.sax.SAXException: Bad types (class java.lang.String -> class com.plumtree.remote.sci.TypeNamespace)
To me this seems like a simply Type Mismatch however its provided by the portal? When I examined to SOAP it seems like the portal is indeed
providing a string for the TypeNamespace parameter.
As expected in the IAdminEditor Interface the stub is as follows public void initialize(String locale, TypeNamespace namesp, NamedValueMap parentInfo)+
And below is what's passed during the calling of the initialize() method.
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <SOAP-ENV:Body>
 <ns1:Initialize SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:plumtree-com:XUIService">
 <Locale xsi:type="xsd:string">en-US</Locale>
 <Namespace xsi:type="xsd:string">plumtree-com:cws:crawl</Namespace>
 <ParentInfo ns2:arrayType="ns3:NamedValue[0]" xmlns:ns2="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="http://www.plumtree.com/xmlschemas/xui/" xsi:type="ns2:Array"/>
 </ns1:Initialize>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Has anyone seen this error or know how to fix it?

Is anybody found the solution to fix this error? I guess it must have been resolved by this time. Please post the solution if you have one.
I'm a newbie to BO. I get the same error 'Unable to initialize the page. Verify that the MDAS server is running and that the database client software has been installed on the MDAS server, and try again."
This error I got when I clicked the "New Connection" button on the 'Voyager Connections' screen at CMC. I had gone through all the postings regarding this error. None of them ended with any solution at all. The suggestions inall these postings I tried did not work.
I tried
(1) stopping and restarting SIA and MDAS and enabling all servers.
(2) Verified that the database client software 'Microsoft Analysis Services and the Analysis database' were installed. Next I stopped and restarted MS Analysis Server.
This did not work. I have a system Windows 7 Home Edition, and BO XI Enterprise 3.1. Checked the License for Voyager. It is valid and unexpired. Machine is 64 bit Windows 7 Home laptop. But all of my other 32 bits programs works fine on this machine safely.
One more thing this error did not arise in Windows Server 2003 desktop. Voyager and connections works fine in Windows server 2003.
Any help appreciated. Thanks.

Unable to initialize Graphing service in Solaris 9 using ColdFusion MX 7

Similar Messages

Maybe you are looking for