January 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Configuring ESB to be a multicast receiver to external s

by Kevin.Conner＠jboss.com

We do not have anything in the code base at present but it would be possible to add this. What are your requirements? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201283#4201283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201283

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - EJB 3.1 TimerService

by wolfc

For the EJB 3.1 TimerService there are two goals: 1. EJB 3.1 functionality 2. true clustering For the EJB 3.1 functionality refer to chapter 18 of the spec. Right now the timer service doesn't do real clustering. It's setup as a HA-singleton, which makes for an imbalanced cluster. The new timer service should also make use of a Hibernate backend. This to eliminate any problems with different databases and SQL schemas. It would be nice to have timers back on stateful objects. Since EJB 2.1 entities are eliminated, stateful beans become the obvious choice. (Note that this is in violation of the spec.) So in the end I would like to see two components: 1. a 'light' version that implements the spec 2. a 'heavy' version that extends it with clustering features Both components should be runnable (and testable) in a standalone environment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201257#4201257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201257

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: run-as-principal is missing in schema

by alex.loubyansky＠jboss.com

Nothing. Upgrade to metadata 1.0.0.CR13 should fix it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201253#4201253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201253

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Cannot run Hudson on AS5

by ALRubinger

I've updated https://www.jboss.org/community/docs/DOC-13233 to reflect the error and warn users. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201234#4201234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201234

17 years, 2 months

1
0
0 / 0

[Design of JBossCache] - when will we get org.jboss.util.NestedSQLException

by mudaykumarreddy

any suggestions about what to do , if we get below exeption ? need help (http-0.0.0.0-8080-Processor2:) SQLException org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )) ------ ------ ------- many exceptions ------ ------ ---- (http-0.0.0.0-8080-Processor2:) SystemException AxisFault View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201231#4201231 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201231

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Cannot run Hudson on AS5

by ALRubinger

@see https://hudson.dev.java.net/issues/show_bug.cgi?id=2831 This will stall our installation of new Hudson instances based on AS5 until resolved. The simple fix (ie. correcting the protocol assumptions) lead to errors elsewhere, so I need to spend more time digging. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201228#4201228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201228

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 2: Servlet Invoker

by ALRubinger

Thanks, will give a spin tomorrow. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201208#4201208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201208

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 2: Servlet Invoker

by ron.sigal＠jboss.com

For what it's worth, I just had a successful EJB2 invocation over the servlet transport. In jboss-service.xml I have <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:service=connector,transport=servlet" | display-name="Servlet transport Connector"> | <attribute name="Configuration"> | <config> | <invoker transport="servlet"> | <attribute name="dataType" isParam="true">invocation</attribute> | <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute> | <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute> | <attribute name="return-exception" isParam="true">true</attribute> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">8080</attribute> | <attribute name="path">unified-invoker/ServerInvokerServlet</attribute> | </invoker> | <handlers> | <handler subsystem="invoker">jboss:service=invoker,type=unified,transport=servlet</handler> | </handlers> | </config> | </attribute> | </mbean> | and in web.xml I have | <servlet> | <servlet-name>ServerInvokerServlet</servlet-name> | <description>The ServerInvokerServlet receives requests via HTTP protocol | from within a web container and passes it onto the ServletServerInvoker | for processing. | </description> | <servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class> |  | <init-param> | <param-name>locatorUrl</param-name> | <param-value> | <![CDATA[servlet://${jboss.bind.address}:8080/unified-invoker/ServerInvokerServlet/?dataType=invocation&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&return-exception=true&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]]> | </param-value> | <description>The servlet server invoker</description> | </init-param> | <load-on-startup>1</load-on-startup> | </servlet> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201207#4201207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201207

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Declaration and deployment of threads and thread pools i

by david.lloyd＠jboss.com

"alesj" wrote : ...And the MC part into deployers/deployers-impl. | (similar place where I put my -scanning.xml and -dependency.xml metadata) | Is this really the right place for adding a threads deployer? All the deployers that "do stuff" seem to be in deployers-vfs (that's where all the other SchemaResolverDeployers are), but this doesn't really seem like the right place either since they're all related to J2EE deployment unit types for the most part. This project might be the right place but maybe the threads deployer should be its own module? I don't think it fits in in deployers-impl, unless that module is *intended* for such general-purpose deployers and there just doesn't happen to be any yet... The most similar deployer to the ThreadsMetaData deployer I can think of is the ClassLoadingMetaData deployer, and that project lives completely separately. This suggests to me that perhaps jboss-threads ought to be a separate project after all. Also, What is there to gain by providing an interface-based view over metadata (like how it's done in org.jboss.deployers.spi.annotations)? I haven't done this in my project - partially because I don't see the benefit, and partially because implementing BeanMetaDataFactory on the root metadata object might complicate things. Am I missing out? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201192#4201192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201192

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 2: Servlet Invoker

by ALRubinger

Sorry Ron, I hadn't put a watch on this Thread until now. "ron.sigal(a)jboss.com" wrote : But there's something strange about your line numbers - they don't match what I see under https://svn.jboss.org/repos/jbossremoting/remoting2/tags/2.5.0.SP2 . Don't know what's going on there. The wrong line numbers may be due to that we had a version of ServletSocketInvoker in WEB-INF/classes of the test, and I'd copied from an older log. But after that issue was resolved, the problem I explained in the previous post persisted. Something's not lining up between the release JARs and what I can build from tags... "ron.sigal(a)jboss.com" wrote : So, for example, the ObjectName for the EJB2 servlet invoker I'm playing with right now is "jboss.remoting:dataType=invocation,host=127.0.0.1,marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller,port=8080,return-exception=true,service=invoker,transport=servlet,unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller". Just tried the ObjectName of that form from my JMX console; same IllegalArgumentException. "ron.sigal(a)jboss.com" wrote : By the way, I didn't even know there was a servlet test in the EJB3 test suite. I'll take a look at that. But not tonight. :) Great. We'll plan to move this out of EJB3 and into AS (as the EJB3 component responsibility ends with invoking upon the correct endpoint) once it's passing. For the time being I have this marked as a "known issue" to help us track true regressions. BTW we've got a Thread on this regression over here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201180 S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201181#4201181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201181

17 years, 2 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 January 2009