Hub startup failed due to licensing failure
Hi all.
I have just installed weblogic 6.0 sp1 on solaris 2.8. the web server starts
up and everything is hunky dory.
furthermore i downloaded collaborate 1.0.1 and installed it. the
installation went fine.
here is my problem. when i execute the startWeblogic.sh script in the hub,
Weblogic reports the following error:
<24-Apr-01 13:49:03 GMT+01:00> <Error> <WLC> <<Hub> ERROR: Hub startup
failed due to licensing failure.>
I get this problem using jdk122 and jdk130.
I cannot seem to find the problem.
Any feedback would be appreciated.
PS. My license.bea file looks as follows:
<?xml version="1.0"?>
<bea-licenses>
<license-group format="1.0" product="WebLogic Collaborate"
release="1.0">
<license
component="Core Server"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MC0CFCoH/XUHiZuu+yhzpuzv6UFl
kJ44AhUA2/U26g1keq5nNoO00NC2u9ezWeA="
/>
</license-group>
<license-group format="1.0" product="wlpi" release="1.2">
<license
component="WebLogic Process Integrator"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
users="5"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MCwCFEh5H427STpTMX1y25DSmc65
b/MVAhQMNJo1ujoB6DudzF59hL/Tx2vbGQ=="
/>
</license-group>
<license
component="WebLogic"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OFcm7oSc4jOT5vonluVZpsAHX2g=0MCwCFEmkcBweXEoxtJxzCIarx8i+
XBguAhQvCxM9E/T4HGfbIUfb4+OiNUYsPw=="
/>
<license
component="SSL/Export"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OgS8PvglCrGr5xglLHeut8tE5vc=0MC0CFQDcxuNftALK3tZYuJw6hI15
GaqrBgIUcTi0vNzwoG1alTX1WXnvcX9EOiM="
/>
<license
component="2PC"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="CcdspC/3P0iELwWsETBWI/hEalw=0MC0CFQCtTlW7enw3kFZ7IU09jaa/
BVle5wIUSSfMk23C19hznredmfr+soEYiX0="
/>
<license
component="In-memory Replication - Servlet"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="c+mtrQ1ZuRiKeiELua/hSxvHqew=0MC4CFQC4qvLRsblTBvC5+IEVrDI1
Tek1YwIVAJ1NYWZE6xPHYyyVdlaXRJbhayCj"
/>
<license
component="In-memory Replication - EJB"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="ZenJ1bPXGf2N/Bq8XugDnDIP8sQ=0MC0CFQC+ayYQFxhpIMug7ZHtZIfS
vg4tlwIUHIYgx30GoxIdmR19cGddWM/mp3E="
/>
<license
component="EJB 1.1"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="XwwhoY5ysJ8h1pjzx23ujxZI9nY=0MC4CFQC2ATLeRv6cStQE1B/gyMUT
R6SRvQIVAMsQmtFC0/J4sF26n+B1zEyDOmv/"
/>
<license
component="EJB 2.0"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
units="5"
signature="ksI9jkE6gL9u8GdVEpZNQtOvjm8=0MCwCFBUir1rQV/FLNdc+4lfdIV1x
+xk5AhQpQwwWMfUd6TbL3UvB0u9DbZponQ=="
/>
<license
component="JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Z4Q4VngOAJSqSsr1UXC37DTOyVg=0MC0CFQCZtOwzb02hOSR3z9Hp6k86
nl1uFQIUfhy+ODL+Y7B9DkGDS7yT4zQPPpE="
/>
<license
component="Cluster"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Tkg9CGjEik3MbkFmi6rPsSiO0J0=0MC0CFEAV5hPKLVSgV8YoeCEVu5m7
5ktkAhUA2lBI0PwiMigvK1E/pVS0vqmsy3w="
/>
<license
component="Clustered JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="nEpfLZwWyM4Bo7UZZHE4hQgntMc=0MCwCFBKYtPvqZE18JdGBvU6cZomM
xW1cAhR3moJKg7FHMxvsZphQz5jVCahrfA=="
/>
<license
component="jDriver/MSSQLServer4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Dgw2DzDWyBNob6pJunUY1Xoz7c8=0MC0CFQC4PKj8UFoC3J0XuC7pmzRL
TtgP8QIUAhJF5DuvZ10zvf/6mxe0Ti/rG4c="
/>
<license
component="jDriver/Informix4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="6O/i8fVnKIeVwzz+e0zUMQL5uRU=0MC0CFH+NK7nnRm+Qp+qRXZdeV2yF
6YxdAhUA3vch2xTdmM5Ao+00+IOR5f3jGH0="
/>
<license
component="jDriver/Oracle"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="NtSVpPAloTJqBstOWKVnuh3q0H4=0MC0CFA+2ny24Zdyrb0lsL3duwfEB
9zKMAhUAqDtTbLMN3QfJWUVhJr+NBQU/x/k="
/>
</license-group>
</bea-licenses>
Gotta add listeners.ContextListener to your CLASSPATH
in Eclipse.
I don't think that package name is right. You've got
another problem besides your context XML.
%The context XML may not be the problem at all. Such tomcat errors are standard when it was unable to load required classes on startup.
The listeners all being interfaces, it's impossible to say whether it is the standard listeners or custom listener classes (regd in your web.xml) that's not being found on startup.
cheers,
ram.
Similar Messages
-
Management Data Warehouse Data Collection fails due to login failure
Hello,
I am trying to set up a Management Data Warehouse on a server other than the one I want statistics of. Unfortunately, each upload fails because the data collector upload job cannot log onto the warehouse server. For some inexplicable reason the process is trying to log on using domain\serverName. Obviously no such user exists, and the process fails. Below is the error message I see in the logs:
Description: An error occurred with the following error message: "An error occurred while verifying the result set schema against the output table schema. The data collector cannot connect to the management data warehouse. : Login failed for user 'domain\server name$'.".
Any help would be greatly appreciated.
Thanks,
Zacharyhttp://technet.microsoft.com/en-us/library/bb677211.aspx says
The data warehouse is installed on a different computer from the data collector. Probable causes are network connectivity problems or an unavailable host server. This error only affects upload packages.
Handling: Because there is no advance notification about a server shutdown, this error cannot be anticipated and handled automatically. The error is logged and after a brief interval, the upload is restarted. After four unsuccessful upload attempts, the collection set is disabled and its state is written to the execution log.
Note:
Any data that is collected while the collection set is running is kept and accumulated. If the upload package can connect to the data warehouse, the accumulated data is uploaded.
Blog: http://dineshasanka.spaces.live.com -
Job execution fails using SQLServerAgent account but runs successfully under another windows personal account.
Both have same security access on server and DB.
The Windows account is mapped to dbo on the database .
The package uses procedures and views which are using encryption by certificates.
Please advice on how to provide security so that job runs from the agentHi Prady26,
If the SQL Server Agent Service account and the proxy account generated based on a Windows user account have the same permissions on both the SQL Server database and the File System of the server, it may be related to the protection level of the package.
If the package is set to encrypt with UserKey, the job will fail unless it runs under the security context of the Windows user that designs the package in BIDS/SSDT. You can check the
ProtectionLevel of the package in the BIDS/SSDT to see if it is EncryptSensitiveWithUserKey or EncryptAllWithUserKey, if it is, re-deploy/reinstall the package and set the package protection
level to “Relay on server storage for encryption”.
If the issue persists, post the error message in the job history for further analysis.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support -
Baseline failing due to 'ConfigurationGeneratorForge' failure
Hi,
The baseline update is failing giving the below mentioned error.
[04.10.13 15:49:06] SEVERE: Batch component 'ConfigurationGeneratorForge' failed. Refer to component logs in F:\testApplication\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge on host ITLHost.
Occurred while executing line 20 of valid BeanShell script:
17|
18| // Generate instance configuration
19| ConfigurationGeneratorForge.archiveLogDir();
20| ConfigurationGeneratorForge.run();
21|
22| // archive logs and run ITL
23| Forge.archiveLogDir();
[04.10.13 15:49:06] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.component.BatchComponent run - Batch component 'ConfigurationGeneratorForge' failed. Refer to component logs in F:\testApplication\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge on host ITLHost.
[04.10.13 15:49:06] INFO: Released lock 'update_lock'.
Please suggest what needs to be done.
Thanks
VarunHi Pankaj,
PFB the error from the logs.
ERROR 04/10/13 10:58:10.282 UTC (1365591490281) FORGE {config}: (AdapterRunner): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationAdapter' defined in class path resource [config/script/fcm.context.xml]: Cannot resolve reference to bean 'forgeConfigurationManager' while setting bean property 'forgeConfigurationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'forgeConfigurationManager' defined in class path resource [config/script/fcm.context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.endeca.itl.fcm.ForgeConfigurationManager]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
com.endeca.edf.adapter.AdapterException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationAdapter' defined in class path resource [config/script/fcm.context.xml]: Cannot resolve reference to bean 'forgeConfigurationManager' while setting bean property 'forgeConfigurationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'forgeConfigurationManager' defined in class path resource [config/script/fcm.context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.endeca.itl.fcm.ForgeConfigurationManager]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at com.endeca.esource.springadapter.SpringDelegateAdapter.loadApplicationContext(SpringDelegateAdapter.java:121)
at com.endeca.esource.springadapter.SpringDelegateAdapter.loadDelegateAdapter(SpringDelegateAdapter.java:73)
at com.endeca.esource.springadapter.SpringDelegateAdapter.execute(SpringDelegateAdapter.java:60)
at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)
at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationAdapter' defined in class path resource [config/script/fcm.context.xml]: Cannot resolve reference to bean 'forgeConfigurationManager' while setting bean property 'forgeConfigurationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'forgeConfigurationManager' defined in class path resource [config/script/fcm.context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.endeca.itl.fcm.ForgeConfigurationManager]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:93)
at com.endeca.esource.springadapter.SpringDelegateAdapter.loadApplicationContext(SpringDelegateAdapter.java:119)
... 4 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'forgeConfigurationManager' defined in class path resource [config/script/fcm.context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.endeca.itl.fcm.ForgeConfigurationManager]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:839)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269)
... 22 more
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.endeca.itl.fcm.ForgeConfigurationManager]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:115)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:877)
... 33 more
Caused by: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at com.endeca.itl.fcm.ForgeConfigurationManager.<init>(ForgeConfigurationManager.java:226)
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:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
... 35 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
... 41 more
ERROR 04/10/13 10:58:11.332 UTC (1365591491332) FORGE {config}: The java process evaluating the java manipulator class 'com.endeca.esource.springadapter.SpringDelegateAdapter' failed. Check the file 'F:\testApplication\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.LoadSchemaRecordStore.log' for more information.
INFO 04/10/13 10:58:11.332 UTC (1365591491332) FORGE {config}: RecordCache 'SchemaRecordStoreCache (LoadSchemaRecordStore)' read 0 records.
INFO 04/10/13 10:58:11.332 UTC (1365591491332) FORGE {config}: RecordCache 'SchemaRecordStoreCache (LoadSchemaRecordStore)' loaded 0 record, combined 0 records.
INFO 04/10/13 10:58:11.332 UTC (1365591491332) FORGE {config}: RecordCache 'SchemaRecordStoreCache' heap used: 0 MB (total: 7.01563 MB).
INFO 04/10/13 10:58:11.332 UTC (1365591491332) FORGE {config}: JavaManipulator 'LoadSchemaRecordStore': Finished
INFO 04/10/13 10:58:11.333 UTC (1365591491332) FORGE {config}: RecordCache 'SchemaCsvCache (MappedSchemaCsv)' loading records.
INFO 04/10/13 10:58:11.468 UTC (1365591491467) FORGE {config}: (AdapterRunner): Adapter class: com.endeca.itl.fcm.integration.cadk.ifdi.RecordPropertyRenamer
ERROR 04/10/13 10:58:11.468 UTC (1365591491467) FORGE {config}: (AdapterRunner): java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
com.endeca.edf.adapter.AdapterRunner$LoadAdapterException: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at com.endeca.edf.adapter.AdapterRunner.loadAdapter(AdapterRunner.java:326)
at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:162)
at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
Caused by: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
at com.endeca.itl.fcm.integration.cadk.ifdi.RecordPropertyRenamer.<init>(RecordPropertyRenamer.java:44)
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:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.endeca.edf.adapter.AdapterRunner.loadAdapter(AdapterRunner.java:317)
... 2 more
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
... 10 more
ERROR 04/10/13 10:58:12.491 UTC (1365591492491) FORGE {config}: The java process evaluating the java manipulator class 'com.endeca.itl.fcm.integration.cadk.ifdi.RecordPropertyRenamer' failed. Check the file 'F:\testApplication\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.MappedSchemaCsv.log' for more information.
Regards,
Varun -
Error in Tomcat --- context start up failed due to previous errors
Feb 27, 2008 11:05:11 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/jstl] startup failed due to previous errors
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ComponentRule end
WARNING: [ComponentRule]{faces-config/component} Merge(com.mycompany.TabLabel)
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ComponentRule end
WARNING: [ComponentRule]{faces-config/component} Merge(com.mycompany.Tree)
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ValidatorRule end
WARNING: [ValidatorRule]{faces-config/validator} Merge(com.mycompany.jsf.validat
or.LATER_THAN)
Feb 27, 2008 11:05:14 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Feb 27, 2008 11:05:14 AM org.apache.catalina.core.StandardContext startHello frnds i dont understand what should i do? anybody familiar with this kind of error. please let me know in this case what should i do?
even if i am trying to copy whole files in another folder it shows same msg for that folder too. please help me
Thankyou everybodyHi ,
I also face this same kind of problem.
I tried to fix the problem but not work out.
I got another solution. I am not sure its a current solution .
Try it carefully.
Finally 1, I take back up -copy of server.xml and common/lib .
2, Un-install Tomcat server.
3, After i have installed fresh tomcat server.
4, Replace back-up copy of server.xml and common/lib.
its working fine -
Portal failed to access remote resource due to network failures
Hi,
We have a portlet that allows users to upload files to a SQL Server database and make it available for other users to access. The portlet code is on our remote servers. Everything works fine in dev environment, but certain files fail in pre-prod and prod within the portal, but work fine when the code is executed outside the portal.
I keep getting this error:
Error - Portal failed to access remote resource due to network failures. Try again later or contact your portal administrator.
What could the problem be?
Thank you for your help.
RadIf the Studio service looks good on the remote server where Studio is installed (check that
the service is started and look in the Studio logs for any warnings or errors), you should
also verify the configuration settings in the Studio remote server object. Is it properly
configured and pointing to the correct remote server?
If so, check the portal servers access to the Studio server via the port specified in the remote
server (default is 11935). You can test this by doing a telnet test on the portal server. In a cmd
prompt (Windows) or on the CLI (Unix), type 'telnet [studioserver] 11935', where "<servername> is
the name of your Studio remote server. The screen should just go blank, meaning that there is
something accepting connections on that port on the given server. (We would hope it's the Studio
app and not another service occupying that port.) If you get "Could not open connection to the host"
or some such similar result, check that the network between the portal and the Studio remote server
is open (ie, make sure there isn't any port blocking or a firewall in place that would hinder the
communication between the two servers). -
I have reset both my torch and playbook back to original only thing that I kept was my contact. And still problems I am a few min away from leave my loved blackberry and going android !! Or heaven help us Phone
Issues 1) playbook wont connect to desktop manager anymore
2) Play book has 2 calendar icons with two different settings on them ??? I have one that is currently working with my yahoo email and calendar account.
3) my Phone when connected to desk top software shows the calendar as read only
4) Unable to update my phone says During an update of the applications on the BlackBerry® smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatisfactory dependencies."
I just want my email and Calendars to work I am tried of spending nights trying to get these deices working !!!
someone please help me. !!
I know you are going to ask I have updated everything last time and it is all as update as it can get.
As for now as I wait I am going to wipe my phone again and just set everything up again !! If I have to even my contacts AHHHH Help I am starting to think crazy thoughtsDid you try to eboot the your PC or laptop where your device is connected ?
I experienced this with my windows laptop, after a failed to do an update, I restart the laptop and my Torch, then retried, and it's worked -
I recently got a macbook Air and needed to reinstall my adobe creative suite to said new computer. I purchased creative suite online so I downloaded it from there and followed the installation instructions to a T.
I originally purchased Adobe Creative Suite in 2011 so it is version CS5.1
Everything installed successfully except Adobe Illustrator, which at the end left me this error message
ERROR: DW050: - Adobe Illustrator CS5.1_AdobeIllustrator15_1en_USLanguagePack: Install failed
ERROR: DW050: - Adobe Illustrator CS5.1: Failed due to Language Pack installation failure
how can I get illustrator on my computer?!
Hoping to sell my previous computer soon and I'm almost done transferring programs and photographs.
Thanks so much!Which language is the application?
Which language is your system?
Which system? -
after a licensing failure message, I tried to reinstall CS3 design standard but the error "Component Install Failed" occurred and I still am unable to use Photoshop or InDesign Please Help!
J3liu1 I would recommend reviewing the installation log files for the specific error message which you are facing. You can find details on how to locate an interpret your installation log files at Troubleshoot installation with install logs | CS3, CS4. You are welcome to post any specific errors you discover to this discussion.
-
TP error: connect failed due to DbSL load lib failure
Hi All,
I have prepared Quality system from Production system as System copy.I have upgarded Kernel from 620 to 640 in Quality system.
After Kernel upgrade , Server details are as below
Operating System : windows 2003 IA 64
Database : SQL server 2000 IA 64
Kernel :640 and compiled for 64 bit non unicode system ,
patch number is 43.
SAP : SAP R/3 4.7
Before kernel upgrade , server details are as below
Operating System : windows 2000 server
Database : SQL server 2000
Kernel :620 and compiled for Non unicode system ,patch number
is 1363
SAP : SAP R/3 4.7
I am able to transport request from Development to Quality . But when I try to import request from Quality I am getting error message "Connect failed due to DBSL Load lib failure"
Error message is " connect failed due to DBSL load lib failure
cannot find the DLL dbmssslib.dll in path( K:\usr\sap\NBQ\SYS\exe\run)
problem when loading DB-dependent DLLs."
I have set Environmnet variable ( DBMS_TYPE value as mss) for nbqadm user.
I have seen that dbmssslib.dll file is exist in exe/run path.
Does anyone having an Idea , how to resolve this issue.Pls help me
Thanks in advance
Regards
VenuHi ,
Thanks for all
Issue is resolved by myself.
Instead of update Kernel to 640 , I have downloaded latest 620 kernel patch on IA 64 .
Since my production server is running on x86 and 620 kernel , i have downloaded 620 kernel for IA 64 .
That resolved my issue.
Regards
Sai -
my daughter has not used her ipod touch for 16 months and has forgotten her passcode. restore factory settings keeps failing due to a software update failure!
how can i get this ipod reset. She now has an iphone so this is going to be used by someone else in the family and should be simple to do but itunes just keeps booting it out even though it recognises that it was previously connected to our itunes account as all of the children were on my accountThat has nothing to do with an update server. Do the following:
Place the iOS device in Recovery Mode and then connect to your computer and restore via iTunes. The iPod will be erased.
iOS: Forgot passcode or device disabled
If recovery mode does not work try DFU mode.
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
For how to restore:
iTunes: Restoring iOS software
To restore from backup see:
iOS: Back up and restore your iOS device with iCloud or iTunes
If you restore from iCloud backup the apps will be automatically downloaded. If you restore from iTunes backup the apps and music have to be in the iTunes library since synced media like apps and music are not included in the backup of the iOS device that iTunes makes.
You can redownload most iTunes purchases by:
Downloading past purchases from the App Store, iBookstore, and iTunes Store
If problem what happens or does not happen and when in the instructions? When you successfully get the iPod in recovery mode and connect to computer iTunes -
Hello All,
Can anyone please, please help me out?!!! I really would appreciate any possible help. I've searched every where seeking a solution and have yet to have found one.
I cannot get appServer8 up and running without a "server startup failed" error. I am running WinDozeXP Pro.
I tried re-installing, seperate bundle and full bundle downloads, checking system/global variables, path/classpath for spaces and quotes, followed all troubleshooting docs, checked the <http-listener> default ports in the domain1/config/domain1.xml
Startup shows: Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Press any key to continue . . .
Shut down shows: The domain (domain1) isn't running.
CLI157 Could not stop the domain domain1.
Press any key to continue . . .
Server log shows:
[#|2005-06-05T13:28:06.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/jdk1.5.0_03\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:/jdk1.5.0_03/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\jdk1.5.0_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\jdk1.5.0_03\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\System32;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/jdk1.5.0_03/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-06-05T13:28:12.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-06-05T13:28:13.625-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-06-05T13:28:15.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-06-05T13:28:16.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-06-05T13:28:19.937-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-06-05T13:28:20.312-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2005-06-05T13:28:22.187-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:22.218-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1375 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:22.906-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-06-05T13:28:23.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2005-06-05T13:28:23.140-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.171-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-06-05T13:28:23.328-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 73269464414158848|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2005-06-05T13:28:23.859-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4438 msec, Total EJB Compiler Module Time: 4016 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 4016 msec, CMP Generation: 641 msec (15%), Java Compilation: 3297 msec (82%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:28.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-06-05T13:28:28.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:28.265-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.406-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 73269464784896000|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-06-05T13:28:29.109-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:29.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-06-05T13:28:29.281-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.421-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-06-05T13:28:29.453-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-06-05T13:28:29.453-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.484-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-06-05T13:28:29.578-0700|INFO|sun-appserver-pe8.1_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-06-05T13:28:31.046-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:101)
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)
Caused by: java.io.IOException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
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:173)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:93)
... 3 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
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)
... 5 more
Caused by: java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
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)
... 9 more
Caused by: java.net.ConnectException: Connection timed out: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 14 more
|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-06-05T13:28:52.546-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:118)
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)
|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:52.562-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/06/05 13:28:52]|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-06-05T13:28:53.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-06-05T13:28:53.015-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Thanks in Advance,
~StacyIs your windoze machine on the network ? Does this machine have a firewall ? Does it have a static IP address or a DHCP ? Can you check if port 8686 is being used by some other process ?
If you have checked all of the above, not really sure what else could be the problem. I have installed AS8.1on a wondoze xp laptop and it's running merrily. -
Sun AppServer 8-Startup failed
Hello All,
Can anyone please, please help me out?!!!
I cannot get appServer8 up and running without a "server startup failed" error. I am running WinDozeXP Pro.
I tried re-installing, seperate bundle and full bundle downloads, checking system/global variables, path/classpath for spaces and quotes, followed all troubleshooting docs, checked the <http-listener> default ports in the domain1/config/domain1.xml
Startup shows: Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Press any key to continue . . .
Shut down shows: The domain (domain1) isn't running.
CLI157 Could not stop the domain domain1.
Press any key to continue . . .
Server log shows:
[#|2005-06-05T13:28:06.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/jdk1.5.0_03\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:/jdk1.5.0_03/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\jdk1.5.0_03\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\jdk1.5.0_03\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\jdk1.5.0_03\bin;C:\WINDOWS\System32;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin;C:\apache-ant-1.6.2\bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/jdk1.5.0_03/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-06-05T13:28:12.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-06-05T13:28:12.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-06-05T13:28:13.625-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-06-05T13:28:14.234-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-06-05T13:28:15.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-06-05T13:28:15.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-06-05T13:28:16.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-06-05T13:28:19.937-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-06-05T13:28:20.312-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\MEjbApp.ear for autodeployment.|#]
[#|2005-06-05T13:28:22.187-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:22.218-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2005-06-05T13:28:22.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1375 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:22.906-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2005-06-05T13:28:23.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2005-06-05T13:28:23.140-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.171-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2005-06-05T13:28:23.328-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 73269464414158848|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-06-05T13:28:23.531-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
[#|2005-06-05T13:28:23.859-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2005-06-05T13:28:27.875-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2005-06-05T13:28:27.984-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 4438 msec, Total EJB Compiler Module Time: 4016 msec, Portion spent EJB Compiling: 90%
Breakdown of EJBC Module Time: Total Time for EJBC: 4016 msec, CMP Generation: 641 msec (15%), Java Compilation: 3297 msec (82%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2005-06-05T13:28:28.031-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2005-06-05T13:28:28.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.250-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:28.265-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2005-06-05T13:28:28.406-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 73269464784896000|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-06-05T13:28:29.093-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-06-05T13:28:29.109-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:29.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-06-05T13:28:29.281-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.421-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-06-05T13:28:29.453-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-06-05T13:28:29.453-0700|WARNING|sun-appserver-pe8.1_01|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|#]
[#|2005-06-05T13:28:29.484-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-06-05T13:28:29.578-0700|INFO|sun-appserver-pe8.1_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-06-05T13:28:31.046-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.062-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.156-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:31.203-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:101)
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)
Caused by: java.io.IOException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
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:173)
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:93)
... 3 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]
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)
... 5 more
Caused by: java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
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)
... 9 more
Caused by: java.net.ConnectException: Connection timed out: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 14 more
|#]
[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-06-05T13:28:52.546-0700|WARNING|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException
at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:118)
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)
|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-06-05T13:28:52.546-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-06-05T13:28:52.562-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2005/06/05 13:28:52]|#]
[#|2005-06-05T13:28:52.781-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-06-05T13:28:52.796-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
[#|2005-06-05T13:28:53.015-0700|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
[#|2005-06-05T13:28:53.015-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
Thanks in Advance,
~Stacy[#|2005-06-05T13:28:52.546-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]4 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://romeo:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: romeo; nested exception is:
java.net.ConnectException: Connection timed out: no further information]|#]
is the start of your problem, but I expect you've guessed that.. Have you googled for the messages? is host romeo available on that port??? -
Post Author: LeeCUK
CA Forum: Authentication
I have installed Enterprise XIR2 onto a Windows 2003 server and all services are running.I have installed the client on another windows 2003 server and I can connect to the console via the web.
Firstly desktop intel would not work and gave me the error below, however a new entry appeared in my server dropdown with servername (.Net Portal) and after selecting this Desktop intell worked.
When I try to run designer I dont get the extra server in the dropdown nor does it connect when tryped manually and gives me the same error I was getting for desktop intel.
Im using enterprise authentication
Has anyone figured this out please?
The error im getting is below[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(hr=#0x80042a01)Post Author: jsanzone
CA Forum: Authentication
LeeCUK:
The [repo_proxy 13] error seems to be a catch-all for BO in that I've worked with this software (XI R2) for 1 1/2 years now and each time I've encountered [repo_proxy 13] it has been for a different reason, thus, you're going to have to apply troubleshooting checks all over the place until you find the problem. In my particular case I just resolved my [repo_proxy 13] error I've been working on this week, and here was my scenario. Our server in the lab died due to a hard drive failure, so we cut our losses and installed a new & more powerful server. When the rebuild was done I could not connect from my laptop to the repository via Designer (good old [repo_proxy 13] error). After much angst, etc, etc I found out that the servers in the CMC (/businessobjects/enterprise115/admin/en/admin.cwrwere">http://<server>/businessobjects/enterprise115/admin/en/admin.cwrwere) were all down except for one (even though CCM showed all servers "up"). When I went to start the servers in the CMC I was prompted for an account, and no matter what account I tried it won't work. So I went back to the CCM servers and stopped them all, then changed the default account it was using from LocalSystem to the administrator account, restarted all servers in CCM, went back to CMC and noted that all servers were now up as well. Then I went back to my laptop and used Designer and was able to successfully log in. Thus, the end of my story, however, it seems that many [repo_proxy 13] errors have different beginning and endings. For instance, a year ago I had the same [repo_proxy 13] error and brought it to BO tech support. They determined that I had to uninstall my client from my laptop, clean out the registry for any references to BO keys, and remove the c:\program files \Business Objects folder, then reinstall, and sure enough it worked in that case, but not in this case when I tried it again. By digging deeper I found out the root cause to my current problem, and voila, I'm in!
Good luck! -
Import of a request failing : ERROR: connect failed due to DbSL load lib fa
Hi,
I am using ecc6, on hp-unix and oracle as database.
When i try to import a request from stms, i get this error.
DURING IMPORT ERROR:
Transport control program tp ended with error code 0249
Errors: connect failed due to DbSL load lib failure
TP ERROR:
Transport control program tp ended with error code 0249
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT E07K901512 DEV client100 U01 pf=/usr/sap/tr
Return code: 0249
Error text: connect failed due to DbSL load lib failure
Request: E08K901525
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.
THEN I TRIED TO IMPORT USING TP COMMAND:
WITH OUT DIR_LIBRARY
% ./tp connect DEV
This is ./tp version 370.00.09 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
% ./R3trans -d
This is ./R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).
unicode enabled version
2EETW169 no connect possible: "environment variable DIR_LIBRARY is not set."
./R3trans finished (0012).
% # export DIR_LIBRARY=/usr/sap/DEV/SYS/exe/run
% ./R3trans -d
This is ./R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = ORACLE --- ORACLE_SID =
'DEV'"
./R3trans finished (0012).
% ./tp connect DEV
This is ./tp version 370.00.09 (release 700, unicode enabled)
E-TPSETTINGS could not be opened.
EXIT
ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
COULD SOMEONE GIVE ME A SOLUTION TO OVERCOME THIS.
YOUR SOLUTION AND GREATELY APPRITIATED.
REGARDS,
DHANANJAYHi Dhanajay,
Firstly check if R3trans -d is working fine.
If so, please chek if the following parameters are set properly.
DIR_LIBRARY=/usr/sap/<SID>/SYS/exe/run
TRANSDIR = ....\trans
<SID>/DBHOST = <HOSTNAME>
<SID>/DBNAME = <SID>
<SID>/DBTYPE = ora
Execute the below command and check the transport profile:
tp check all pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
Please confirm the permission of the /oracle/ directory
The permission of the /oracle should be 755.
Also check if the import queue is not locked.
Also please ensure the Kernel is of latest version, if not, please update the DBSL shared library.Please look at the note 19466.
Finally you can try once distributing and activating the transport routes once.
When you executed command R3trans -d logfile trans.log will be created.
Please check this file for exact error information.
Paste the log file here.
Let us know the outcome.
Regards,
Sujit.
Maybe you are looking for
-
What DAC is used in Z10? How does Z10 sounds like as a music player?
Can't find anythere what DAC is used in Z10 device? Is there any information / test result on sound quality (sound quality = quality of audio output through the headphone connector) Solved! Go to Solution.
-
Hi there, I would like to have the output stream coming from the server to the client displayed on a JTextArea. However, because the coming file is a text document that had its file name passed as a local variable in the main method header with Strin
-
BEA Workshop Studio 3.2: Server classpath customization & Remote Debugging
BEA Workshop Studio 3.2: The server classpath customization and remote debugging issues have been fixed in the 3.2 release, which is now available for download at http://workshopstudio.bea.com/download.do. Workround for the 3.1 release: By switching
-
Siri not showing up after upgrade to IOS 6
I have an IPAD 3. I updated to IOS last night. But I am not seeing Siri anywhere. Even Settings>General>Siri is not showing. I am wondering if I made an error in installing as another Ipad is showing Siri correctly. How do I fix this?
-
Erron in Mini HTTP server.
Hi, <b>I linked one B1 company with R/3 via B1i. R/3 company is 'eccides' But when i start mini Http -> i get following error.</b> <i>Failed to connect eccides com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gate way fai