Aslak Knutsen [http://community.jboss.org/people/aslak] created the discussion
Re: Intégration jbpm 4.4 jsf
To view the discussion, visit: http://community.jboss.org/message/617596#617596
--
I think this is better suited for the JBPM
Aslak Knutsen [http://community.jboss.org/people/aslak] created the discussion
Re: Intégration jbpm 4.4 jsf
To view the discussion, visit: http://community.jboss.org/message/617629#617629
--
It's already moved
for a bridge like application.
The Bisocket config works like a charm as far as this issue goes..
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4105461#4105461
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4105461
Sorry for the slow response on this, but I've finally gotten the time to look
more into the issue.
It's the same issue mentioned in this post:
http://www.jboss.org/index.html?module=bbop=viewtopict=119302
A solution to the problem is to add Persistence to the XMBean desc and generate
a
The actually issue is not the combination of two providers on the same server,
but rather using the jboss.messaging.callback.bind.port variable at all in the
application server. I see the same behavior on a single local provider.
When deploying a MDB it first creates a connection to the DLQ,
should be able to supply this kinda information by setting properties
on the JMSProviderAdaptor or something similar.
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100270#4100270
Reply to the post :
http://www.jboss.com/index.html?module=bbop
happened.
1.
Shouldn't the MessageSucker inherit the connections credentials,
or bypass normal security all together being an internal service?
2.
Shouldn't this fail back to the client,
notifying him that we have failed to guaranty his response?
-aslak-
| 09:19:47,094 ERROR
As far as the JMS 1.1 Specification goes on the topic:
3.4.3 JMSMessageID
The JMSMessageID header field contains a value that uniquely identifies
each
message sent by a provider.
...
A JMSMessageID is a String value which
Actually, the ActiveMQMessage converts the JbossDestination to a
ActiveMQDestination. Then the ActiveMQMessage is converted to a JbossMessage
with the ActiveMQDestination still set, hench the ClassCastException.
:o)
View the original post :
Try sourceforge:
http://sourceforge.net/project/showfiles.php?group_id=22866package_id=157261
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072899#4072899
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072899
in
ServerConnectionEndpoint.sendMessage:
JBossDestination dest = (JBossDestination)msg.getJMSDestination();
Any ideas?
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072340#4072340
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode
In this case, the 1.3.0 behavior seems to be more correct.
Since the foreign destination is not known to Jboss there is no need to set it.
The producer has the correct JbossDestination, but it is set on the message
before it is converted to a JbossMessage, meaning it ends up being ignored.
constraint on message id.
Around line 1671, it tries to insert the MessageRef before inserting the
Message. Changing the order seem to work..
.. not sure what other errors I might have introduced with these changes but..
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop
I have setup a JbossMessaging Bridge to listen to a ActiveMQ queue via a
ActiveMQ JMSProvider configured on Jboss.
The Bridge reads the sourceDestination messages from ActiveMQ fine, it's
sending this ActiveMQ Message object to the targetProducer/targetDestination
that is the problem.
Is
Yes, I'm running CR1.
When is CR2 planed?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4072495#4072495
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072495
___
jboss-user
| connection-factories
|
| mbean code=org.jboss.jms.jndi.JMSProviderLoader
| name=jboss.mq:service=JMSProviderLoader,name=ActiveMQJMSProvider
| attribute name=ProviderNameActiveMQJMSProvider/attribute
| attribute name=ProviderAdapterClass
|
timfox wrote : aslak wrote :
| |
| | INSERT_MESSAGE_REF is inserted before INSERT_MESSAGE.
| |
|
| I guess you must be using CR1, this is fixed in CR2
Is the database fix not commited?
I can't see it in: https://svn.jboss.org/repos/messaging/trunk
View the original post
This might be the wrong forum but..
I've had a look at the jboss 4.2.0 code and as far as I can see the DLQ handler
never receives the exception,
it only receives the Message again and has to figure out if it should be dlq'ed
or not..
I haven't had a chance to look at Messaging 1.4.0.CR1
rollback
Am I missing something, or is this a feature request?
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068720#4068720
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068720
works:
/opt/jboss-4.2.0.GA/server/messaging/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
The client lib shouldn't have to depend directly on a server deployed lib..
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4058076#4058076
Reply to the post
JbossTemporaryQueue/Topic or JbossTopic/Queue to jndi..
Any thoughts?
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4054389#4054389
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4054389
):
if (dest.isTemporary()) {
if(dest.getClientConnectionId != clientConnection.id)
throw SecurityException
}
I havn't found the correct semantics yet.
-aslak-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4054542#4054542
22 matches
Mail list logo
