Marcel Friedmann

Greenhorn
+ Follow
since Nov 07, 2014
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
2
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Marcel Friedmann

Implementing asynchronous stuff with the WorkManager is quite exhausting. For heavy workloads you need a sophisticated websphere configuration - the standard does not work so well for that.
The programming model is also not neat.
Since Java EE 6 you can simply add an @Asynchronous Annotation to mark an method as async. Thats a lot easier to handle. You can also combine this quite easily with Java Futures.
However you may have to break down your WorkManager-code for that.

This blog post explains briefly how to use asynchronous methods in WebSphere
liferay-home can also be configured in portal-ext.properties :-). So you can define which folder to use.
All available properties can be extracted from portal-impl.jar/portal.properties.

This blog post describes how to install liferay 6 in WebSphere.
http://www.devops-insight.com/2014/08/liferay-62-in-websphere-application.html.
9 years ago
Expand Resource > JMS > Queue/Topic Connection Factory > "your factory"
Under Provider endpoints enter the following triplet: <Server-Host-name>:<SIB-Endpoint-Port-of-Server/JVM>:BootstrapBasicMessaging

This is necessary when using external jms clients.

Source:
http://www.devops-insight.com/2014/08/jms-in-websphere.html
9 years ago
WebSphere supports to listen to queues and topics without mdbs.

Simply instanciate a TopicSubscriber (IBM class) or create a message listener.



Source:
http://www.devops-insight.com/2014/08/jms-in-websphere.html
9 years ago
Hi. thats a common error then a port conflict occurs.
If its a internal websphere port which is causing the trouble you can adjust the serverindex.xml of the AppServer instance directly. This is usually the easiest way :-) but it is dirty.

This post explains how to fix this error
9 years ago
Threads in Java EE are a no-go! Probably the connection (and hence the threads) are not properly closed (terminated).
Please use Asynchronous Methods or Work Managers in WebSphere instead of threads. Or in your case - use JDBC Connection pools correctly!

This post explains how to use asynchronous Methods in WebSphere
9 years ago