|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 34
Messages: 34
Messages: 34
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Sun Java System Application Server PE 8.2 has been released
Sun has announced the release of the Sun Java System Application Server PE 8.2, an update to their production J2EE 1.4 application server. Improvements include better multicore support, Fast Infoset for webservices, JMS connections to MQSeries and Sun's MQ Server, and the inclusion of Apache Derby for database support. SJSAS is available for download at no cost from Sun.
SJSAS is the reference implementation for J2EE 1.4, and is included (as one of many possible downloads) in Netbeans as the default container for J2EE.
For full details on updates included in SJSAS 8.2, see the release notes.
|
|
|
Message #198824
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Sun Java System Application Server PE 8.2 has been released
One feature that jumps out from the original posting is the support for Fast Infoset. Have any TSS readers had any experiences (good or bad) with Fast Infoset yet? It's an intriguing idea and could potentially yield significant performance improvements in WS / SOA apps but I expect interoperability will be enough of any issue to prevent widescale adoption.
Keen to hear if anyone has tried Fast Infoset in real applications.
Cheers,
Andy Grove
FireStorm/DAO 3.0 Generates Java code from relational schemas
|
|
|
Message #198847
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
documentation
Sun one 8 appserver has the worst documentation.
Sun has to learn to document things before they come out with nice things.
Sun One Studio 8 E is great but no documentation, all they say is its built on netbeans and refer to netbeans documentation in bits and peices...
Wake up guys and look around.. documentation is the need of the hour
|
|
|
Message #198855
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
documentation
Sun one 8 appserver has the worst documentation.Sun has to learn to document things before they come out with nice things.Sun One Studio 8 E is great but no documentation, all they say is its built on netbeans and refer to netbeans documentation in bits and peices...Wake up guys and look around.. documentation is the need of the hour
Nithya, I'd be interested in knowing exactly what is broken so we can fix it. You say the App Server documentation is the "worst" but you actually use Sun java Studio Enterprise 8 (I think) as an example. That's a different product but important to me nonetheless.
Could you elaborate on the issues you've hit - on this forum or via direct email - sharps at sun do com.
Thanks, Rich
Rich Sharples
Sun Microsystems
http://blogs.sun.com/theaquarium
|
|
|
Message #198883
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
A question about "reference implementation"
SJSAS is the reference implementation for J2EE 1.4, and is included (as one of many possible downloads) in Netbeans as the default container for J2EE.
Small question about the use of "reference implementation" here. I thought reference implementation meant "do not use in production, good for learning though". Is this still the case or is SJSAS 8.2 a full J2EE web application server that can fully compete with WebLogic, Websphere and JBoss in a deployed production environment? And what exactly does "reference implementation" mean anyway?
|
|
|
Message #198887
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: A question about "reference implementation"
It's both.
As the reference implementation, it's basic role is if you want to know how the specification is supposed to work, the reference implementation works "correctly".
But that doesn't mean that the RI can't be a reliable or performant server.
Obviously, given a choice between correct behavior and performance and/or stability, then the RI should lean towards correctness. But one can argue that if the "correct" behavior is not performant, or stable, then that behavior may well just be flat out questionable.
On the other hand, production servers may well offer options or configurations that may, perhaps, sacrifice comapatability for performance. The RI may well not offer those kind of choices.
Rich can no doubt comment better on this, but the SJAS has demonstrated performance (through SPEC benchmarks), and folks are using it in production.
So, SJAS is "all of the above".
|
|
|
Message #198894
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: A question about "reference implementation"
It's both.As the reference implementation, it's basic role is if you want to know how the specification is supposed to work, the reference implementation works "correctly".But that doesn't mean that the RI can't be a reliable or performant server.
What Will said + a bit of background / history :
Up to the J2EE 1.3 SDK there was an explicit clause in the license inhibiting use in production. People complained and were deploying anyway so we changed the license to allow production use. We also tarted the RI up a fair bit to make it more accessible and useful - the original RI was pretty basic and wasn't exactly built for speed. So, the publically available thing became the Platform Edition - a basic App Server intended to promote J2EE that was based on the Reference Implementation.
The "RI" still exists - it's the barebones thing that is made available only to licencees along with the compatibility kit (TCK).
Today you won't see all the features you'd expect to see in an enterprise product (ie. clustering, HA, multi-machine management, etc) - those feature would make the product less accessible (ie. more complex) and would hinder adoption of J2EE. For production deployments - I'd say the sweet-spot is probably a single, dual-CPU machine serving a couple of hundred concurrent users - we achieved some pretty decent SPECjAppServer numbers to demonstrate that.
If you are doing this kind of thing with Tomcat and need more than a servlet engine you should take a look.
Rich Sharples
Sun Microsystems
http://blogs.sun.com/theaquarium
|
|
|
Message #198908
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Memory leaks
The same story as for 8.1 version. Try several deployment/undeployment of J2EE applications. You'll be soon out of memory. Tis are an academic implementations, both Netbeans and SJS AS. Oy can play, you can educate, but you can't seriously develop.
|
|
|
Message #198926
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJAS on Linux
Is anybody using SUN AS PE or Glassfish on Linux in production ? It would be very interesting to know.
We wrote a system for online payments consolidation using NetBeans and SUN AS. So we decided to use SUN AS on production server as well. However we experienced several problems:
1) It seems that there is a resource leakage - AS opens Linux pipes quite often and doesn't close them. So number of open file descriptors grows until it reaches about one thousand.
2) Sometimes SUN AS stops responding to HTTPS requests. There are no error messages and AS is still working, other HTTP listeners are working and it's possible, for example, to open admin console.
Other people have had those problems as well. And it's possible to reproduce first problem without any application deployed. Just install SUN AS and open admin console. SUN AS will open 180 file descriptors.
Both problems happen on Redhat Enterprise Linux 3.0, 4.0 and SUSE, both for SUN AS and Glassfish. So after we tried all those configurations (including JDK update) we had no choice but to migrate to JBoss. It was not a pleasent process either, but our system is rock stable on JBoss.
|
|
|
Message #198984
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Windows service
Can it now be installed as a Windows service? This was possible Sun ONE AppServer 7, but for some strange reason not in 8.0 or 8.1.
|
|
|
Message #198998
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Sometimes SUN AS stops responding to HTTPS requests.
Yes, I've had the same problem on Windows with Sun App Server 7. I had to restart the server once in a while for that reason. This was quite annoying, and I was hoping it has been fixed...
|
|
|
Message #199017
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Out of memory with deploy/undeploy?
I have a large scale production installation of SJAS 7 EE on Solaris 9 and have never experienced "out of memory" exceptions in regards to application deployment. The applications deployed range in size and initial resource usage from the very small to the very large. I am interested in the size of the applications you are deploying as well as the resource usage you are incurring (i.e.:data caching in memory on app start-up).
What I do find problematic is the way the connection pool mechanism is implemented. Apparently if a DB connection is left open, the connection will not be closed, even if the object that created the connection is GC'ed. Obviously this is not a problem if you are closing your connections, but in the event of programmer error connections will continue to open until the pool max is reached and then we are left with the all to familiar 'wait time expired' exception. Since this behavior is continued in SJAS 8, I must assume that this is a purposeful implementation intended to make developers keep their code 'tight'. This would not be problem if I did not have a gaggle of consultants that claim this behavior is exhibited in no other application server.
Does anyone else have any experience with this issue?
|
|
|
Message #199034
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
We use 8 PE in production
I work for an organization that uses 8 PE in production. We have it running on some pretty old servers. I have not noticed any major memory issues.
Also, I think that the documentation is pretty good. We also do WebSphere and we can find things in the Sun documentation a lot faster then in the RedBooks of IBM.
Mike
|
|
|
Message #199061
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re : Out of memory with deploy/undeploy?
this behavior is exhibited in no other application server.
You can have the appserver configured to clean up rogue connections in the connection pool (and monitor them using admin console) in weblogic 9.0, websphere 6.0, tomcat5.1 etc.,
Sun one doesn't have this feature although you can monitor the connection pool using the CLI utility (on 7.x) and admin gui in 8.0.
|
|
|
Message #199071
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
A question about "reference implementation"
SJSAS is the reference implementation for J2EE 1.4, and is included (as one of many possible downloads) in Netbeans as the default container for J2EE. Small question about the use of "reference implementation" here. I thought reference implementation meant "do not use in production, good for learning though". Is this still the case or is SJSAS 8.2 a full J2EE web application server that can fully compete with WebLogic, Websphere and JBoss in a deployed production environment? And what exactly does "reference implementation" mean anyway?
Originally the RI was to show a potential way to implement the spec but Sun has turned it into a seeding vehicle where they hope you will use it and "graduate" to their commercial product. Any other explanation is pure salesmanship...
|
|
|
Message #199081
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
A question about "reference implementation"
Originally the RI was to show a potential way to implement the spec but Sun has turned it into a seeding vehicle where they hope you will use it and "graduate" to their commercial product. Any other explanation is pure salesmanship...
Reference Implementation is a technical term in the context of a JCP specification. It means an implementation that is compliant with that specification and passes the TCK tests. There is a wide range of RIs out there, in some cases they are just showing that the spec is feasible, in others they are fully featured products.
The old J2EE RI from Sun was indeed based on a separate code base than Sun's product. That was quite a while ago. For the last few releases the Reference Implementation for the J2EE platform has been based on the exact same code base as Sun's commercial products. Nothing else would make sense for Sun, specially since Sun's AppServer products are free for use.
The GlassFish project is where the next version (Java EE 5-compliant) of the AppServer is being created. Project home is at http://glassfish.dev.java.net. A good source of news from the community is http://blogs.sun.com/theaquarium
Hope this helps - eduard/o
|
|
|
Message #199084
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
All versions are free now
All of the versions of Sun App Server are free now. That happened in late 2005. They are all free and open source.
As for the service on the Platform Edition, Appendex A of the admin guide will show you how to do it. I have done it to a couple of servers.
|
|
|
Message #199093
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Windows service
Yes, I know about this solution, thanks. Still this is a workaround. I would prefer the Sun's native implementation -- the one found in Sun App Server 7. This is quite simple but important feature for this kind of software -- why Sun decided to drop it?
|
|
|
Message #199096
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Out of memory with deploy/undeploy?
Well, if application does not close connection, then that is bad anyway. So, I wont blame appserver for that.In any case, GlassFish has some interesting features to help you out, even if some developers have done some mistakes.https://glassfish.dev.java.net/javaee5/integration-tech/glassfish_connpooling.htmlLook for lazy connection association and lazy connection enlistment.
Well stated. It would seem apparent that the pooling issue is addressed post GlassFish. So in summary, for those of us using SJAS versions prior to GlassFish, just close your connections.
|
|
|
Message #199103
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJS as open source
This seems to be a pretty rumour running round the world regarding SJS as open source. Can someone point us, where the SJS 8.1 or 8.2 source code can be downloaded? I don't see anywhere this code...
|
|
|
Message #199117
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJS as open source
This seems to be a pretty rumour running round the world regarding SJS as open source. Can someone point us, where the SJS 8.1 or 8.2 source code can be downloaded? I don't see anywhere this code...
Appserver.next with J2EE 1.5 support called Glassfish is opensource, see:
https://glassfish.dev.java.net/
The Aquarium is the good starting point for Glassfish related infos:
http://blogs.sun.com/theaquarium
|
|
|
Message #199160
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
All versions are free now
All of the versions of Sun App Server are free now. That happened in late 2005. They are all free and open source.
Take a look at Solaris Enterprise System. The audiocast explains the details.
"...Sun builds on success of the Solaris OS by announcing Java Enterprise System, developer tools and N1 Software are now available at no cost."
|
|
|
Message #199164
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
All versions are free now
All of the versions of Sun App Server are free now. That happened in late 2005. They are all free and open source. Take a look at Solaris Enterprise System. The audiocast explains the details. "...Sun builds on success of the Solaris OS by announcing Java Enterprise System, developer tools and N1 Software are now available at no cost."
<br><br>
Note all Sun sw is now free to download, but if you want support, you will need to buy that separately. As Eduardo pointed out, Sun App Server from the next version (9) is available as open source. No previous versions have been, or are planned to be, open sourced. You can get the open source Java EE 5 implementation at the Open GlassFish Community java.sun.com/javaee/glassfish. It is this implementation that will serve as the basis of App Server 9.
|
|
|
Message #199171
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
handling rogue connections
Nithya,
It depends on what you meant by Rogue connection.
- If a connection in the pool goes bad, Sun app Server can detect it (validates connection before giving one to client from pool, there is a configurable policy for this) it can re-establish it before giving it to the requestor. This has existed since 7.0 release. It can also pro-actively look at the rest of the connections and clean them up too. This continues in all releases 8.x and in 9.0 as well. This is automatic. No manual administrator intevention is even reqd. If this is what you mean by handling rogue connection, I think we handle it nicely.
- If there is a bad or rogue application that is creating connections and does not close them, it is going to run out of connections eventually. It all depends on how quickly it is leaking the connections. If the abandoned connection is not involved in a transaction and appears to be idle for too long, it may be possible to switch or recycle the connection. This can keep a bad application going for longer. We do plan to support this sort of thing in a forthcoming enterprise edition release of the product (slated for a Java EE 5 synch).
- A new self management framework has been introduced in project GlassFish (see: https://glassfish.dev.java.net/javaee5/selfmanagement/selfmanagementhome.html)
in many cases it may be possible for you to write a little MBean that looks out for your favorite bad scenario and do what is appropriate for your environment.
If you have any feature suggestions, we would love to hear more from you.
Thanks
Sreeram Duvur
Lead, J2EE High Availability
Sun Microsystems
|
|
|
Message #199173
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJAS on Linux
You might face this problem:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6313023
A possible workaround is to increase PermSize=128m
But I'm puzzled about the file descriptor problem you are seeing. I'm developping GlassFish (the Grizzly Http Connector, which is a good candidate for fd leak) on Fedora 4, and I'm not getting the 180 fd, for both 8.2 and GlassFish. They share the same HTTP connector BTW.
Info on the HTTPS problem would also be usefull if you are able to reproduce the problem (a thread dump will be perfect).
Thanks
-- Jeanfrancois
|
|
|
Message #199179
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJAS on Linux (possible workaround)
I also suspect you may face a VM bug on Linux where socket stay BOUND forever. See the forum thread for a possible workaround.
-- Jeanfrancois
|
|
|
Message #199213
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJAS on Linux (possible workaround)
thank you, we will try this workaround when we will do a new installation of our app.
|
|
|
Message #199215
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
SJAS on Linux
Info on the HTTPS problem would also be usefull if you are able to reproduce the problem (a thread dump will be perfect).Thanks-- Jeanfrancois
I have posted a stack trace in this forum.
this thread
It's not easy to reproduce this problem, because with our system it happened once a week at indeterminate time.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman continues to explore the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(January 21, Article)
Ted Neward is an independent consultant specializing in high-scale enterprise systems, and an authority in Java and .NET technologies. He is the author and co-author of several books, including Effective Enterprise Java. At TheServerSide Java Symposium in March, he will be presenting sessions on pragmatic architecture, ECMAScript and Scala.
(January 15, Article)
Now that Oracle is absorbing Sun Microsystems, there mixed views on what should come of the Java Community Process (JCP). While some say Oracle should become the new steward of Java and keep the JCP much as it was, others argue that it may be time to open-source this widespread language.
(November 24, Article)
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
