Integrating Sun App Server with WebSphere MQ

Hi,
I am using Sun App server V8.1 . I also have a websphere MQ v5.3 installed in my system. I want to integrate this MQ with the App server.
I created a queueManager and a Queue in MQ and using the JMSAdmin console of the Mq, i created jndi lookup resources using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
In the application server side, i created a Resource adapter using the command:
create-resource-adapter-config --property SupportsXA=true:ProviderIntegrationMode=jndi:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:D\\:\\MQ:LogLevel=finest mqra
Then i deployed this resource adaptor using the command :
deploy name mqra target server "D:\Sun\AppServer\lib\addons\resourceadapters\genericjmsra\genericra.rar"
Using this resource adapter i created a connection pool, connector resource and an admin object using the commands
create-connector-connection-pool raname mqra connectiondefinition javax.jms.QueueConnectionFactory transactionsupport  XATransaction property ConnectionFactoryJndiName=MQQCF mymqpool
create-connector-resource --poolname mymqpool jms/MyMqQCF
create-admin-object raname mqra restype javax.jms.Queue --property DestinationJndiName=RTQueue jms/MyMqQueue
After that, i wrote a java code to lookup these resources and put a message into the queue.
This is the snippet of my java code
InitialContext ic = new InitialContext();
QueueConnectionFactory cnxFact = (QueueConnectionFactory)ic.lookup("jms/MyMqQCF");
Queue qu = (Queue)ic.lookup("jms/MyMqQueue");
try {               
QueueConnection qConn = cnxFact.createQueueConnection();
QueueSession qSess = qConn.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
QueueSender qSend = qSess.createSender(qu);
TextMessage msg = qSess.createTextMessage();
msg.setText("1");
qSend.send(msg);
qConn.close();
I am getting an exception in the line, QueueConnection qConn = cnxFact.createQueueConnection();
here is the stack trace
java.lang.ClassCastException: com.ibm.mq.jms.MQQueueConnectionFactory
at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createXAConnection(ManagedQueueConnectionFactory.java:45)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:127)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:111)
at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:90)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResource(IASNonSharedResourcePool.java:437)
at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:355)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:250)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:213)
at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:174)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:286)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:145)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121)
at com.sun.genericra.outbound.ConnectionFactory.createConnection(ConnectionFactory.java:69)
at com.sun.genericra.outbound.ConnectionFactory.createQueueConnection(ConnectionFactory.java:101)
Can anybody help???

bump
update:
So to avoid this problem I added spring.jar to the server classpath. that got rid of this message but then it started complaining that its missing struts2 core jar..i added that in server classpath as well...I did same for 4 other files and in the end it said 'bean for xwork has already been initialized' (because all these jars are in the application as well).
So I am stuck. if I add all jars to server classpath..it says beans have already been initialized. If I take out the jars from server classpath then it says that stuff is missing (eg. contextLoader.properties missing - orig post)
again, all this goes away when I restart the server..so i am just trying to avoid having to restart server every code change.

Similar Messages

  • Integration of sunone server with Websphere MQ

    I am trying to use an MDB with WebsphereMQ. The Sunone Server and the MQ services are on physically different machines. I have followed the example setup in the MDB Simple Sample Application. I beleive my problem is that the Sun One server is assuming that MQ is on the same machine.
    This is the dump:
    INFO: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_01] from [Sun M
    icrosystems Inc.]
    INFO: JTS5014: Recoverable JTS instance, serverId = [100]
    INFO: RAR5060: Install JDBC Datasources ...
    INFO: RAR5059: Binding [JDBC DataSource Name: jdbc/ORMdb, Pool Name: ORMPool]
    INFO: RAR5059: Binding [JDBC DataSource Name: jdbc/QDEdb, Pool Name: QDEPool]
    INFO: JMS5015: Install JMS resources ...
    INFO: MDB00044: Deploying message-driven bean [orm:InvoiceMDB], consuming from [
    jms/InvoiceQ]
    WARNING: MDB00032: [orm:InvoiceMDB]: Message-driven bean container connection fa
    ctory not specified. Use default
    SEVERE: MDB00030: [orm:InvoiceMDB]: Exception in setting up message-driven bean
    container: [[C4003]: Error occurred on connection creation. - caught java.net.Co
    nnectException]
    SEVERE: MDB00017: [InvoiceMDB]: Exception in creating message-driven bean contai
    ner: [javax.jms.JMSException: [C4003]: Error occurred on connection creation. -
    caught java.net.ConnectException]
    SEVERE: javax.jms.JMSException
    javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught
    java.net.ConnectException
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(Exce
    ptionHandler.java:183)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(Exce
    ptionHandler.java:136)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(Port
    MapperClient.java:145)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClien
    t.java:86)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperCli
    ent.java:47)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<in
    it>(TCPConnectionHandler.java:46)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openCon
    nection(TCPStreamHandler.java:101)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.
    java:501)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandle
    r.java:930)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(Connect
    ionImpl.java:1482)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.ja
    va:403)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.
    java:234)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedC
    onnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConne
    ctionImpl.java:32)
    at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueC
    onnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXA
    QueueConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.creat
    eXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.creat
    eXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
    at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection
    (ConnectionFactoryWrapper.java:118)
    at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperB
    ase.java:394)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContain
    er.java:206)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Container
    FactoryImpl.java:173)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:34
    5)
    at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:
    81)
    at com.iplanet.ias.server.AbstractManager.load(AbstractManager.java:134)
    at com.iplanet.ias.server.ApplicationLifecycle.onStartup(ApplicationLife
    cycle.java:168)
    at com.iplanet.ias.server.ApplicationServer.onStartup(ApplicationServer.
    java:269)
    at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:162)
    SEVERE: EJB5090: Exception in creating EJB container [javax.jms.JMSException: [C
    4003]: Error occurred on connection creation. - caught java.net.ConnectException
    SEVERE: appId=orm moduleName=EJBModule_ImageMDB_jar ejbName=InvoiceMDB
    SEVERE: LDR5004: UnExpected error occured while creating ejb container
    javax.jms.JMSException: [C4003]: Error occurred on connection creation. - caught
    java.net.ConnectException
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSException(Exce
    ptionHandler.java:183)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleException(Exce
    ptionHandler.java:136)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(Port
    MapperClient.java:145)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClien
    t.java:86)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperCli
    ent.java:47)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<in
    it>(TCPConnectionHandler.java:46)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openCon
    nection(TCPStreamHandler.java:101)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.
    java:501)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandle
    r.java:930)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(Connect
    ionImpl.java:1482)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.ja
    va:403)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.
    java:234)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedC
    onnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConne
    ctionImpl.java:32)
    at com.sun.messaging.jmq.jmsclient.XAQueueConnectionImpl.<init>(XAQueueC
    onnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionImpl.<init>(JMSXA
    QueueConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.creat
    eXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:75)
    at com.sun.messaging.jmq.jmsclient.JMSXAQueueConnectionFactoryImpl.creat
    eXAQueueConnection(JMSXAQueueConnectionFactoryImpl.java:51)
    at com.sun.enterprise.jms.ConnectionFactoryWrapper.createQueueConnection
    (ConnectionFactoryWrapper.java:118)
    at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperB
    ase.java:394)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContain
    er.java:206)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(Container
    FactoryImpl.java:173)
    at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:34
    5)
    at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:
    81)
    at com.iplanet.ias.server.AbstractManager.load(AbstractManager.java:134)
    at com.iplanet.ias.server.ApplicationLifecycle.onStartup(ApplicationLife
    cycle.java:168)
    at com.iplanet.ias.server.ApplicationServer.onStartup(ApplicationServer.
    java:269)
    at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:162)
    WARNING: CORE5021: Application NOT loaded: [orm]
    INFO: HTTP3072: HTTP listener http-listener-1 [http://orm-java-app:80] ready to
    accept requests
    startup: server started successfully
    INFO: CORE3274: successful server startup
    INFO: CORE5053: Application onReady complete.
    INFO: CORE5008: Resource Redeployed: [external-jndi:jms/ImageQCF].
    All the links to setting up external resourses appear to be either dead, or non-reponsive. I need to use MQ as I need to swap messages with an IMS (Mainframe) application.
    This is the binding file that sits in the directory pointed to by the java.naming.provider.url parameter.
    #This file is used by the JNDI FSContext.
    #Mon Feb 23 11:12:23 EST 2004
    jms/ApprovalQ/RefAddr/5/Type=TC
    jms/ImageQCF/RefAddr/12/Encoding=String
    jms/InvoiceQCF/RefAddr/5/Encoding=String
    jms/InvoiceQCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
    jms/InvoiceQ/RefAddr/9/Encoding=String
    jms/ApprovalQCF/RefAddr/7/Content=false
    jms/ApprovalQCF/RefAddr/1/Encoding=String
    jms/ApprovalQ/RefAddr/9/Type=QMGR
    jms/InvoiceQCF/RefAddr/1/Type=TRAN
    jms/ApprovalQCF/RefAddr/10/Type=MBS
    jms/ImageQ/RefAddr/6/Content=273
    jms/ApprovalQ/RefAddr/0/Encoding=String
    jms/ImageQ/RefAddr/7/Encoding=String
    jms/ImageQ/RefAddr/9/Content=ORM_Queue_Manager
    jms/InvoiceQCF/RefAddr/13/Content=SYSTEM.DEFAULT.MODEL.QUEUE
    jms/InvoiceQCF/RefAddr/10/Encoding=String
    jms/InvoiceQCF/RefAddr/5/Type=CHAN
    jms/ApprovalQCF/RefAddr/14/Type=MRET
    jms/ApprovalQCF/RefAddr/3/Type=HOST
    jms/ImageQCF/RefAddr/9/Encoding=String
    jms/InvoiceQ/ClassName=com.ibm.mq.jms.MQQueue
    jms/ImageQ/RefAddr/0/Content=1
    jms/ImageQCF/RefAddr/13/Encoding=String
    jms/InvoiceQCF/RefAddr/6/Encoding=String
    jms/ImageQCF/RefAddr/11/Content=1
    jms/InvoiceQCF/RefAddr/9/Type=PINT
    jms/InvoiceQ/RefAddr/0/Encoding=String
    jms/ImageQ/RefAddr/3/Content=-2
    jms/ApprovalQCF/RefAddr/7/Type=SPAG
    jms/ImageQCF/RefAddr/14/Content=1
    jms/ImageQCF/RefAddr/2/Type=QMGR
    jms/ApprovalQ/RefAddr/6/Content=273
    jms/InvoiceQCF/RefAddr/10/Content=10
    jms/ApprovalQ/RefAddr/1/Encoding=String
    jms/ImageQ/RefAddr/8/Encoding=String
    jms/ApprovalQ/RefAddr/9/Content=ORM_Queue_Manager
    jms/InvoiceQ/RefAddr/7/Content=1
    jms/ImageQCF/RefAddr/6/Type=CCS
    jms/InvoiceQCF/RefAddr/11/Encoding=String
    jms/ImageQCF/RefAddr/8/Content=true
    jms/InvoiceQ/RefAddr/1/Type=EXP
    jms/ApprovalQ/RefAddr/0/Content=1
    jms/ImageQCF/RefAddr/0/Encoding=String
    jms/ImageQ/RefAddr/9/Type=QMGR
    jms/ImageQCF/RefAddr/14/Encoding=String
    jms/ImageQ/FactoryName=com.ibm.mq.jms.MQQueueFactory
    jms/InvoiceQCF/RefAddr/7/Encoding=String
    jms/InvoiceQ/RefAddr/1/Encoding=String
    jms/ApprovalQCF/RefAddr/12/Content=5000
    jms/ApprovalQ/RefAddr/3/Content=-2
    jms/InvoiceQ/RefAddr/5/Type=TC
    jms/ImageQ/RefAddr/1/Type=EXP
    jms/ApprovalQCF/RefAddr/2/Encoding=String
    jms/ImageQCF/RefAddr/11/Type=FIQ
    jms/InvoiceQ/FactoryName=com.ibm.mq.jms.MQQueueFactory
    jms/InvoiceQ/RefAddr/1/Content=-2
    jms/ImageQCF/RefAddr/2/Content=ORM_Queue_Manager
    jms/ApprovalQ/RefAddr/2/Type=PRI
    jms/InvoiceQ/RefAddr/4/Content=1208
    jms/ApprovalQ/RefAddr/2/Encoding=String
    jms/ImageQCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
    jms/ImageQ/RefAddr/5/Type=TC
    jms/InvoiceQ/RefAddr/9/Type=QMGR
    jms/ImageQ/RefAddr/9/Encoding=String
    jms/InvoiceQCF/RefAddr/12/Type=RINT
    jms/InvoiceQCF/RefAddr/12/Encoding=String
    jms/ApprovalQ/RefAddr/6/Type=ENC
    jms/ApprovalQCF/RefAddr/8/Content=true
    jms/ImageQCF/RefAddr/1/Encoding=String
    jms/InvoiceQCF/RefAddr/9/Content=5000
    jms/InvoiceQCF/RefAddr/8/Encoding=String
    jms/InvoiceQ/RefAddr/2/Encoding=String
    jms/InvoiceQCF/RefAddr/2/Type=QMGR
    jms/ApprovalQCF/RefAddr/11/Type=FIQ
    jms/ApprovalQCF/RefAddr/3/Encoding=String
    jms/ApprovalQCF/RefAddr/0/Type=VER
    jms/InvoiceQCF/RefAddr/0/Content=2
    jms/ApprovalQCF/RefAddr/2/Content=ORM_Queue_Manager
    jms/ApprovalQ/RefAddr/3/Encoding=String
    jms/ImageQ/RefAddr/0/Encoding=String
    jms/InvoiceQCF/RefAddr/6/Type=CCS
    jms/InvoiceQCF/RefAddr/3/Content=localhost
    jms/ApprovalQCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
    jms/ApprovalQCF/RefAddr/4/Type=PORT
    jms/InvoiceQCF/RefAddr/13/Encoding=String
    jms/ApprovalQ/FactoryName=com.ibm.mq.jms.MQQueueFactory
    jms/InvoiceQCF/RefAddr/6/Content=819
    jms/ImageQCF/RefAddr/2/Encoding=String
    jms/InvoiceQCF/RefAddr/9/Encoding=String
    jms/ApprovalQCF/RefAddr/8/Type=UCP
    jms/ImageQ/RefAddr/7/Content=1
    jms/ImageQCF/RefAddr/3/Type=HOST
    jms/ApprovalQCF/RefAddr/10/Encoding=String
    jms/ApprovalQCF/RefAddr/4/Encoding=String
    jms/ImageQ/ClassName=com.ibm.mq.jms.MQQueue
    jms/InvoiceQCF/RefAddr/14/Content=1
    jms/ApprovalQ/RefAddr/4/Encoding=String
    jms/ImageQCF/RefAddr/7/Type=SPAG
    jms/ImageQ/RefAddr/1/Encoding=String
    jms/InvoiceQ/RefAddr/2/Type=PRI
    jms/ImageQ/RefAddr/1/Content=-2
    jms/InvoiceQCF/RefAddr/14/Encoding=String
    jms/ImageQCF/RefAddr/12/Content=5000
    jms/ImageQ/RefAddr/4/Content=1208
    jms/ApprovalQ/RefAddr/4/Content=1208
    jms/InvoiceQ/RefAddr/6/Type=ENC
    jms/ImageQ/RefAddr/2/Type=PRI
    jms/InvoiceQ/RefAddr/3/Encoding=String
    jms/ImageQCF/RefAddr/12/Type=RINT
    jms/InvoiceQCF/RefAddr/0/Encoding=String
    jms/ApprovalQ/RefAddr/7/Content=1
    jms/ApprovalQCF/RefAddr/11/Encoding=String
    jms/InvoiceQCF/RefAddr/11/Content=1
    jms/ApprovalQCF/RefAddr/5/Encoding=String
    jms/InvoiceQ/RefAddr/5/Content=0
    jms/ApprovalQ/RefAddr/3/Type=PER
    jms/ImageQ/RefAddr/6/Type=ENC
    jms/InvoiceQ/RefAddr/8/Content=InvoiceQ
    jms/ImageQCF/RefAddr/9/Content=5000
    jms/InvoiceQCF/RefAddr/13/Type=TM
    jms/ApprovalQ/RefAddr/5/Encoding=String
    jms/ApprovalQ/RefAddr/7/Type=FIQ
    jms/ApprovalQ/RefAddr/1/Content=-2
    jms/ImageQCF/RefAddr/0/Content=2
    jms/ApprovalQCF/RefAddr/13/Content=SYSTEM.DEFAULT.MODEL.QUEUE
    jms/ImageQCF/RefAddr/3/Encoding=String
    jms/ApprovalQCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
    jms/InvoiceQ/RefAddr/2/Content=-2
    jms/ImageQCF/RefAddr/3/Content=localhost
    jms/ImageQCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
    jms/InvoiceQCF/RefAddr/3/Type=HOST
    jms/ApprovalQCF/RefAddr/12/Type=RINT
    jms/InvoiceQ/RefAddr/4/Encoding=String
    jms/InvoiceQCF/RefAddr/1/Encoding=String
    jms/ApprovalQCF/RefAddr/1/Type=TRAN
    jms/InvoiceQCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
    jms/ApprovalQCF/RefAddr/6/Encoding=String
    jms/ImageQCF/RefAddr/6/Content=819
    jms/InvoiceQCF/RefAddr/7/Type=SPAG
    jms/ApprovalQ/RefAddr/6/Encoding=String
    jms/ImageQ/RefAddr/2/Encoding=String
    jms/ApprovalQCF/RefAddr/5/Type=CHAN
    jms/InvoiceQCF/RefAddr/7/Content=false
    jms/ApprovalQCF/RefAddr/10/Content=10
    jms/ApprovalQCF/RefAddr/9/Content=5000
    jms/ImageQCF/RefAddr/0/Type=VER
    jms/ImageQCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
    jms/ImageQCF/RefAddr/4/Encoding=String
    jms/ApprovalQCF/RefAddr/9/Type=PINT
    jms/ImageQCF/RefAddr/4/Type=PORT
    jms/InvoiceQ/RefAddr/5/Encoding=String
    jms/ApprovalQCF/RefAddr/12/Encoding=String
    jms/InvoiceQCF/RefAddr/1/Content=0
    jms/ApprovalQCF/RefAddr/3/Content=localhost
    jms/ApprovalQCF/RefAddr/7/Encoding=String
    jms/InvoiceQCF/RefAddr/4/Content=1414
    jms/ApprovalQCF/RefAddr/6/Content=819
    jms/ImageQCF/RefAddr/8/Type=UCP
    jms/InvoiceQ/RefAddr/3/Type=PER
    jms/ApprovalQ/RefAddr/7/Encoding=String
    jms/ImageQ/RefAddr/3/Encoding=String
    jms/ApprovalQ/RefAddr/0/Type=VER
    jms/InvoiceQCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
    jms/InvoiceQ/RefAddr/7/Type=FIQ
    jms/ImageQ/RefAddr/3/Type=PER
    jms/ImageQ/RefAddr/8/Content=ImageQ
    jms/ImageQCF/RefAddr/13/Type=TM
    jms/ImageQCF/RefAddr/5/Encoding=String
    jms/ApprovalQCF/RefAddr/0/Content=2
    jms/InvoiceQCF/RefAddr/10/Type=MBS
    jms/ApprovalQ/ClassName=com.ibm.mq.jms.MQQueue
    jms/InvoiceQCF/RefAddr/12/Content=5000
    jms/InvoiceQCF/RefAddr/2/Encoding=String
    jms/InvoiceQ/RefAddr/6/Encoding=String
    jms/ApprovalQ/RefAddr/4/Type=CCS
    jms/ApprovalQCF/RefAddr/13/Encoding=String
    jms/ImageQ/RefAddr/7/Type=FIQ
    jms/ApprovalQCF/RefAddr/8/Encoding=String
    jms/InvoiceQCF/RefAddr/14/Type=MRET
    jms/ImageQ/RefAddr/2/Content=-2
    jms/ApprovalQ/RefAddr/8/Encoding=String
    jms/ApprovalQ/RefAddr/8/Type=QU
    jms/InvoiceQCF/RefAddr/0/Type=VER
    jms/ImageQCF/RefAddr/13/Content=SYSTEM.DEFAULT.MODEL.QUEUE
    jms/ImageQ/RefAddr/4/Encoding=String
    jms/ImageQ/RefAddr/5/Content=0
    jms/ApprovalQ/RefAddr/5/Content=0
    jms/ApprovalQCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
    jms/ApprovalQ/RefAddr/8/Content=ApprovalQ
    jms/ApprovalQCF/RefAddr/13/Type=TM
    jms/InvoiceQCF/RefAddr/4/Type=PORT
    jms/ImageQCF/RefAddr/6/Encoding=String
    jms/ImageQCF/RefAddr/10/Encoding=String
    jms/InvoiceQ/RefAddr/6/Content=273
    jms/ImageQCF/RefAddr/7/Content=false
    jms/ApprovalQCF/RefAddr/2/Type=QMGR
    jms/InvoiceQCF/RefAddr/3/Encoding=String
    jms/InvoiceQ/RefAddr/7/Encoding=String
    jms/ApprovalQCF/RefAddr/14/Encoding=String
    jms/InvoiceQ/RefAddr/9/Content=ORM_Queue_Manager
    jms/ApprovalQCF/RefAddr/9/Encoding=String
    jms/InvoiceQCF/RefAddr/8/Type=UCP
    jms/ImageQCF/RefAddr/10/Content=10
    jms/ApprovalQ/RefAddr/2/Content=-2
    jms/ApprovalQCF/RefAddr/6/Type=CCS
    jms/ImageQCF/RefAddr/1/Type=TRAN
    jms/ApprovalQ/RefAddr/9/Encoding=String
    jms/InvoiceQ/RefAddr/0/Content=1
    jms/ImageQ/RefAddr/5/Encoding=String
    jms/ImageQCF/RefAddr/1/Content=0
    jms/ApprovalQCF/RefAddr/14/Content=1
    jms/InvoiceQ/RefAddr/3/Content=-2
    jms/ImageQCF/RefAddr/4/Content=1414
    jms/ImageQCF/RefAddr/5/Type=CHAN
    jms/ImageQCF/RefAddr/7/Encoding=String
    jms/InvoiceQ/RefAddr/0/Type=VER
    jms/ImageQCF/RefAddr/11/Encoding=String
    jms/InvoiceQCF/RefAddr/4/Encoding=String
    jms/InvoiceQ/RefAddr/8/Encoding=String
    jms/ImageQ/RefAddr/8/Type=QU
    jms/ImageQCF/RefAddr/9/Type=PINT
    jms/ApprovalQCF/RefAddr/0/Encoding=String
    jms/ImageQ/RefAddr/0/Type=VER
    jms/InvoiceQCF/RefAddr/8/Content=true
    jms/ApprovalQCF/RefAddr/11/Content=1
    jms/InvoiceQ/RefAddr/4/Type=CCS
    jms/ImageQCF/RefAddr/10/Type=MBS
    jms/ImageQ/RefAddr/6/Encoding=String
    jms/ApprovalQ/RefAddr/1/Type=EXP
    jms/ImageQ/RefAddr/4/Type=CCS
    jms/ApprovalQCF/RefAddr/1/Content=0
    jms/InvoiceQ/RefAddr/8/Type=QU
    jms/ImageQCF/RefAddr/14/Type=MRET
    jms/InvoiceQCF/RefAddr/11/Type=FIQ
    jms/InvoiceQCF/RefAddr/2/Content=ORM_Queue_Manager
    jms/ApprovalQCF/RefAddr/4/Content=1414
    jms/ImageQCF/RefAddr/8/Encoding=String
    Can anyone help me with this.

    Hi Midhun Joseph,
    Please check the below thread and see if it helps.
    https://supportforums.cisco.com/thread/2070836
    Thanks,
    Anand

  • Web Services with Sun App Server

    We are load testing a simple web service running in SJSAS 8.0 Standard. With 1 or 2 users concurrent it seems OK, but once we move up to 5 concurrent users calling the WS, the domain in SJSAS crashes.
    Does anyone have experience or information regarding the app server and load with web services? Are there some config options that we can tweak? Are there any numbers out there about how many simultaneous connections the server can handle?
    A final note, things seem fine if we are just serving a simple web page from the server, its only when we try to call a WS that we run into these performance issues.
    Thanks.

    Are you connecting to any external resource using JNDI by any chance? If you're using Unix, check the number of file descriptors being opened on the Sun App server. "new dirContext(env)" creates OS file descriptors each time it's invoked (calling the web service for example).
    use
    $ps -ax
    get the process number of sjas and try issuing a:
    lsof -p <sjas_process_number> |wc -l
    and keep invoking the web service. If this number keeps increasing then you've an "fd" leak (perhaps not closing the dirContext). Linux for example has a default max file limit of 1024 under "root" user and when depleted, sjas will hang.
    Could this be the problem?
    Cheers
    Steve

  • "Message Driven Bean" doesn't work with Sun App Server

    Hello all,
    i have a little bit problems, running a simple "Message Driven Bean" under the Sun App Server. The deployment of it works fine, but after starting the SUN App Server i get the following error message:
    An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.
    Has anybody a workaround for this problem?
    The queue seems to be correctly installed. A simple client programm from the Sun Tutorial (Consumer & Producer) works fine without any Errors or Exceptions.
    I am a little bit confused, because the queue seems to work with the client programms but not with a MDB running on the SUN App Server.
    Thanks for you help!
    Greetings
    Manuel

    Hello Mr Manuel!
    could you plz help me with the steps for creating a message driven bean using netbeans ver 5.0(with Sun Java� System Application Server Platform Edition 8.2 )
    I just know how to work with Session beans & Entity Bean, and am try to learn to work on Message Driven Beans too. there are no proper tutorials where i can find steps for creating these..
    I need the steps from the scratch.,like creating QueueConnection Factory & Destination etc..
    It will be gr8 if you can help me with this at the earliest .
    Thank you
    Bye

  • Problem : App works with Sun App server 8.0 but fails with 8.1

    Hi All
         I am experiencing some strange problem with executing my JSF application with Sun App Server.
         I have an EAR deployed on Sun Application Server 8.0 and 8.1.
         Strangely it works quite fine with 8.0 but fails with 8.1.
         In my JSP page ..I have a dummy component whose getter method is used as a "FormLoad" event of the page.
         <h:form id="imageForm" enctype="multipart/form-data">
         <h:messages showDetail="true" />
         <table width="980" border="1" cellpadding="0" cellspacing="0" bordercolor="#A9B8C2">
              <tr>
    <td>     
                   <h:inputHidden value="#{Screen1.initializeService}"/>
              <h:selectOneListbox styleClass="style2" id="cmbMiddleArea" immediate="true" value="#{Screen1.selectedMiddleArea}">
              <f:selectItems value="#{Screen1.middleAreaList}" />
         </h:selectOneListbox>
         In my backing bean i have ..
         public String getInitializeService() {
              ..... Retrieve all the data from DB to initialize all the components on the JSP page
              .......setMiddleAreaList......
              .......setSelectedMiddleArea.....
              ........set the values of the individal component...
         I am retrieving all the data from DB in this getter method and intializing the components on the JSP page.
         I have also checked the code generated for JSP by both the servers.I am posting the code here for reference although
         i did not find any significant difference between the two...
         For Server 8.0
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
         return false;
         For Server 8.1
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         PageContext pageContext = jspxpage_context;
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
         return false;
         Now the actual problem is "getInitializeService" method never gets called when i deploy and run the application on Sun App Server8.1
         However with Sun App Server 8.0 it woeks perfectly fine.
         Can anybody help me in resolving these issues ?
         

    Actually generated JSP code can be referred as ...
    For Server 8.0
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
         return false;
         For Server 8.1
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         PageContext pageContext = jspxpage_context;
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
         return false;
         }

  • How to Non-ACC Client connect Sun App Server 8 with SSL

    I have create a Rich Client(Non-ACC) that connect to Sun App Server 8 with IIOP(8001) and is working fine. However, when I try to connect to same server with using SSL (8002) and throw exception during lookup a Bean as below.
    Please help!!
    Server Configuration
    ================
    IIOP Port(s): 8001, 8002, 8003
    All listener ports are enabled
    Client Coding
    ===========
    env.put(javax.naming.Context.PROVIDER_URL, "iiop://"+url);
    env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
    System.setProperty("javax.net.ssl.keyStoreType", "jks");
    System.setProperty("javax.net.ssl.keyStore", "D:\\Sun\\AppServer\\domains\\adsr\\config\\keystore.jks");
    System.setProperty("javax.net.ssl.keyStorePassword", "password");
    System.setProperty("javax.net.ssl.trustStore", "D:\\Sun\\AppServer\\domains\\adsr\\config\\cacerts.jks");
    System.setProperty("javax.net.ssl.trustStorePassword", "password");
    System.setProperty("com.sun.CORBA.connection.ORBSocketFactory", "com.sun.enterprise.iiop.IIOPSSLSocketFactory");
    ic = new InitialContext(env);
    Object objref = ic.lookup("ejb20/statelessSession/EntControllerHome");
    Exception
    ========
    [java] Mar 18, 2005 4:43:59 PM com.sun.corba.ee.spi.logging.LogWrapperBasedoLog
    [java] INFO: "IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/4645"
    [java] Mar 18, 2005 4:44:00 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl readFully
    [java] WARNING: "IOP00410215: (COMM_FAILURE) Read of full message failed :
    bytes requested = 12 bytes read = 7 max wait time = 300 total time spent waiting = 364"
    [java] org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 215 completed: No
    [java] at com.sun.corba.ee.impl.logging.ORBUtilSystemException.transportReadTimeoutExceeded(ORBUtilSystemException.java:2629)
    [java] at com.sun.corba.ee.impl.logging.ORBUtilSystemException.transportReadTimeoutExceeded(ORBUtilSystemException.java:2655)
    [java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.readFully(SocketOrChannelConnectionImpl.java:676)
    [java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.read(SocketOrChannelConnectionImpl.java:545)
    [java] at com.sun.corba.ee.impl.protocol.giopmsgheaders.MessageBase.readGIOPHeader(MessageBase.java:119)
    [java] at com.sun.corba.ee.impl.transport.CorbaContactInfoBase.createMessageMediator(CorbaContactInfoBase.java:153)
    [java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.readBits(SocketOrChannelConnectionImpl.java:325)
    [java] at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.handleEvent(SocketOrChannelConnectionImpl.java:1175)
    [java] at com.sun.corba.ee.impl.transport.SelectorImpl.run(SelectorImpl.java:275)
    [java] javax.naming.CommunicationException: Can't find SerialContextProvider [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 208 c
    ompleted: Maybe]
    [java] at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:133)
    [java] at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:290)
    [java] at javax.naming.InitialContext.lookup(InitialContext.java:347)
    [java] at com.shkco.jaf.test.JAFLogonTest.connect(JAFLogonTest.java:110)
    [java] at com.shkco.jaf.test.JAFLogonTest.setUp(JAFLogonTest.java:134)
    [java] at junit.framework.TestCase.runBare(TestCase.java:125)
    [java] at junit.framework.TestResult$1.protect(TestResult.java:106)
    [java] at junit.framework.TestResult.runProtected(TestResult.java:124)

    I don't think tomcat supports the ejb-ref portion of web.xml. If you're using ejbs your best bet is to use a web container within a J2EE implementation.
    --ken                                                                                                                                                                                                                                                                                                                                           

  • Problem with sun app server startup

    hi,
    i am getting problem with sun app server default start.the error is::
    [#|2006-03-01T13:54:35.121+0530|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    now i am useing Win Xp operating system,
    show me a solution.
    Regs..
    Narasimha

    You haven;t specified the exceptions you r getting ........while starting your default server.
    if u r getting exception about InetClass then connect your system with LAN/Internet then your problem will be solved becoz i m using same location address as you specified, space doesn't matter at all - i think so, it is running fine........

  • Is soap provider agent only available for Sun app server 9.1?

    See the blue print on securing web services with soap provider agent. Is this agent embedded within the J2EE agent for sun app server 9.1? Is the same "soap provider agent" available for websphere 6.x or iis server?
    Thanks

    the agentadmin --install script does not seem to add all the required things to the server-classpath in the domain.xml
    mine now looks like this:
    /opt/j2ee_agents/appserver_v9_agent/lib/agent.jar
    /opt/j2ee_agents/appserver_v9_agent/locale
    /opt/j2ee_agents/appserver_v9_agent/Agent_001/config
    /opt/j2ee_agents/appserver_v9_agent/lib/amclientsdk.jar
    /opt/j2ee_agents/appserver_v9_agent/lib/fmclientsdk.jar
    /opt/j2ee_agents/appserver_v9_agent/lib/opensso-installtools.jar
    /opt/j2ee_agents/appserver_v9_agent/lib/opensso-installtools-launcher.jar
    AND, I've added a system property:
    -Dcom.sun.identity.agents.config.location=/opt/j2ee_agents/appserver_v9_agent/Agent_001/config/AMAgent.properties
    I now at least get a different error:
    Servlet.service() for servlet jsp threw exception
    java.lang.ExceptionInInitializerError
         at com.sun.identity.agents.filter.URLPolicyTaskHandler.initialize(URLPolicyTaskHandler.java:63)
    com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
    Caused by: java.lang.RuntimeException: Exception caught in AmWebPolicyManager initializer: Unable to load IAmWebPolicy: com.sun.identity.agents.policy.AmWebPolicy
         at com.sun.identity.agents.policy.AmWebPolicyManager.<clinit>(AmWebPolicyManager.java:135)
         ... 24 more

  • Fedora core 6 sun app server won't start

    Sun app server 8.2 bundled with creator 2u1 doesn't start. This install was running fine under fc5. Among other things I get the following with pe-start -reset which I think might be the crust of the problem:
    "Unable to read system environment. No system environment will be used."
    Any help appreciated.

    Exported projects to nb5.5 with visual-web pack and after fixing datasources and libraries things are working again. Could not find a solution for Creator2 on Fedora Core 6. Thanks anyway.

  • Sun app server problem using asadmin tool

    I have installed sun app server and trying to do the simplemessage tutorial. When I run the
    ant create-cfcommand I get the following
    [exec] Invalid user or password
    [exec] CLI137 Command create-jms-resource failed.I have put an echo line in app-server-ant.xml to see what the command is and it is.
    [echo] c:/Sun2/SDK/bin/asadmin.bat create-jms-resource --user admin  --passwordfile C:/Sun2/SDK/javaee-5-doc-tutorial-1.0_03/javaeetutorial5/examples/common/admin-password.txt --host localhost --port 4850 --restype javax.jms.ConnectionFactory --enabled=true jms/ConnectionFactoryI have checked the password file and it is
    AS_ADMIN_PASSWORD=adminadminAny ideas?
    I have checked around about using parameter password but when running this I get an error saying this is not valid and that I should use passwordfile
    Kelvin

    You haven;t specified the exceptions you r getting ........while starting your default server.
    if u r getting exception about InetClass then connect your system with LAN/Internet then your problem will be solved becoz i m using same location address as you specified, space doesn't matter at all - i think so, it is running fine........

  • Can JSC support Sun App Server 9?

    Does anyone know if JSC can support sun app server 9?
    Last I heard was that 8.2 is the max version.
    Along the same line, is there any word of another update to JSC
    that will work with app server 9 and jdk 6???

    Hi!
    Actually You can deploy your application to Sun App Server 9.0, but probably not all features will work. But now You can download NetBeans 5.5 and Visual Web Pack for it (it's a next step of Creator's evolution) and this IDE supports GlassFish (opensourced Sun App Server 9.0).
    Thanks,
    Roman.

  • Exceptions trying to run JSF on Sun App Server

    Hi!
    I have downloaded the Sun App Server and am trying to run the JSF Sample on it. The first page comes up fine, and when I enter data, it processes but does not come back with the response. I get the following errors:
    java.lang.ClassNotFoundException: com.sun.faces.application.StateManagerImpl$TreeNode
    java.lang.ClassNotFoundException: com.sun.faces.application.WebappLifecycleListener
    java.lang.IllegalStateException: No FacesContext is available to process this request.
    Not sure if this is the right forum..
    Thanks

    Make sure you started the default server. Try
    http://localhost:8080. This will allow you to see if the appserver is running. The first page is a jsp an will run regardless of if the server is running. To start the defaul server look at you windows menu under Sun Microsystems.

  • Can I run Servlets in the Sun App Server?

    I am trying to run a servlet. I am not sure if I can run the same using the Sun app server. any help to clarify the following queries would be appreciated.
    1. Should I have to specify a path in the environmental variables?
    2. Is there a web site that tells me the same with respect to running the servlet on a Sun app server.
    Thanks in advance.
    --Srikanta                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

    I'm not sure what you want in regards to question, but I can assure you that you can run servlets in S1AS7. My recommendation is to just package your servlet into a web archive (war) and deploy it. You can deploy it via the commandline (asadmin) or the web based administrative client (likely http://localhost:4848). For more information on this I suggest reading:
    http://docs.sun.com/source/816-7150-10/index.html
    You must likely want to read the section on assembling and deploying web applications.
    Matt Bauer

  • Sun App Server 8.1 and 8.2 could not start

    Hi friends, thank for various suggestions. pls i'm having problem with Sun App Server 8.1 and 8.2. I installed Portal 7 on Red Hat Enterprise Linux 3 and also Sun Portal 6 on Suse Linux 9. The problem is that App server keep giving Login exception after using them for a while. The details is given below:
    after typing ./asadmin start-domain --user admin domain1. Instead of it to give me the password prompt, it threw the following exception:
    INFO: SEC5046: Audit: Authentication refused for [admin]
    Login Failed javax.security. auth.login.LoginException: Failed file for login admin
    CL1156 could not start the domain domain1.
    I always login to the O/S as root.
    Any suggestion will be highly appreciated. Thanks

    Thanks very much kedar.mhaswade for your suggestions.
    I do not have a regular access to the Internet, I
    would have gotten back earlier than this, so i'm
    sorry. Anyway, i checked the content of
    ~/.asadminprefs and the password is not the same with
    the one i'm using. I found the default password
    supplied by Sun but I don't think this could be the
    problem. I'm actually using the App server that is
    bundled with Sun Portal 6 and 7 and so i supplied my
    own password during installation and i've logged in
    several times after installation. It just failed in
    one of those logins and had stopped working since. I
    always encountered the same problem either when using
    Sun Portal 7 or 6 on Red Hat ES 3 and Suse 9
    respectively.
    I'm posting the content of admin-keyfile as you
    requested:
    admin;{SSHA}Qf/m4KEBDPojsP1mkjywE5XZA6SPh7i8WQmV/A==;a
    sadmin
    # Domain User and Password - Do Not Delete Entry
    Above
    So i will so much appreciate your help and i wouldn't
    mind if you could send me your phone number. Thanks.Hi tolulike,
    Even if you supplied your own password, we have this developer friendly
    feature that has side effects that are at times hard to diagnose. Can you
    please
    - rename the .asadminprefs file and make sure that there is no .asadminprefs file in your home directory?
    - attempt to start the domain.
    You should be prompted for the password.
    The idea is that when you've got that file and that entry AS_ADMIN_PASSWORD in your home directory, asadmin will read it
    from there and you land in this (unfortunate) situation.
    Obviously doing this might have some side effects with other domains. This
    is because for all domains, asadmin reads this file as a last resort. So,
    it might so happen that this file is actually required for functioning of your
    other domains.
    But now you know when this file is used, so there is no mystery (hopefully).
    Let me know if this works.
    Thank you.
    Kedar

  • Installing sun apps server 7 on redhat 7.3

    Firstly I have redhat 9 so can I install the sunapps server 7 on redhat 9 ?
    secondly
    can I install sun apps server 7 on atleast redhat 7.3?
    the document with sun apps says that I can install sun apps server 7 on 7.2
    regards
    Mishra

    Hey Paul,
    I'm having problems just installing SUN ONE AS Standard Edition 7.0 on my Redhat 7.2 as ROOT. Did you not get any problems even starting it. It installed okay, but when I initially ran the script to start it (./asadmin start-appserv)... it kept crapping out. I did notice some JMS errors in the log, but I haven't come across any documentation on possible bugs. Thanks in advance,
    Tak.

Maybe you are looking for