See comment below
(https://fisheye6.atlassian.com/browse/cxf/rt/rs/client/src/main/java/org/apache/cxf/jaxrs/client/WebClient.java?r=c1f3dd3d7051636da5b978866f5df48c8857cdc6)
/**
* Retrieves ClientConfiguration
* @param client proxy or http-centric Client
* @return
end of org.apache.openejb.config.AutoConfig#processActivationConfig:
if (javax.jms.Topic.equals(destinationType)) {
if (!properties.containsKey(clientId)) {
mdb.getActivationConfig().addProperty(clientId,
ejbDeployment.getDeploymentId());
}
if
FYI https://issues.apache.org/jira/browse/TOMEE-1552
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber
http://www.tomitribe.com
Warm greetings,
I am searching at the web looking Tomee clustering/HA documentation. But so
far could not found any convincing docs anywhere for beginner like me.
May I know where could I get documentation/article/book regards to Tomee
clustering?
--
View this message in context:
2015-04-20 20:49 GMT+02:00 sgjava sgj...@gmail.com:
The actual error:
at org.apache.cxf.jaxrs.client.WebClient.getConfig(WebClient.java:309)
is there anything here? seems swallowed.
--
View this message in context:
doesnt jms.clientId=myId works in the broker uri?
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber
http://www.tomitribe.com
2015-04-20
The id needs to be unique per
Connection from the same host to the same topic
http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
On 20 Apr 2015 15:02, Romain Manni-Bucau rmannibu...@gmail.com wrote:
doesnt jms.clientId=myId works in the broker uri?
Romain Manni-Bucau
Hi Romain!
The suggested workaround preloading the locking classes in a
ServletContextListener might work, but:
The thread deadlock happens only from time to time (about every 5th day).
Therefore identifying the locking classes is not possible as we observe a
different one every time.
Le 20 avr. 2015 13:51, tschuler thomas.schu...@opentext.com a écrit :
Hi all!
We got about ten thread dumps right now with threads in deadlock
situation.
The pattern is always the same (see attachment DeadlockThreadsPattern.txt
DeadlockThreadsPattern.txt
Traveling atm, but seem to recall that there's a way to override the
activemq generation. Focus search there.
http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
On 20 Apr 2015 13:51, hwaastad he...@waastad.org wrote:
Hi Andy and thx for answering.
I've started to realize that.
for MDB clientId can be set in activation specs. So in tomee you can:
- use a system property to set it
- use a placeholder in the activation config
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
Nope.
I've tried (and mind its case sensitive...) to modfy my resourceadadpter:
ServerUrl = tcp://a.b.c.d:61616?jms.clientID=myId
But no, still the MDB name is used.
br hw
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/JMS-Topic-MDB-tp4674499p4674509.html
Hi Andy and thx for answering.
I've started to realize that.
Made simple test using same code and maven profiles for different tomee
containers.
Switching clientId on MDB makes it work.
Now, how to solve the clientId issue?
I tried adding an clientId option in tomee.xml resourceadapter config,
Don't think that is strictly true about client id as it must be unique
from the same host
http://www.tomitribe.com - @AndyGeeDe - On a small screen device.
On 20 Apr 2015 09:50, hwaastad he...@waastad.org wrote:
Hi,
I've startet to play around clearing jcs cache on multiple installations
Hi,
I've startet to play around clearing jcs cache on multiple installations
using a JMS topic.
It's non-durable.
I've seen that clientId is only needed for durable topic.
However, I see that if I have two webapps deployed(having a MDB), activemq
complains about:
retry tomorrow, nightly build should have redeployed the snasphot and it
should contain the fix
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau |
Looks to me like it expects WebClient, not WebTarget:
/**
* Retieves ClientConfiguration
* @param client proxy or http-centric Client
* @return underlying ClientConfiguration instance
*/
public static ClientConfiguration getConfig(Object client) {
if (client
Hi,
pretty simple:
https://github.com/hwaastad/TomeeMdbTest.git
1. mvn tomee:run -Pnode1
2. mvn tomee:run -Pnode2
I've removed entries in system properties (which made it work)
br hw
--
View this message in context:
weird first if block should match it:
public static ClientConfiguration getConfig(Object client) {
if (client instanceof WebTargetImpl) {
client = ((WebTargetImpl)client).getWebClient();
}
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
hmm, i checked cxf 3.0.3 (our version in tomee 2.0.0-SNAPSHOT), what's your
version? Looks like a 2.x
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn
I'm using 2.0.0 SNAPSHOT. I was looking at WebClient from latest CXF
source, not in TomEE since I build from SNAPSHOT artifacts and not TomEE
source.
On Mon, Apr 20, 2015 at 1:48 PM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
hmm, i checked cxf 3.0.3 (our version in tomee 2.0.0-SNAPSHOT),
call org.apache.cxf.jaxrs.client.WebClient#getConfig on your client,
then org.apache.cxf.jaxrs.client.ClientConfiguration#getHttpConduit:
WebClient.getConduit(jaxrsClient).getHttpConduit()
Side note: when we'll upgrade cxf we'll get the feature you wanted:
I'll be damned
That was it!
This actually solves quite an issue I have.
I'm deploying topic MDBS in a network of brokers and as long as every MDB is
on a separate broker its working however when a failover situation occurs,
the clientid issue appears.
Thanks alot.
BTW, I've noticed that
java.lang.IllegalArgumentException: Not a valid Client
I guess it doesn't like javax.ws.rs.client.Client even though its
implementation is the CXF client?
// Set up web client
final Client client = ClientBuilder.newClient();
// Timeout not covered by client properties, so
java.lang.IllegalArgumentException: Not a valid Client
final HTTPConduit httpConduit =
WebClient.getConfig(client.target(url)).getHttpConduit();
client.target(url) returns
org.apache.cxf.jaxrs.client.spec.ClientImpl$WebTargetImpl
--
View this message in context:
Hi,
so would i t be possible to add an ejb-jar.xml and set clientid as an -D
variable?
ex: -Dmdb.clientid=whatever and in ejb-jar.xml have an
activation-config-property-value${mdb.clientid}/activation-config-property-value
...or something similar?
br hw
--
View this message in context:
to do it with a system property directly it should be:
ejbName.activation.property name = property value IIRC
Using this system property you don't need to do anything on
ejb-jar.xml/annotation level
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
My understanding it CXF does not unmarshall JSON and returns (XML uses
JAX-B for instance):
java.lang.ClassCastException:
sun.net.www.protocol.http.HttpURLConnection$HttpInputStream cannot be cast
to...
well if you call put(versionDto, VersionDto.class) and ensures your
webclient has a json provider then it works
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn
Assume it will be included in TomEE 1.7.2 snapshot.
Am I right?
From: Romain Manni-Bucau [via TomEE OpenEJB]
[mailto:ml-node+s979440n467451...@n4.nabble.com]
Sent: Montag, 20. April 2015 17:05
To: Thomas Schuler
Subject: Re: thread deadlock at URLClassLoaderFirst
retry tomorrow, nightly build
OK, I just switched back to the generic javax.ws.rs.client.Client and removed
the GlassFish stuff and it works.
final Client client = ClientBuilder.newClient();
final VersionDto versionDto = new VersionDto(xxx);
final VersionDto response =
yep
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber
http://www.tomitribe.com
2015-04-20 17:20 GMT+02:00 tschuler
32 matches
Mail list logo
