Jndi lookup fails on Sun app server 8

My standalone client on java is able to lookup TopicConnectionFactory on localhost on Sun Server 7 perfectly, but fails on Sun Server 8. I've set up the resources correctly as described in the J2EE 1.4 tutorial, but I get the following error:
SEVERE: NAM5003: CommunicationException in SerialContext lookup()
java.lang.NullPointerException
     at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:64)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:148)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
javax.naming.CommunicationException:
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:174)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)What could be wrong??

It turned out to be a JMS library version issue. I had files for Server 8.0, but was running 8.1. Who knew it would be that big a deal.
Now that I have the right version, I'm able to look up topics and queues, but cannot lookup TopicConnectionFactory. The client does not return at connectionFactory = (TopicConnectionFactory)initial.lookup("jms/FieldTopicConnectionFactory"); and no error in server.log.
Here's the rest of the code:
try {
         Context initial = new InitialContext();
           connectionFactory = (TopicConnectionFactory)initial.lookup("jms/FieldTopicConnectionFactory"); //does not return
         dest = (Topic) initial.lookup("jms/FieldTopic"); //this works!!
} catch{...}I run my standalone through these JVM args:
-Dorg.omg.CORBA.ORBInitialPort=3700 -Dorg.omg.CORBA.ORBInitialHost=myserver.com

Similar Messages

Opensso.war deployment fails in Sun App server 8.2 windows vissta business

I tried deploying opensso.war in Sun App server 8.2 on windows vista business machine. Am getting following error.
Deploying application in domain failed; C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied) ; requested operation cannot be completed C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied)
Am I missing something

This is windows permission to the folder issue

EJB not getting bound to JNDI name using Sun App Server upon deployment

Hello,
I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
               jndiProperties = new Properties();
               jndiProperties.put("java.naming.factory.initial",
                    "com.sun.jndi.cosnaming.CNCtxFactory");
               jndiProperties.put("java.naming.provider.url",
                    "iiop://localhost:3700"); // ORB listener is listening on port 3700...
               context = new InitialContext(jndiProperties);
               home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
               ...The exception I receive is:
               [java] 234 ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
org/CosNaming/NamingContext/NotFound:1.0]
     [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
     [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
     [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
4)
     [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
Context/NotFound:1.0
     [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
     [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
     [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
     [java]     ... 4 moreHere is my ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar
     xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
     version="2.1">
     <enterprise-beans>
          <session>
               <ejb-name>HelloWorldEJB</ejb-name>
               <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
               <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
               <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
               <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
               <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
          </session>
     </enterprise-beans>
</ejb-jar>Here is my sun-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
<sun-ejb-jar>
     <enterprise-beans>
          <ejb>
               <ejb-name>HelloWorldEJB</ejb-name>
               <jndi-name>HelloWorldEJB</jndi-name>
          </ejb>
     </enterprise-beans>
</sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
Thank you very much for your time and help.

Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

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;
     }

HELP - Can't connect to Sun App Server

Hi,
I'm confused. The Sun App Server documentation states that the protocol to use in the JNDI context lookup is jms or tcpjms, and that the service runs on port 7676:
javax.naming.ConfigurationException: Invalid URL: jms://localhost:7676 [Root exception is java.net.MalformedURLException: unknown protocol: jms]
When I use the other (commented-out) line: iiop://localhost:3700, I get a different error (and I don't think this is the protocol I want to use anyway).
JNDI API lookup failed: javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
So which is it?? Here is my code...thanks in advance for your help!
package com.tpc.jms.simpleProducer;
import javax.jms.*;
import javax.naming.*;
import java.util.Hashtable;
import java.util.Properties;
public class SimpleJMSTest {
// public static final String PROVIDER_URL = "iiop://localhost:3700";
public static final String PROVIDER_URL = "jms://localhost:7676";
public static final String CONTEXT_FAC = "com.sun.jndi.cosnaming.CNCtxFactory";
public static void main (String argv[]) {
try {
Properties properties = new Properties();
properties.put(Context.PROVIDER_URL, PROVIDER_URL);
properties.put(Context.INITIAL_CONTEXT_FACTORY, CONTEXT_FAC);
properties.put(Context.SECURITY_PRINCIPAL, "guest");
properties.put(Context.SECURITY_CREDENTIALS, "guest");
InitialContext initialCtx = new InitialContext(properties);
System.out.println("Good!");
//TopicConnectionFactory topicConnFactory = (TopicConnectionFactory) initialCtx.lookup (fac);
//Topic nasdaqTopic = (Topic)initialCtx.lookup(topic);
/* System.out.println("Creating topic connection");
TopicConnection topicConnection = topicConnFactory.createTopicConnection();
topicConnection.start ();
System.out.println("Creating topic session: not transacted, auto ack");
TopicSession topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
System.out.println("Creating topic, subscriber");
TopicSubscriber nasdaqTopicSubscriber = topicSession.createSubscriber (nasdaqTopic);
System.out.println ("Ready to subscribe for messages :");
nasdaqTopicSubscriber.setMessageListener(new SubscriberListener());*/
catch (Exception e) {
e.printStackTrace ();
}

Hi,
First of all, you don't use iiop in JMS.
And also for your problem, did you by any chance forget to create your connectionfactory in the application server?

Deploying a WAR file to Sun App Server 8.1 PE

So I thought that if I downloaded Sun App Server PE 8.1 and put it on my soon-to-be production machine, it should be pretty easy right?
Nope. So I have JSC update 6 (which includes Sun Application Server 8.0) (God how I wish there was a catchy name like Tomcat or something)
And I have a machine running a good copy, installed and everything, of Sun Application Server 8.1 Platform Edition (another catchy name) up on the production target.
I create a WAR file in JSC, scp it up.
Then try to deploy it - so I get bit by the no DB connection thing.
Ok, but when I copy each of my connection's attributes (the driver (which I did copy up to the lib directory) is MySQL's Connector/J)
I copy the username, password, URL and DriverClass attributes to the connection pool.
I still get a
"Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.sun.sql.datasource.DriverAdapter"
when I try to Ping the ConnectionPool
I have javax.sql.DataSource as the resource type... (same as 8.0 uses)
what JAR file is DriverAdapter in? anyone know?
cheers,
Kris

Okay. mysql folks - this works......
here's what happened, on the production server, different from the dev machine....
mysql 4.1.9
sun application server platform edition PE 8.1
connector/j - latest
and on the dev machine: JSC Update 6 and the app works fine on the dev machine.
first, there is a JAR file in ~whatever/Create/SunAppServer/lib/ named
driveradaptor.jar
and it it comtains
com.sun.sql.datasource.DriverAdapter
which 8.1 ain't got
and should be copied up to
/installdir/SunAppServer/domains/domain1/lib/ext/driveradapter.jar
(domain1 is your app svr domain that runs your app.)
your Connector/J JAR needs to go here too. I used:
mysql-connector-java-3.2.0-alpha-bin.jar
downloaded from mysql.com.
and then there is the whole thing about Added Properties in the Connection Pool page inside the 8.1 Admin Console (which is nice work guys). Gawd, I added a bunch of properties and am, frankly, not sure which ones actually work (for the Ping, for the initial connection creation and the eventual successful connection all seem to use different combinations...)
and I found this in the domain's domain.xml once all the admin console page filling was done - but you'll need to add each one as a Property in the connection pool:
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.sun.sql.datasource.DriverAdapter" fail-all-connections="false" [blah...]
<property name="Username" value="root"/>
<property name="Password" value="secret"/>
<property name="ValidationQuery" value="SELECT 1"/>
<property name="DriverClassName" value="com.mysql.jdbc.Driver"/>
<property name="LoginTimeout" value="0"/>
<property name="Url" value="jdbc:mysql://localhost/databasename?autoReconnect=true"/>
<property name="User" value="root"/>
<property name="password" value="secret"/>
<property name="PasswordCredential" value="secret"/>
</jdbc-connection-pool>
(and you see how User and Username and username are all the same thing? well, different parts of 8.1 seem to use different attributes...)
Just keep Adding Properties in the connection pool until you get them all....
Oh and, the two key class references for the pool are:
datasource class: com.sun.sql.datasource.DriverAdapter
resource type: javax.sql.ConnectionPoolDataSource
Finally: in the /installdir/SunAppServer/domains/domain1/applications/j2ee-modules/YourAppName/WEB-INF/
your 'sun-web.xml' (don't delete it, like some have advocated, I think that wrong) needs to look like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd">
<sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>/yourcontext</context-root>
<resource-ref>
<res-ref-name>jdbc/Yourname</res-ref-name>
<jndi-name>jdbc/Yourname</jndi-name>
<default-resource-principal>
<name>root</name>
<password>secret</password>
</default-resource-principal>
</resource-ref>
</sun-web-app>
and I think that's all of it. the only Bug I would I would say is that the sun-web.xml should have the right res-ref-name, but then I think the Creator Team knows this and will fix it sometime soon.
cheers,
and Roger Federer lost in the Aussie Open. (I think he lost tomorrow too, that whole time zone thing being so damn Einsteinian...)
-Kristofer

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.

Connecting to EJ bean in Sun App Server 8

I am working my way through the j2eetutorial14, and have successfully built the Converter app. However, I need to run the stand-alone client, connecting to the bean, in a server-independent way. So, as part of my exercise, I copied the client code in Eclipse, and made the following changes to the code:
from the original example:
Context initial = new InitialContext();
Context myEnv = (Context) initial.lookup("java:comp/env");
Object objref = myEnv.lookup("ejb/SimpleConverter");
ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);to this:
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
properties.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:3700");
Context initial = new InitialContext(properties);
Object objref = initial.lookup("ConverterBean");
ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);Now I am getting this exception in the narrow() method:
java.lang.ClassCastException
     at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
     at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
     at ConverterClient.main(ConverterClient.java:27)When I run the client from the script:
appclient -client ConverterAppClient.jarit works as expected. I am obviously missing something in my Eclipse runtime environment, but the manual was of no help so far. (But j2ee.jar library from C:\Sun\AppServer\lib is in the classpath.)
If anyone successfully connected to the Sun App Server 8 EJB from a stand-alone client and can share their wisdom, I will appreciate it.
On a more general note, what are the pitfalls to watch for when writing, packaging and distributing an EJB app (bean and stand-alone client) in a server-independent way? Any pointers?
Thanks for any help.
Alex.

Did you have the EJB client JAR in your classpath? Yes, and I spent all day searching the Forums for the clues. I found the answer, and was going to post it here. The client JAR was missing the RMI stubs. The process of generating the stubs is quite cumbersome - at least, the one that I discovered. It involves deploying the EAR first, then going to the Admin Console and manually setting a number of options, then collecting the sought-for JAR from the Sun App Server's applications directory. The generated file will contain the stubs, and also the Home and Remote interface files, as well as the bean class (something that the client will never need). So, I may have to write a script to strip off the needless baggage from the client JAR.
I have been working with JBoss and its plugin for Eclipse for some time now, and grew spoiled by the ease of deployment there, including the fact that the JBoss/Eclipse combo took care of the RMI stubs and many other things that Sun's server exposes to the developer.
Anyway, here is my cookbook that I made as I was working through the process of generating the stubs:
====================================
Creating a stand-alone Client:
The stand-alone client need RMI stubs to communicate with the EJ bean on the server side. To create the stubs:
1. Start the Admin Console web page (Start > All Programs > Sun Microsystems > Application Server PE > Admin Console). In the left-hand frame select: Applications > Enterprise Applications.
2 In the right-hand frame, press Deploy button.
3 Select file to upoad (navigate to the application EAR). Press Next.
4. Set Application Name field (it should be preset), and check the Generate: RMIStubs checkbox. If this procedure was done before, check the Redeploy box to force generation of the file.
5. Press OK button.
The JAR file with stubs will be placed into C:\Sun\AppServer\domains\domain1\applications\j2ee-apps directory.
The stubs have format _name_Stub.class and _nameHome_Stub.class (e.g. for Converter app the files are ConverterStub.class and ConverterHomeStub.class). These files must be extracted and placed into the client's classpath. Alternatively, the entire JAR file can be made part of the client's classpath.
====================================
Thank you for the quick reply.
Alex.

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

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

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

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

Sun App server can't start

Hello,
I've got Sun One Studio and I can't start the Application Server. I have created a domain like this int the command prompt :
asadmin> create-domain path /global/appserver adminport=4848 adminuser xxx adminpassword xxx scdomain
Domain scdomain successfully
But when I start the server, I've got a message :
Le service Sun App Server 7 Admin Server (domain1:admin-server) d�marre.....
Le service Sun App Server 7 Admin Server (domain1:admin-server) n'a pas pu �tre
lanc�.
Le service n'a pas signal� d'erreur.
Vous obtiendrez une aide suppl�mentaire en entrant NET HELPMSG 3534.
C:\Sun\jstudio\AppServer7\domains\domain1\admin-server\bin>net helpmsg 3534
Le service n'a pas signal� d'erreur.
In english, it is said that the server can't have been started. And there isn't any error ...
Whith Sun Studio one, I've got this message :
Could not start the instance
server failed to start: abnormal subprocess termination
Can somenone help me please ?
Thanks in advance.

OK thanks caseylou. The server.log file contains that :
[12/Oct/2004:14:29:02] INFO ( 2612): CORE1116: Sun ONE Application Server
[12/Oct/2004:14:29:03] FATAL ( 2612): CORE4005: Internal error: unable to create JVM
[12/Oct/2004:14:29:03] SEVERE ( 2612): CORE4009: Failed to load JVM (check your JRE)
[12/Oct/2004:14:29:03] SEVERE ( 2612): CORE3187: Late initialization failed: Error running init function(late) init-j2ee: unknown error
Sorry, I have created two topics in the forum (J2SE and J2EE) because on the J2SE I have been recommended this forum.
Maybe it is better to continue on the first topic ?
http://forum.java.sun.com/thread.jsp?forum=17&thread=561619&tstart=0&trange=15
Sorry for "flooding".

How to install j2ee sun app server 8.0 in debain linux

hi guys
i am new to linux and i have downloaded the j2ee sun app server 8.0(linuxversion) from sun.java
in sun.java documentation says first we have to change the mode to excecutable
then he is saying to do this
1. To run the installation program that uses a graphical interface, at the command prompt type the name of the bundle file at the command prompt.
2.To run the installation program that uses the command-line interface, at the command prompt type the name of the bundle file followed by the -console option.
after chmod + x <bundle name >
the next step i am not able to do it
what to do next
any suggestions
regards
sandeep

Hi rlubke
Thanks for the suggestion
1.Change the permission of the bundle file so that you have execute access:
chmod +x <bundle-file-name>
2. To run the installation program that uses a graphical interface, at the command prompt type the name of the bundle file at the command prompt.
3.To run the installation program that uses the command-line interface, at the command prompt type the name of the bundle file followed by the -console option.
Step 1. After chmod + x <bundle name >
Step 2. sun/appserver/# <bundle name>
bash: <bundle name>: command not found
Step 3. sun/appserver# <bundle name>
bash: <bundle name#>: command not found
any suggestions
i have done what u have said now
Step 1. After chmod + x <bundle name >
Step 2. sun/appserver/#./ <bundle name>
Checking available disk space....
Checking Java(TM) 2 Runtime Environment...
Extracting Java(TM) 2 Runtime Environment files...
Extracting installation files...
Launching Java(TM) 2 Runtime Environment....
Error: There are no files requiring installation.
Deleting Temporary files...
Step 3. sun/appserver# <bundle name>
Checking available disk space....
Checking Java(TM) 2 Runtime Environment...
Extracting Java(TM) 2 Runtime Environment files...
Extracting installation files...
Launching Java(TM) 2 Runtime Environment....
Error: There are no files requiring installation.
Deleting Temporary files...
this is what happening excatly

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.

Jndi lookup fails on Sun app server 8

Similar Messages

Maybe you are looking for