About Sun Java System AS PE 9.0 UR1

Hi everyone.
I have saw that Glassfish v1 UR1 released.
http://www.glassfishwiki.org/gfwiki/Wiki.jsp?page=GlassFishV1UR1
but, where can i download the SJS AS PE UR1?

I'm striving too to get it but no use, where is it?

Similar Messages

  • About Sun Java System Application Server

    Can SJSAS dealing with 2 LAN Card (NIC) and 2 Ips? let's say i want to separate my client's network and the server's network. clients connects to the Application Server using IP 192.168.11.xxx and the application server connects to the database server using ip 192.168.22.xxx, so the the apllication have 2 IPs and also 2 LAN Card (NIC). Does SJSAS support my needs? thanks for your help
    i really appreciate it

    You probably just need to update your hosts file to include an entry for localhost

  • About Sun Java System Directory Services Connectors

    hi all,
    When i finished my SJSDS connector and tried to run the SJSDS schedue task "SJSDS Trusted Recon Task", one error heppend:
    11:46:39,343 INFO [SJSDS] tcTskIPlanetUserReconciliation[RO=SJSDS User] --> The value cannot be null for the attribute
    11:46:39,375 FATAL [SJSDS] tcTskIPlanetUserReconciliation[RO=SJSDS User] --> init(): Init Failed
    11:46:39,375 FATAL [SJSDS] tcTskIPlanetUserReconciliation[RO=SJSDS User] --> execute(): Variables not initialized properly. Terminating !!!!!!!!
    SJSDS Trusted Recon Task attribute:
    Attribute Name          Attribute Value
    ITResourceName          SJSDS Server
    NumberOfBatches          All Available
    Organization          Xellerate Users
    ReconQuery          I=Santa Clara
    ResourceObjectName     SJSDS User
    Role               Part-Time
    TrustedSource          true
    UserContainer          ou=people,dc=constractor,dc=com
    Xellerate Type          End-User
    XLDeleteUsersAllowed     false
    I am harried ,pls give me some help! thanks.

    Hold on man ! ! There is no point of pooling in threads with same question. If their is a solution which exists then even one thread would bring you answers.
    - Follow the document religiously.
    - Confirm the attributes ReconQuery and UserContainer
    - Enable DEBUG level logs and then paste the error over here. See document to do that.
    Thanks
    Sunny

  • Doubt about Sun Java System Messaging Server 6 2005Q1

    Hi all,
    After some problems with our Messaging Server 5.2, my manager and his manager are agree now with the messaging server upgrade.
    But now they want a detailed report explaining the improvements between the 5.2 version and the 6 2005Q1 one.
    Any of you know any link with this kind of information (technical characteristics, costs, ...) ?
    Any link or idea will be really welcome.
    Thanks in advance for your help
    Kind Regards

    There have been MANY improvements in the product, as well as hundreds of bugs fixed.
    Some of the highlights:
    1. Automatic repair of many database and mailbox problems.
    2. Automatic restart of crashed processes
    3. Improved Cluster control and debugging
    4. Improved integration with external virus and spam scanning solutions
    5. Improved monitoring tools
    Your Sales Engineer should have a presentation available for you, if you like.

  • Sun Java System Communications Express 6

    Does anyone have information about Sun Java System Communications Express?
    Has it been released? What are your opinions, etc?
    Thanks,
    GB

    i started with schema 2
    so installed directory identity - verified them
    ran instalelr again and instaleld messagign , calendar - tested them
    then installed communicatiosn express and configured as per setup docs - configured them for identity sso not messaging sso
    l8r

  • 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.3

    If 7.0 was released, how come http://www.sun.com/webserver still only talks about 6.1?

  • 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?
    thanks

    Use 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      &n

    Hi,
    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
    Gagan

    Do you have ANT installed and available?
    Thanks,
    Kedar

  • 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

  • The Sun Java System Application Server could not start

    Hello All,
    I downloaded the Java Pet Store example from sun's website and followed the instructions for installation. After successful installation, I tried to deploy the project and gave the following error
    C:\Documents and Settings\sina\My Documents\Projects\services\nbproject\build-impl.xml:194: Deployment error:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    See the server log for details.
    BUILD FAILED (total time: 5 minutes 20 seconds)
    The link above points to the following line in the build-impl.xml file
    <nbdeploy debugmode="false" forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" clientModuleUri="${client.module.uri}"/>
    Can any one help whats wrong.An early response will be highly appreciated.
    Kind Regards.
    Hasnain Javed.

    Hi,
    Maybe you already got this fix but here is a suggestion, a snippet from the readme index,html of the petstore download
    # Start the Sun Java System Application Server and the JavaDB database. To do so, open a command prompt and change directory to <javaeesdk.home>/bin and issue the following commands:
    asadmin start-database
    asadmin start-domain
    # Change directory to <petstore.home> and enter the following commands
    ant setup
    ant run
    This will setup, build and deploy the petstore on the application server, and then launch the application homepage in your default browser.
    The "ant setup" that you run from <petstore.home> (petstore.home is the directory where petstore is installed or where you unzipped it) will populate the database wth data and setup the proper database tables etc that are used by the application.
    hth,
    Sean

  • Sun Java System Application Server could not start

    Hi
    I have installed JDK1.5 Update1 + netbeans 5.5 with the JBOSS bundle and added the Sun Java System Application Server 9.1.02.
    I am creating the EJB-JMS application described at
    http://www.netbeans.org/kb/55/ejb30.html
    All the steps are followed properly, but while running the project i get the error
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    D:\MyNBProjects\EJBAPP1\nbproject\build-impl.xml:183: Deployment error:
    The Sun Java System Application Server could not start.
    More information about the cause is in the Server log file.
    Possible reasons include:
    - IDE timeout: refresh the server node to see if it's running now.
    - Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
    - Incorrect server configuration (domain.xml to be corrected manually)
    - Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
    - Invalid installation location.
    See the server log for details.
    BUILD FAILED (total time: 5 minutes 3 seconds)

    Hi Roman,
    Sorry for the long wait....
    In the mean time I have downloaded NB6.1 (final Release) and JDK 1.6.0_04,added the sjsas-9_1_02 to NB6.1, all are in D:\javak (where previous setup of NB5.5 and jdk1.5 and SJSAS-9_1_02 is AS IS in D:\java)
    Current Scenario:
    Product Version: NetBeans IDE 6.1 (Build 200805300101)
    Java: 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19
    System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
    Userdir: D:\Documents and Settings\kedar\.netbeans\6.1
    Now, when i try to Run the SAME code i get the following error:
    Created dir: D:\ProjectsNB\EJBAPP1\dist
    Building jar: D:\ProjectsNB\EJBAPP1\dist\EJBAPP1.ear
    post-dist:
    dist:
    pre-run-deploy:
    Initial deploying EJBAPP1 to D:\ProjectsNB\EJBAPP1\dist\gfdeploy
    Error during incremental deploy: java.lang.NullPointerException
    Start registering the project's server resources
    Finished registering server resources
    java.lang.NullPointerException
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.getFileArchive(DirectoryDeploymentFacility.java:264)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:168)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    Deployment error:
    cannot find FileArchive class...
    See the server log for details.
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:166)
    at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:277)
    at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:460)
    at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
    Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:194)
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeployment.initialDeploy(DirectoryDeployment.java:413)
    at org.netbeans.modules.j2ee.sun.ide.j2ee.incrdeploy.DirectoryDeploymentFacade.initialDeploy(DirectoryDeploymentFacade.java:218)
    at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:519)
    at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:151)
    ... 16 more
    Caused by: java.lang.IllegalStateException: cannot find FileArchive class...
    at org.netbeans.modules.j2ee.sun.bridge.DirectoryDeploymentFacility.initialDeploy(DirectoryDeploymentFacility.java:170)
    ... 20 more
    BUILD FAILED (total time: 9 seconds)
    Thanks,
    Kedar.

  • SOAP on Sun Java System Application Server 9

    I am running the Sun Java System Application Server 9 (SJSAS). My goal is to have SOAP running on the server to handle incoming messages. I cannot find the answers to the following critical questions anywhere.
    1. Should I be creating my own soap client/server with the javax.xml.soap package, using some utility that might come bundled with SJSAS that I don't know about, or using something like Apache AXIS?
    2. Whatever I use, how should it be deployed to the application server? AXIS comes as a bunch of jar files, but to deploy a web service to SJSAS requires a war. Instructions for other application servers for using AXIS seem not to apply for SJSAS for this reason.
    3. After I get the server installed, how do I actually connect that to any of the rest of the code on my server. For instance, would I put the actual business logic to query the persistence layer in a stateless session bean and then somehow reference the methods in that bean to compose the return message to go to the client?
    If anybody knows of or is willing to create a tutorial to achieve this goal on SJSAS and has a place to post it, that would probably be a great contribution to the information available online. If I am missing such a tutorial, I apologize and would be glad to have it pointed out to me. Any assistance with actually deploying soap for SJSAS would be tremendously helpful. There is a lot of why to use it, when to use it, what the spec is, and so on online. There is precious little how to use it and even less how to deploy it. Thank you for any help.
    Ryan

    the sun java system application server 8 and 9 comes with certutil and pk12util (http://www.mozilla.org/projects/security/pki/nss/tools/pk12util.html) programes. using them you can import them
    or check on google how to conver pk12 certs to NSS format.
    another option is to open the certificate in Internet explorer and save to cer format and then convert.

  • Not able to start the Sun Java System Access Manager 7 Console

    Hi All,
    I have successfully installed the Sun Java System Portal Server 7 on RHEL 4.0.The problem I am facing is not able to start the Sun Java System Access Manager 7 Console while accessing the URL: http://fqdn:8080/amconsole
    As soon as I try to access this URL it gives me following Excepiton:::::::
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    com.iplanet.jato.NavigationException: Exception encountered during forward
    Root cause = [java.lang.NullPointerException]
         com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:386)
         com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:267)
         com.iplanet.am.console.base.ConsoleServletBase.onUncaughtException(ConsoleServletBase.java:338)
         com.iplanet.jato.ApplicationServletBase.fireUncaughtException(ApplicationServletBase.java:1023)
         com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:469)
         com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
         com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:294)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
         sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         java.lang.reflect.Method.invoke(Method.java:585)
         org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         java.security.AccessController.doPrivileged(Native Method)
         javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
    If anyone have any idea about the cause of this error,please let me know.All suggestions are welcome .
    Thanx and Regards,
    Chirag.

    Hi All,
    I am having exactly the same problem with the same stack trace. Has anybody have an idea how to fix this?
    I have downloaded the Java Identity Management Suite.(java_es-5-identsuite-ga-windows-x86.zip) The first time installation was fine and I was able to bring the Access Manager console. I was able to create users groups etc.
    However, when I uninstalled and installed it again, I got exactly the same error described in the thread. Running "amserver start" and "amserver restart" did not help. I did the installation one more time
    but again I got the same error.
    Thanks for the help.
    celikkan

  • SetConnectTimeout Doesn't Work in Sun Java System App Server EE 8.1

    Hi all,
    I have a code that sends a request through HTTP using HttpURLConnection. Roughly, the code is as follows.
    HttpURLConnection huc = (HttpURLConnection) url.openConnection();
    huc.setConnectTimeout(10000); // 10 seconds.
    ....I tested it in a normal Java console program and it was working fine. I tested it again inside a servlet using Tomcat and it was okay. But when I tested in a servlet using Sun Java System Application Server, it didn't work. I reckon there must be some configuration that I need to set in Sun Java Application Server, but I just don't know where. I've been googling it for few days with no answer :( Do you guys have any idea about this?
    Thanks in advance.

    Hi all,
    I have a code that sends a request through HTTP using HttpURLConnection. Roughly, the code is as follows.
    HttpURLConnection huc = (HttpURLConnection) url.openConnection();
    huc.setConnectTimeout(10000); // 10 seconds.
    ....I tested it in a normal Java console program and it was working fine. I tested it again inside a servlet using Tomcat and it was okay. But when I tested in a servlet using Sun Java System Application Server, it didn't work. I reckon there must be some configuration that I need to set in Sun Java Application Server, but I just don't know where. I've been googling it for few days with no answer :( Do you guys have any idea about this?
    Thanks in advance.

Maybe you are looking for