Category: JBoss

Posted on

Show Spring SQL Code for Debugging

You can show the SQL being generated in the log file by setting the showSql parameter to true in hal-web/src/main/webapp/WEB-INF/config/spring/spring/webapp-jpa.xml, line 31.  You’ll need to rebuild the application and restart it after changing this parameter.

Posted on

Install SQL Developer on VM

Download link of Oracle SQL Developer Tool (Linux RPM package): http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html

How to install
sudo rpm -ivh sqldeveloper-3.2.09.23-1.noarch.rpm

Information about RPM
rpm -qpl sqldeveloper-3.2.09.23-1.noarch.rpm

Remove RPM
rpm -evh sqldeveloper-3.2.09.23-1.noarch.rpm

List of RPM's
rpm -qa | grep -i sql

Information about RPM
rpm -qi sqldeveloper-3.2.09.23-1

Running SQL Developer
/opt/sqldeveloper/sqldeveloper.sh

Installs on menu too:
Applications/Programming/SQL Developer

Connections:

DEVWEB
Connection Type: Advanced
Role: Default
Custom JDBC URL: jdbc:oracle:thin:@//haltstdbs02:37200/devweb

TSTWEB
Connection Type: Advanced
Role: Default
Custom JDBC URL: jdbc:oracle:thin:@//haltstdbs02:37100/tstweb

Additional Details:

The connections property file can be found in:
hal-web/src/main/webapp/WEB-INF/config/spring/spring/jdbc-e1.properties.

Posted on

Spring / Struts Upgrade

Want to start using Spring annotations and also to update Struts to avoid pitfalls with current application.

Spring upgrade to 2.5.6.0.3 and Struts 2.3.4 (going to release 2.3.5 soon)

Struts 1.2.9 for Struts 1.0 application

and then 3.1.2.RELEASE for Spring

From: Virginia Angélica Martz [mailto:vmartz@hexacta.com]
Sent: Tuesday, August 28, 2012 7:54 AM
To: Guillaume Radde
Cc: Thompson, Sonya (HAL); Ruckman, Maurice (HAL); Fillman, Eric (HAL); Mario Hartman; Ignacio Peluffo
Subject: WITG-146 Pending dependencies

Hello all,

Yesterday we were changing third-party dependencies in order to take them from Central Repository.

This is a summary of the dependencies that are still pending for changes.

Some of them are not available in Central, others don’t have a well defined version and in all these cases your help would be appreciated.

struts2-ssl-plugin-1.2

<dependency>
<groupId>com.hal.thirdparty</groupId>
<artifactId>struts2-ssl-plugin-1.2</artifactId>
<version>0.1-hal</version>
<scope>runtime</scope>
</dependency>

This dependency is not in Central nor in our Google Code mirror in Nexus, so I cannot replace it with the last version (1.2.1) .

Two options:

1)      download from this site http://code.google.com/p/struts2-ssl-plugin/ the 1.2.1 version and make it manually available in third-party.

2)      Update GoogleCode mirror in Nexus.

IngrianLog4j/ IngrianNAE-5.1.1

<dependency>
<groupId>com.hal.thirdparty</groupId>
<artifactId>IngrianLog4j</artifactId>
<version>0.1-hal</version>
</dependency>

<dependency>
<groupId>com.hal.thirdparty</groupId>
<artifactId>IngrianNAE-5.1.1</artifactId>
<version>0.1-hal</version>
</dependency>

They are third-party but I think they should be kept in this way.

gson-1.4-javadoc

<dependency>
<groupId>com.hal.thirdparty</groupId>
<artifactId>gson-1.4-javadoc</artifactId>
<version>0.1-hal</version>
<scope>runtime</scope>
</dependency>

Is this dependency used for anything? In general javadoc dependencies are not needed.

sslext

<dependency>
<groupId>com.hal.thirdparty</groupId>
<artifactId>sslext</artifactId>
<version>0.1-hal</version>
<scope>runtime</scope>
</dependency>

I don’t know which version we should use.

http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22sslext%22%20AND%20a%3A%22sslext%22

ojdbc14

<dependency>

<groupId>com.hal.thirdparty</groupId>

<artifactId>ojdbc14</artifactId>

<version>0.1-hal</version>

<scope>runtime</scope>

</dependency>

When I replaced it with the dependency in Central it failed…. dependency is empty in central and maven repository (0 bytes)

http://mvnrepository.com/artifact/ojdbc/ojdbc/14

http://search.maven.org/#artifactdetails%7Cojdbc%7Cojdbc%7C14%7Cjar

We are still analyzing if “spring-webmvc” is needed. We think that it can be removed but we are testing to be sure.

Thanks again!

Virginia

From: Virginia Angélica Martz [mailto:vmartz@hexacta.com]
Sent: Tuesday, September 11, 2012 11:20 AM
To: Fillman, Eric (HAL); Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Thompson, Sonya (HAL); Ignacio Peluffo
Subject: RE: WITG-146: Update

Hi Eric,

Good questions… I’ll try to answer them J

1)      Basically one of the changes from Spring 2 to Spring 3 is the organization of the framework. While in Spring 2 there was only one jar, Spring 3 has a set of jars and you have the opportunity to include only the functionality that you need. This link can help you: http://dushyanthinguva.blogspot.com/2010/03/what-to-expect-while-migrating-to.html. In short it says:   “The first thing you will notice when upgrading to Spring 3 from Spring 2 is that it is packaged in a bunch of jars (or maven dependencies). This changed in Spring 2.5 and is generally regarded a good move although it makes upgrading a bit of a pain (even with maven). The good part is, the jar/dependency names are pretty self descriptive.” More info here à http://blog.springsource.com/2009/12/02/obtaining-spring-3-artifacts-with-maven/

2)      You are right, spring-context dependency is duplicated L. Can I fix it in the same feature branch or we have to create a new one? Please let me know and I’ll do it as soon as possible.

3)      It’s true, some of the dependencies are not necessary in hal-web, but we need them in both places because of the way you are deploying. From what I’ve talked with Mario, Guillaume and Ignacio, you need the dependency in the module for compilation purposes and then you need it also in hal-web in order to be placed in WEB-INF/lib folder during the deploy.

I hope this helps, if something is not clear or you need more info just let me know..

Regards,

Virginia

Posted on

Modular Applications Development with Maven

Notes:

Different ways to run Maven:
http://www.vineetmanohar.com/2009/11/3-ways-to-run-java-main-from-maven/

/home/jboss1./m2/repository

<version>1.0</version> is for application, and SNAPSHOT for development

These three tags are mandatory:

<groupId>com.hollandamerica</groupId>
<artifactId>ModularApplicationTutorial</artifactId>
<version>1.0</version>

1) Create a pom.xml to compile the application into a jar called cruiser.jar. Run the test suite.

2) You want to move the development of the booking service to a separate project. Create a separate pom.xml to compile Booking.java, BookingService.java and BookingServiceImpl.java into a separate jar called booking.jar. Have cruiser.jar use booking.jar. Execute cruiser.jar to verify it works correctly.

3) You want cruiser.jar and booking.jar to always have the same version number. Create a parent pom.xml for your 2 projects called booking-parent, and define a property called VERSION. Have booking.jar and cruiser.jar make use of this VERSION property as their version number.

4) You want to compile both cruiser.jar and booking.jar in one single command. Have cruiser.jar and booking.jar be two submodules of booking-parent.

5) Split booking.jar into booking-api.jar (containing the interface) and booking-impl.jar (containing the implementation of the service). Execute cruiser.jar to verify it still works correctly.

6) We want to prevent developers of cruiser.jar to make direct calls to a specific booking-api implementation. Propose a way to remove the direct dependency between cruiser.jar and booking-impl.jar. Implement it.

Posted on

JBoss Operation Network (JON) – JBoss Monitoring Tool

From: Augustine, Anila (HAL)
Sent: Monday, July 30, 2012 8:16 AM
To: Guillaume Radde
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: RE: Looking for Thread Deadlocks on JBoss

Cool! That’s easy J. I mentioned this to Don on Friday too. Good news is we will be getting another linux admin (possibly this week) – woohoo! That should free up 40 hours for Don.

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Friday, July 27, 2012 10:01 AM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

Around 40 man-hour. Depends on how many environments we want to monitor.
http://www.redhat.com/v/swf/jboss_on/2122_RedHat_JONOverview.html

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Sent: Friday, July 27, 2012 9:11:27 AM
Subject: RE: Looking for Thread Deadlocks on JBoss

So what would it take to deploy JON?

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 6:46 PM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

I will add jmx-console. JBoss Operation Network is a separate monitoring tool (kind of like Foglight) that we did not deploy.

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>
Sent: Thursday, July 26, 2012 2:52:34 PM
Subject: RE: Looking for Thread Deadlocks on JBoss

Guillaume - in your documentation, please add JBoss Operation Network -  I think the team would benefit from a show   & tell, if that’s not done already.

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 10:31 AM
To: Thompson, Sonya (HAL)
Cc: Augustine, Anila (HAL); Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

There are a lot of things that can be seen through the jmx-console. Globally, it can be used to review the internal of a JBoss server while it's running. The downside is that it's hard to find what you're looking for. I usually just google what I'm looking for with "jmx-console"

 

From: Augustine, Anila (HAL)
Sent: Monday, July 30, 2012 8:16 AM
To: Guillaume Radde
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: RE: Looking for Thread Deadlocks on JBoss

 

Cool! That’s easy J. I mentioned this to Don on Friday too. Good news is we will be getting another linux admin (possibly this week) – woohoo! That should free up 40 hours for Don ;-)

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Friday, July 27, 2012 10:01 AM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

 

Around 40 man-hour. Depends on how many environments we want to monitor.

http://www.redhat.com/v/swf/jboss_on/2122_RedHat_JONOverview.html

 

 

 

 

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Sent: Friday, July 27, 2012 9:11:27 AM
Subject: RE: Looking for Thread Deadlocks on JBoss

So what would it take to deploy JON?

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 6:46 PM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

I will add jmx-console. JBoss Operation Network is a separate monitoring tool (kind of like Foglight) that we did not deploy.

 

 

 

 

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>
Sent: Thursday, July 26, 2012 2:52:34 PM
Subject: RE: Looking for Thread Deadlocks on JBoss

Guillaume – in your documentation, please add JBoss Operation Network -  I think the team would benefit from a show   & tell, if that’s not done already.

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 10:31 AM
To: Thompson, Sonya (HAL)
Cc: Augustine, Anila (HAL); Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

There are a lot of things that can be seen through the jmx-console. Globally, it can be used to review the internal of a JBoss server while it's running. The downside is that it's hard to find what you're looking for. I usually just google what I'm looking for with "jmx-console"

 

 

 

 

From: "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
To: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>
Cc: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>, "Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)" <guillaume.radde@redhat.com>
Sent: Thursday, July 26, 2012 9:09:58 AM
Subject: RE: Looking for Thread Deadlocks on JBoss

Guillaume & Maurice,

Thanks so much for sharing this info with us!

~Sonya

From: Ruckman, Maurice (HAL)
Sent: Thursday, July 26, 2012 7:49 AM
To: Fillman, Eric (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: RE: Looking for Thread Deadlocks on JBoss

Link to Console

haldevjbsXX.hq.halw.com/jmx-console/
admin/admin

List of sessions:

jboss.web
host=localhost,path=/,type=Manager
listSessionIds

Looking for a thread deadlock, how to

jboss.system
type=ServerInfo

listThreadCpuUtilization

Look for a thread taking a huge amount of CPU

Such as ajp-haldevjbs04%2F10.194.50.211-8009-3
and go back to type=ServerInfo

listThreadDump
and then search for thread found previously

From: Fillman, Eric (HAL)
Sent: Thursday, July 26, 2012 6:33 AM
To: Ruckman, Maurice (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: RE: Looking for Thread Deadlocks on JBoss

I’m not following this.

Are you supposed to type this stuff in on command line or something or in the JBoss console?

From: Ruckman, Maurice (HAL)
Sent: Wednesday, July 25, 2012 4:47 PM
To: Fillman, Eric (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: Looking for Thread Deadlocks on JBoss

Guillaume showed me how he found the deadlocked thread.  Here are the notes:

Looking for a thread deadlock, how to

jboss.web

host=localhost,path=/,type=Manager

Looking for deadlocks

jboss.system

type=ServerInfo

listThreadCpuUtilization

Look for a thread taking a huge amount of CPU

Such as ajp-haldevjbs04%2F10.194.50.211-8009-3

and go back to type=ServerInfo

listThreadDump

and then search for thread

Thanks,

From: Augustine, Anila (HAL)
Sent: Monday, July 30, 2012 8:16 AM
To: Guillaume Radde
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: RE: Looking for Thread Deadlocks on JBoss

 

Cool! That’s easy J. I mentioned this to Don on Friday too. Good news is we will be getting another linux admin (possibly this week) – woohoo! That should free up 40 hours for Don ;-)

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Friday, July 27, 2012 10:01 AM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

 

Around 40 man-hour. Depends on how many environments we want to monitor.

http://www.redhat.com/v/swf/jboss_on/2122_RedHat_JONOverview.html

 

 

 

 

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Sent: Friday, July 27, 2012 9:11:27 AM
Subject: RE: Looking for Thread Deadlocks on JBoss

So what would it take to deploy JON?

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 6:46 PM
To: Augustine, Anila (HAL)
Cc: Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL); Thompson, Sonya (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

I will add jmx-console. JBoss Operation Network is a separate monitoring tool (kind of like Foglight) that we did not deploy.

 

 

 

 

From: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>
To: "Guillaume Radde" <guillaume.radde@redhat.com>, "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
Cc: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>
Sent: Thursday, July 26, 2012 2:52:34 PM
Subject: RE: Looking for Thread Deadlocks on JBoss

Guillaume – in your documentation, please add JBoss Operation Network -  I think the team would benefit from a show   & tell, if that’s not done already.

From: Guillaume Radde [mailto:guillaume.radde@redhat.com]
Sent: Thursday, July 26, 2012 10:31 AM
To: Thompson, Sonya (HAL)
Cc: Augustine, Anila (HAL); Ruckman, Maurice (HAL); Fillman, Eric (HAL); Klein, Brian (HAL)
Subject: Re: Looking for Thread Deadlocks on JBoss

There are a lot of things that can be seen through the jmx-console. Globally, it can be used to review the internal of a JBoss server while it's running. The downside is that it's hard to find what you're looking for. I usually just google what I'm looking for with "jmx-console"

 

 

 

 

From: "Sonya Thompson (HAL)" <SThompson@HollandAmerica.com>
To: "Maurice Ruckman (HAL)" <MRuckman@HollandAmerica.com>, "Eric Fillman (HAL)" <EFillman@HollandAmerica.com>, "Brian Klein (HAL)" <BKlein@HollandAmerica.com>
Cc: "Anila Augustine (HAL)" <AAugustine@HollandAmerica.com>, "Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)" <guillaume.radde@redhat.com>
Sent: Thursday, July 26, 2012 9:09:58 AM
Subject: RE: Looking for Thread Deadlocks on JBoss

Guillaume & Maurice,

Thanks so much for sharing this info with us!

~Sonya

From: Ruckman, Maurice (HAL)
Sent: Thursday, July 26, 2012 7:49 AM
To: Fillman, Eric (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: RE: Looking for Thread Deadlocks on JBoss

Link to Console

haldevjbsXX.hq.halw.com/jmx-console/
admin/admin

List of sessions:

jboss.web
host=localhost,path=/,type=Manager
listSessionIds

Looking for a thread deadlock, how to

jboss.system
type=ServerInfo

listThreadCpuUtilization

Look for a thread taking a huge amount of CPU

Such as ajp-haldevjbs04%2F10.194.50.211-8009-3
and go back to type=ServerInfo

listThreadDump
and then search for thread found previously

From: Fillman, Eric (HAL)
Sent: Thursday, July 26, 2012 6:33 AM
To: Ruckman, Maurice (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: RE: Looking for Thread Deadlocks on JBoss

I’m not following this.

Are you supposed to type this stuff in on command line or something or in the JBoss console?

From: Ruckman, Maurice (HAL)
Sent: Wednesday, July 25, 2012 4:47 PM
To: Fillman, Eric (HAL); Thompson, Sonya (HAL); Klein, Brian (HAL)
Cc: Augustine, Anila (HAL); Guillaume Radde (guillaume.radde@redhat.com) (guillaume.radde@redhat.com)
Subject: Looking for Thread Deadlocks on JBoss

Guillaume showed me how he found the deadlocked thread.  Here are the notes:

Looking for a thread deadlock, how to

jboss.web

host=localhost,path=/,type=Manager

Looking for deadlocks

jboss.system

type=ServerInfo

listThreadCpuUtilization

Look for a thread taking a huge amount of CPU

Such as ajp-haldevjbs04%2F10.194.50.211-8009-3

and go back to type=ServerInfo

listThreadDump

and then search for thread

Thanks,

Maurice Ruckman

Voice: (206) 626-7497 x67497

Cellular: (206) 650-7576

Maurice Ruckman

Voice: (206) 626-7497 x67497

Cellular: (206) 650-7576