[JBoss Messaging] - log out properties of jboss.messaging:service=Connector, transport=bisocket
by Robert Bruckbauer
Robert Bruckbauer [http://community.jboss.org/people/brombertje] modified the document:
"log out properties of jboss.messaging:service=Connector,transport=bisocket"
To view the document, visit: http://community.jboss.org/docs/DOC-15133
--------------------------------------------------------------
Hi,
I really need help on how to solve this problem! Our application monitors critical values using log4j. We want to extend our monitor to log jboss properties of jboss.messaging:service=Connector,transport=bisocket.
Here is a sample:
<!-- the following parameters are useful when there is a firewall between client and server. Uncomment them if so.--> <!-- Das Auskommentieren folgender Paramter bewirkt keine Deaktivierung dieser Einstellung, sondern die die Verwendung der Default-Einstellungen. Das würde nach JBossRemotingGuide folgendes heißen: numberOfCallRetries=3, pingFrequency=5000, pingWindowFactor=2, generalizeSocketException=false Das würde bedeuten, dass wir mit Einführung dieser Einstellung in JBM 1.4.5 alle 5! Sekunden, alle verbundenen Clients vom Server gepingt werden würden. In JBM 1.4.4 war die Einstellung auf 214748364ms, also ca. 60 Stunden. Generell könnte man sagen, dass das Pingen alles Clients nicht notwendig ist, weil wir hier eine direkte Verbindung zum Server ohne Firewall haben. In Bezug auf den Fehler JBMESSAGING-1733 ( https://jira.jboss.org/jira/browse/JBMESSAGING-1733 https://jira.jboss.org/jira/browse/JBMESSAGING-1733) kann das aber auch bedeuten, dass gewisse veraltete Sockets am Server (evtl. WorkerThreads) ohne einen Ping nicht richtig aufgeräumt werden. Um diesen Szenario entgegen zu wirken, pingen wir jede Stunde (pingFrequency=3600000) alle Clients an. Die Clients erwarten in einem doppelten Zeitfenster den Ping vom Server (pingWindowFactor=2) -->
<!-- End immutable parameters --> <attribute name="stopLeaseOnFailure" isParam="true">true</attribute> <!-- Periodicity of client pings. Server window by default is twice this figure --> <!-- Mit clientLeasePeriod=60000 wird das zulässige max. Alter eines Ping vom Client an den Server festgelegt. Hier gilt ein typisches Lease-Verhalten am Server, dass die Lease regelmäßig aktualisiert werden muss. Um dieses Lease-Verhalten zu gewährleisten werden Pings vom Client in halben Abständen validatorPingPeriod=30000 an der Server geschickt. Hier müssen wir erwarten, dass unter Lastsituationen bzw. wegen writeTimeout=30000 sich die Rückantwort des Servers verzögern kann. Mit der validatorPingTimeout=60000 bestimmen wir die max. Zeit für die Rückantwort des Servers auf den Client Ping. -->
<!-- Max Number of connections in client pool. This should be significantly higher than the max number of sessions/consumers you expect --> <attribute name="JBM_clientMaxPoolSize" isParam="true">500</attribute> <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery --> <attribute name="callbackTimeout">10000</attribute> <!-- Use these parameters to specify values for binding and connecting control connections to work with your firewall/NAT configuration
Especially I'm interested in the following value:
The idea ist to use a JMX-Server to get a reference of the configuration value. The problem is to find out how I navigate through the JMX model and to associate classes with XML content.
Can anybody provide a code snippet for that purpose?
Thanx in advance
robert
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15133]
Create a new document in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
16 years
Re: [jboss-user] [JBoss Web Services Development] - JBWS-2210 : CXF Username Token JAAS integration
by Darran Lofthouse
Darran Lofthouse [http://community.jboss.org/people/darran.lofthouse%40jboss.com] replied to the discussion
"JBWS-2210 : CXF Username Token JAAS integration"
To view the discussion, visit: http://community.jboss.org/message/536495#536495
--------------------------------------------------------------
Hi Sergey - I have worked on some of the similar areas you are looking at here in our Native stack so have been interested to see your comments here.
Looking at your comments regarding the changes needed in CXF it looks like you are along the same lines I would consider, essentially I came to the same conclusion that the UsernameTokenProcessor within WSS4J is making an unsuitable assumption that you can obtain a users password.
Regarding how all of this would fit with the application server there are a couple of other things to consider, when integrating with the application server we are really looking to pass as much back to the application server provided containers as possible and not just have an independent authentication / authorization process within the web services stack.
The approach of having two interceptors (one for authentication and one for authorization) is probably the biggest part of this problem already solved.
Where this becomes really apparent is where endpoints are deployed as EJB3 session beans, in this case the container can already be configured to perform authentication and authorization - as a deployed session bean can potentially be called from multiple different clients it makes sense for the authorization checks to remain with the bean.
A second requirement would be related to endpoints deployed as POJOs - although these do not have any container security before the invocation there is still the potential that the implementations will call other secured resources so any identity would need to be propagated for these calls.
The point of these two comments really is to highlight that this is not just a case of obtaining a Subject from whatever app server you are running in but actually associating the users identity with the request so that is propagates for further calls within the application server. Using the APIs suggested from Anil should help with this so this is just something to keep in mind.
A final feature related to this that I know there is user demand for would be the ability to annotate the POJO endpoints with the same role annotations as used on EJB3 sesstion beans - we were unable to do this for our Native implementation of this as we had to support JAX-RPC as well as JAX-WS but as this would be JAX-WS only this could be an option and may help simplify the role configuration.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536495#536495]
Start a new discussion in JBoss Web Services Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [jBPM] - How to configure 4.3 the right way?
by Maciej Swiderski
Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion
"How to configure 4.3 the right way?"
To view the discussion, visit: http://community.jboss.org/message/536480#536480
--------------------------------------------------------------
Hi,
I have created very basic cache configuration for jbpm 4.3 in jbpm.hibernate.cfg.xml, as follows:
<property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>
<property name="hibernate.cache.use_second_level_cache">true</property>
<property name="hibernate.cache.use_query_cache">true</property>
<class-cache \class="org.jbpm.pvm.internal.repository.DeploymentImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.repository.DeploymentProperty" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.id.PropertyImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.model.ExecutionImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.job.JobImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.task.TaskImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.task.ParticipationImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.task.SwimlaneImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.identity.impl.UserImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.identity.impl.MembershipImpl" usage="nonstrict-read-write"/>
<class-cache \class="org.jbpm.pvm.internal.identity.impl.GroupImpl" usage="nonstrict-read-write"/>
P.S. Please remove \ from class attribute.
By doing that execution of 50 process instances took about 150 - 200 ms less than without it.
Perhaps you could give it a try on your test to see if that makes any difference.
Cheers
Maciej
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/536480#536480]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years