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

[Design of POJO Server] - Re: Deployers in AS

by adrian＠jboss.org

"ALRubinger" wrote : "ALRubinger" wrote : Back to the main question of the Thread: What is preventing us from moving the EJB / Metadata Deployers out of the AS Source tree... | | Aside from the pieces Scott has identified as needing abstraction and extraction. I just want to hear "Yes, this is possible with some work, and wouldn't violate a central tenant of the AS Structuring Rules." | Yes, that's possible. But that's a minor task compared with making sure the cart doesn't lead the horse, i.e. the EJB3 runtime doesn't depend upon the deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151711#4151711 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151711

17 years, 10 months

1
0
0 / 0

[Design of JBoss Web Services] - [JBWS-2187] javax.xml.ws.Service handlers and thread safety.

by darran.lofthouse＠jboss.com

I am currently working on the following Jira issue: - http://jira.jboss.com/jira/browse/JBWS-2187 I wanted to bring it up here to confirm the intended behaviour. In the past we have always recommended that the Service is thread safe and should be used as the factory for the Port instances and then the Port instances should only be used by one thread at a time. Personally my interpretation is that any action on a Port instance should not affect any of the other Port instances so if the configuration is set on one instance it should be local to that instance and not alter the others or be retained by the Service. The Service should always retain it's base configuration that should always be the base for new Port instances but the new instances can always override this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151707#4151707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151707

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Support marshaling or unmarshaling the soap message using

by jim.ma

This feature will help use make publishing the esb services as web services more easily . Publishing esb services as web services can be achieved through two steps: 1. publish contract info for the esb service . 2. convert the request soap message to a esb aware message and deliver it ActionPipeLineProcess to process, finally convert the response esb message to soap message and send back . For 1 step , we can use pojo classes to give the in/out and fault information for the esb service, for example <actions inClass="com.foo.Request" outClass="com.foo.Response", faultClass="com.foo.Fault" jaxbAnnoIntro="anno.xml"> | </actons> Use JAXB and JAXB Annotaion Introduction , we can generate the schema files from these classes defined in actions attributes. Use these schema and esb service name and category information , wsdl contract can be constructed. For 2 step: Use the JAXB and JAXB Annotation Introduction , we also can easily unmarshal the soap message as a request object and put it in Esb message payload to run the ActionPipeLineProcessor. Does XStream can do this also ? Appreciated your thoughts and comments . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151701#4151701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151701

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Proxy Remote Call Handling

by alesj

"ALRubinger" wrote : How are we intending on handling a remote call using the new Proxy component? Check how we handle remote invocation of KernelBus here: - http://anonsvn.jboss.org/repos/jbossas/trunk/profileservice/src/main/org/... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151694#4151694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151694

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Proxy Remote Call Handling

by ALRubinger

How are we intending on handling a remote call using the new Proxy component? Currently, I've got in StatelessProxyInvocationHandler the following: KernelBus bus = getKernel().getBus(); | bus.invoke("mcNameOfContainer","invoke",arguments); The problem here is that this assumes the Kernel is accessible via the local JVM, and in a remote invocation this is not the case. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151647#4151647 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151647

17 years, 10 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler 2

by jbn1v

I read the README.txt from which I could figure out how to get a snapshot, but it didn't answer any of the questions in my post. Could you update it to describe what parameters, if any, the commands to the client utility take, what the various snapshot commands do, and what the column headings in the snapshot reports are? One other thing I have noticed is .jps files showing up. What are they for? Can they be deleted? Thanks again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151633#4151633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151633

17 years, 10 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: [2.0.Beta1] jboss-profiler.properties/host doing nothing

by jesper.pedersen

The host binding name when running inside the application server is located in jboss-profiler.sar/META-INF/jboss-service.xml. But you make a point - so we will look into this for the Beta2 release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151627#4151627 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151627

17 years, 10 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler 2

by jesper.pedersen

The current documentation is the README.txt file in the distribution. We are working on a web ui for the GA release. Hope this helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151626#4151626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151626

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Race condition in OrderedExecutorFactory

by timfox

I've had to revert the latest change to OrderedExecutorFactory that altered it to use a LinkedBlockingQueue - this change introduced a race condition which meant that Runnables didn't get executed. This resulted in messages appearing to silently "disappear". I have reverted back the old version for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151625#4151625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151625

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Clients Hanging...

by timfox

"clebert.suconic(a)jboss.com" wrote : When I run the perfSender (without perfListener) it's very common the client hanging without an answer. | | The client keeps waiting on this condition, as if a message was dropped on the wire. | | [java] "main" prio=1 tid=0x000000004011d620 nid=0xa70 in Object.wait() [0x00007fff4bbc1000..0x00007fff4bbc2190] | | [java] at java.lang.Object.wait(Native Method) | | [java] - waiting on <0x00007f693877a5f0> (a org.jboss.messaging.core.client.impl.RemotingConnectionImpl$ResponseHandler) | | [java] at org.jboss.messaging.core.client.impl.RemotingConnectionImpl$ResponseHandler.waitForResponse(RemotingConnectionImpl.java:276) | | [java] - locked <0x00007f693877a5f0> (a org.jboss.messaging.core.client.impl.RemotingConnectionImpl$ResponseHandler) | | [java] at org.jboss.messaging.core.client.impl.RemotingConnectionImpl.sendBlocking(RemotingConnectionImpl.java:167) | | [java] at org.jboss.messaging.core.client.impl.ClientSessionImpl.close(ClientSessionImpl.java:485) | | [java] - locked <0x00007f691bbc12d0> (a org.jboss.messaging.core.client.impl.ClientSessionImpl) | | [java] at org.jboss.messaging.core.client.impl.ClientConnectionImpl.closeChildren(ClientConnectionImpl.java:222) | | [java] at org.jboss.messaging.core.client.impl.ClientConnectionImpl.close(ClientConnectionImpl.java:163) | | [java] - locked <0x00007f691bbc1490> (a org.jboss.messaging.core.client.impl.ClientConnectionImpl) | | [java] at org.jboss.messaging.jms.client.JBossConnection.close(JBossConnection.java:219) | | [java] at org.jboss.jms.example.PerfExample.runSender(PerfExample.java:137) | | [java] at org.jboss.jms.example.PerfExample.main(PerfExample.java:74) | | [java] | | | | This happens on Persistent or NonPersistent messages. Allthough on NonPersistent messages it would happen more frequently. | | Any idea why? | | | I may do some research on this later (maybe monday). But maybe this is known issue. When you close, the close is sent blocking and and will be ordered against any non blocking prior invocations, so all the sends need to be processed before close completes. If this takes longer than the block timeout it will timeout. Try increasing the timout. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151614#4151614 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151614

17 years, 10 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 May 2008