July 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - WLS to jBoss Messaging Bridge Configuration

by MrGurgeh

I'm in the process of setting up a WLS Messaging bridge between JBM and WLS JMS. Unfortunately, it seems that I cannot get this working, with WLS, at best, receiving the following exception -------------- Linked Exception 2 ------------ javax.jms.InvalidDestinationException: Destination cannot be foreign at org.jboss.jms.message.JBossMessage.setJMSDestination(JBossMessage.java:454) at org.jboss.jms.message.MessageProxy.setJMSDestination(MessageProxy.java:198) at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:427) at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186) at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:699) at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80) at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:645) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144) at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:642) at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:140) at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149) at $Proxy8.send(Unknown Source) at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1409) at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:927) at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:1005) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170) It seems to me that this is a jBoss excpetion, but I don't fully understand what it is doing - something about testing JMS Destination names? I was wondering if anyone has attempted this before and had some insight into this? The WLS version that I'm using is WLS 8.1 sp6 and the JBM version is 1.4.0. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164701#4164701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164701

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Scoping of war/jar file embedded in sar service archives

by adrian＠jboss.org

The reason for not doing it in the structure determination is that we don't know the classloading rules until much later. Parsing jboss-classloading.xml in the structure deployers is not an option because the rules can come from legacy deployment descriptors and anybody could write their own deployer to create or modify the classloading metadata in an ad hoc anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164697#4164697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164697

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Scoping of war/jar file embedded in sar service archives

by adrian＠jboss.org

http://jira.jboss.com/jira/browse/JBDEPLOY-59 Actually, I think the StructureDeployer is probably not the correct place to add this behavour? The issue is that we now allow greater control of what/how subdeployment classloaders get constructed. Even to the extent that a subdeployment classloader may not be able to see the parent deployment classloader. e.g. top-level: domain=foo parent=DefaultDomain sub-deployment: domain=bar parent=DefaultDomain Although, I'm not sure somebody would really want to do the above :-) It would mean that sub-deployment's classloaders needs the manifest entry even though it is already included in the top-level. So I think the correct place to put this code would be in the usage of ClassPathVisitor to "weed out" duplicates in sub-deployment classloader that are already in one of the parent classloaders (if the parent deployment's classloader is really a parent of the sub-deployment). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164696#4164696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164696

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by mircea.markus

IMHO this *might* be useful and we should add it only if there are explicit requirements from users for it. This is a public API we want to keep as simple/small as possible. It should also do the job, of course :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164679#4164679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164679

17 years, 8 months

1
0
0 / 0

[Design of Clustering on JBoss] - jboss clustering shell script for rhel5

by suvra82002

Hi, I need a help... I wil explain the setup 1st....I need to install rhel5 images on some linux boxes.The requirement is that ones the system boots Jboss shud be up and running.Yups.....I have the init script with meto do that..... But the requirement is to write a script for Jboss clustering so that when the system is booted clustering on jboss is setup and up and running. So i shud have the init script for service and one more script for automating the cluster in all the nodes.....(may be 2-4 nodes cluster) Pls if any one has such script or knows some pdf or links kindly send me asap...... i need it urgently.... Regards Suvra Chakraborty View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164674#4164674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164674

17 years, 8 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: JBAS-4960 - broken merge

by suvra82002

Hi, I need a help... I wil explain the setup 1st....I need to install rhel5 images on some linux boxes.The requirement is that ones the system boots Jboss shud be up and running.Yups.....I have the init script with meto do that..... But the requirement is to write a script for Jboss clustering so that when the system is booted clustering on jboss is setup and up and running. So i shud have the init script for service and one more script for automating the cluster in all the nodes.....(may be 2-4 nodes cluster) Pls if any one has such script or knows some pdf or links kindly send me asap...... i need it urgently.... Regards Suvra Chakraborty View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164671#4164671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164671

17 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining the API Mission

by jbarrez

Wow Tom, seems like vacation has recharged your batteries ;-) You do have some valid points though, and if all the ideas in this thread become reality...it will simply rock View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164668#4164668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164668

17 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining the API Mission

by tom.baeyens＠jboss.com

anonymous wrote : How is the correctness of the API verified? That's what I'm now doing on the PVM. I don't think that is possible without actually building all the different patterns/features. Without enough coverage of the patterns implemented, you cannot know whether the runtime datastructure is rich and simple enough to handle all the cases. That describes the work I have been doing in PVM. This iterative incremental approach cannot start from zero. The first iteration of the PVM API will definitely have to cover jPDL 3 concepts and feature capabilities. They might not all have to be implemented in full, but for sure, the runtime data structure must be able to handle all forms of process concurrency that we have in mind, sub process execution, timers and asynchronous continuations. All of those have a big impact on the API and you can't build a stable subset if you don't have proof on how you're going to deal with those features later on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164661#4164661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164661

17 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining the API Mission

by tom.baeyens＠jboss.com

anonymous wrote : What is expected to be stable, what is not? API is one part. DB and process XML are two other very important aspects of stability/migration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164660#4164660 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164660

17 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Defining the API Mission

by tom.baeyens＠jboss.com

anonymous wrote : There are a number of BPMN editors available that allow you to draw BPMN conform process models. | | * SOA Tools BPMN Editor | * eBPMN | * Intalio Designer | We'll use the eclipse STP BPMN editor and add an export functionality to it. @see https://jira.jboss.com:8443/jira/browse/JBIDE-2237 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164659#4164659 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164659

17 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2008