Hi,
I've written a Stateless Bean, and inside I am using an ExecutorService which
spawns threads, and I await the result of all of them. My concern is, that I
don't want to see any InterruptedException's.
How is this managed by the container? Is this passivate proof while it waits?
Thanks in
Hi,
Not sure if this is the right place, but here goes:
I was wondering if Jboss allows a different implementation of the
DatabaseManager? Why? I want to explore and possibly implement a different way
of dealing with transactions using a native XML-database using Jboss. So,
instead of a
Hi,
I've wrapped a complex WAR (using its own log4j.xml config) inside an EAR and
deployed that in Jboss (4.2.2 Ga) and encounter the following:
- Logging fails: ERROR: invalid console appender config detected, console
stream is looping
- The application IS deployed and runs as expected, just
Thank you jaikiran, that did the trick!
Mike
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163314#4163314
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163314
___
jboss-user
Hi,
When I look at the web-console, I see the following list of applications:
| localhost
| phonegreetings/jmx-console [1]
| localhost/invoker
| localhost/web-console
| phonegreetings
| phonegreetings/jbossws [1]
| localhost/webservices [2]
|
Hi,
I am using Jboss 4.2.2.GA in the following situation; multiple jboss instances
and virtual hosts on a single machine. I am also using apache with ajp/proxy to
forward requests to the appropriate virtual hosts.
For the webservices, I have stateless EJB with annotations, and I can see Jboss
Hi,
Did a little more investigation, and it seems the problem is somewhere in the
server.xml (jboss-web.deployer), at least that is what I think.
In there I have a Host configuration that matches with the virtual host.
Meaning all request go through that specific web application, including the
Hi,
Brief situation:
A - B (remote ejb lookup + invocation - success)
B performs some ejbTimer logic, in the timeout I proceed
B - A (remote ejb lookup + reflection/invocation - fails due container not
yet available)
I'm using Jboss 4.2.2.GA and pass the JNDI properties, as well as the
Oke, heres the stacktrace:
2008-04-04 18:38:42,531 WARN [org.jboss.ejb3.LocalProxy] Container
jboss.j2ee:ear=phonemessage-1.0.0.ear,jar=phonemessage-engine-1.0.0.jar,name=CallHandlerServiceBean,service=EJB3,VMID=ff2143713a7260c3:-350bd643:1191a4ce5d2:-7ffd
is not yet available
2008-04-04
Oke, going to put in some background:
Instance A:
From boot.log:
15:56:18,265 DEBUG [ServiceCreator] Created bean: jboss:service=Naming
15:56:18,265 DEBUG [ServiceConfigurator] CallByValue set to false in
jboss:service=Naming
15:56:18,266 DEBUG [ServiceConfigurator] Port set to
From which instance you'd like to know the JNDI settings? But the
code/annotation is configured for both:
| @Stateless
| @Local({CallHandlerService.class})
| @Remote({CallHandlerService.class})
| @Interceptors({NullReferenceCheck.class})
| public class CallHandlerServiceBean
Now to think of it,
Could it be that:
Adding some JNDI property to search for a remote proxy will solve it? If so,
how and what do I do that?
or
I split the local and remote interface, so they come with unique names. That
will 'force' the lookup in obtaining the right proxy.
Your thoughts?
Problem solved, by enforcing lookup of remote interface. I did this by changing
the name of the interface to: CallHandlerServiceRemote.
Hopefully others are helped by this as well.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4141836#4141836
Reply to the
Thats ok, anyways I want to thank you for the support/effort!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4141848#4141848
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4141848
Hi,
Brief situation:
A - B (remote ejb lookup + invocation - success)
B performs some ejbTimer logic, in the timeout I proceed
B - A (remote ejb lookup + reflection/invocation - fails due container not
yet available)
I'm using Jboss 4.2.2.GA and pass the JNDI properties, as well as the
Using jboss 4.0.5; a callback timer method on a stateless bean with transaction
attribute REQUIRED_NEW does not seem to 'isolate' the transaction when called
concurrently. A org.hibernate.StaleStateException occurs and the whole thing is
rolled back.
| @Timeout
|
16 matches
Mail list logo
