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

Similar Messages

Sun App Server cannot use JMS expiration date due to constant pool resize?

Hello,
I thought that max-pool-size property could limit the amount of MDB beans created, and thus force the client to wait (and drop the timed out messages). But after reading this description:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4972762
It looks like that's not the case. So if you combine that with the notion of setting time to live on MDB messages, what does that equal to? Does that mean that your JMS messages will NEVER time out, even if they have TTL or expiration date set on them, because there will always be a new bean created to handle the request?
I'd appreciate it if someone could explain what's the deal here - what good is setting JMS expiration date if your message never expires? And what is the pool size for, if the number of beans can always be exceeded?
Thank you,
Mark

Hi,
Please go through the tutorial titled "Deploying to a Sun Java System Application Server" which is available at: http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/appserverdeploy.html
Thanks,
RK.

Sun App Server as a Web Server

Can the Sun App Server be used as a simple Web Server (like Apache)? If so, how does one set the root directory for HTML files?
Thanks

Thanks.
Just to clarify for any others who are interested, heres the deal:
1) Package the static HTML files using the 'deploytool' (See Packaging Web Modules in Chapter 3 of The J2EE(TM) 1.4 Tutorial). This creates a .war file with the required deployment descriptors(?); anyway it creates a bunch of .xml files that have the right data in them.
2) Take the .war file and drop it in the 'quick deploy' icon (copies the .war file to the 'autodeploy' directory for the App Server instance).
Anyhow thats the drill.
Good luck.

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

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

What does the Sun App Server Use as a web container?

Does the Sun App Server use tomcat? Or is it some derivative of Tomcat?
thanks for the info.

Thanks.
Just to clarify for any others who are interested, heres the deal:
1) Package the static HTML files using the 'deploytool' (See Packaging Web Modules in Chapter 3 of The J2EE(TM) 1.4 Tutorial). This creates a .war file with the required deployment descriptors(?); anyway it creates a bunch of .xml files that have the right data in them.
2) Take the .war file and drop it in the 'quick deploy' icon (copies the .war file to the 'autodeploy' directory for the App Server instance).
Anyhow thats the drill.
Good luck.

Different behavior using JSC and Sun App server 8.2 - why?

I have developed a JSF application using Java Studio Creator 2.
JSC2 uses Sun App Server 8.2 as the development application server.
I also have Sun App Server 8.2 on a server that is used for deployment.
When I run an application within the IDE, I get a set of behavior that I expect to see, but not when deployewd to the server.
In particular, in one case, a grid created within a session bean is redrawn when running in the IDE but not when deployed.
In another case, I attempt to read the value of the grid text field.
In the IDE, I get a properly set 'submittedValue' property, but in the deployed environment, it is null.
Why am I seeing differences in behavior between the two environments?
How can I get the deployed version to work tge same as in the development enviroment.

I am sorry but I don't understand. Which path specifically do you mean?
dear mr/mises
you have to change your path with net beans with8.2
you will be solving your problems

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

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.

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

"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

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

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.

Bouncycastle, sun app server 8.1, jar is not signed by a trusted signer

hi,
i am facing following problem,
im trying to use 3rd party security provider signed with SUN, however, after everything is properly configured and i run webapplication code (sun app server 8.1) that should load registered 3rd party provider application crashes with following exception:
Caused by: java.util.jar.JarException: file:/usr/jdk/instances/jdk1.5.0/jre/lib/ext/bcprov-jdk15-138.jar is not signed by a trusted signer.
     at javax.crypto.SunJCE_d.b(DashoA12275)
     at javax.crypto.SunJCE_d.a(DashoA12275)
     at javax.crypto.SunJCE_d.a(DashoA12275)
     at javax.crypto.SunJCE_b.b(DashoA12275)
     at javax.crypto.SunJCE_b.a(DashoA12275)
     at javax.crypto.SunJCE_b.b(DashoA12275)
     at javax.crypto.Cipher.getInstance(DashoA12275)
     at sk.tempest.anypay.helpers.Sha1Signer.sign(Sha1Signer.java:38)
this happens with both, bouncycastle and cryptix and both are having valid certrificates
this is machine specific problem
does anybody know or solution or at least some information what could cause this?
Has to be Java Code Signing CA in NSS cert8.db of application server?

importing public key?
have you ever seen JCE source code?
well if you write provider you have to send it to SUN they will sign it,
with Java Code Signing CA certificate.
These certficate's other part of asymetric cipher code is hardcoded in jce.jar
JCESecurity.java.
I finally solved that configuration problem with making own modified jce.jar.,
with provider signature checking turned off.
Btw i think problem was caused with multiple libraries in system using same classes.
There was some archaic jce.jar in SUNwam or somewhere.

Sun app server problem using asadmin tool

Similar Messages

Maybe you are looking for