Jaikiran Pai

+ Follow
since Jul 20, 2005
Jaikiran likes ...
IntelliJ IDE Ubuntu
Merit badge: grant badges
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Rancher Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jaikiran Pai

Injection is supported only for "managed" instances. Using new() to instantiate doesn't allow injection to happen since the object is no longer managed by the container(s). So you will have to use the techniques specified by the Java EE spec to instantiate them (like using JNDI lookups or injection).
When/where in the code are you trying to access that injected bean instance? Can you post the NullPointerException or whatever exception stacktrace you are seeing?
A quick look suggests, you might be missing an index.html (the default welcome file for an application). If you want to use StaticTime.jsp as your welcome file (the one which gets rendered when you access the root of the web application), then you'll have to edit the web.xml to include it as the welcome file. Take a look at the web.xml's xsd file to see how to specify that in the web.xml.

Jeanne Boyarsky wrote:A Jumpin JForum Day to y'all.

Happy Jumpin JForum day to everyone here!

Jeanne Boyarsky wrote:
To celebrate, we have some shiny new features for you complements of Devaka, Jaikiran, Jeanne and Tim.

I haven't really been active in the past few months here and just happened to see the new view (which we used to call beta view) and am really pleased to see how good it looks. I did contribute to it when we decided to upgrade the look and feel of this site, but a lot of credit should go to Devaka, Jeanne and Tim for getting this to production ready stage and having it available to everyone. I see that the new look, looks a lot more polished and smooth compared to what I saw the last time I contributed. It even works great on a tablet. Congratulations
7 years ago
Just a FYI - Someone else ran into this problem today and raised it in the undertow-dev mailing list and it appears that this has been acknowledged as an open bug:

8 years ago
Welcome to CodeRanch!

This question got answered in the other forum where you asked this https://developer.jboss.org/thread/261261
8 years ago
Also being discussed here https://developer.jboss.org/thread/261001. As Justin noted in that thread, it's combination of the pool size the and maxSession @ActivationConfigProperty on the MDB. If it still isn't working, please provide more details in that other thread including the exact configurations you are using and also add some details on how you are checking the number of instances.
8 years ago
Which version of JBoss AS or WildFly is this?
8 years ago
Sergiy, we don't have too many Drools experts in here. I think a better place to ask this is the drools user mailing list which is listed here http://www.drools.org/community/forum.html
8 years ago
I don't fully understand what is being tried out, but port 1099 was a legacy of JBoss AS before version 7.x. It is no longer used for JNDI. Neither is the JNP protocol.

Are you doing some kind of JNDI lookups? What does the relevant code/configuration look like?
8 years ago
Just to be sure, did you really use:

./standalone.sh -b=

If so, then it's incorrect. There should be no '=' sign in there. It should be:

(notice the space between the -b and the value)
8 years ago
Welcome to CodeRanch!

JBoss AS 7.1.1.Final is an old version and was never tested with Java 8. Have you tried using a lower version of Java to run it?

On a related note, I highly recommend that you use the latest released WildFly version (9.0.0.Final currently) http://wildfly.org/downloads/ instead of AS 7.x. JBoss AS was renamed to WildFly (http://jaitechwriteups.blogspot.in/2013/06/wildfly-release-and-history-behind-the-release.html) and thus WildFly releases are a continuation of the JBoss AS releases.

8 years ago
I think this is relevant http://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q1. Although it is from the Tomcat site, the explanation there applies to all servers.

A snippet from there:

Change all your JSPs to include charset name in their contentType.

For example, use <%@page contentType="text/html; charset=UTF-8" %> for the usual JSP pages and <jsp:directive.page contentType="text/html; charset=UTF-8" /> for the pages in XML syntax (aka JSP Documents).

8 years ago



Maya, welcome to CodeRanch!

Log4j doesn't play a role here since the original message being logged (from some library) itself doesn't have the necessary formatting in that text. You'll have to check who is logging that message and probably change the code to format the message being logged, before passing that message to the logger.