Hello, thenks for your reply
I have tried changing the code as suggested....
server.invoke(new ObjectName("jboss.jca:name=OracleDS,service=ManagedConnectionPool"), "BlockingTimeoutMillis", new Object[] { "5" } ,new String[] { Integer.TYPE.getName() });
but I still get the same error...........no way to get it working with this syntax ?
By the way, I'm using JBoss 4.0.5 GA on an XP box....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104102#4104102
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104102
Here's one difference between my poms for an ear and yours.
In the parent pom, it's my experience that I should generally build the ejb jar(s) before the webapp war(s) - often the webapp(s) depend on the ejb(s) (mainly for custom converters).
| <modules>
| <module>ejb</module>
| <module>webapp</module>
| <module>ear</module>
| </modules>
|
Also, presumably, you've put a seam.properties file in ${PROJECT_HOME}/ejb/src/main/resources - there have been times in a new project when I haven't done this and run into the same problem. After you've checked that, my guess is it's time to double check the jndiPattern in your webapp's components.xml file.
Good Luck
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104099#4104099
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104099
gvnanil, since you're asking a new question and not answering the one I posted it would make sense to start a new thread on it. That would beneficial in two ways
1) You have more chance of someone answering your specific question
2) It would prevent others from wasting their time by drilling down on this topic only to realize that someone had posted a different question on this thread.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104093#4104093
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104093
Damian,
thirdPartyHelper is a SLSB - the intent here is to simply provide the suggested options - it takes about 2-3 seconds to respond.
my core:manager settings are as follows:
| <core:manager concurrent-request-timeout="500"
| conversation-timeout="900000"
| conversation-id-parameter="cid"/>
|
I believe my conversation timeout parameter is longer than your suggestion (15 minutes above). I wonder what that concurrent-request-timeout param does...
Thanks,
Brad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104089#4104089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104089