would ejbCreate work for your needs? it's called after deployment and before
execution of any "business" methods.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940008#3940008
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=rep
i'd recommend looking at the jndibinding-service.xml in the jboss deploy
folder. i'm told you can bundle this as part of an ear to isolate things to a
particular application, but haven't really tried that much.
in the slsb, i'd get all values from jndi during the setSessionContext method,
and
you don't really give any details about your method execution. there's many
reasons an app server will remove a slsb from the pool as required from the ejb
specification. anytime a bean throws a checked exception, it gets removed from
the pool.
i don't know the details of how to control the si
btw, i created a simple slsb, and set the timeout to 2 seconds. the client
(remote java app) did indeed just hang. a message was posted on the server
that the transaction timed out.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938880#3938880
Reply to the
i'm sorry, you'll have to read xdoclet's documentation for that one.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938879#3938879
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938879
if you're doing a potentially long running transaction and you don't want the
client to wait, i would choose a MDB instead of a stateless session bean.
client posts message and is done.
though i would think that if a transaction timed out, the container should
throw a remote exception possibly
have you tried it and encountered an error?
dynamic class loading should just work unless you've taken steps to configure
your server otherwise.
i've had numerous remote clients to ejb's that only have the ejb-client jar's
and the jboss client jar's in their classpath. i am under the impressi
kalai,
it's truely a bit challenging to piece through the words and make sense of your
problem ( especially with sentences like: "have you understand my query??? "
), but it seems that you have a stateless session bean that is not able to
access another bean in the same jar file correct? this
i can't seem to edit my previous posts?
anyway, i tried jboss-4.0.4CR2 i think it's working kinda like i expected. i
can start a job by calling the slsb, which as i said, gets the timer service,
and creates a timer. it'll be fun to see how easy it is to get 4.0.4CR2 on a
production machine :)
btw, i'm on jboss 4.0.3RC1. will try 4.0.4 when i get a chance later today.
do i need some special transaction stuff in the dd's? i don't think i even
have a jboss-ejb-jar.xml or what ever it it is. just ejb-jar.xml for the slsb.
i couldn't find info that dd stuff is needed for timedobject.
How can I persist a TimedObject across server recycles / ejb redeployments?
I create a simple slsb which accesses the TimerService to create a timer.
ATM, the timer is scheduled every 3 seconds. My bean implements the
TimedObject interface, and I can see the ejbTimeout method being called eve
hi,
we've encountered situations where our connection pool fills up and can't get
any more connections. this does indicate a possible leak or error somewhere,
but what we would like to have is a way for an snmp trap to be sent when the
pool reaches say 90% utilization or so.
i notice jboss
"ploskikl" wrote :
| Does JBoss plan to provide server definitions elements for current (and
future) JBoss releases that can be downloaded using the Eclipse update manager?
|
i'm also interested in weather JBoss will support a JBoss app server definition
for eclipse wtp. i have eclipse wtp
we get this error message in the server.log when starting our jboss servers.
it seems that it's due to the jms Persistance Manager trying to ensure tables
are available for it to persist jms messages.
when working with other team members to search for errors they encounter, we
typically will
we'd like to use jndi to store heirarchictal (sp) information that can be
configured per server insatance (or really per target environment: dev, prod,
qa, etc). the tree would be something like:
/orange/three/FOO = "orange3foo"
/blue/four/BAR = "blue4bar"
etc. basically a few levels of nestin
we're looking to secure access to the core jboss mbeans (and possibly other
aspects of the system). specifically, we want to prevent "rogue" access to
shutting down the jboss server instance. i believe in the default
configuration, once a server has been started, that any user on the network,
i'll just give a bit more details. i've been learning (or trying to learn) too
much about jboss class loaders and such lately. it always seems to come back
to the jdk including stuff that it probably shouldn't include. (these xml
parsers).
the sun jdk 1.4.2_06 or so includes some old, but us
we currently have an error running xerces/xalan on jboss. our web app is
deployed fine to a stock 4.1.30 tomcat instance. we wanted to use jboss 4.0.0
instead. when running the application we see an error like:
17:02:06,345 INFO [STDOUT] java.lang.NoSuchFieldError: S_KEY_INDENT_AMOUNT
17:02:06
we have two web applications (one is more a web service than a web app, but
it's packaged as a war and is accessed via http post), i'll call them
webService.war and nonWebService.war. the nonWebService.war uses a custom
security module to provide authentication. we'd like the webService.war to
i'm also interested in using snmp for monitoring the jboss server's "health".
one thing that has been mentioned as interesting to watch are free memory
levels. if the free memory gets above say 90%, i'd like to send an snmp trap
to the snmp manager.
i haven't really worked much with snmp as
ok, i'll reply with my solution. running jboss.split will kill all sessions for
the testWeb application:
|
|
|
|
|
|
| session ids:${some.property}
|
|
|
|
|
|
|
i'm looking for a way to expire all web sessions, then call the garbage
collector to help determine if we have a memory leak somewhere in our
application. i've got the following ant task that'll list the sessions, but
can't _easily_ get each session id into a property to call the expireSession
thanks for the response. this looks like exactly what we're after. i was
looking into creating a custom mbean to put my values into the jndi, but will
looking into patching this in first.
the need is definately there for configuring url resource ref's outside the
war.
the patch seems far
we're looking for a way to manage our configuration outside of our application.
specifically, when we get a URL resource reference, we're currently
configuring the value of the URL in the jboss-web.xml.
i think this requires us to "touch" the ear/war if we want to change the value
of the u
we have coded a wait after the shutdown, but 10sec doesn't seem to be enough.
the problem with checking the ports is that they can be configured on different
environments. plus there's lots of ports being opened by jboss. which ones to
check?
isn't there a synchronous shutdown call for jboss
i'm after some recommended procedures for shutting down jboss. we're using win
2k, tao linux, and SuSE linux.
we currently aren't using init.d scripts on the linux machines. we're using an
ant build script which calls the run.sh and shutdown.sh
here'sthe issue we're seeing. in order to recy
that suspend=y seems only usefull if you're debugging jboss itself, or if
you're debuggin a startup servlet that'll be run when the app is deployed on
startup. i'd guess most folks would rather the default be suspend=n. took me
a bit to find this "bug" in the run.bat.
View the original post :
any thoughts out there? i've heard something about writing a custom mbean to
provide the URL's application, but am not sure how that would look.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876582#3876582
Reply to the post :
http://www.jboss.org/index.ht
on p 480 there shoudl be ant.properties file instead of .ant.properties file.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876408#3876408
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876408
where should bugs for the docs be posted? p 359. first paragraph continued
from last page:
"but there is no way to specify and a element"
maybe should be
"but there is no way to specify that as an element can have..."
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
if anyone is interested, i was able to bring up a completely new jboss instance
up and running on a new machine, deploy the postgresql-ds.xml and
login-config.xml with the encrypted passwords generated on the other server,
and it worked ok. it _appears_ to be something that you can generate onc
i'm configuring our web application to get URL's from doing a JNDI lookup. i
have the resource-ref defined in web.xml, and have the coresponding
resource-ref defined in jboss-web.xml. this seems to work, but we would really
like to have these definitions outside of the jboss-web.xml.
it woul
i've went through the steps to use an encrypted datasource password, covered in
the faq. works nicely once i have all the peices in place. my question is, is
the encrypted password per server instance? per jboss install? or is the
login-config.xml portable?
i'm interested if i can version i
is there a method in jboss (via an MBean perhaps) to view the count of object
creation/garbage collected? we're researching some oom exceptions we've been
having. perhaps we're keeping too many sessions around ( we have an unusually
high session timeout), but would also like to see if there's p
34 matches
Mail list logo