Sun Java 1.4.2+
I can run Schwab Streetmart trading platform on my Imac but am promted on my iPad2 that it needs Sun Java 1.4.2+
any solutions??
There is no way to view Java on the iPad. You'll have to go back to your iMac to use this site (or connect to your desktop remotely through an app such as Splashtop).
Similar Messages
-
Sun java convergence error - Message no longer exist
Hi
Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)
libimta.so 7.3-11.01 64bit (built 19:44:36, Sep 1 2009)
Using /opt/sun/comms/messaging64/config/imta.cnf (not compiled)
SunOS 5.10 Generic_141445-09 i86pc i386 i86pc
We moved mailboxes from one server to another. After that we have problems with some accounts. Users see their messages in Sun Java Convergence but can't open and read it. Error appears: Message no longer exist. We tried reconstruct command but it didnt helped.
Thanks in advanceluk4s1984 wrote:
Did you also transfer across the mboxlist database? Were both the source/destination Messaging Server instances down when you performed the move?I didn't move mboxlist database and bouth source and destination instances were up.This method of migrating mailboxes is bound to cause problems. Why did you choose to use this method rather then use the rehostuser command?
Did you change the users mailhost: parameter?I didn't changed mailhost.Do both the source and destination systems have the same hostname?
What exact reconstruct command(s) did you run?reconstruct -aIf you run "reconstruct -r user/<uid>" for one of the accounts reporting problems, are any errors reported?
Check the imap and http log files when the error occurs -- do you see any errors?There is no errors in imap and http logs.Interesting. Which emails return "message no longer exists"?
Newly delivered (unread) emails, emails delivery prior to migration, emails delivered after migration or some combination of all three?
Regards,
Shane. -
Adding a JDBC driver in Sun Java System Web Server 7
I'm trying to configure JDBC database connection pooling for a Microsoft SQL Server 2005 Express Edition though the Sun Java System Web Server 7 administration console. I don't want to use the MSSQL JDBC driver that comes bundled with the SJSWS 7. So I've downloaded the lastest MSSQL JDBC driver from the Microsoft website and put in the "lib" subdirectory of the SJSWS installation directory. So when I go to add a new JDBC resource through the administration console, the newly added MSSQL database driver doesn't appear in the "Driver Vendor" drop-down box.
How do I add the downloaded JDBC driver to the server so that it appears in the "Driver Vendor" drop-down under "Create JDBC resource".Check this documentation from MS on using the JDBC driver with DataSource
http://msdn2.microsoft.com/en-us/library/ms379052.aspx
SJS Web Server 7.0 should work with any driver that has support for javax.sql.DataSource. The great majority of drivers do.
So instead of using the driver name, use the DataSource class name:
com.microsoft.sqlserver.jdbc.SQLServerDataSource
The properties to add should be:
user=username
password=password
servername=sql_server_hostname
portnumber=sql_server_port
databasename=databasename
In general, all the setters required to get the datasource configured can be set as properties. -
Sun Java System Web Server 7.0 available
I am delighted to announce that Sun Java System Web Server 7.0 is now available for download, purchase, deployment, and more.
This release builds on the highly scalable and stable heritage of Web Server. It features an entirely re-designed Administration interface designed around clusters, easy access to frequently performed tasks, simplification of frequently performed tasks., and a fully scriptable command line interface featuring functional parity with the browser-based interface.
In addition to the administration changes this release features:
o Full 64-bit support for Solaris SPARC and Solaris AMD64 platforms
o Regular expression pattern matching for URL re-writing and mass hosting
o If/Then/Else constructs within request processing
o Advanced sed based input and output filters
o Dynamic loading of Certificate Revocation Lists (CRLs) without requiring daemon restart
o Elliptic Curve Cryptography (ECC)
o Built in request mapping for protection against abnormal load patterns and Denial of Service protection
o WebDAV ACL support
o Out-of-box Java support for Servlets 2.4, JSP 2.0, JSF 1.1, JSTL 1.1, JWSDP 2.0 based web services
o Java session failover and recovery within a cluster of peers
o Integrated HTTP reverse proxy User-Agent
o Bundled FastCGI client for use with third party scripting environments such as Perl, PHP, Ruby on Rails, etc
o Enhancement of perfdump, stats-xml, and SNMP as well as more ability to monitor the Java container and the ACL system
o Much more
The software can be downloaded from:
http://www.sun.com/download/products.xml?id=45ad781d
The documentation is available at:
http://docs.sun.com/app/docs/coll/1308.3If 7.0 was released, how come http://www.sun.com/webserver still only talks about 6.1?
-
How to make weblogic proxy to work on Sun Java system web server 7?
Hi Every one,
I am working on upgrade our Sun one 6.1 webserver to Sun Java system web server 7. Our website uses weblogic server to process jsp, web server only send static pages. I did all configurations as on Sun one. But somehow, the webserver does not forward "get jsp page" request to weblogic. The log record is:
for host 10.78.124.118 trying to GET /home.jsp, send-file reports: HTTP4142: can't find /www/a/WebServer7/docs/bmd9i/home.jsp (File not found)
home.jsp is at weblogic server.
And redirect "NameTrans fn="redirect" from="/" url="/home.jsp"" seems does not work. when I type on IE http://32.69.253.131/ (32.69.253.131 is http listener IP), it always shows index.html page under the document root.
Could some on can help? I am the first time to configurate web server. Thanks in advance.
The configuration files are like:
1. magnus.conf
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="/www/a/WebServer7/weblogic6.1sp6/libproxy.so"
Init fn="wl_init"
2. obj.conf
# Copyright 2010 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# You can edit this file, but comments and formatting changes
# might be lost when you use the administration GUI or CLI.
#<Object name="weblogic">
#Service fn="wl_proxy" WebLogicCluster="32.69.253.86:7210" ConnectTimeoutSecs="240" ConnectRetrySecs="60"
#</Object>
<Object name="default">
<Client method="TRACE">
AuthTrans fn="set-variable" remove-headers="transfer-encoding" set-headers="content-length: -1" error="501"
</Client>
#AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"
NameTrans fn="strip-params"
NameTrans fn="redirect" from="/" url="/home.jsp"
NameTrans fn="redirect" from="/index.jsp" url="/home.jsp"
NameTrans fn="redirect" from="/index.html" url="/home.jsp"
NameTrans fn="document-root" root="$docroot"
NameTrans fn="pfx2dir" from="/mc-icons" dir="/www/a/WebServer7/lib/icons" name="es-internal"
NameTrans fn="home-page" path="index.html"
<If $uri =~ "/*.jsp">
Service method="(GET|HEAD|POST|PUT)" fn="wl_proxy" WebLogicCluster="32.69.253.86:7210" ConnectTimeoutSecs="240" ConnectRetrySecs="60"
#Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl_proxy" WebLogicCluster="32.69.253.86:7210" ConnectTimeoutSecs="240" ConnectRetrySecs="60"
</If>
PathCheck fn="unix-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-compressed" check-age="off" vary="on"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain" charset="iso_8859-1"
ObjectType fn="set-default-type" charset="iso_8859-1"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="send-error"
Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
AddLog fn="flex-log" name="access"
</Object>
<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>
<Object name="send-precompressed">
PathCheck fn="find-compressed"
</Object>
<Object name="compress-on-demand">
Output fn="insert-filter" filter="http-compression"
</Object>
3.mime.types
I add one line: type=text/jsp exts=jspQuick obvious question - Are you positive you're editing the correct obj.conf? Check the config directory and see if there is a second one called something like <instance>.obj.conf (where <instance> is the name of your configured instance).
Alternatively you can grep for object-file in the server.xml to see which obj.conf the server is using:
# grep object-file server.xml
<object-file>bare-php.obj.conf</object-file>Assuming that you are editing the correct obj.conf file, are you making certain to restart Web Server after making your changes? -
SUN Java System Web Server 7.0U1 How to install certificate chain
I am trying to install a certificate chain using the SUN Java Web Server 7.0U1 HTTPS User interface. What I have tried so far:
1. Created a single file using vi editor containing the four certificates in the chain by cutting an pasting each certificate (Begin Certificate ... End Certificate) where the top certificate is the server cert (associated with the private key), then the CA that signed the server cert, then the next CA, then the root CA. Call this file cert_chain.pem
2. Go to Certificates Tab/Server Certificates
3. Choose Install
4. Cut and paste contents of cert_chain.pem in the certificate data box.
5. Assign to httplistener
6. Nickname for this chain is 'server_cert'
7. Select httplistener and assign server_cert (for some reason, this is not automatically done after doing step 5).
8. No errors are received.
When I display server_cert (by clicking on it), only the first certificate of the chain is displayed and only that cert is provided to the client during the SSL handshake.
I tried to do the same, except using the Certificate Authority Tab, since this gave the option of designating the certificate as a CA or chain during installation. When I select ed "chain," I get the same results when I review the certificate (only the first cert in the file is displayed). This tells me that entering the chain in PEM format is not acceptable. I tried this method since it worked fine with the F5 BIG-IP SSL appliance.
My question is what format/tool do I need to use to create a certificate chain that the Web Server will accept?turrie wrote:
1. Created a single file using vi editor containing the four certificates in the chain by cutting an pasting each certificate (Begin Certificate ... End Certificate) where the top certificate is the server cert (associated with the private key), then the CA that signed the server cert, then the next CA, then the root CA. Call this file cert_chain.pemIn my opinion (I may be wrong) cut and pasting multiple begin end
--- BEGIN CERTIFICATE ---
... some data....
--- END CERTIFICATE ---
--- BEGIN CERTIFICATE ---
... some data....
--- END CERTIFICATE ---is NOT the way to create a certificate chain.
I have installed a certificated chain (it had 1 BEGIN CERTIFICATE and one END CERTIFICATE only and still had 2 certificates) and I used the same steps as you mentioned and it installed both the certificates.
some links :
[https://developer.mozilla.org/en/NSS_Certificate_Download_Specification|https://developer.mozilla.org/en/NSS_Certificate_Download_Specification]
[https://wiki.mozilla.org/CA:Certificate_Download_Specification|https://wiki.mozilla.org/CA:Certificate_Download_Specification] -
Installation Problem Sun Java App Server 8.2 PE
Hello! every body Please help me to get out of this Monster :(
For last 2 day i m trying to install Sun Java Application Server 8.2 PE. Installing & uninstalling Dozens of time.
The Installation halted at *51% at Uncompressing sun-as-jsr88-dm.jar*
I have searched the SDN forums at done every thing provided on the forum but in vain. So please help me i m using Win XP SP2`Hello!!!
Any body there!!
Such a big forum any body please help me i want to install the server. -
Problem with GlassFish and Sun Java System Message Queue
Hi,
I used application server PE.8 and I upgraded to Sun Java System Application Server Platform Edition 9.0 Update 1 Patch 1, and I changed all my CLASSPATH and everything. My system is working fine, but the Sun Java System Message Queue that I used before is still showing the queues and physical queues of the previous application server, not the new one. Do you know if there is way to change that and link it to the new version?
thanksUse an ESB like ServiceMix to bridge JMS providers
http://servicemix.org/
Or write your own MessageListener to consume from one JMS and publish on another one. Be careful with queues to avoid loosing the ordering - so you probably want to use a single MessageListener per subscription/queue - or to take advantage of Tibco's exclusive queues to ensure ordering is preserved. If ordering doesn't matter then don't worry too much about it and maybe have a pool of consumers to improve throughput
James
http://logicblaze.com/ -
Sun Java System Application Server8 can not startup (help me )
I work in an japanese compay in China. recently, my JSC can not work
who can help me
the error infomation is :
The Sun Java System Application Server could not start:
Possible reasons:
1.port conflict
2.Incorrect server configuartion
3.corrputed deployed application
my java Studio Creator version: 2004Q2 Update9
I have used this tool for three weeks , in the frist week. everything is ok.
no probroblem happened. in the second week ,sometimes my JSC can not startup, so I restarted my JSC. and it can work again. later, the same problem happened again. when I restarted my JSC , it sill does not work, so I have to restart my computer and it startup successfully,
two days later, the same problem happened again. I restarted my computer , it still did not work. so I have to change my port number in the domain.xml. sometimes it woks well, but sometimes I can't not startup.
in the third week, no matter what I do, the problem can not be solved.
some of my colleagues don't have such problem. but some of them have the same problem. when I run my project on the computer that don't have such problem , it can startup. I don't know why, just a little weird.
till now , no one in our company can tell why this problem happened.
and I believe that anybody who use JSC will encountered this error sooner or later.
who can tell me why will this problem happen? and where can I find some related imformation about this problem. thanks!!!!!!
my domain.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE domain PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 8.0 Domain//EN" "http://www.sun.com/software/appserver/dtds/sun-domain_1_0.dtd">
<!--
Copyright 2004 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
-->
<!-- Generated from default-domain.xml.template -->
<domain application-root="${com.sun.aas.instanceRoot}/applications" log-root="${com.sun.aas.instanceRoot}/logs">
<applications>
<j2ee-application enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/MEjbApp" name="MEjbApp" object-type="system-all"/>
<j2ee-application enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-apps/__ejb_container_timer_app" name="__ejb_container_timer_app" object-type="system-all"/>
<web-module context-root="/web1" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/adminapp/adminapp_war" name="adminapp" object-type="system-admin">
<!-- System Web Module - DO NOT DELETE! -->
</web-module>
<web-module context-root="/asadmin" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/admingui/adminGUI_war" name="admingui" object-type="system-admin">
<!-- System Web Module - DO NOT DELETE! -->
</web-module>
<web-module context-root="/com_sun_web_ui" enabled="true" location="${com.sun.aas.installRoot}/lib/install/applications/com_sun_web_ui" name="com_sun_web_ui" object-type="system-admin">
<!-- System Web Module - DO NOT DELETE! -->
</web-module>
</applications>
<resources>
<jdbc-resource enabled="true" jndi-name="jdbc/__TimerPool" object-type="system-all" pool-name="__TimerPool"/>
<jdbc-resource enabled="true" jndi-name="jdbc/PointBase" object-type="user" pool-name="PointBasePool"/>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.pointbase.xa.xaDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="__TimerPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="DatabaseName" value="jdbc:pointbase:embedded:ejbtimer,database.home=${com.sun.aas.instanceRoot}/lib/databases"/>
<property name="User" value="pbPublic"/>
<property name="Password" value="pbPublic"/>
</jdbc-connection-pool>
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.pointbase.xa.xaDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="PointBasePool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="DatabaseName" value="jdbc:pointbase:server://localhost:9092/sun-appserv-samples"/>
<property name="Password" value="pbPublic"/>
<property name="User" value="pbPublic"/>
</jdbc-connection-pool>
</resources>
<configs>
<config name="server-config">
<http-service>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="server" enabled="true" id="http-listener-1" port="28080" security-enabled="false" server-name="" xpowered-by="true">
</http-listener>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="server" enabled="true" id="http-listener-2" port="21043" security-enabled="true" server-name="" xpowered-by="true">
</http-listener>
<http-listener acceptor-threads="100" address="0.0.0.0" default-virtual-server="__asadmin" enabled="true" id="admin-listener" port="24848" security-enabled="false" server-name="" xpowered-by="true">
</http-listener>
<virtual-server hosts="sif-caicj" http-listeners="http-listener-1,http-listener-2" id="server" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}/docroot"/>
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
</virtual-server>
<virtual-server default-web-module="admingui" hosts="sif-caicj" http-listeners="admin-listener" id="__asadmin" state="on">
<property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access"/>
</virtual-server>
</http-service>
<iiop-service client-authentication-required="false">
<orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1"/>
<iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="23700" security-enabled="false"/>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="21060" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
<iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="21061" security-enabled="true">
<ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
</iiop-listener>
</iiop-service>
<admin-service type="das-and-server">
<das-config admin-session-timeout-in-minutes="60" autodeploy-dir="${com.sun.aas.instanceRoot}/autodeploy" autodeploy-enabled="true" autodeploy-jsp-precompilation-enabled="false" autodeploy-polling-interval-in-seconds="2" autodeploy-verifier-enabled="false" deploy-xml-validation="full" dynamic-reload-enabled="true" dynamic-reload-poll-interval-in-seconds="2"/>
</admin-service>
<web-container/>
<ejb-container cache-idle-timeout-in-seconds="600" cache-resize-quantity="32" commit-option="B" max-cache-size="512" max-pool-size="32" pool-idle-timeout-in-seconds="600" pool-resize-quantity="8" removal-timeout-in-seconds="5400" session-store="${com.sun.aas.instanceRoot}/session-store" steady-pool-size="0" victim-selection-policy="nru"/>
<mdb-container idle-timeout-in-seconds="600" max-pool-size="32" pool-resize-quantity="8" steady-pool-size="0"/>
<jms-service init-timeout-in-seconds="60" type="LOCAL">
<jms-host admin-password="admin" admin-user-name="admin" host="sif-caicj" name="default_JMS_host" port="27676"/>
</jms-service>
<log-service alarms="false" file="${com.sun.aas.instanceRoot}/logs/server.log" log-rotation-limit-in-bytes="2000000000" log-to-console="false" use-system-logging="false">
<module-log-levels admin="INFO" classloader="INFO" cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO" corba="INFO" deployment="INFO" ejb-container="INFO" javamail="INFO" jaxr="INFO" jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO" mdb-container="INFO" naming="INFO" resource-adapter="INFO" root="INFO" saaj="INFO" security="INFO" server="INFO" verifier="INFO" web-container="INFO"/>
</log-service>
<security-service anonymous-role="ANYONE" audit-enabled="false" audit-modules="default" default-realm="file" jacc="default">
<auth-realm classname="com.sun.enterprise.security.auth.realm.file.FileRealm" name="file">
<property name="file" value="${com.sun.aas.instanceRoot}/config/keyfile"/>
<property name="jaas-context" value="fileRealm"/>
</auth-realm>
<auth-realm classname="com.sun.enterprise.security.auth.realm.certificate.CertificateRealm" name="certificate">
</auth-realm>
<jacc-provider name="default" policy-configuration-factory-provider="com.sun.enterprise.security.provider.PolicyConfigurationFactoryImpl" policy-provider="com.sun.enterprise.security.provider.PolicyWrapper">
<property name="repository" value="${com.sun.aas.instanceRoot}/generated/policy"/>
</jacc-provider>
<audit-module classname="com.sun.enterprise.security.Audit" name="default">
<property name="auditOn" value="false"/>
</audit-module>
</security-service>
<transaction-service automatic-recovery="false" heuristic-decision="rollback" keypoint-interval="2048" retry-timeout-in-seconds="600" timeout-in-seconds="0" tx-log-dir="${com.sun.aas.instanceRoot}/logs"/>
<monitoring-service>
<module-monitoring-levels connector-connection-pool="OFF" ejb-container="OFF" http-service="OFF" jdbc-connection-pool="OFF" orb="OFF" thread-pool="OFF" transaction-service="OFF" web-container="OFF"/>
</monitoring-service>
<java-config classpath-suffix="${com.sun.aas.installRoot}/pointbase/lib/pbclient.jar${path.separator}${com.sun.aas.installRoot}/pointbase/lib/pbembedded.jar${path.separator}" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=creator-14848" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" server-classpath="${com.sun.aas.javaRoot}/lib/tools.jar${path.separator}${com.sun.aas.installRoot}/lib/install/applications/jmsra/imqjmsra.jar${path.separator}${com.sun.aas.imqLib}/jaxm-api.jar${path.separator}${com.sun.aas.imqLib}/fscontext.jar${path.separator}${com.sun.aas.antLib}/ant.jar">
<!-- various required jvm-options -->
<jvm-options>-client</jvm-options>
<jvm-options>-Djava.endorsed.dirs=${com.sun.aas.installRoot}/lib/endorsed</jvm-options>
<jvm-options>-Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy</jvm-options>
<jvm-options>-Djava.security.auth.login.config=${com.sun.aas.instanceRoot}/config/login.conf</jvm-options>
<jvm-options>-Dsun.rmi.dgc.server.gcInterval=3600000</jvm-options>
<jvm-options>-Dsun.rmi.dgc.client.gcInterval=3600000</jvm-options>
<jvm-options>-Xmx512m</jvm-options>
<jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}/config/keystore.jks</jvm-options>
<jvm-options>-Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}/config/cacerts.jks</jvm-options>
<jvm-options>-Djava.ext.dirs=${com.sun.aas.javaRoot}/jre/lib/ext${path.separator}${com.sun.aas.instanceRoot}/lib/ext</jvm-options>
<jvm-options> -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver</jvm-options>
<jvm-options>-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar</jvm-options>
<jvm-options>-XX:NewRatio=2</jvm-options>
</java-config>
<thread-pools>
<thread-pool idle-thread-timeout-in-seconds="120" max-thread-pool-size="200" min-thread-pool-size="0" num-work-queues="1" thread-pool-id="thread-pool-1"/>
</thread-pools>
</config>
<!-- config model with name "server-config" ends -->
</configs>
<servers>
<server config-ref="server-config" name="server">
<application-ref enabled="true" ref="adminapp" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="admingui" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="com_sun_web_ui" virtual-servers="__asadmin"/>
<application-ref enabled="true" ref="MEjbApp" virtual-servers="server"/>
<application-ref enabled="true" ref="__ejb_container_timer_app" virtual-servers="server"/>
<resource-ref enabled="true" ref="jdbc/__TimerPool"/>
<resource-ref enabled="true" ref="jdbc/PointBase"/>
</server>
</servers>
</domain>
my server.log
I am sorry there are some japanese words in the log
�v���I: fatal
����: information
�x��:warning
�R�l�N�V���������������G���[�������������� : error happened when connecting
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-02-10T12:59:48.050+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-02-10T12:59:49.206+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-02-10T12:59:49.394+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-02-10T12:59:51.628+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-02-10T12:59:51.659+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-02-10T12:59:51.738+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-02-10T12:59:53.910+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-02-10T12:59:55.519+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-02-10T12:59:55.707+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-02-10T12:59:56.394+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-02-10T12:59:57.019+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-02-10T12:59:57.769+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-02-10T12:59:57.769+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-02-10T12:59:57.816+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-02-10T12:59:57.957+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2006-02-10T12:59:58.113+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2006-02-10T12:59:58.113+0800|�x��|sun-appserver-pe8.0.0_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|#]
[#|2006-02-10T12:59:58.129+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2006-02-10T12:59:58.129+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2006-02-10T12:59:58.129+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2006-02-10T12:59:58.222+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2006-02-10T13:00:01.285+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|�A�v���P�[�V������web.xml�����������������A�f�t�H���g�������g�p������ StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2006-02-10T13:00:03.191+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g28080��������������|#]
[#|2006-02-10T13:00:03.254+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g 28080 ���N��������|#]
[#|2006-02-10T13:00:03.348+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g21043��������������|#]
[#|2006-02-10T13:00:03.363+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g 21043 ���N��������|#]
[#|2006-02-10T13:00:03.379+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g24848��������������|#]
[#|2006-02-10T13:00:03.379+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Coyote HTTP/1.1���|�[�g 24848 ���N��������|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory E:\Sun\Creator\SunAppServer8\imq\var\instances|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2006-02-10T13:01:04.883+0800|�v���I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: �R�l�N�V���������������G���[���������������B - ���o java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: �R�l�N�V���������������G���[���������������B - ���o java.net.ConnectException: Connection refused: connect
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
... 25 more
|#]
[#|2006-02-10T13:01:04.883+0800|�v���I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2006-02-10T13:01:04.883+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 28080 server:type=ThreadPool,name=http28080|#]
[#|2006-02-10T13:01:04.899+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 21043 server:type=ThreadPool,name=http21043|#]
[#|2006-02-10T13:01:04.915+0800|����|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 24848 server:type=ThreadPool,name=http24848|#]
[#|2006-02-10T13:01:05.008+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-02-10T13:01:05.008+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/02/10 13:01:05]|#]
[#|2006-02-10T13:01:05.008+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2006-02-10T13:01:05.008+0800|�x��|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: �R�l�N�V���������������G���[���������������B - ���o java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2006-02-10T13:01:05.008+0800|�v���I|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
[#|2006-02-10T13:01:05.024+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2006-02-10T13:01:05.024+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2006-02-10T13:01:10.743+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2006-02-10T13:01:11.728+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-02-10T13:01:11.868+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-02-10T13:01:14.634+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2006-02-10T13:01:14.650+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2006-02-10T13:01:14.665+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-02-10T13:01:16.337+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2006-02-10T13:01:17.603+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2006-02-10T13:01:17.790+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2006-02-10T13:01:18.462+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2006-02-10T13:01:19.025+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-02-10T13:01:19.728+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-02-10T13:01:19.728+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-02-10T13:01:19.775+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2006-02-10T13:01:19.916+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2006-02-10T13:01:20.041+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2006-02-10T13:01:20.041+0800|�x��|sun-appserver-pe8.0.0_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|#]
[#|2006-02-10T13:01:20.041+0800|����|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2006-02-10T13:01:20.056+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2006-02-10T13:01:20.056+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2006-02-10T13:01:20.150+0800|����|sun-appserver-pe8.0.0_01|org.apache.catalina.c &nHi,
Restarting the computer should have stopped the appserver.
To kill the appserver manually you can go to the command prompt
<install-dir>\Sun\Creator2\SunAppServer8\bin\asadmin.bat\stop-appserv
Thanks,
RK. -
Regarding Sun Java System Application Server Issue with JVM
Regarding Sun Java System Application Server Issue with JVM
Hi
I have installed SJSAS9.1 on solaris system. I m trying to deploy war file which i compiled in windows enviorment by jdk1.5.0_05. Every time i got the following error :
type Exception report
message
descriptionThe server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP
PWC6199: Generated servlet error:
[javac] javac: invalid target release: 1.5
[javac] Usage: javac
[javac] where possible options include:
[javac] -g Generate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source} Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the compiler is doing
[javac] -deprecation Output source locations where deprecated APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirs Override location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source files
[javac] -source Provide source compatibility with specified release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
note The full stack traces of the exception and its root causes are available in the Sun Java System Application Server 9.1 logs.
I have cheked jvm version on both system the only difference is :
Solaris points to jdk 1.5.0_09
Windows point to jdk1.5.0_05
Even i tried to run blank jsp also but again i got the same error.
Can any help me to sort out the problem or give me any idea so i can do something by my own.
Thanks in Advance
GaganDo you have ANT installed and available?
Thanks,
Kedar -
Help needed with Sun Java Studio Creator and EJB in a Portlet Project
Hi
I have created an web-application with JSF in Sun Java Studio Creator 2. The web application uses a lot of EJB's which acts as the dataProviders. In a typical jsp page i have more that one data providers(the EJB's) getting used. When i run the project everything opens up properly in the browser and the application seems to be fine.
But when i create a JSP 168 Portlet project and do exactly the same thing for some reason the Apache Pluto(comes as the default Portlet Container with Studio Creator) conks off.
Then i started going ahead step by step:
1. First i created a portletpage and added only one dataProvider(EJB) and ran the project...It gets deployed properly in Pluto and the browser comes up and everything shows up fine.
2. Just to re-confirm i did the same thing with another dataProvider(EJB). So still we have just 1 EJB in the portlet page. As expected it also worked fiine.
3. Then when I added more that one dataProviders(EJBs) in the porlet page the Apache Pluto conks off(saying that Pluto is not available)
I tried doing a lot of things but nothing works...Surprisingly the same thing works when u create a JSF web Application project but the same thing does not work when u create a JSR 168 JSF Portlet Project...
Did anybody face the same problem..Is it a bug in the Studio Creator...Any help would be highly appreciated.Hi,
There are a few discussion threads in the feedbackprograms portal for Creator 2 EA 2. The URL is:
https://feedbackprograms.sun.com/login.html
In the EA discussion forum you will find threads which discuss the concerned topic. In specific look for threads titled:
# Deploying Portlets
# Taking a JSC Portlet to Tomcat creates a Faces Mapping Error
# Problem with Pluto when trying to deploy a portlet
# Request: JSR-168 Portlet Project without JSF
We kindly request you to post your further queries related to EA in the above mentioned forum.
Cheers
Giri -
My sun java application server not run and give me error
hi master
sir i use
sun java system with studio creator but when i start deployment server
that give me this error
==================
The sun java system application server 8.2 could not start.
more information about the cause is in the server log file .
possible reasons include:
-Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
-Incorrect server configuration (domain.xml to be corrected muanually)
-Corrupted Deployed Application preventing the server to start.(this can be seen in the server.log file. in the case, domain.xml needs to be modified).
==========
this is my server.log file
=======
[#|2007-10-23T09:43:55.144+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T09:58:09.886+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T10:12:34.768+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T11:10:28.081+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
[#|2007-10-23T12:58:46.034+0500|SEVERE|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request.
com.sun.enterprise.config.ConfigException: Error refreshing ConfigContext:D:\Creator2_1\SunAppServer8\domains\creator/config/domain.xml
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:368)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:450)
at com.sun.enterprise.config.impl.ConfigContextImpl.getRootConfigBean(ConfigContextImpl.java:241)
at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getDomainBean(ServerBeansFactory.java:74)
at com.sun.enterprise.config.serverbeans.ConfigAPIHelper.getDomainConfigBean(ConfigAPIHelper.java:57)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildInternalCommand(ProcessLauncher.java:429)
at com.sun.enterprise.tools.launcher.ProcessLauncher.buildCommand(ProcessLauncher.java:404)
at com.sun.enterprise.tools.launcher.ProcessLauncher.process(ProcessLauncher.java:204)
at com.sun.enterprise.tools.launcher.ProcessLauncher.main(ProcessLauncher.java:128)
Caused by: org.netbeans.modules.schema2beans.Schema2BeansNestedException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
Attribute "name" was already specified for element "jdbc-connection-pool".
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:718)
at org.netbeans.modules.schema2beans.BaseBean.createGraph(BaseBean.java:2262)
at com.sun.enterprise.config.impl.ConfigContextImpl.refresh(ConfigContextImpl.java:345)
... 8 more
Caused by: org.xml.sax.SAXParseException: Attribute "name" was already specified for element "jdbc-connection-pool".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1027)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:714)
... 10 more
|#]
please how i start my application server
thank's
aamirPlease see the following FAQ:
Why doesn't application server Start.
http://developers.sun.com/jscreator/reference/faqs/technical/depsrvs/index.jsp -
Unable to install Sun Java System Web Server 6.1 Service Pack 7 on Wndows
Dear All,
I recently downloaded Sun Java System Web Server 6.1 Service Pack 7 and now I am trying to install it.
The previous version of Web Server 6.1 that i installed is running successfully on Windows 2000 Prof. though it is not meant for it.
To install SP7, i uninstalled the previous Web Server 6.1. I also removed the folder Sun and all the child folders of it. The Sun ONE Web Server services are still available and i can't able to delete them even from registry so i disabled them.
Then I tried to install SP7. But after few steps, it gives error:
You already have a Sun ONE Web Server installed. Install can not proceed.
I am sure that i am able to remove completely the previous instance of webserver as i removed all the entries from registry also and also disabled the services related to it.
Still why i am getting this error?
Will it work on Windows 2000 Professional like its previous version?
If not can i able to install previous version of the Web server 6.1 (without SP7) on Windows 2000 Prof?
Please help me regarding this.
-SameerSameer, you should have uninstalled Web Server 6.1 using the Web Server uninstallation program instead of just deleting its files and directories. Your Windows registry is now in an inconsistent state.
If you can restore your previous Web Server 6.1 installation from a backup, you can run the uninstaller to correctly uninstall it.
If you cannot uninstall Web Server 6.1 using its uninstallation program, you will need to manually delete the Windows services and edit the Windows registry to remove all references to the files you deleted. Note that you can render your computer inoperable by deleting services or modifying the Windows registry. Don't do this if you're not confident with what you're doing.
To delete the services using SC.EXE:C:\>sc delete https-admserv61
C:\>sc delete https-hostname(You can find the hostname for the Web Server 6.1 service(s) using the Services program in the Administrative Tools folder of the Control Panel.)
To clean up the registry, use REGEDIT.EXE to delete HKEY_LOCAL_MACHINE/Software/Sun Microsystems/WebServer. -
How can I clean up queue one-time on Sun Java system messaging 6.3
Hi,
<address>Our Email server have a problem, When I run _./imsimta qm directory tcp_local_, There are about 5 Millions of messages in the queue.</address>
Now our Email server send messages very slowly, how can I clean up queue one-time?
the command _./imsimta qclean_ is very slowly.
What can I do to prevent this problem?
our Email server version is :
Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)
libimta.so 6.3-6.03 (built 17:12:37, Mar 14 2008; 32bit)
SunOS email-1 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V890
Thank you !If you have more than 100,000 messages in the queue, then look at the MAX_MESSAGES parameter in [the job_controller.cnf file|http://wikis.sun.com/display/CommSuite/Job+Controller+Configuration+File]. If the parameter is not specified, it defaults to 100000. If you have more than that number of messages in the channel queues, it will take a long time for new/legitimate messages to be sent because job_controller is only considering the first 100,000 messages in the queue.
If you get into the "imsimta qm" command do do "sum -database", it will show a summary of what job_controller has in its internal cache and therefore what job_controller is working on. If you compare that to "sum -directory" you will probably see a difference.
If these are all legitimate messages, you need to increase MAX_MESSAGES, cnbuild, and restart job_controller.
If they are not, then preventing this in the future will require determining how they got into your queue and correcting that.
As for removing them, the "imsimta qm" commands allow you to select messages by various criteria and then you can "return" or "delete" them. But yes, that will take a long time if there are many messages because it is a single threaded process and it needs to open and examine each message. You may be able to accomplish the task more quickly with a shell script that works on individual channel queue subdirectories and then run multiple copies of that script in parallel. After you have cleaned out the queue, restart job_controller.
Also, you might want to consider [the subdirs channel keyword|http://msg.wikidoc.info/index.php/Subdirs_and_nosubdirs_Channel_Options]. -
How to access JDBC Resource registered in Sun Java System App Server ?
I want to create a stand-alone JDBC application with Java SE using Swing technologies and JNDI technology. The purpose of using JNDI technology is to avoid change of Java Source Code every time I move the database to different location. This Java application will be used in a standalone PC installed with Windows XP Professional with no LAN / WAN connection. Of course, Internet connection is available with the PC.
I use JavaDB to store the data tables and the location of the database is D:\E-DRIVE\SAPDEV. Tomorrow, if I move this database to C:\SAPDEV or any network drive, I do not want to change the Java Source code. I want to use JNDI which, if I am not wrong, helps developers to avoid manual change of Java source code whenever the database location is changed. Changes have to be made only in the JNDI Name which contains all relevant information about the database in order to get connection no matter where the database SAPDEV is stored; it can be placed under D:\E-DRIVE directory or C:\ directory of the hard disk. To implement my intention, I started developing Java application as per the steps mentioned below:
Step 1:
To proceed, first, I sought the help of Sun Java System Application Server Admin Console. I created JNDI object for Connection Pool using the menu path Common Tasks->Resources->JDBC->Connection Pools.
JNDI Name : ABAPRPY
Resource Type : javax.sql.DataSource
Datasource class : org.apache.derby.jdbc.ClientDataSource
Description : ABAP Program Repository
The Connection Pool creation has options for General, Advanced and Additional Settings tabs and I made all the settings relevant to the database I created in D:\E-DRIVE\SAPDEV.
To confirm whether the above settings are correct, I pressed the Ping push button which is available in the General tab of the connection pool creation screen. The system responded with the message Ping Succeeded.
Step 2:
I created a JDBC Resource using the menu path Common Tasks->Resources->JDBC->JDBC Resources.
JNDI Name : jdbc/SAPDEV
Pool Name : ABAPRPY
Description : Database Connection for SAPDEV database
Status : Enabled
I can see all the above settings recorded in the domain.xml which is placed in the folder
C:\Sun\AppServer\domains\domain1\config
Step 3:
I have made sure that Sun Java System Application Server is up and running in the background with JavaDB server. I created a Java Program making sure the following JAR files are included in the classpath:
appserv-admin.jar
appserv-ee.jar
appserv-rt.jar
javaee.jar
fscontext.jar
Plus, the lib directory of JDK 1.6 & C:\Sun\AppServer\domains\domain1\config
Source code of the program is as follows: I used NetBeans IDE to create my project file.
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.naming.*;
import javax.activation.DataSource;
public class JNDILookup {
public static void main(String[] args) {
try {
InitialContext initCtx = new InitialContext();
DataSource ds = (DataSource) initCtx.lookup("java:comp/env/jdbc/sapdev>");
} catch (NamingException ex) {
Logger.getLogger(JNDILookup.class.getName()).log(Level.SEVERE, null, ex);
When I attempted to compile the above program in NetBeans IDE ,no compilation error reported. But while executing the program, I got the following run-time error message:
SEVERE: null
javax.naming.NameNotFoundException: No object bound for java:comp/env/jdbc/sapdev> [Root exception is java.lang.NullPointerException]
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:224)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:396)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at SAPConnect.JNDILookup.main(JNDILookup.java:21)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173)
... 3 more
Now, I want to come out of this situation; at the same time, I want to preserve the settings I have made in the Sun Java System Application Server Admin Console. That is, I want to programmatically access the data source using Connection Pool created in Sun Java System Application Server Admin Console.
I request dear forum members to provide me an appropriate solution.
Thanks and regards,
K. Rangarajan.jay44 wrote:
Bare in mind I am attempting the context.lookup() from inside the container (my code is in a session bean). I have accessed the server and have my bean "say hello" first to verify the bean works OK, then I call a method with this rather standard code:
String jndiDataSourceName ="Second_EJB_Module_DataBase";
Logger.getLogger(DynamicPU.class.getName()).log(Level.INFO,"Programatically acquiring JNDI DataDource: "+ jndiDataSourceName);
InitialContext ctx;
try {
ctx = new InitialContext();
ds =(DataSource)ctx.lookup("java:comp/env/jdbc/"+jndiDataSourceName);
} catch (NamingException ex) {
Logger.getLogger(DynamicPU.class.getName()).log(Level.SEVERE, null, ex);
return "Exception generated trying to preform JDBC DataSource lookup. \n"+ex.toString();
But when I run the code the server log shows the initial context is created Ok, but an exception is thrown becasue the resource name is not found:
(and i have tried vriations of ctx.lookup("jdbc/"+jndiDataSourceName) etc etc
You are fine here. It works in container because the InitialContext properties have been supplied already. That was the link I forwarded earlier. The InitialContext you create locally needs to locate the container JNDI. That is what the properties specify.
Where I am confused is where you indicate the stack below is from the server log. So, you initiate a standalone (java main method) application, create an InitialContext, and you see the results in your app server log?
LDR5010: All ejb(s) of [EJB_Module_1] loaded successfully!
Programatically acquiring JNDI DataDource: Second_EJB_Module_DataBase
The log message is null.
javax.naming.NameNotFoundException: Second_EJB_Module_DataBase not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:192)...
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
This is strange since I can see this resource (a JDBC connection named Second_EJB_Module_DataBase) is configured on the server from the server's admin console.
That is why you can obtain a lookup from within the container (app server).
For this lookup to work it may be that one must map the name inside an ejb-jar.xml deployed with the application, but I have also read some resources like jdbc connection should have a default name. Does anyone know if my lookup() should work without using an ejb-jar.xml mfile to explcitly map the reource for my application?
Both EBJ's and data sources can be referenced via JNDI. It's a remote lookup (that is normally optimized if it is running in the same JVM). You should not have any dependencies on a JDBC data source being set-up on ejb-jar.xml. That file can of course impact your EJB's. However, data sources are normally set-up on a container-specific basis (e.g., you probably did it through a console, but there is a spec somewhere about how to set up a data source via a resource the app server looks for; it varies from app server to app server). However, once you have that container-specific data source set-up, JNDI operates vendor-neutral. You should be able to take the code above and move it to JBoss or Weblogic or Tomcat or whatever (this is an ideal, in practice, the vendors sometimes put a data source in a name you would not expect, but again, you can use their JMX console to see what the JNDI name is).
(As I stated above if I have to use a deployment discriptor to get at this JNDI datasource, then solution is not "programmatic" as newly configured datasources could not be accessed without redeploying the entire application).
As JSchell alluded to, you will always have at least something vendor-specific. JNDI itself (the code you wrote) is totally portable. However, you have to set the various JNDI environment properties to a given vendor's spec. Ideally, you should not need a vendor's actual InitialContext application, but it's a possibility. Once you can safely cast to Context, you should be vendor-neutral (if not, demand your money back).
So that is exactly where I am stuck, trying to get the lookup to work and wondering if it should work without and xml file mapping the resource for my app.
What we ended up doing for standalone was to provide our own JNDI. If you look at the open source project JOTM, there are examples on how to use that with XBean (if integrating with Spring, as we did), you can easily set up a data source that runs standalone exactly as you get in the container. Another benefit is you get full JTA/JTS support and the ability to run XA transactions. (This might all be alphabet soup, but the app server gives it to you, and this is the way we ended up doing the same: JNDI + JTA + JTS + XA). It ends up the same application code uses a "vanilla" InitialContext and all we have to do is write one or two xml files (one for our app server, a couple for JOTM), and our actual code works the same.
I still think you have a shot at getting to the container's JNDI, just not using their full-blown app server JAR.
I think there must be a simple way to do this with an ejb-jar.xml, I am no expert in JNDI, I could be missing something simple, I will keep at it and post an answer here if I come up with it.
Thanks, jayIt is simple to code. Getting it to integrate with your app server, yes, that can be challenging. But it has nothing to do with EJB's. Write a simple test. Using nothing but DataSource and InitialContext. Let us know where you get stuck.
- Saish -
Sun java DIRECTORY SERVER 6.0 WITH SUN OPENSSO 8
Hi all,
I have install the sun java directory server 6.0.
Now I have install the sun openssl ( I could had installed the sun java access manager but i wanna use the sun opensso 8 for SSO).
when created the directory i.e. by using command from directory preparation tool, the directory server stop starting.
It do not start and is asking me the error as follows,
bash-3.00# /var/opt/SUNWdsee/dsins1/start-slapd
[20/Feb/2009:14:44:30 +0500] - ERROR<4131> - Bootstrap config - conn=-1 op=-1 msgId=-1 - System error The entry cn=schema in file /var/opt/SUNWdsee/dsins1/config/schema/99user.ldif is invalid (error 20: Type or value exists) - attribute type sunIdentityServerDiscoEntries: Does not match the OID "1.3.6.1.4.1.42.2.27.9.1.821". Another attribute type is already using the name or OID..
[20/Feb/2009:14:44:30 +0500] - ERROR<4129> - Bootstrap config - conn=-1 op=-1 msgId=-1 - Configuration error Please edit the configuration file to correct the reported problems and then restart the server. Server exiting.
Server not running!! Failed to start ns-slapd process.
Note: while preparing the directory (sun java directory preparation tool) I mentioned the schema 2 i.e. ACCESS MANAGER, because sun opensso 8 is the latest version for Sun java access manager ?
Any help??????????????
Regards
AdeelLooks like the attribute sunIdentityServerDiscoEntries is defined twice in the schema. Run the following and see where it is defined for the second time.
# cd /var/opt/SUNWdsee/dsins1/config/schema
# grep -w sunIdentityServerDiscoEntries *.ldif | grep -iv objectclasses
Edited by: etst123 on Mar 3, 2009 1:28 PM
Maybe you are looking for
-
PS report: wbs element relation with PO, Pur Req. and vendor
Hello, I need to build a report on WBS element which also shows PO number, Pur. Requisition, vendor details along with budget, actual, committements. I found datasources that can provide informations except PO, Pur Req. Can anyone help in providing a
-
How to create spool in an online report
Hi All, I have a requirement where the ALV report output has customers and details related to it.For example My report output has three customers(with a check box against it) and each customer has 5 line items.The user will select first and the last
-
Unpairing remote on mavericks osx
Help! I have my Mac mini that acts as a file server for my Apple TV, however when I control my Apple TV using my Apple remote, it also controls my iTunes. I have opened up system preferences as all the forums say, gone into security and privacy in th
-
Only excise posting need to be done
Hi, 1. Once a material is manufactured & posted to unrestricted stock, its available for sales & the subsequent RG1 entries are posted. 2. If the same material is required again for reprocessing, the goods can be removed from the stock only with the
-
Hi, I'm new to JSP and have met such a problem. I use <%=output%> to print out the contents generated in JavaBean, whenever I refresh the page the contents will be printed out once more, while I need once only. Can you tell me what the possible probl