Sun 1 RH8, Debian fails
Hello All,
I am brand new to J2. I am trying to install J2SE on two Linux systems just to learn things and have something to play with when I read the tutorial book - A Redhat 8.0 Intel and a newest Debian intel.
I downloaded:
J2re-1_4_1...i585.bin
J2sdk-1_4_1...i585.bin
J2sdk-s1studio-1_4_1...linux.bin
I am trying to install in the /usr/local directory logged in as root.
On both Linux systems, the J2re and J2sdk bin files seem to install OK. I get corresponding directories and the script says "done".
Q: Is there a way to test the installs to see if they are working?
On both systems the s1studio fails in different ways.
On the Linux RH8 system, I run the bin file and get "Install shield Wizzard Init", then 5 or so lines of 40 or so dots quickly and 1 line of 3 dots slowly. The install wizzard opens. I go through the install. The last dialog screen says "run /usr/local/..../runide.sh to start ide". But, there is no runide.sh file in the specified dir or anywhere else. I looked at the log file in the dir where runide was supposed to be and the last lines had a "Null return" error and nothing much else very informative.
On the Debian system, I run the bin file and get "Install shield Wizzard Init", then 5 lines of 40 dots quickly and 1 line of 3 dots slowly. Then the command line prompt returns and the install wizzard never opens. No error messages. No studio dir.
Wonderful software SUN...
Any ideas or suggestions are very appreciated.
Thanks,
Barry.
Hi, Barry,
First of all, I'd like to tell u the differences/similarities between the j2re, j2sdk and j2sdk-s1studio installers, which is quite useful to know.
These r what each installer is for:
1. j2re - Java Runtime Environment or JRE;
2. j2sdk - Software Development Kit or SDK (used to known as JDK or Java Development Kit; renamed to SDK in 1999), and in your case it's the Standard Edition for the SDK;
3. j2sdk-s1studio - cobundle for SDK and Sun ONE Studio.
The JRE is for running Java programs. The SDK is, again, as the name suggests for Java program development. It includes command-line development tools, such as a compiler and a debugger, and also the JRE. So if u run the j2sdk installer, u don't need to run the j2re installer. And since the j2sdk-s1studio cobundle includes the SDK, u don't need to run the j2sdk installer if the cobundle installer installs the cobundle without problem.
Not sure if u've had a look at the troubleshooting section of the s1studio getting started guide? If u haven't, for the Debian problem, the last table cell at the bottom of p.53 of
http://forte.sun.com/ffj/documentation/s1s41/getstartedce41.pdf
might give u some ideas (hopefully useful).
It seems there could a possibility that for both the Red Hat and Debian problems, the cause might be a corrupted installer file. U could try checking the file size as said here:
http://java.sun.com/j2se/1.4.1/install-s1s4-linux.html
and c if u've missed a few other things noted here for the cobundle installation.
Hope this is where the problem is. Good luck.
Jack
Similar Messages
-
Hi There,
I am trying to deploy an EJB module into the Sun Application Server 8 using ANT scripts.
The given below is the script, I use.
<taskdef name="sun-appserv-deploy"
classname="org.apache.tools.ant.taskdefs.optional.sun.appserv.DeployTask">
<classpath>
<pathelement location="${appSerLib}/sun-appserv-ant.jar"/>
</classpath>
</taskdef>
<target name="doDeploy">
<sun-appserv-deploy file="${destDir}/${ejbJarName}" name="SampleEjb"
force="true" type="ejb" verify="false" user="admin" password="#infy123"
host="localhost" port="4848" generatermistubs="true" asinstalldir="${appServer}"/>
</target>
The build fails throwing the below error
A Sun Java System Application Server 8 admin CLI class could not be found (com.sun.enterprise.cli.framework.InputsAndOutputs). Use the asinstalldir attribute, set the asinstall.dir property, or add the appropriate JARs to the classpath.
See the script I have mentioned the asinstalldir attribute in the sun-appserv-deploy.
Need help to resolve it.
..Thiruppathy.RUse the 'asant' command to run your script rather than 'ant'. This will set up the required environment variables to allow the task to execute.
Cheers
Spencer -
Sun Update Connection install fails on Patch 119574-02
Just finished installing Solaris 10 (3/05) on my brand new Sun Blade 1500. I then downloaded the latest version of Sun Update Connection, but the installer fails as follows:
# ./installUpdateConnection
Adding patch 119574-02
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
119574-02
Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Patch 119574-02 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/119574-02/log for details
Patchadd is terminating.The above log file reads as follow:
# cat /var/sadm/patch/119574-02/log
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
/export/home/richard.cross/updateConnection/patches/119574-02/SUNWcsu/install/checkinstall: /export/home/richard.cross/updateConnection/patches/119574-02/SUNWcsu/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.Where have I gone wrong? I haven't done anything to my system between installing Solaris 10 and downloading SUC, so why is it complaining about an existing patch?Solved it. Solution is to move all of the patches into /var/spool/pkg and run patchadd on each one in there (in the right order).
-
SUN Cluster.PMF.pmfd Failed to stay up
Dear All,
Please help I am facing problem and unable to start sun cluster concurrent manager resource group it is showing me status "starting" but unable to start please find below the log
Oct 16 14:06:24 iat-dc-ebpdb02 Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="prdclone-rg,PRODE-cmg-res,0.svc", cmd="/bin/sh -c /opt/SUNWscebs/cmg/bin/start_cmg -R 'PRODE-cmg-res' -G 'prdclone-rg' -C '/bkpclone/acvetprdcm/inst/apps/PRODE_iat-dc-prdclone' -U 'acvetprdcm' -P 'apps' -V '12.0' -S 'PRODE' -O '/bkpclone/acvetprdcm/apps/tech_st/10.1.2' -L '77' ", Failed to stay up.
Oct 16 14:06:24 iat-dc-ebpdb02 Cluster.PMF.pmfd: [ID 534408 daemon.notice] "prdclone-rg,PRODE-cmg-res,0.svc" restarting too often ... sleeping 8 seconds.
Oct 16 14:06:32 iat-dc-ebpdb02 SC[SUNWscebs.cmg.start]:prdclone-rg:PRODE-cmg-res: [ID 567783 daemon.error] startebs - ld.so.1: sh: fatal: /usr/lib/secure/libschost.so.1: open failed: No such file or directory
Oct 16 14:06:32 iat-dc-ebpdb02 Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="prdclone-rg,PRODE-cmg-res,0.svc", cmd="/bin/sh -c /opt/SUNWscebs/cmg/bin/start_cmg -R 'PRODE-cmg-res' -G 'prdclone-rg' -C '/bkpclone/acvetprdcm/inst/apps/PRODE_iat-dc-prdclone' -U 'acvetprdcm' -P 'apps' -V '12.0' -S 'PRODE' -O '/bkpclone/acvetprdcm/apps/tech_st/10.1.2' -L '77' ", Failed to stay up.
Oct 16 14:06:32 iat-dc-ebpdb02 Cluster.PMF.pmfd: [ID 534408 daemon.notice] "prdclone-rg,PRODE-cmg-res,0.svc" restarting too often ... sleeping 16 seconds.
Oct 16 14:06:48 iat-dc-ebpdb02 SC[SUNWscebs.cmg.start]:prdclone-rg:PRODE-cmg-res: [ID 567783 daemon.error] startebs - ld.so.1: sh: fatal: /usr/lib/secure/libschost.so.1: open failed: No such file or directory
kindly help to resolve the issue.
Regards,Thanks unable to resolve the issue.
Please see below are my setup:
Database tier:
Sun cluster 3.2u3
oracle EBS 12.1.3
Two node sun cluster active node a1 and passive b1.
Application Tier:
App01
I want to move concurrent manager from appo1 to database tier what I did below was my action plan.
step-1 cloned application(app01) to DB on primary host and enabled only batch processing and other all disabled using same virtual host as we have same defined virtual host for database resource group LH (vhost)
the problem is when I start CM it started but immediately stop when I cloned again with physical host
CM is started and working fine but I need anyone to tell me how can i start manually and move to CM resource sun cluster.
Question: Can I choose same LR host for application or I need to put physical name of the primary node during cloning process as I said same we are using LR host for DB tier or need to add new virtual host for CM.
thanks
Regards, -
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??? -
RAC using SUN Geo Clusters with Fail over
Hi ,
My customer is in the process of investigating and deploying Sun GeoClusters to fail over a RAC from one location to another, the distance between the primary and fail over site is 1200km, they are going to use TrueCopy to replicate the storage across the sites.
I am in the process of gathering information and need to find out more detail and if any one has any knowledge of this software.If anybody knows about the clients who are using(some urls) the same please let me know.
Regards
ManojTrueCopy is a way of replicating storage offsite. RAC works using a single source for the database. That means that RAC can not be used simultaneously at both locations with the files being used locally.
If my memory serves me well, Hitachi TrueCopy was OSCP (oracle storage compatiblity program) certified, but the OSCP program seems to be discontinued per januari 2007 (see http://www.oracle.com/technology/deploy/availability/htdocs/oscp.html)
That means that you can use TrueCopy to replicate the storage layer to another location (according to the OSCP note), and use the replicated storage to startup the RAC database in case of failover. -
Sun Ultra 20 M2 fails to boot if an USB storage device is plugged in
Hi.
If any of my LaCie external USB disks are plugged in my Sun Ultra 20 M2, BIOS hangs and fails to boot. Bios is upgraded with latest version (Tools and drivers CD v. 1.6a). Furthermore, my LaCie mobile disk is listed on Solaris HCL.
LaCie Lacie Mobile Hard Drive 250 GB
Any hint on how to troubleshoot this issue?
Thanks,
Enrico.I indeed each a test with every USB device I could collect, including keyboards, and I did have the same problems with others disks, although no one with other kind of hardware.
Not being a problem of my disk, is it possible to file a bug for a workstation BIOS?
Thanks,
Enrico, -
Sun implementation of WebRowSet fails for FLOAT values
I have been attempting to use the sun reference implementation of WebRowSet class to query a vendor table and serialize the rowset to XML.
Oracle's proprietary RowSet package does not include an implementation of WebRowSet.
For simple tables everything works ok. However, a few of the vendor's more robust tables define numeric columns as FLOAT(126) in the DDL. These columns return thru the Oracle driver as type NUMBER (numeric Type 2) with driver recommended java class java.math.BigDecimal. The Precision is correctly returned as 126.
The problem seems to be that the driver considers these columns to have a Scale of -127 which is nonsensical. When populating the WebRowSet from a ResultSet an exception is thrown which indicates that a negative scale has been encountered.
Since WebRowSet can only be populated from a ResultSet and the scale property is returned by the driver, this means that WebRowSet is effectively unavailable for Oracle databases.
BTW, our Oracle database is v 9.2.0.4.0 and the Oracle JDBC driver is 9.2.0.5. The WebRowSetImpl class was downloaded from javasoft this month - it is version 1.01.
Has anyone else observed FLOAT columns with negative scale ? Is there any way to coerce the driver into returning a more accurate scale ?I have been attempting to use the sun reference implementation of WebRowSet class to query a vendor table and serialize the rowset to XML.
Oracle's proprietary RowSet package does not include an implementation of WebRowSet.
For simple tables everything works ok. However, a few of the vendor's more robust tables define numeric columns as FLOAT(126) in the DDL. These columns return thru the Oracle driver as type NUMBER (numeric Type 2) with driver recommended java class java.math.BigDecimal. The Precision is correctly returned as 126.
The problem seems to be that the driver considers these columns to have a Scale of -127 which is nonsensical. When populating the WebRowSet from a ResultSet an exception is thrown which indicates that a negative scale has been encountered.
Since WebRowSet can only be populated from a ResultSet and the scale property is returned by the driver, this means that WebRowSet is effectively unavailable for Oracle databases.
BTW, our Oracle database is v 9.2.0.4.0 and the Oracle JDBC driver is 9.2.0.5. The WebRowSetImpl class was downloaded from javasoft this month - it is version 1.01.
Has anyone else observed FLOAT columns with negative scale ? Is there any way to coerce the driver into returning a more accurate scale ? -
RMI stub compilation in Sun AS 8.1 failed with Java 5
I made some tests running the Sun AS 8.1 on Java 5, but I got exceptions when trying to generate static RMI stubs for an application which was compiled on Java 5. I've read from the forums that Java 5 is not officially allowed to use, although most things seem to working well.
So I won't complain about the problems I accountered but I'd like to know if there are already some announcements when Java 5 can officially be used with Sun AS?Slightly different issue, but you shouldn't need to statically generate RMI stubs when using AS 8.x or later. By default the appserver uses dynamic RMI-IIOP stubs that are generated on-the-fly. As long as you are invoking the Remote EJBs from within a web/ejb component in the appserver, from within an Application Cliient container, or from a stand-alone client that uses the appserver's naming service (meaning the use of new InitialContext() with appserv-rt.jar in the classpath) you shouldn't need any static RMI-IIOP stubs.
--ken -
Dear all ,
I haved problem when access to CAM when I login success I can't access to Configuration Service , I met notification: {color:#0000ff}An error occurred during login . Unable connect to CIMOM .Please review the system logs or contack your system administrator .
{color:#000000}Please help me !{color}
{color}I see that you asked the same question on the cacti forums and I can provide much the same answer. I don't have a 6920, I thought it would not scale enough so I got a 9990...
Anyway, I would install StorAde and configure it for the 6920. Then run the folowing command to see what StorAde is looking at:
rasagent -d 3 -r
The output can determine what StorAde knows about the 6920. Look for any snmpwalk in particular. Once you get that information, you can get cacti to graph it if it is graphable.
Normally I just do an snmpwalk of the agent on the system and then I can figure out roughly what is available. It takes a bit of skill but I imagine you can figure it out.
BTW, I will be going to the Czech Repubic soon. I believe you are there by your email address on the cacti forum..
Stephen -
Hi Techies,
I am facing small problem with deployment thru cosole deployment.. details below.I am using Jdeveloper 11.1.2.1.0 ver.
I am able to deploy the application thru Jdeveloper Run/Debug Option. But If i create an EAR file and deploying thru server console , then i am getting below error. hence its not deploed.
.Till yesterday it was working ..Just to day i am facing this issue.What can be the reasons for this ?
Can anyone help me plz..
---------------------- Error Message on log---------------------------------------------------------------------------------
<ConfigureListener> <contextInitialized> Critical error during deployment:
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
... 38 more
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver.
java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:294)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
Truncated. see log file for complete stacktrace
Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! javax.faces.el.VariableResolver
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:108)
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:327)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1374785326461' for task '2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:54 PM GMT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'EmersonMMI_QACerts'.>
<Jul 25, 2013 8:50:54 PM GMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
Truncated. see log file for complete stacktrace
>
<Jul 25, 2013 8:50:55 PM GMT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ClassNotFoundException: javax.faces.el.VariableResolver
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
at com.sun.faces.util.Util.loadClass(Util.java:291)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)
at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(ApplicationConfigProcessor.java:626)
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:302)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:216)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:338)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)..
[03:58:26 AM] Deployment cancelled.
[03:58:26 AM] ---- Deployment incomplete ----.
[03:58:26 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Thanks,
Rajeshjava.lang.ClassNotFoundException: javax.faces.el.VariableResolver
Add the jsf-api.jar to the runtime classpath of the server. -
Com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED!
Hi,
I installed new 5158 build and I get this exception wlile trying to run MyApp:
<Dec 12, 2008 11:58:00 AM CET> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED!
Source Document: zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/MyApp/saai2d/war/WEB-INF/lib/adf-controller.jar!/META-INF/faces-config.xml
Cause: Class 'oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener' is missing a runtime dependency: java.lang.NoClassDefFoundError: javax/faces/event/PhaseListener.
com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED!
Source Document: zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/MyApp/saai2d/war/WEB-INF/lib/adf-controller.jar!/META-INF/faces-config.xml
Cause: Class 'oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener' is missing a runtime dependency: java.lang.NoClassDefFoundError: javax/faces/event/PhaseListener
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:211)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:184)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
Truncated. see log file for complete stacktrace
{code}
This app worked with 5156, any help?
Pedjajava.lang.ClassNotFoundException: javax.faces.el.VariableResolver
Add the jsf-api.jar to the runtime classpath of the server. -
Problem with Java System Application Server *(Sun one 8 or J2EE 1.4 app server)
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.VeerendraM.S. Veerendra-
This is a known incompatibility, described at:
http://support.solarmetric.com/Ticket/Display.html?id=14082
Can you try the workarounds listed at:
http://forum.java.sun.com/thread.jsp?forum=136&thread=499803&tstart=0&trange=15
and let us know if it works?
In article <[email protected]>, veerendra wrote:
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
Deploying a WAR file to Sun App Server 8.1 PE
So I thought that if I downloaded Sun App Server PE 8.1 and put it on my soon-to-be production machine, it should be pretty easy right?
Nope. So I have JSC update 6 (which includes Sun Application Server 8.0) (God how I wish there was a catchy name like Tomcat or something)
And I have a machine running a good copy, installed and everything, of Sun Application Server 8.1 Platform Edition (another catchy name) up on the production target.
I create a WAR file in JSC, scp it up.
Then try to deploy it - so I get bit by the no DB connection thing.
Ok, but when I copy each of my connection's attributes (the driver (which I did copy up to the lib directory) is MySQL's Connector/J)
I copy the username, password, URL and DriverClass attributes to the connection pool.
I still get a
"Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.sun.sql.datasource.DriverAdapter"
when I try to Ping the ConnectionPool
I have javax.sql.DataSource as the resource type... (same as 8.0 uses)
what JAR file is DriverAdapter in? anyone know?
cheers,
KrisOkay. mysql folks - this works......
here's what happened, on the production server, different from the dev machine....
mysql 4.1.9
sun application server platform edition PE 8.1
connector/j - latest
and on the dev machine: JSC Update 6 and the app works fine on the dev machine.
first, there is a JAR file in ~whatever/Create/SunAppServer/lib/ named
driveradaptor.jar
and it it comtains
com.sun.sql.datasource.DriverAdapter
which 8.1 ain't got
and should be copied up to
/installdir/SunAppServer/domains/domain1/lib/ext/driveradapter.jar
(domain1 is your app svr domain that runs your app.)
your Connector/J JAR needs to go here too. I used:
mysql-connector-java-3.2.0-alpha-bin.jar
downloaded from mysql.com.
and then there is the whole thing about Added Properties in the Connection Pool page inside the 8.1 Admin Console (which is nice work guys). Gawd, I added a bunch of properties and am, frankly, not sure which ones actually work (for the Ping, for the initial connection creation and the eventual successful connection all seem to use different combinations...)
and I found this in the domain's domain.xml once all the admin console page filling was done - but you'll need to add each one as a Property in the connection pool:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.sun.sql.datasource.DriverAdapter" fail-all-connections="false" [blah...]
<property name="Username" value="root"/>
<property name="Password" value="secret"/>
<property name="ValidationQuery" value="SELECT 1"/>
<property name="DriverClassName" value="com.mysql.jdbc.Driver"/>
<property name="LoginTimeout" value="0"/>
<property name="Url" value="jdbc:mysql://localhost/databasename?autoReconnect=true"/>
<property name="User" value="root"/>
<property name="password" value="secret"/>
<property name="PasswordCredential" value="secret"/>
</jdbc-connection-pool>
(and you see how User and Username and username are all the same thing? well, different parts of 8.1 seem to use different attributes...)
Just keep Adding Properties in the connection pool until you get them all....
Oh and, the two key class references for the pool are:
datasource class: com.sun.sql.datasource.DriverAdapter
resource type: javax.sql.ConnectionPoolDataSource
Finally: in the /installdir/SunAppServer/domains/domain1/applications/j2ee-modules/YourAppName/WEB-INF/
your 'sun-web.xml' (don't delete it, like some have advocated, I think that wrong) needs to look like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd">
<sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>/yourcontext</context-root>
<resource-ref>
<res-ref-name>jdbc/Yourname</res-ref-name>
<jndi-name>jdbc/Yourname</jndi-name>
<default-resource-principal>
<name>root</name>
<password>secret</password>
</default-resource-principal>
</resource-ref>
</sun-web-app>
and I think that's all of it. the only Bug I would I would say is that the sun-web.xml should have the right res-ref-name, but then I think the Creator Team knows this and will fix it sometime soon.
cheers,
and Roger Federer lost in the Aussie Open. (I think he lost tomorrow too, that whole time zone thing being so damn Einsteinian...)
-Kristofer -
SAPINST failed step "Install Oracle Database (post processing)"
i will install ep6.0 with oracle database 9.2.0.4 on sun solaris.
the SAPINST failed at the step "Install Oracle Database (post processing) with follow error.
the oui - installer (runinstaller) finished sucessfully.
ERROR 2004-08-31 16:05:17
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-01501: CREATE DATABASE failedORA-01101: database being created currently mounted by some other instance
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning optionJServer Release 9.2.0.4.0 - Production. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
no user is logged on the Database. Database is not running (is shutdowned and unmounted). No Oracle process is running.
pleas help.
thanks
armin hadersbeckHi Armin,
We're going to install EP 6 stack3 with Oracle 9.2.0.4 and Solaris 9. We have exactly the same error as you during sapinst.
How do you solved that ?
Thanks a lot for your help,
Regards from Mexico,
Diego
Maybe you are looking for
-
Equium 100-147 upgrade to windows vista home premium
Have been upgraded for 9 months but get compatibility error windows appearing for various toshiba drivers. On opening toshiba assist/protect&fix/preinstalled drivers/tools&utilities it lists everything as my old xp media centre. Can this page be upgr
-
How to create punlic connection in discoverer plus
Hi All, There is one public connetion in discoverer plus but now it is disable , i dont know how to create public connetion pls help me its urgent thanks regards,
-
Problem installing SD Firmware v2.0. Help needed!
I installed the firmware through the Apple Software Update tool and upon restarting my computer got stuck. I had just rebooted the computer, after installing the QT 7.1.1 update. I re-ran the SW, it popped the Firmware update, I clicked install, it d
-
JSF Validation failure causes entered values to be lost
I've created a JSP that has required="true" and a requiredMessage on several elements. If any one element on the page fails it's validation on submit(ie was left blank), when the screen is redrawn all the entered values have disappeared. This is obvi
-
DEAR ALL, I have two questions regarding proxy server 3.6: 1. I would like to know the Maximum number of simultaneous requests a proxy server can hold. 2. Maximum number of simultaneous connections a proxy server can hold. Thanks alot, Scotty