Hyperion system 9.3 analytic server problem

i installed Hyperion system 9.3 in my computer.i got some error so i uninstall it.and i again install hyperion system 9.3 this time i successfully installed and configured every thing.i open the analytic server and enter password to start analytic server.every thing is working fine.but when i restart my computer iam not able to start my analytic server.the window to enter password is not opening.the window is just appearing and vanishing.what to do in order to solve that error.

first i installed lincense server.then shared services then i configure shared services.after that in analytic server there are two components.first i installed server now i configured again and then client.after i installed administrative services.

Similar Messages

Problem in Starting the Analytical Server

Hi,
I was instaled the Hyperion 9.3 license,Shared services, Aanlytical servers in my PC successfully it was running. But after restart my system The Analytical server get corrupted it was not started. After runnig the configuration utility it was woking. What is the reason ?. Could you please give me the solution.. My Operating system Windows XP SP2.
Thanks in advance

Hi,
NoClassDefFoundError signifies that there is a classpath problem.
May be you are missing some critical jars in your classpath
for ex. weblogic.jar, jdk's rt.jar or something else.
You need to find this out.
HTH
VJ

Problem in Starting Analytical Server

Hi,
I was instaled the Hyperion 9.3 license,Shared services, Aanlytical servers in my PC successfully it was running. But after restart my system The Analytical server get corrupted it was not started. After runnig the configuration utility it was woking. What is the reason ?. Could you please give me the solution.. My Operating system Windows XP SP2.
Thanks in advance

I think Microsoft Windows users must have a minimum JDK 1.4.1_07 installed.
When viewing the platform requirements, it says JDK 1.4.2_04.
Also, set the PATH environment variable to include the Application Server install_dir/bin directory. (ex. C:\Sun\AppServer\bin)

Problem by Maintaining a Business System for the Integration Server

Hi to all,
I have the following problem. I tried to change some Business systems configuration in SLD but accidentally deleted defined Business System for our Integration Server. After that I tried to create that business system again but I have the following error:
Integration Server already defined. There is already an integration server defined for the selected technical system. Please select role Application System.
Since than Im receiving the following error message when I try to refresh my adapter engine cache:
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element
Do you know how can I define the Business System again currently I can't see it in SLD Business systems?
Ive also checked the IS URL (TR: SXMB_MONI) and it seems that its ok.
Regards
Naycho

Hi Naycho,
i think you have to clean up some sld rubbish
Go to SLD / Administration / Content Maintenance. Choose left side "all classes" or "landscape description" and right side "business system". Delete all entries you find for your business system, after that try to recreate it.
Regards,
Udo

Exchange profile parameter problem after system copy of XI server

I'm getting problem after the system copy of XI server. Following is the details. pls help to fix this one:
XQA is the system copy of XDV server. XQA is installed on rx2n1v1 server and XDV is installed on dbcixdv server. Following is weblink of XQA and XDV.
XQA: http://rx2n1v1:57400
XDV: http://dbcixdv:57000
After the system copy of XQA, i changed all xdv related parameters (hostname/port) in visual admin and configtool of XQA server.
Now when i run sxmb_ifr tcode in XQA, it should open the link of XQA server ( http://rx2n1v1:57400). But it open the link of XDV server (http://dbcixdv:57000).
The cause of this problem is the xdv parameter entires (hostname/portnumber of xdv) in exchange profile of XQA server (http://rx2n1v1:57400/exchangeProfile).
Now if i change hostname/portnumber of xdv in XQA server (http://rx2n1v1:57400/exchangeProfile), it also make the same change in XDV server (http://dbcixdv:57000/exchangeProfile).
Both XQA and XDV are in differnet hardware server. I don't understand why making changes of exchangeprofile in XQA also changed the value of exchangeprofile in XDV.
Hope it clarify.
Pls give the solution of this problem.
Thanks
Amar

Arjun,
http://<SAPHOSTNAME>50000/exchangeProfile
Yes, I can use above, but changing connection information gives me
RFC call returned an error code: 399
Use this one
http://hostname:50000/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp
This one, yes I get to the exchange give me an error: RFC call returned an error code: 399
http://hostname:50000/dir/start/index.jsp -->Administration -->login with PISUPER -->ExchangeProfile.
Internal Error
Internal error; contact your system administrator
Unable to read configuration data (ExchangeProfile/aii.properties)

Problem Addition Reporting Client tools for Hyperion System 9.3.1

Hi,
I'm using Hyperion System 9.3.1 (on SQL Srv).
I had no Reporting tools installed.
Then Reporting Client 9 products has been installed and configured successfully.
After that I logged into Workspace, system lost any apps and tools. Nothing except Shared Services (User Mngmnt).
When I tried to reconfigure Reporting products I got error "Invalid DB schema for Reporting product".
New DB schema has been created for this products and deploied it. But I have no positive result.
What can be a reason?

Hi
"Invalid DB schema for Reporting product" is a bug, have a patch to solve, i dont remember the number.
The workarround:
- Make Backup of DB.
- Drop DB table
- Reconfigure the Reporting creating a new table
- Restore Backup

Very Urgent: Hyperion System 9 Planning license was encountered

Hi,
I am working on Planning Version 9.2X. On every weekend, Hyperion Planning and Essbase servers are scheduled to start. After that, all the services are being recycled as part of weekly maintenance. The next day, when I tried to login into Planning, I am experiencing below issue soon after the server restart. To overcome this, again I am stopping and starting all services. Please refer to the Below Error and its Server log.
Can you please help in fixing this issue permanantly.
And one more issue with other Planning Application: This application does not have this kind of problem, but it has strange issue. This application also goes under weekly maintenace and does not any problem with the login. But, If I won't login soon after the server and Services recycle, Business Rules that are scheduled to run won't start. I have to have login into Planning to make the Business Rules to run.
Please suggest me if I need to change any settings with in the planning properties to overcome these issues.
Thanks,
UB.
Planning Login issue errro and its log:
A Problem with Hyperion System 9 Planning license was encountered. Please see log for details
####<Jan 24, 2010 10:31:56 AM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
####<Jan 24, 2010 10:35:29 AM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
####<Jan 24, 2010 6:51:56 PM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
####<Jan 24, 2010 6:55:26 PM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
#

user640496 wrote:
Why have to login after services recycled? Is it a product bug or it is common practice to login into the Planning to run the BR's once the services recycled.It has always been that way, I have never understood the logic but that is the way it is...
Also, Please give your inputs on this issue which was raised in the begining of this thread.
A Problem with Hyperion System 9 Planning license was encountered. Please see log for details
I am not sure on that one, have you checked any of the license server logs, I would contact Oracle if nobody else comes up with some ideas.
Cheers
John
http://john-goodwin.blogspot.com/

Unable to connect to Analytic server 7.2

Hi, I have been using Essbase 7.2.5.2 on windows 2000 which have been working fine so far. I had to install CDF in one of my essbase application. To make the required changes, I stopped the services & restarted the server.
Now when I try to connect to analytic server thru essbase console it shows an error message “network error: 10061 : unable to connect to <analytic server name>”
If I try to start the analytic services from command prompt by executing “essbase.exe from c:\hyperion\essabse\bin folder, it display following error “ Failed in GCInit()”
I shall appreciate if someone can help me by providing solution to this problem.
Thanks in advance.
Regards,

Hi John,
yes I did. However later I changed it back.The current setting are as follows:-
ARBORPATH = C:\Hyperion\essbase
Classpath = C:\Hyperion\essbase,C:\Hyperion\essbase\bin,C:\Hyperion\essbase\java
EASPATH=C:\Hyperion\AdminServices
HYPERION_HOME = C:\Hyperion
Path = C:\Hyperion\essbase\bin;C:\Hyperion\essbase\bin;C:\Hyperion\essbase\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Hyperion\SharedServices\7.2.5\openLDAP;%HYPERION_HOME%\common\CSS\7.2.5.2\bin;%HYPERION_HOME%\common\ODBC\Merant\5.1\Drivers;%HYPERION_HOME%\common\CSS\3.0.1\bin;%analyzer_install_root%\adm\bin\nt;%analyzer_install_root%\common;%hyperion_home%\common\adm\7.2.1\Essbase\7.2.1\bin;%hyperion_Home%\Common\CSS\2.7.0\bin;%Hyperion_Home%\common\ADM\7.2.1\ODBO\7.2.1;%Path%,C:\Hyperion\essbase\java
Have I specified any thing wrong inthe settings?
Regards,

Analytic Server not reflecting in Shared Services Console

Everything was working fine until yesterday. Now the problem is i am able to connect to analytic server through admin console and excel.
But for provisioning a user when i log into shared services
http://servername:58080 brings up the user diectory list. When i click on a username and provision it. I dont find my analytic server on the left hand side (so i am not able to see the cubes available). I just dont have a clue why this is happeneing. There is just one tab as "Hyperion Shared Services" but the analytical server is missing.
Kindly help me on this. How can i proceed further.
Additional Info:
Shared Service admin log has the following details.
2008-01-22 11:44:48,048 [http-58080-Processor10] ERROR com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:122) - Exception : Problem in processing action class.................
2008-01-22 11:45:12,034 [http-58080-Processor2] ERROR com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:122) - Exception : Problem in processing action class.................
2008-01-22 11:45:12,127 [http-58080-Processor15] ERROR com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:122) - Exception : Problem in processing action class.................
2008-01-22 11:45:13,127 [http-58080-Processor14] ERROR com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:122) - Exception : Problem in processing action class.................
2008-01-22 11:45:21,893 [Timer-0] ERROR com.hyperion.cas.web.util.memory.CASUsedMemoryTracker.run(CASUsedMemoryTracker.java:27) - Memory in use[12742 kb] = Total memory available[115736 kb] - Free memory available[102994 kb]
2008-01-22 11:50:21,921 [Timer-0] ERROR com.hyperion.cas.web.util.memory.CASUsedMemoryTracker.run(CASUsedMemoryTracker.java:27) - Memory in use[12728 kb] = Total memory available[117243 kb] - Free memory available[104515 kb]
2008-01-22 11:55:21,916 [Timer-0] ERROR com.hyperion.cas.web.util.memory.CASUsedMemoryTracker.run(CASUsedMemoryTracker.java:27) - Memory in use[12615 kb] = Total memory available[111083 kb] - Free memory available[98468 kb]
2008-01-22 12:00:21,928 [Timer-0] ERROR com.hyperion.cas.web.util.memory.CASUsedMemoryTracker.run(CASUsedMemoryTracker.java:27) - Memory in use[12790 kb] = Total memory available[114163 kb] - Free memory available[101373 kb]
2008-01-22 12:05:21,940 [Timer-0] ERROR com.hyperion.cas.web.util.memory.CASUsedMemoryTracker.run(CASUsedMemoryTracker.java:27) - Memory in use[12743 kb] = Total memory available[120782 kb] - Free memory available[108039 kb]

this similarity is quite odd. Since last friday we are not able to connect o analytical service vua EAS/SS user management and also the analytical server windows services are not starting anymore, essbase logs gives 1 relevant message:
Analytical Services global application does not exist at Shared Services..
We have been changing ip numbers of servers (but flused dns cache too) and also changed default admin password.
I haven't got a clue what to do. Fortunately we are still in in an OTA environment

Manual Deployment of Hyperion SS on Websphere Application server 6.1

Hi
I am trying to delopy Hyperion Shared Service R11.1 (interop.war) on
Websphere Application server 6.1 .
I am following the steps given in Deploying EPM System into WebSphere Application Server (epm_manual_deployment.pdf) page 100
After deploying according to the steps i am getting following error
Welcome to Hyperion® Shared Services Console
SEVERE ERROR: The Hyperion Shared Services database is not configured correctly. Please contact your system administrator.
After proper configuration, please restart Hyperion Shared Services and access this URL to continue.
Deregister the mbean because of uncaught init() exception thrown by servlet webdav: javax.servlet.ServletException: java.lang.NoClassDefFoundError: com.hyperion.eie.common.EIELog (initialization failure)
     at org.apache.slide.webdav.WebdavServlet.init(Unknown Source)
     at javax.servlet.GenericServlet.init(GenericServlet.java:256)
     at org.apache.slide.webdav.WebdavServlet.init(Unknown Source)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185)
Can anyone please help me deploy the HSS on WAS?
Thanks
Shraddha

Hey Guys,
OS: Windows 2003
App Server: Websphere 6.1
Hyperion version: 9.3.1
DB: SQL Server 2008
When i initially started out trying to deploy the hyperion system 9.3.1 using SQL server 2008 with Websphere 6.1 as my app server it gave me problems but i found a workaround and i have the shared services screen coming up however it says...
SEVERE ERROR: The Hyperion Shared Services database is not configured correctly. Please contact your system administrator.
And an idea someone gave on a thread was to mess with the HubProductBean.jar file and remove the classes of the javax/crypto - however that did not work. If anyone has any suggestions to get passed this issue it would be great. Thank you!
ZS

Adapter Engine / Integration Server Problem

Hi,
I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
Problem:
In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
What I've done & Observations:
1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
2. SLDCHECK reveals that the connection to SLD is successful.
3. RWB component monitoring shows:
    Integration Server - No light (Node cannot be expanded)
    Integration Engines - No light (Node cannot be expanded)
    Non-Central Adapter Engines -
        Adapter Engine ootspdbs02 (Red Light)
          - Self Test Failed - Details: Client 010 is not available in this system.
          - Cache Connectivity Test:
            Attempt to fetch cache data from Integration Directory failed; cache could not be updated
            [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
    J2SE Adapter - No light (Node cannot be expanded)
    Tools
        - System Landscape Directory ootspdbs02 (Green Light)
        - Integration Directory ootspdbs02 (Green Light)
        - Integration Repository ootspdbs02 (Green Light)
        - Runtime Workbench ootspdbs02 (Green Light)
4. In my SLD - I've defined a business system PI_BS_01
    Role: Integration Server
    Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
    Group - No Group Assigned.
    Client: 001 of PI1
    Technical System: PI1 on ootspdbs02 - Release 700
Given the above observations, can anyone please point out to me where I went wrong?
Any advise is greatly appreciated.
Thank you.
Best Regards,
Ron Lai

Hi Archana,
The configuration in SLD DataSupplier is:
Latest Send Activity
     2007/01/04 09:18:09:564
Used HTTP Parameters [http host:port] [user] [protocol]
     [ootspdbs02:50100] [SLDDSUSER] [http]
Sending Node [nodeID] [hostname]
     [11621750] [ootspdbs02]
Send Result
     Success
Next Automatic Send Timestamp
     2007/01/04 21:18:08:189
Send Type
     Automatic (Time Scheduled)
Configuration Status
     Valid
The hierarchy of this business system is:
Business System:
   BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
Technical System:
   TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
Basically I created product, software component, technical system, business system from scratch.
I did not put any dependencies to existing products/software components.
Regards,
Ron

Help is not working in Hyperion System 9 WebAnalysis

two months back we have installed Hyperion System 9.2.0.3 BI+ server and is working fine. however recently one user complained that WebAnalysis help is not working. we are getting "page cannot be displayed" when clicking on Help --> contents and index from WebAnalysis -- <a target=_blank class=ftalternatingbarlinklarge href="http://hostname:19000/WenAnalysis">http://hostname:19000/WenAnalysis</a> this is the direct link to the webanalysis help <a target=_blank class=ftalternatingbarlinklarge href="http://hostname:19000/workspace/docs/en/wa_user/frameset.htm?/workspace/docs/en/wa_user/launch.html">http://hostname:19000/workspac...n/wa_user/launch.html</a> Do you know how to fix this?

Hi Friends,
I am working on Sandbox Server, in that Help (F1) is not working. When i try to click F1 system is opening the popup and showing the following message-
The page cannot be displayed
Plz help
Regards
Goutham

Checking status of scheduled jobs in Hyperion System 9.3.1 ....

Hi All,
We have Hyperion System 9 9.3.3. We have a Daily job scheduled every morning to check the status of the scheduled jobs that run daily. One of the jobs has a status message as below.
Failure - Internal error.ContainerCache.populate: The object "0000011386a6823b-0000-a99f-0a103a4a" is not found. It either does not exists, or it may be inaccessible.
But when I check the job status in View Job Status > Job Scheduler module, I see the report is still running. It's just that this report is taking longer to run and completes some time after the Daily Job Status check report runs.
In this case, shouldn't the status should say something like the job is still running instead of "Failure" which is misleading?
Thanks in advance.
Z

Hi,
I have the same problem with Oracle EPM 11.1.2:
com.sqribe.transformer.ObjectNotFoundException: ContainerCache.populate: The object "0000012f0710ca12-0000-a4ad-c0a80003" is not found. It either does not exists, or it may be inaccessible.
Who gives me the right answer?
Thanks in advance, Ron

APP Server Problem - HELP!!!!

I've read all the previous postings and can't resolve this after a week of re-installs, deleting files, PATH, Environment Variable changes, etc. Can someone please provide definitive advice on this? I'm installing on XP for now. Server Log File is as follows:
Thanks,
Jeremy
[#|2007-03-18T11:31:37.703-0400|WARNING|sun-appserver-pe8.2|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. |#]
[#|2007-03-18T11:31:37.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Sun/java\bin\java
-client
-XX:PermSize=32m
-XX:MaxPermSize=128m
-XX:+CMSPermGenSweepingEnabled
-XX:+CMSClassUnloadingEnabled
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
-Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
-Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
-Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=creator
-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/SunAppServer8/domains/creator
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=creator
-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/SunAppServer8/config
-Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/SunAppServer8/lib\commons-launcher_fr.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ja.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ko.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh_CN.jar;C:/Sun/SunAppServer8/lib\commons-logging.jar;C:/Sun/SunAppServer8/lib\deployhelp_es.jar;C:/Sun/SunAppServer8/lib\deployhelp_fr.jar;C:/Sun/SunAppServer8/lib\deployhelp_ja.jar;C:/Sun/SunAppServer8/lib\deployhelp_ko.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh_CN.jar;C:/Sun/SunAppServer8/lib\dom.jar;C:/Sun/SunAppServer8/lib\driveradapter.jar;C:/Sun/SunAppServer8/lib\j2ee-svc.jar;C:/Sun/SunAppServer8/lib\j2ee.jar;C:/Sun/SunAppServer8/lib\j2ee_es.jar;C:/Sun/SunAppServer8/lib\j2ee_fr.jar;C:/Sun/SunAppServer8/lib\j2ee_ja.jar;C:/Sun/SunAppServer8/lib\j2ee_ko.jar;C:/Sun/SunAppServer8/lib\j2ee_zh.jar;C:/Sun/SunAppServer8/lib\j2ee_zh_CN.jar;C:/Sun/SunAppServer8/lib\jax-qname.jar;C:/Sun/SunAppServer8/lib\jaxr-api.jar;C:/Sun/SunAppServer8/lib\jaxr-impl.jar;C:/Sun/SunAppServer8/lib\jaxrpc-api.jar;C:/Sun/SunAppServer8/lib\jaxrpc-impl.jar;C:/Sun/SunAppServer8/lib\jdic_0_9.jar;C:/Sun/SunAppServer8/lib\jmxremote.jar;C:/Sun/SunAppServer8/lib\jmxremote_optional.jar;C:/Sun/SunAppServer8/lib\jsf-api.jar;C:/Sun/SunAppServer8/lib\jsf-impl.jar;C:/Sun/SunAppServer8/lib\mail.jar;C:/Sun/SunAppServer8/lib\PEtray.jar;C:/Sun/SunAppServer8/lib\relaxngDatatype.jar;C:/Sun/SunAppServer8/lib\rmissl.jar;C:/Sun/SunAppServer8/lib\saaj-api.jar;C:/Sun/SunAppServer8/lib\saaj-impl.jar;C:/Sun/SunAppServer8/lib\smbase.jar;C:/Sun/SunAppServer8/lib\smdb2.jar;C:/Sun/SunAppServer8/lib\sminformix.jar;C:/Sun/SunAppServer8/lib\smoracle.jar;C:/Sun/SunAppServer8/lib\smresource.jar;C:/Sun/SunAppServer8/lib\smspy.jar;C:/Sun/SunAppServer8/lib\smsqlserver.jar;C:/Sun/SunAppServer8/lib\smsybase.jar;C:/Sun/SunAppServer8/lib\smutil.jar;C:/Sun/SunAppServer8/lib\xalan.jar;C:/Sun/SunAppServer8/lib\xercesImpl.jar;C:/Sun/SunAppServer8/lib\xsdlib.jar;C:/Sun/SunAppServer8/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/SunAppServer8/imq/lib/jaxm-api.jar;C:/Sun/SunAppServer8/imq/lib/fscontext.jar;C:/Sun/SunAppServer8/lib/ant/lib/ant.jar
com.sun.rave.tray.RavePEMain
start
display
native|#]
[#|2007-03-18T11:31:46.921-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\SunAppServer8\imq\bin].|#]
[#|2007-03-18T11:31:46.937-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2007-03-18T11:31:47.531-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
[#|2007-03-18T11:31:47.546-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-03-18T11:31:47.812-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2007-03-18T11:31:48.984-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/24700"|#]
[#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22060"|#]
[#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22061"|#]
[#|2007-03-18T11:31:50.015-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [24700]|#]
[#|2007-03-18T11:31:53.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-03-18T11:31:53.515-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2007-03-18T11:31:55.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2007-03-18T11:31:55.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2007-03-18T11:31:55.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2007-03-18T11:31:56.000-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1688 msec, Total EJB Compiler Module Time: 63 msec, Portion spent EJB Compiling: 3%
Breakdown of EJBC Module Time: Total Time for EJBC: 63 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 47 msec (74%),
|#]
[#|2007-03-18T11:31:56.093-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2007-03-18T11:31:56.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2007-03-18T11:31:56.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2007-03-18T11:31:56.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2007-03-18T11:31:56.437-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 76954462832623616|#]
[#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear.|#]
[#|2007-03-18T11:31:56.578-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2007-03-18T11:31:56.875-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2007-03-18T11:31:59.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2007-03-18T11:31:59.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2007-03-18T11:32:00.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 3468 msec, Total EJB Compiler Module Time: 3031 msec, Portion spent EJB Compiling: 87%
Breakdown of EJBC Module Time: Total Time for EJBC: 3031 msec, CMP Generation: 594 msec (19%), Java Compilation: 2359 msec (77%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 16 msec (0%),
|#]
[#|2007-03-18T11:32:00.109-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2007-03-18T11:32:00.156-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2007-03-18T11:32:00.187-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2007-03-18T11:32:00.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2007-03-18T11:32:00.343-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 76954463102959616|#]
[#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2007-03-18T11:32:00.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2007-03-18T11:32:00.796-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2007-03-18T11:32:00.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2007-03-18T11:32:00.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2007-03-18T11:32:00.921-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2007-03-18T11:32:00.953-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2007-03-18T11:32:01.062-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
[#|2007-03-18T11:32:02.671-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
[#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
[#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
[#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
[#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
[#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
[#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@1a428d5 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.net.SocketTimeoutException: Read timed out]|#]
[#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.net.SocketTimeoutException: Read timed out]
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
     at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
Caused by: java.io.IOException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.net.SocketTimeoutException: Read timed out]
     at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
     at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
     at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:177)
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
     ... 4 more
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.net.SocketTimeoutException: Read timed out]
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
     at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
     at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
     ... 6 more
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
     at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
     ... 10 more
Caused by: java.net.SocketTimeoutException: Read timed out
     at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:123)
     at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:81)
     at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:73)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
     at java.io.DataInputStream.readByte(DataInputStream.java:241)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
     ... 14 more
|#]
[#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2007-03-18T11:33:02.968-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
     at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
     at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
|#]
[#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
[#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
[#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
[#|2007-03-18T11:33:03.125-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2007/03/18 11:33:03]|#]
[#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2007-03-18T11:33:03.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2007-03-18T11:33:03.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2007-03-18T11:33:03.890-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2007-03-18T11:38:11.046-0400|WARNING|sun-appserver-pe8.2|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. |#]
[#|2007-03-18T11:38:11.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Sun/java\bin\java
-client
-XX:PermSize=32m
-XX:MaxPermSize=128m
-XX:+CMSPermGenSweepingEnabled
-XX:+CMSClassUnloadingEnabled
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
-Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
-Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
-Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=creator
-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/SunAppServer8/domains/creator
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=creator
-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/SunAppServer8/config
-Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/Sun

Hi,
Seems you are having socket time out exception. I use to get the same while deploying on XP with (640MB RAM) but able to re-run after freeing some memory. Creator needs optimally atleast 1GB RAM. You have not mentioned your machine RAM...
It might just help..
dr.am mohan rao

Hyperion System 9.3.1 reports taking longer time for the very first time

We are on Hyperion System 9.3.1. The Financial reports are taking longer time (like 2 to 3 minuter) for the very first time for each login. The subsequest reports are does work faster.
The behaviour is same for the Production and Development environments.
All the reporting services have given enough JVM heap size.
FYI, Reporting and Workspace runngin on the same server. Workspace/Reporting are clusted in two servers. HFM app is running on different server. HFM web is on different server. Shared Services is also on running on different server.
Any help would be greately appreciated.
Thanks.

The reason they run quicker the subsequent times, is because the data has already been cached in the system.
You could try the usual tricks to speed the report up:
- move items into POV
- have children and parent in the same row
- arrange dimensions in inverse outline order
- remove excessive formatting
- push report calculations back to the data source
We have found that using lots of dynamically calculated members also slows down reports, so try and limit the number of these.
Hope this helps. If not maybe give us an idea of how the report is created to see if other changes could be made.

Hyperion system 9.3 analytic server problem

Similar Messages

Maybe you are looking for