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

[JBoss Web Services Development] - Re: Keep alive doesn't doesn't work for closed TCP/IP connec

by alessio.soldano＠jboss.com

Fixed in ropalka branch. Richard, please merge along with all your stuff once you're done. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258219#4258219 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258219

16 years, 2 months

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by alexf83

It does make sense and that was what I was afraid of. Is there at least a way to know which user started a process? (so that we could use a java node after the start, to check who started the process and in case cancel it) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258186#4258186 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258186

16 years, 2 months

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by heiko.braun＠jboss.com

In that case you'd need to discuss such an authentication schema first the jBPM core team first, because if the engine doesn't have it build in, the console cannot make that up. It needs to be metadata associated with the process definition in the first place. Does that make sense? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258175#4258175 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258175

16 years, 2 months

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by alexf83

First of all thank you for your kind answer. We would like each user to log in (in the console) and be able to view and start only certain processes (the business processes he should have the right to start). A per group/per user authorization mechanism would be really great for our needs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258170#4258170 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258170

16 years, 2 months

1
0
0 / 0

[jBPM Development] - Re: (JBPM 4.1) Console process definition list

by heiko.braun＠jboss.com

it's currently not possible. we don't have any kind of authorization scheme in the console yet. but if you outline your use case further we can put it on the roadmap. Do you want restrict it to certain process definitions only, or in general? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258168#4258168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258168

16 years, 2 months

1
0
0 / 0

[JBoss XML Binding Development] - Re: XB profiling during the AS start-up

by bill.burke＠jboss.com

Because of marshalling, I don't understand why we can't use Sun's JAXB? WHy spend another year getting marshalling right? What *REAL* benefits will be obtained? Also, again, please try your benches against XJC generated Java code. I'd be interested how it compares. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258159#4258159 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258159

16 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Re: Keep alive doesn't doesn't work for closed TCP/IP connec

by richard.opalka＠jboss.com

Cross reference issue: JBWS-2753 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258145#4258145 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258145

16 years, 2 months

1
0
0 / 0

[jBPM Development] - (JBPM 4.1) Console process definition list

by alexf83

Hi, we are currently trying to understand if it's possible to limit the visibility of some process definitions (and consequently inhibit the ability to start the related process instances) only to certain users (in the JBoss web console process definition list). Any help you could offer would be greatly appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258139#4258139 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258139

16 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Re: Keep alive doesn't doesn't work for closed TCP/IP connec

by richard.opalka＠jboss.com

Steps to reproduce the issue: svn checkout the following branches: * spi/branches/ropalka * common/branches/ropalka * framework/branches/ropalka * container/jboss50/branches/ropalka * stack/native/branches/ropalka Do 'mvn clean install' for: * spi/branches/ropalka * common/branches/ropalka * framework/branches/ropalka * container/jboss50/branches/ropalka Comment out the following line in org.jboss.test.ws.jaxws.endpoint.jse.UsecasesTestCase.setUp(): System.setProperty(Constants.HTTP_KEEP_ALIVE, Boolean.FALSE.toString()); Run the test: mvn -Ptestsuite,hudson,jboss510 -Dtest=**/jaxws/endpoint/jse/UsecasesTestCase test View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258138#4258138 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258138

16 years, 2 months

1
0
0 / 0

[JBoss Web Services Development] - Keep alive doesn't doesn't work for closed TCP/IP connection

by richard.opalka＠jboss.com

My usecase: I'm using JBossWS Netty client (via JAX-WS proxy API) with keep-alive feature enabled (this is the default). When remote http server goes down and up again all lately used cached connections on client side will fail with the following exception: | java.io.IOException: Could not transmit message">javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message | at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:392) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | at $Proxy13.echo(Unknown Source) | at org.jboss.test.ws.jaxws.endpoint.jse.UsecasesTestCase.invokeEndpoint1(UsecasesTestCase.java:128) | at org.jboss.test.ws.jaxws.endpoint.jse.UsecasesTestCase.testTwoPortsAndLongPaths(UsecasesTestCase.java:86) | Caused by: java.io.IOException: Could not transmit message | at org.jboss.ws.core.client.transport.NettyClient.invoke(NettyClient.java:194) | at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:150) | at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:69) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:344) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290) | ... 31 more | Caused by: java.util.concurrent.ExecutionException: java.nio.channels.ClosedChannelException | at org.jboss.ws.core.client.transport.WSResponseHandler$FutureResult.get(WSResponseHandler.java:178) | at org.jboss.ws.core.client.transport.WSResponseHandler$FutureResult.get(WSResponseHandler.java:113) | at org.jboss.ws.core.client.transport.NettyClient.invoke(NettyClient.java:156) | ... 35 more | Caused by: java.nio.channels.ClosedChannelException | at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:624) | at org.jboss.netty.channel.socket.nio.NioWorker.write(NioWorker.java:353) | at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:124) | at org.jboss.netty.channel.Channels.write(Channels.java:889) | at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:76) | at org.jboss.netty.channel.Channels.write(Channels.java:869) | at org.jboss.netty.channel.Channels.write(Channels.java:818) | at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:236) | at org.jboss.ws.core.client.transport.NettyTransportOutputStream.close(NettyTransportOutputStream.java:142) | at org.jboss.ws.core.client.transport.NettyClient.writeRequest(NettyClient.java:240) | at org.jboss.ws.core.client.transport.NettyClient.invoke(NettyClient.java:147) | ... 35 more | Our client side Netty connections cache have to implement algorithm that will detect, if cached connection is still alive (the one going to be returned to client). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258137#4258137 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258137

16 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2009