My last post dealt with Websphere configuration for Hibernate with a Datasource for MySQL.  I also mentioned how I typically use Apache Tomcat to do a lot of my testing before deploying to Websphere.  Smart readers will know that the types of applications I am referring to do not include JMS or EJBs but are straight Servlet or Web Services type apps.  Development and Testing for full J2EE based applications should take place using other Application Servers, and or development environments.

With that said, I thought I would post the steps I went through to configure Tomcat for a Datasource, and what I had to do to configure my Hibernate configuration file for that source.

First off, I made no changes to my hibernate.cfg.xml from the one I deployed to Websphere.  So the following configuration parameters are still the same.

<div><property name=”current_session_context_class”>thread</property></div>
<div id="_mcePaste"><property name=”hibernate.bytecode.use_reflection_optimizer”>false</property></div>
<div id="_mcePaste"><property name=”hibernate.connection.datasource”>java:comp/env/jdbc/mysqlblogpostdataref</property></div>
<div id="_mcePaste"><property name=”show_sql”>true</property></div>
<div id="_mcePaste"><property name=”dialect”>org.hibernate.dialect.MySQLDialect</property></div>
<div><property name=”hibernate.bytecode.use_reflection_optimizer”>false</property></div>
<div><property name=”hibernate.connection.datasource”>java:comp/env/jdbc/mysqlblogpostdataref</property></div>
<div><property name=”show_sql”>true</property></div>
<div><property name=”dialect”>org.hibernate.dialect.MySQLDialect</property></div>

I also kept my web.xml the same as my deployment to Websphere.

<resource-ref>
<description>My Blog DataSource</description>
<res-ref-name>jdbc/mysqlblogpostdataref</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Secondly edit your Context.xml file stored in the $CATALINA_HOME/conf directory and add a Resource entry.

<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true" crossContext="true">

<!-- maxActive: Maximum number of dB connections in pool. Make sure you
configure your mysqld max_connections large enough to handle
all of your db connections. Set to -1 for no limit.
-->

<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit.  See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->

<!-- maxWait: Maximum time to wait for a dB connection to become available
in ms, in this example 10 seconds. An Exception is thrown if
this timeout is exceeded.  Set to -1 to wait indefinitely.
-->

<!-- username and password: MySQL dB username and password for dB connections  -->

<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->

<!-- url: The JDBC connection url for connecting to your MySQL dB.
-->

<Resource name="jdbc/mysqlblogpostdataref" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="dbuser" password="yourpassword" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/yourdatabase"/>
</Context>

The key here is to make sure your resource name in the context.xml matches your reference name in the web.xml, this is the only way Tomcat environments know how to map resources from your deployment descriptor to the context.xml.

далее указываем  путь до сервера (CATALINA_HOME – папка bin от tomcat).

Выбираем последнюю доступную версию. После этого eclipse загрузит файл vaadin-6.1.5.jar

package com.example.testvaadin;

import com.vaadin.Application;
import com.vaadin.ui.*;
import com.vaadin.ui.Button.ClickEvent;
import com.vaadin.ui.Button.ClickListener;

public class TestvaadinApplication extends Application {
@Override
public void init() {
final Label hello = new Label("Hello, %username%");
hello.setVisible(false);
Window mainWindow = new Window("My new web 2.0 application with vaadin");
Panel rootPanel = new Panel("<h1 align='center'>My First Vaadin Application</h1>");
rootPanel.setSizeFull();
Button clickMe = new Button("Say, Hello world!");
clickMe.addListener(new ClickListener()
{
public void buttonClick(ClickEvent event)
{
hello.setVisible(!hello.isVisible());
}
});
rootPanel.setSizeFull();
rootPanel.setContent(new VerticalLayout());
rootPanel.addComponent(hello);
rootPanel.addComponent(clickMe);
mainWindow.addComponent(rootPanel);
setMainWindow(mainWindow);
}

}

* This source code was highlighted with Source Code Highlighter.

нажимаем run on server и видим следующую картинку:

Вот так.  Сами поэкспериментируйте с виджетами, но учтите, что нужно постоянно чистить кеши tomcat`a, иначе будут сложности (сделать это можно в свойствах сервера “Clean Tomcat Work Directory”).

My Liferay application was running on the domain www.pojoe.ca and resided on Tomcat 6 in its own VM while my SSO server was running on another Tomcat 6 instance on another VM under the domain sso.pojoe.ca. I wanted to establish an SSL connection between the two over a self-signed certificate.

I started by setting up HTTPS on my SSO server.

• Create the keystore and private key in some directory. I use /opt/tomcat/security

keytool -genkey -alias mykey -keypass changeit -keyalg RSA -keystore server.keystore

• Answer the prompts.  Use sso.pojoe.ca (your domain) when asked for first/last name.  This is critical.

NOTE: From http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html

I am using name-based virtual hosts on a secured connection which can be problematic. This is a design limitation of the SSL protocol itself. The SSL handshake, where the client browser accepts the server certificate, must occur before the HTTP request is accessed. As a result, the request information containing the virtual host name cannot be determined prior to authentication, and it is therefore not possible to assign multiple certificates to a single IP address. If all virtual hosts on a single IP address need to authenticate against the same certificate, the addition of multiple virtual hosts should not interfere with normal SSL operations on the server. Be aware, however, that most client browsers will compare the server’s domain name against the domain name listed in the certificate, if any (applicable primarily to official, CA-signed certificates). If the domain names do not match, these browsers will display a warning to the client user. In general, only address-based virtual hosts are commonly used with SSL in a production environment.

• server.keystore is generated.

• List the keys currently stored in your keystore.

keytool -list -keystore server.keystore

• You should see the PrivateKeyEntry named mykey in the listing.

• This should be sufficient to begin receiving connections using HTTPS.

• Generate the certificate.

keytool -export -alias mykey -keypass changeit -file mycert.crt -keystore server.keystore

• mycert.crt is generated.

• Import the certificate into the keystore.

keytool -import -alias mycert -keypass changeit -file mycert.crt -keystore server.keystore

• You receive a warning that it already exists in the keystore.  Ignore it.  It is because Java expects separate keystore and trust store files and we are using only one.

• List the keys currently stored in your keystore.

keytool -list -keystore server.keystore

• You should see a TrustedCertEntry named mycert in the listing as well as the PrivateKeyEntry named mykey.

Next I configured Tomcat to use the keystore I just setup. In server.xml uncomment the SSL connector port 8443. I’ve added the keystore file we created.

<Connector port=“8443″ protocol=“HTTP/1.1″ SSLEnabled=“true” maxThreads=“150″ scheme=“https” secure=“true” clientAuth=“false” sslProtocol=“TLS” keystoreFile=“/opt/tomcat/security/server.keystore” keystorePass=“changeit”/>

My SSO server is now ready to rock over HTTPS.

Next I’ll enable HTTPS on my Application server running Liferay.

Create the keystore and private key in some directory. I use /opt/tomcat/security

keytool -genkey -alias mykey -keypass changeit -keyalg RSA -keystore server.keystore

• Answer the prompts.  Use www.pojoe.ca (your domain) when asked for first/last name.  This is critical. See notes from above.

• Copy the mycert.crt certificate from the SSO server to /opt/servers/tomcat/security

keytool -import -alias mycert -keypass changeit -file mycert.crt -keystore server.keystore

• List the keys currently stored in your keystore.

keytool -list -keystore server.keystore

• You should see a TrustedCertEntry named mycert in the listing as well as the PrivateKeyEntry named mykey.

Next we’ll set the JVM parameters to tell the application to use the trust store.

-Djavax.net.ssl.trustStore=/opt/servers/tomcat6.0.18/server.keystore

-Djavax.net.ssl.trustStorePassword=changeit

My Liferay application server and my CAS SSO server can now talk over HTTPS.

Reference:

http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html

This position is an Application Administrator to support operations within our client’s department. This position has a critical role in delivering our services to clients and ensuring successful ongoing operation of our applications and services. It services a highly interactive software development build/release process as well as a rich operational environment with many interrelated applications/database services. The candidate should be self-motivated, detail oriented, adaptable to change and must work well in a flexible team environment with developers, QA, operations staff, system administrators and managers.

RESPONSIBILITIES:

Application and database support

• Provide on-going database administration in both back-end and front-end with application infrastructure support for our client’s administration systems, including the deployment of new applications.
• Review the physical design of existing databases for optimal database structures, database performance tuning, security, database backup/recovery strategy, implementing high-availability, and pro-active and reactive performance analysis, monitoring, troubleshooting and resolution of issues, capacity planning, monitoring data growth and system utilization, trend analysis and predicting future database resource requirements.
• Install web-base applications from ground up to full-ballooned implementation and support, including configuration at Unix/Linux/Windows system level, back-end integration with database, front-end integration with user-interface, final delivery to users to fulfill users’ requirement and on-going maintenance.
• Take the lead in ensuring that application and web services are configured and tuned according to application needs; provide troubleshooting as needed.
• Work with System Administrators to ensure test and production boxes conform to the software application configuration needs.
• Support the department-wide infrastructure application for database management, system monitoring and notification, job scheduling, deployment, provision and patching automation, application topology and service level management for campus-wide system performance.

Build/release activities

• Manage the build, tagging and release processes for a number of interdependent Java web applications and background processes in the QA and production environments. Ensure the build and release process is scalable and repeatable.
• Work with the development team to ensure efficient and understandable build procedures are adhered to and conform to a standard process for configuration and release management
• Develop and maintain tools that automate the building of software releases for an Agile-based development process. This is one of continuous integration, where the automated build process can be run many times a day if necessary.
• Work with and support the QA team to ensure automated test suites run as part of the continuous integration build process.

REQUIREMENT FOR SKILL AND COMPETENCIES:

• Expert hands-on with shell scripts, other scripting languages, preferably Perl, and tool automations
• Minimum 2 years database administration experience in Oracle and 3 years Application administration experience in Unix/Linux infrastructure environments is required.
• Hands-on experience of Oracle databases 10g for 24/7 database operations and tool automation in installation, configuration, backup/recovery, startup/shutdown, data refresh, and application integrations.
• Experience with OEM/Grid Control is highly desired.
• Knowledge and understanding of large scale ERP implementation and support like Oracle Financial and PeopleSoft systems.
• Expert knowledge of Apache and Tomcat, and other web/application servers such as JBoss
• Strong Unix and system administration skills with basic network and security knowledge
• Strong experience and ability in web applications deployment, configuration and integration from both OpenSource and Commercial based systems with or without sophisticated vendor support.
• Java/J2EE based programs
• Java/servlet/JSP based web applications
• Experience with Subversion, PVCS or similar source code repository
• Experience with Maven and familiarity with automated build processes
• Experience with the Agile development methodology and concepts of extreme programming and continuous integration
• Understanding of the layers/tiers of web applications and the communication protocol between the tiers with networking protocols (TCP/IP, HTTP, SSL, DNS, FTP, etc.)
• Ability to multi-task and work in a team environment is critical and should have excellent communication skills in both verbal and written forms.
• Ability to manage multiple competing priorities and work under pressure in high stress situations
• Excellent communication skills in both verbal and written
• Ability to work under pressure and to deliver results in a complex and dynamic operational environment

Qualifications

Minimum 5 years as an IT professional in build/release and application/database administration, plus one or more of the following areas: IT infrastructure operations 24/7, systems analysis and design, or application development.

Education
Bachelors Degree in Computer Science, Engineering or related field or equivalent experience

If you are interested, please send your resume to tsotelo@mindsource.com.

I recently needed to install tomcat 6 on debian lenny, however it is not in the repository and there is no backport.

There were two options, either use the tar or install the debian testing package. I have opted for the testing package as it is a debian specific setup and integrates properly.

I am assuming that you already have the debian java 6 package installed. Run the following as root.

First set the release to stable:

echo 'APT::Default-Release "stable";' > /etc/apt/apt.conf

This is important and not setting this will cause issues.

Now add the testing repository:

cat <<EOF>/etc/apt/sources.list.d/squeeze.list
# Repository for Squeeze, to get Tomcat6
deb http://ftp.uk.debian.org/debian squeeze main contrib non-free
deb-src http://ftp.uk.debian.org/debian squeeze main contrib non-free
EOF


Now pin the new packages:

cat <<EOF>/etc/apt/preferences
Package: *
Pin: release o=Debian,a=stable
Pin-Priority: 990
Package: *
Pin: release o=Debian,a=testing
Pin-Priority: 500
Package: tomcat6,tomcat6-admin,tomcat6-common,libtomcat6-java,libservlet2.5-java
Pin: release o=Debian,a=testing
Pin-Priority: 990
EOF


The above with ensure that testing packages will only take the priority for the tomcat related packages. The higher pin priority takes precedence.

Now update the repositories and install tomcat 6.

aptitude update
aptitude install tomcat6


Ref:

http://www.waltercedric.com/component/content/article/193-technical/1634-debian-lenny-how-to.html
Why no apt-pinning by release name?
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_tweaking_candidate_version

Hi !

Purpose of this tutorial : To give the reader a better understanding of using Java beans in JSP.

Advantage : This tutorial serves as an instant learning tutorial for those who would want to learn about using  Java bean in JSP.

Sources : The code used in this short tutorial has been extracted from www.jsptut.com

What is a Java Bean ?
Java bean are classes written in the Java programming language conforming to a particular convention. A Java bean has a set of properties that can be read or changed. It is also possible to discover the properties a bea has available, which well suits beans for modeling all kinds of real world things that can also be described as a set of properties.

Illustration:

What we will be doing?

We will create a simple html page(getName.html) that is used to get user’s name, email and age.  When we submit that data, it invokes a JSP page(SaveName.jsp) that inserts the user entered data into a bean. We provide a “click here to continue” link in that same page, which when clicked would invoke another JSP page (NextPage.jsp) that retrieves the data that was inserted into the bean and displays it!

The implementation is simple and straight forward!

Tools needed:

I have tested this code successfully in Tomcat 6.0 configured suitably with jdk1.5.0_14 and jre1.5.0_14.

code :

getName.html

SaveName.jsp

NextPage.jsp

Keep the above files in your webserver directory. My webserver classpath is C:\Tomcat 6.0\webapps\ROOT\ . Now we must develop a Java code to store the values obtained from the form. We then compile that Java code to obtain its “class” file. This class file is the real beauty of Java. Its contents look somewhat junk type when viewed using any editor. And that means that its not easy to hack your data from it(say, a password was sent from the form).

The contents of the Java code are very important. We define a Java class with fields “username”,”email” and “age” which must correspond exactly to the field names in getName.html. We define two types of methods in this Java code viz, a “setter” method and a “getter” method.

In simple,

* The setter method is a method that starts with the keyword “set” followed by the field name. In our example the setter methods would be setUsername,setEmail and setAge. Now compare this with the field names in getName.html. The only point you must note here is  the first letter, following “set”, is in uppercase. These setter methods insert the user entered data into the corresponding variable names into the bean.

At this point, by reasoning you should have understood that a bean is an instance of the Java class(correct me if i am wrong).

* The getter method is a method that returns the values stored in the javabean, to the entity that invoked it(NextPage.jsp in this case). The getter methods are named in the same way as setter methods except that the keyword “set” is replaced by “get”. So now we have getUsername,  getEmail, getAge

The java code is shown below:

UserData.java

Now compile the above Java code and place the code inside a folder named “user” because we have declared a java package by that name. This folder (along with the java class)should be placed in the following location:

<Application_Base\application_name>\WEB-INF\classes\

For me its :

C:\Tomcat 6.0\webapps\ROOT\WEB-INF\classes\

If the folder “classes” is not present then create one.

That is it invoke the getName.html file from the browser after starting Tomcat server and see the code in action. JSP rocks!

Output:

See the output here , here and here.

What I have not explained here?

I have not explained the meaning of the java bean tags in the jsp code given about. Their meanings and pupose are quite intuitive,if not just google to find more info on them.

How could i make use of this idea?

You can use the idea gathered from this tutorial for designing a user login page using java beans. Creativity has no bounds.

References:

• The best site for learning JSP
• More on JSP learning
  

Three weeks ago I wrote that Amazon RDS was going to eat into MySQL’s revenue potential.  I also pointed out that Amazon’s RDS was but a precursor to future Amazon cloud service offerings for other popular open source products.  While that post was centered on Amazon, it wasn’t a stretch to predict that any of the big IT vendors (IBM, Microsoft, HP, Google, Cisco, EMC/VMware, and Sun/Oracle) would offer RDS-like cloud services in the future.

Well, reading details of the Windows Azure platform this week, the prediction badge no longer applies to Microsoft.  According to Microsoft, Azure SQL will support MySQL, and Azure .NET Services will support Apache Tomcat.  Microsoft will also support PHP and Apache Web Server on Azure.  I’ll focus on MySQL, and to a lesser degree Apache Tomcat for this discussion.  I believe MySQL and Apache Tomcat will be the first two products offered as a service on large IT vendor cloud platforms, aside from the IT vendor’s strategic software stack that is.

When Amazon decided to offer MySQL via Amazon RDS, they did so without purchasing MySQL support from Sun.  I’ve confirmed that Microsoft Azure is supporting MySQL on Azure without paying Sun for a MySQL Enterprise subscription.  The logic as to why Amazon could do without a MySQL Enterprise subscription applies equally to Microsoft:

“Amazon’s decision to use the free version of MySQL to build RDS is completely sensible. First, Amazon has the technical skills to support their usage of MySQL without having to acquire the MySQL Enterprise subscription. Second, this decision helps Amazon lower the cost of RDS, which makes RDS more attractive to customers. This is clearly not good news for Sun/MySQL, which is missing out on capturing some portion of the revenue from MySQL users spending on RDS.”

As in my previous post, I don’t want this to be about Amazon or Microsoft versus Sun/MySQL.

The larger point is if Amazon, Microsoft, IBM, HP, Google, Cisco, EMC/VMware, Oracle/Sun offer a simple and supported cloud service for running MySQL, Tomcat, JBoss, Mule or Apache HTTP instances, what reason do customers have to acquire “enterprise subscriptions” from the vendors developing these open source projects?  Until now, the value of an open source “enterprise subscription” has largely been access to support and access to administration and management tooling.  In the case of MySQL, the former is provided by Amazon RDS and Azure SQL as part of the per-hour service.  Again in the case of MySQL, the latter is rendered unnecessary or replicated through Amazon RDS and Azure SQL tools.

If Microsoft can find business justification to offer both a .NET runtime and Apache Tomcat runtime as a service, then I wouldn’t bet on other IT vendors being solely faithful to their strategic software stack in their cloud service offerings.  I expect MySQL and Apache Tomcat will be supported by a plurality of large IT vendor cloud offerings.

Let’s turn our attention to the popular Apache Tomcat runtime. Covalent, now part of VMware via SpringSource, and OpenLogic are leading providers of Tomcat support.  Realizing that the scalable revenue potential is in selling products, SpringSource launched tc Server, or “Apache Tomcat with enterprise management”.  While I applaud the “selling products” angle, I reiterate that enterprise management not enough of a differentiator when up against cloud services from large IT vendors.

I still think that proprietary features in the “enterprise” version of the open source product, which are note available in the “free community” version, will be the path forward for open source vendors. Large IT vendor cloud offerings for open source products will rely on availability of the “free community” version and whatever features are supported in this version.  If there are compelling features outside of administration and management tooling in the “enterprise” version, then customers have a reason to skip the IT vendor cloud service and pay for the “enterprise” open source product.  I know the proprietary features suggestion is difficult for open source vendors to accept, and more importantly, difficult to rationalize in front of customers.  Difficult, but necessary.

In the end, there is no way that all expenditures on open source products such as MySQL or Tomcat will occur through a large IT vendor cloud service.  Clearly customers will want to use open source in their private data centers and acquire support and administration/management tooling from the open source vendor. There is also clearly an issue if IT vendors capture too much of the customer expenditure on open source products via their cloud services, leaving open source vendors behind these products to scrimp on future product development.  A happy medium will be found.  Well, it may not be happy enough for open source vendors as they watch large IT vendors capture revenue around open source products. But that’s competition for you.

Fun times ahead.

Follow me on twitter at: SavioRodrigues

PS: I should state: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions.”

For the first time, when I try to deploy a project using Netbeans, i got this message,

I have a class that performs logging for a servlet.
This class is wrapped up inside a jar and is used in a number of unrelated wars that are deployed in the same tomcat instance.
In order to log useful information the class in the jar file needs to know something that it is human-understandable and unique for the servlet in which is it deployed.

This has been bothering me for a couple of weeks, but I’ve just worked out how to do it:

public class ConfigReporter implements ApplicationListener
{
    private String artifactName;

    @Override
    public void onApplicationEvent( ApplicationEvent event )
    {
        if( event instanceof ContextRefreshedEvent )
        {
            ContextRefreshedEvent refreshEvent = (ContextRefreshedEvent)event;
            this.artifactName = "Unknown";
            if( refreshEvent.getApplicationContext() instanceof WebApplicationContext )
            {
                WebApplicationContext webCtx = (WebApplicationContext)refreshEvent.getApplicationContext();
                this.artifactName = webCtx.getServletContext().getContextPath();
            }
            startup();
        }
        else if( event instanceof ContextClosedEvent )
        {
            shutdown();
        }
    }

The startup method does the actual logging, but it’s the context path from the web servlet context that is the good stuff.
On tomcat this gives the same name that the tomcat manager servlet uses in its list of apps.
The technique should work with any servlet container, but results will vary (i.e. the name given by jetty is not the same as the name given by tomcat).

Clearly this is dependent upon the war file, but if the user deviates from the standard (maven) naming structure then they should still recognise their alternative name in my list.

Vai um café ai?

Um SysAdmin que não utiliza nenhuma ferramenta de monitoramento em seus servidores, está correndo um grande risco. Primeiro por não ter dados mais concretos sobre o desempenho normal de seus “filhotes”. Segundo que ele não pode prever uma falha, já que pode não conseguir visualizar que o número de requisições ao Apache estão crescendo muito rapidamente, por exemplo, ou que o consumo de memória da JVM do tomcat está fora do normal.

Ferramentas de monitoramento é o que não falta no mercado, tanto proprietárias quanto opensource. Entre elas, posso citar: Cacti, Nagios, Munin, Ganglia, Query Analyzer (MySQL – proprietário), Zenoss, etc. Estes são os que eu lembro de cabeça, mas uma busca no Google pode encontrar muitas outras ferramentas. IMHO estatística nunca é demais. Quanto mais dados sobre o desempenho dos servidores que eu cuido eu tiver, melhor será a decisão que eu vou tomar. Tenho meu planejamento para o blog, posts específicos de cada ferramenta que eu utilizo. Espero conseguir fazer todos eles…

Ultimamente tenho trabalho com servidores JAVA. E JAVA, se você não controlar, pode dar muita dor de cabeça, principalmente pelo uso descontrolado de memória. Sem contar que quanto melhor tunado o servidor JAVA estiver, melhor vai ser a performance da aplicação. Como eu precisava de uma ferramenta que me permitisse visualizar o comportamento do servidor, fui atras de alguma q atendesse minhas necessidades. Encontrei o santo JCONSOLE, que já vem com o próprio JAVA. Ele tem tudo que eu precisava. Monitora a memória (Utilização, Garbage Collector, Pool), Threads e Classes.

Para que eu consiga acessá-lo remotamente, preciso adicionar alguns parâmetros na inicialização do meu Application Server. Neste exemplo vou usar o Tomcat, mas acredito que todos os Servlets JAVA aceitem os parâmetros iguais aos que serão apresentados aqui. (Utilizo a mesma configuração no Resin por exemplo)

A configuração consiste em 3 passos:

1. Setar os parametros na variável CATALINA_OPTS;
2. Criar os arquivos de controle de acesso jmxremote.access e jmxremote.password
3. Reiniciar o serviço (tomcat)

1. Setando os parâmetros da variável CATALINA_OPTS:

As opções que vamos incluir nesta variável são:

• -Dcom.sun.management.jmxremote                     # permite o monitoramento da jvm remotamente
• -Dcom.sun.management.jmxremote.port=9099      # porta que  serviço irá rodar
• -Dcom.sun.management.jmxremote.ssl=false        # não utiliza SSL
• -Djava.rmi.server.hostname=meuservidor.com.br  # nome do host

Como aqui eu tenho um script de inicialização do tomcat, eu adiciono estas opções direto no script que fica no /etc/init.d, adicionando a seguinte linha ao script:

Se você não tiver um script de inicialização, você pode criar e exportar a variável na mão antes de iniciar o tomcat, ou colocar a linha acima no arquivo /etc/enviroment, ou no /etc/profile, notando que o profile só é executado quando o usuário faz login na máquina. Feito isso, vamos a próxima parte.

2. Criando os arquivos de controle de acesso:

Como bom SysAdmin, eu quero que o acesso as informações da JVM tenham acesso restrito. Para isso, vamos criar os arquivos que irão controlar esse acesso. Esses arquivos ficam armazenados dentro do diretório do JAVA, e toda vez q alguma aplicação que está com o jmxremote habilitado utilizar autenticação, ele irá consultar estes arquivos, que são o jmxremote.access e jmxremote.password. Uma informação adicional é que eu posso dizer, utilizando outras opções setadas na variável CATALINA_OPTS, quais arquivos o java deve consultar para verificar as permissões de acesso, mas nesse exemplo, esta opção não vem ao caso.

Então, vamos entrar no diretório onde ficarão armazenados os arquivos de controle de acesso:

E agora criamos os arquivos. O conteúdo do arquivo é tão simples, que podemos utilizar o comando echo para cri-alos, já com o conteúdo desejado. neste exemplo, quero criar dois usuários, um com permissões de leitura, e outro com permissão de leitura e escrita:

Cuidado com os caracteres “>” e “>>” para não sobrescrever o conteúdo do arquivo no segundo comando. Mesma coisa para o arquivo que armazena as senhas:

A permissão destes arquivos deve ser modificada paa 600, portanto:

3. Para completar, reiniciamos o serviço:

ou

ou

Feito isso, verifique se o tomcat iniciou corretamente, conferindo se o processo foi criado, e dando uma olhada no log:

Se estiver tudo ok, você já pode se conectar ao servidor utilizando o jconsole.

PS.: Os dados coletados durante a execução do jconsole, não são armazenados. Portanto, se você desligá-lo, e ligá-lo novamente, os dados obtidos na última execução do programa não estarão mais lá, e a timeline fica vazia outra vez.

[]s

WebCT’s CE/Vista application provided a very robust monitoring log file that included among other things JVM memory usage. It doesn’t appear Bb’s Release 9 (Project NG) provides a similar log and I haven’t found a log yet that includes any system monitoring information. JConsole can be used to monitor Tomcat in Bb’s Release 9 (Project NG) application. JConsole will give you a nice view of how Tomcat is running but it’s probably not a good long term monitoring solution. Run a ps -ef | grep java to find the Tomcat’s PID and run a jconsole [PID]. JConsole will give you a good look at the memory usage, garbage collection statistics, and thread information.

JConsole Overview

JConsole VM Summary

The JConsole tool is a JMX compliant GUI tool that connects to a running JVM, which started with the management agent. JConsole is built on top of the java.lang.management API. To run JConsole (if the bin directory of the SDK is in your path) just type jconsole. JConsole will open a dialog box where you can choose to monitor a local or remote process. You can also start JConsole for local monitoring by running jconsole [processID] where processID is the application’s process ID (PID).

One important note about JConsole:
Using jconsole to monitor a local application is useful for development and prototyping, but is not recommended for production environments, because jconsole itself consumes significant system resources. Remote monitoring is recommended to isolate the jconsole application from the platform being monitored.

One of the new features in Java 2 Platform, Standard Edition (J2SE) 5.0 is an API that provides monitoring and management support of the Java virtual machine (JVM). You can manage and monitor the JVM, applications and the operating system. Using JMX technology the platform management API (java.lang.management package) provides access to well defined objects called MXBeans. MXBeans are also referred to as platform MBeans. Each MXBean encapsulates a single functional area of the JVM.

You can use JMX to programatically retrieve all the information that JConsole displays. I struggled for some time figuring this out. You’ll need to use the Java Attach API to connect to the Tomcat JVM via Tomcat’s PID. This Java program will connect to a VM and print VM, class, thread, memory and OS information:

import com.sun.tools.attach.*;
import java.io.File;
import java.lang.management.ClassLoadingMXBean;
import java.lang.management.ManagementFactory;
import java.lang.management.MemoryMXBean;
import java.lang.management.OperatingSystemMXBean;
import java.lang.management.RuntimeMXBean;
import java.lang.management.ThreadInfo;
import java.lang.management.ThreadMXBean;
import javax.management.MBeanServerConnection;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;

public class Attach {

    static final String CONNECTOR_ADDRESS = "com.sun.management.jmxremote.localConnectorAddress";

    public static void main(String[] args) throws Exception {

        // attach to target VM via a PID
        VirtualMachine vm = VirtualMachine.attach("5480");

        // get the connector address
        String connectorAddress = vm.getAgentProperties().getProperty(CONNECTOR_ADDRESS);

        // no connector address, so we start the JMX agent
        if (connectorAddress == null) {
           String agent = vm.getSystemProperties().getProperty("java.home") +
               File.separator + "lib" + File.separator + "management-agent.jar";
           vm.loadAgent(agent);

           // agent is started, get the connector address
           connectorAddress = vm.getAgentProperties().getProperty(CONNECTOR_ADDRESS);
        }

        // establish connection to connector server
        JMXServiceURL url = new JMXServiceURL(connectorAddress);
        JMXConnector JMXConnector = JMXConnectorFactory.connect(url);
        MBeanServerConnection connection = JMXConnector.getMBeanServerConnection();

        RuntimeMXBean remoteRuntime = ManagementFactory.newPlatformMXBeanProxy(connection, ManagementFactory.RUNTIME_MXBEAN_NAME,RuntimeMXBean.class);
        System.out.println("Target VM is: "+remoteRuntime.getName());
        System.out.println("Started since: "+remoteRuntime.getUptime());
        System.out.println("With Classpath: "+remoteRuntime.getClassPath());
        System.out.println("Args: "+remoteRuntime.getInputArguments());
        System.out.println("Bootpath: "+remoteRuntime.getBootClassPath());
        System.out.println("Spec Name: "+remoteRuntime.getSpecName());
        System.out.println("Spec Vendor: "+remoteRuntime.getSpecVendor());
        System.out.println("VM Name: "+remoteRuntime.getVmName());
        System.out.println("VM Version: "+remoteRuntime.getVmVersion());
        System.out.println();

        ClassLoadingMXBean remoteClass =  ManagementFactory.newPlatformMXBeanProxy(connection, ManagementFactory.CLASS_LOADING_MXBEAN_NAME,ClassLoadingMXBean.class);
        System.out.println("Current Classes Loaded: "+remoteClass.getLoadedClassCount());
        System.out.println("Total Classes Loaded: "+remoteClass.getTotalLoadedClassCount());
        System.out.println("Total Classes Unloaded: "+remoteClass.getUnloadedClassCount());
        System.out.println();

        ThreadMXBean remoteThread = ManagementFactory.newPlatformMXBeanProxy(connection, ManagementFactory.THREAD_MXBEAN_NAME,ThreadMXBean.class);
        System.out.println("Thread Count: "+remoteThread.getThreadCount());
        System.out.println("Peak Thread Count: "+remoteThread.getPeakThreadCount());
        System.out.println("Daemon Thread Count: "+remoteThread.getDaemonThreadCount());
        long[] tids = remoteThread.getAllThreadIds();
        for (int i = 0; i < tids.length; ++i) {
                ThreadInfo tinfo = remoteThread.getThreadInfo(tids[i]);
                System.out.println("Thread name = " + tinfo.getThreadName());
        }
        System.out.println();

        MemoryMXBean remoteMemory = ManagementFactory.newPlatformMXBeanProxy(connection, ManagementFactory.MEMORY_MXBEAN_NAME,MemoryMXBean.class);
        System.out.println("Committed: "+remoteMemory.getHeapMemoryUsage().getCommitted());
        System.out.println("Init: "+remoteMemory.getHeapMemoryUsage().getInit());
        System.out.println("Max: "+remoteMemory.getHeapMemoryUsage().getMax());
        System.out.println("Used: "+remoteMemory.getHeapMemoryUsage().getUsed());
        System.out.println();

        OperatingSystemMXBean remoteOS = ManagementFactory.newPlatformMXBeanProxy(connection, ManagementFactory.OPERATING_SYSTEM_MXBEAN_NAME,OperatingSystemMXBean.class);
        System.out.println("OS Arch: "+remoteOS.getArch());
        System.out.println("Number of procs: "+remoteOS.getAvailableProcessors());
        System.out.println("OS Load: "+remoteOS.getSystemLoadAverage());

    }

}

These links are also very helpful:
Using Java platform management beans
How To Retrieve Remote JVM Monitoring And Management Information

Abaixo segue um passo a passo de como configurar o DBCP (pool de conexões)  do Tomcat 6.0 para o Oracle XE

< Resource name="jdbc/myoracle" auth="Container"
              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
              url="jdbc:oracle:thin:@127.0.0.1:1521:mysid"
              username="scott" password="tiger" maxActive="20" maxIdle="10"
              maxWait="-1" />

< description >Oracle Datasource example< /description >
 < res-ref-name >jdbc/myoracle< /res-ref-name >
 < res-type >javax.sql.DataSource< /res-type >
 < res-auth >Container< /res-auth >
< /resource-ref >

Context initContext = new InitialContext();
Context envContext  = (Context)initContext.lookup("java:/comp/env");
DataSource ds = (DataSource)envContext.lookup("jdbc/myoracle");
Connection conn = ds.getConnection();
//etc.

So this error appeared after I compiled my java classes, packaged them in a war, and deployed it to the application server. The only major change that happened to my system was an upgrade to Snow Leopard. I searched the web forums and discovered that this issue is due to compiling the java classes with a different Java compiler version than the JVM version on the application server.

How can this be? It was working fine all this time. I checked my JAVA_HOME environment variable and it was pointing to a JVM-specific directory: 1.X.0

On the command line, I typed:

javac -version

and it returned the latest version. So I thought that maybe the OS upgrade overrided my default Java compiler. I started to look into the ant file to find a task attribute to point to a specific JVM. After redeployment, the error still persisted.

So finally, I thought about testing the actual java compiler, in the 1.X.0 directory. I typed: javac -version and it returned again the latest version. I tried: ./javac -version.. the results are the same.

Then I traversed to the other previous versioned directories. All of them returned the latest version.

This was really odd. So finally, I decided to override all the directories from the AWESOME Time Machine. Specifically, I replaced the directories with the directories before the OS upgrade.

I ran the compilation and deployment and the issue is RESOLVED.

I’m not sure why Snow Leopard overrided my directories with the latest Java compiler, but I’m glad the war file is deployable. If I didn’t discover this issue, then it would have caused me unneccessary stress and panic if it was a release day.

1. Dowload the tar.gz package.
2. Copy the tar.gz package to /usr/local folder
3. Unzip the tar.gz package
>> tar -xzf
4. Create a symbolic link to the tomcat package for simplified upgrades
>> sudo ln -s /usr/local/ /usr/local/tomcat
5. Change the ownership of the folders to nobody to make for restrictive running of tomcat
>> chown -R nobody:nobody /usr/local/tomcat
6. Create scripts to start and stop tomcat (my preference is in ~/bin)
a. start_tomcat
#! bin/sh
export $CATALINA_HOME= /usr/local/tomcat
export $JAVA_HOME= /usr/java
$CATALINA_HOME/bin/startup.sh

b. stop_tomcat
#! bin/sh
export $CATALINA_HOME= /usr/local/tomcat
export $JAVA_HOME= /usr/java
$CATALINA_HOME/bin/shutdown.sh


Note:
a. The $JAVA_HOME line assumes you are using default OS Java package.
b. To use a different version of Java than the default look at the versions in the
/System/Library/Frameworks/JavaVM.framework/Versions/ folder and set the $JAVA_HOME
variable to the appropriate version
c. I highly recommend using the scripts you create to startup and shutdown tomcat because
I have notices that the $JAVA_HOME variables can be set very weirdly if it is done on
the command line if it is not.

Portal de Informações da Via Embratel. Os dados são carregados de forma massiva por arquivo, e visualizados no WebSite. Conta com visualização de Notícias e download de Arquivos.

Noticia

busca

..: Atuação

Atuação como Analista/Desenvolvedor JEE.

..: Cliente

Via Embratel

..: Tipo / Ano

Sistema Web / 2009

..: Tecnologias

Java, JEE, Oracle DB, Apache Tomcat, JPA/Hibernate, JSF/Jboss Rich-Faces,  Jboss Seam

On a Weblogic 10 environment, you may get an error like
javax.servlet.ServletException: javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: “java.sql.SQLException: No suitable driver found for jndi_ds
if you are using the sql-taglib to access your JNDI name from the Weblogic application server, configured via the Weblogic console.

The solution is quiet simple, but not that good documented. It is not possible to use the paramter “driver” inside the sql:setDataSource – tag. You rather have to promote the JNDI name in your web.xml like this:

<resource-ref>
<res-ref-name>jndi_ds</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Than you can set the dataSource with the sql:setDataSource – tag like this:

<sql:setDataSource dataSource="jndi_ds" />

and finally use the sql-taglib as you did in any other environment like Tomcat server and so on.

Siempre, al instalar el Tomcat, cualquier version, tenia el problema de que no podia iniciarse solo, lo terminaba iniciando mediante el Eclipse u otro programa por el estilo. Se instalaba bien, hacia todo correcto, pero al configurarlo para ke arrancara solo me marcaba un error al tratar de iniciar el servicio. Me di cuenta que solo me lo mostrraba cuando lo instalaba en Windows XP SP2 y en algunas ocasiones con Windows Vista Home Premium, buscando, di con el error.

El error esta en una libreria que falta y que Tomcat no instala, dicha libreria es necesaria para arrancar el Tomcat automaticamente al encender Windows. Para aquellos que tienen este mismo problema, aqui esta la solución.

La solución es muy sencilla, solo tienes que bajar la libreria que se llama msvcr71.dll de aqui y pegarla dentro de la carpeta de Windows/System32.

Have you ever seen this when you are starting up tomcat ?

This is because your tomcat installation is not installed with the native apache portable runtime.
Although this is ok in a development environment, its not recomended for production.
In order to have a optimized server with proper scalabillity you should install this on a production server.

For more reading about the subject: Tomcat 6.0 documentation

How to install it
Download the correct dll from one of the links:
Windows 32 dll
Windows 64 dlls

Copy the dll to the bin directory of your tomcat server:

Make sure that the bin directory is in the path before starting up tomcat again.

Voila

Getting a thread-dump is one of the first steps in troubleshooting a misbehaving Java application. There are a few good ways todo this task but the easiest of them all is

kill -3 <PID>

This will send the thread-dump to your stdout logs.

JFastCGI est un projet sous licence BSD démarré il y a quelques mois maintenant. Le but est de permettre a un container de servlet (type tomcat ou jetty) de servir des pages générées par une application compatible fastCGI.

Cela permet par exemple de servir des pages PHP interprétées par le moteur PHP officiel sans avoir a utiliser un serveur apache.

La version 1.1 est “en prod”, et la version 2.0, qui introduit la notion de pool de connexion entre une application tomcat et plusieurs “serveurs” fastcgi est en cours de tests (j’en ai profité pour créer un ensemble de tests unitaires, utilisant mockrunner). Elle permettra un énorme gain de performance pour les applications fortement sollicitées !

La version 2.0 ajoute aussi une meilleur intégration avec Spring, en implémentant HttpRequestHandler.

Des contacts ont même étés pris avec l’équipe de développement de Glassfish, dont jfastcgi pourrait devenir un module optionnel de la version 3 …

Bref, cette librairie semble promise a un bel avenir, et permet d’utiliser les serveurs en java de manière moins “fermée” mais ce projet demande à gagner en maturité, votre aide est la bienvenue !

For Apache to be front end of Tomcat:

Say appname is at http://servername:8080/appname

1.
Redirect / http://servername/appname/
ProxyPass /appname/ http://localhost:8080/appname/
ProxyPassReverse /appname/ http://localhost:8080/appname/

2.
LoadModule jk_module modules/mod_jk.so
JkWorkersFile /etc/httpd/conf/workers.properties
JkShmFile /var/log/httpd/mod_jk.shm
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel info
JkLogStampFormat “[%a %b %d %H:%M:%S %Y]“

$ cat /etc/httpd/conf/workers.properties
# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009

(virtual host config)
RewriteEngine on
Rewriterule ^/$ /appname/ [R=301]
JkMount /appname/ worker1
JkMount /appname/* worker1

3. conf.d/proxy_ajp.conf:
uncomment:
ProxyPass /appname/ ajp://localhost:8009/appname/

W końcu zabrałem się za czytanie książek o JSP. Póki co ustawiłem Tomcat’ a i bazę danych MySQL. Mam zamiar stworzyć galerię zdjęć dodawanych za pomocą komórki tzn. jeszcze będę musiał napisać aplikacje J2ME by móc cokolwiek wysyłać z komórki ale mam nadzieje że się uda dość szybko to zrobić. Przede mną jeszcze rozwikłanie zagadki jak to ze sobą połączyć i jak wykorzystuje się połączenie z internetem w komórkach do przesyłania danych. A potem jak aplikacja ma odbierać te dane i gdzie je składować. Tak więc troszkę jest :] Ale przynajmniej ciekawi mnie to.

Para el proyecto que estoy realizando para una de mis asignaturas, he tenido que intalar Tomcat para hacer unos servidores Web con SOAP.
Aunque aun mi odisea no a terminado, he tenido algunos problemas y algunas soluciones:

• Es mejor no instalar tomcat con ejecutable, es mejor bajarse el zip, ya que netbeans necesita unos archivos que instalador no instala.
• Si da problemas del tipo no se ha encontrado archivo en /conf/catalina/localhot es por que teneis mal los permisos darle permisos a todo . Cuando probe el Tomcat con Eclipse con esta solución ya funcionaba, pero con Netbeans no.
• Si dando permisos aun no conseguis que funcione el Tomcat con Neatbeans, lo mejor que podeis hacer es copiarlo a la C: donde al fin he conseguido que vaya.

Proximamente como pude crear un SW en netbeans, en Eclipse me he dado por vencida.