Accessing Sun App Server JNDI context from j2se client

The following client's code snippet is raising javax.naming.NameNotFoundException.
public static void main(String[] args)
     try
          Context jndiContex = getInitialContext();
          Object ref = jndiContex.lookup("java:comp/env/ejb/ru.srpu.jtest.service.UserRemote");
          UserRemote user = (UserRemote)PortableRemoteObject.narrow(ref,UserRemote.class);
          //logic goes here...
     catch (NamingException e)
          e.printStackTrace();
public static Context getInitialContext( ) throws javax.naming.NamingException
     Properties p = new Properties( );
     p.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
     p.put(Context.PROVIDER_URL, "iiop://localhost:3700/");
     return new javax.naming.InitialContext(p);
}Beans are packed into the ejb-jar module of the EAR and deployed successfully. EJB's jndi-name is correct as well.
Help to find a bug, please!

We have a number of FAQ entries that cover client JNDI access here :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
-ken

Similar Messages

JAXRPC.TIE.01 exception from Sun App Server 8.1 for Mozilla client

Trying to access with Moziall/Firefox web service implementation the simple sayHello stateless session bean sample from J2EE 1.4 tutorial. WSDL parsing works, but when I try to call sayHello, I do get
JAXRPC.TIE.01: caught exception while handling request: unexpected element name: expected=String_1, actual={urn:Foo}String_1.
Seems to be a problem with the targetNamespace/typeNamespace stuff.
My test.html
<html>
<head>
<script src="test.js"></script>
</head>
<body>
<h1>Bart!</h1>
<form>
<input type="text" name="bounceThis" value="bounce me">
<input type="button" onclick="Bounce(document.forms[0].bounceThis.value);" value="Bounce!">
</form>
<h3>Results</h3>
<ol>
<div id="resultsList">
<li>nothing yet ...</li>
</div>
</ol>
</body>
</html>
My test.js
var proxy=null;
var wsdl_uri="/test-ejb/wuerg?WSDL";
function Bounce(value)
if(!proxy)
var listener=
onLoad: function(aProxy)
proxy=aProxy;
proxy.setListener(listener);
alert("Ok!"); // WSDL parsing worked
bounceText(value);
onError: function(aError)
alert("ERROR in proxy!\n" + aError);
var fault = aError.data;
if(fault!=null)
alert("SOAP Fault:\n" +
"\nfaultCode: " + fault.faultCode +
"\nfaultString: " + fault.faultString +
"\nfaultString: " + fault.detail
sayHelloCallback : function(aValue)
aValue=("<li>" + aValue + "</li>" +
document.getElementById("resultsList").innerHTML);
document.getElementById("resultsList").innerHTML=aValue;
createProxy(listener);
} else {
bounceText(value);
function createProxy(aCreationListener)
try
var factory = new WebServiceProxyFactory();
factory.createProxyAsync(wsdl_uri, "WuergPort", "", true, aCreationListener);
//factory.createProxyAsync(wsdl_uri, "HelloIFPort", "", true, aCreationListener);
catch(ex)
alert("ERROR in createProxy()!\n" + ex);
function bounceText(value)
if(proxy)
//proxy.sayHello(value);
proxy.sayHello("wuerg");
else
alert("ERROR in bounceText()!\n" + "Proxy set up not complete!");
My WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="urn:Foo" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="WuergService" targetNamespace="urn:Foo">
<types/>
<message name="Wuerg_sayHello">
<part name="String_1" type="xsd:string"/></message>
<message name="Wuerg_sayHelloResponse">
<part name="result" type="xsd:string"/></message>
<portType name="Wuerg">
<operation name="sayHello" parameterOrder="String_1">
<input message="tns:Wuerg_sayHello"/>
<output message="tns:Wuerg_sayHelloResponse"/></operation></portType>
<binding name="WuergBinding" type="tns:Wuerg">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="sayHello">
<soap:operation soapAction=""/>
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="urn:Foo"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="urn:Foo"/></output></operation></binding>
<service name="WuergService">
<port name="WuergPort" binding="tns:WuergBinding">
<soap:address location="http://localhost:5000/test-ejb/wuerg" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/></port></service></definitions>
The WSDL is generated with J2EE 1.4 Sun RI wscompile, no wsi feature.
Interesting thing: same sample deployed at WebSphere 6.0 works fine with Mozilla! So I guess WebSphere is a bit more sloppy or so in processing incoming SOAP requests ...
Perhaps anybody at Sun could try to test a simple web service with Mozilla or Firefox on the client side ...
Merten

Maybe someone could help me here.
The SOAP request/response is here:
request:
... User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608 Firefox/0.8.0+..Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5..Accept-Language: en-us,en;q=0.5..Accept-Encoding: gzip,deflate..Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7..Keep-Alive: 300..Connection: keep-alive..SOAPAction: ..Content-Type: text/xml..Content-Length: 430..Pragma: no-cache..Cache-Control: no-cache....<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xs="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><env:Header/><env:Body><a0:sayHello xmlns:a0="urn:Foo"><a0:String_1 xsi:type="xs:string">wuerg</a0:String_1></a0:sayHello></env:Body></env:Envelope>..
response:
<?xml version="1.0" encoding="UTF-8"?>..<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="urn:Foo" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><env:Fault><faultcode>env:Client</faultcode><faultstring>JAXRPC.TIE.01: caught exception while handling request: unexpected element name: expected=String_1, actual={urn:Foo}String_1</faultstring></env:Fault></env:Body></env:Envelope>..0....
This is a working request (from MS SOAP Toolkit)
... Content-Type: text/xml; charset="UTF-8"..User-Agent: SOAP Toolkit 3.0...
<?xml version="1.0" encoding="UTF-8" standalone="no"?><SOAP-ENV:Envelope xmlns:SOAPSDK1="http://www.w3.org/2001/XMLSchema" xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAPSDK4:sayHello xmlns:SOAPSDK4="urn:Foo"><String_1>Rums!</String_1></SOAPSDK4:sayHello></SOAP-ENV:Body></SOAP-ENV:Envelope>
So, the "String_1" parameter is really send in different ways. :-)
Again, WebSphere 6.0 seems to accept both "formats".
Thanx for any help.
Merten

How to access the apps server inside guest from host.

my setup is
windows 7 - host
OEL 5 - virtualbox guest
i have it setup with bridged networking with static IP 192.168.1.91.
my virtualbox guest is running oracle ebs 12. i can access from firefox inside the guest the url http://xt12:8000
i can ping the guest ip from host .
however when i try to open the url(http://192.168.1.91:8000) from Internet Explorer browser inside the host it do not open.
appreciate any suggestion.
thanks in advance.
-Kart

user12046749 wrote:
however when i try to open the url(http://192.168.1.91:8000) from Internet Explorer browser inside the host it do not open.
appreciate any suggestion.Check iptables inside the guest: a default Oracle Linux install has the firewall enabled, which will block inbound connections.

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.

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

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

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.

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

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?

Using Sun Web Server 6.1 from the IDE

Using JSE 8 with Sun Web Server 6.1 set as the target container, I have a SUNWS61deployment.xml file created.
That didn't exist in JSE 7. Is it WS 6.1 SP4 or SP5 -related ?
I also have ws61-sun-web.xml with a simple <sun-web-app/> tag (empty deployment descriptor).
What should this file contain? Is it a replacement for sun-web.xml?
Do I still need sun-web.xml? Its DTD declaration sounds like Sun
App Server 7 (http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-1.dtd)
So you have plans to make "Sun Resources" (pools, JNDI resources, ...) created in the IDE be registerable directly in the Web Server just like it's possible with the sun app server?
How safe is it to use JSE 8 with an older Web Server Service Pack (say 6.1SP1)?

SUNWS61deployment.xml is created bythe IDE to be used internally and not to be used by the developer. This file wouldn't be sent to webserver after deployment.
The ws61-sun-web.xml is sun-web.xml only and yes it is same as it is in Appserver7 as the webcontainer for both Webserver6.1 and Appserver7 are same. After deployment to webserver, ws61-sun-web.xml is renamed to Webserver as sun-web.xml by the IDE. When opened the developer can edit in the XML editor.
The reason for having it as ws61-sun-web.xml in IDE is to avoid the clash between sun-web.xml of Appserver8.1 which is J2EE1.4 based whereas Webserver6.1 Web container is J2EE1.3 based.
It should be okay to use any service pack of Webserver6.1 with JSE8
Hope this helps

"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

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

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

Sun App Server 8 as a Windows Service

Is it possible to install Sun App Server 8 as a Windows Service so I could run it under Windows 2003 Server? If yes, how -- I could not find any information on it.
Sincerely,
Sergei Batiuk.

I received a reply from Paul Ko at Sun Microsystems.
Paul is the product line manager for Sun's Java application server.
>
Sean,
To run the AppServer as a Windows service, you need to use 3rd party
software to enable this. The AppServer is designed to run as a
Windows application, not as a service. You can do a Google search to
find a suitable 3rd party software to fulfill you needs.
Unfortunately, we do not publish which 3rd party software can be used
to do this -- as a policy, we don't endorse any particular vendor.
Best,
Paul

Accessing Sun App Server JNDI context from j2se client

Similar Messages

Maybe you are looking for