September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2174) Clustered session proxies load balance across different bindings on the same server

by Brian Stansberry (JIRA)

Clustered session proxies load balance across different bindings on the same server ----------------------------------------------------------------------------------- Key: EJBTHREE-2174 URL: https://jira.jboss.org/browse/EJBTHREE-2174 Project: EJB 3.0 Issue Type: Bug Components: Clustering Reporter: Brian Stansberry With a bean config like this: <session> <ejb-name>HelloBean</ejb-name> <remote-binding> <jndi-name>HelloBean/http</jndi-name> <client-bind-url> http://${jboss.bind.address}:8080/unified-invoker/Ejb3ServerInvokerServlet/?return-exception=true </client-bind-url> </remote-binding> <remote-binding> <jndi-name>HelloBean/https</jndi-name> <client-bind-url> https://${jboss.bind.address}:8443/unified-invoker/SSLEjb3ServerInvokerServlet/?return-exception=true </client-bind-url> </remote-binding> </session> and client code like this: 51 Properties p = new Properties(); 52 p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.HttpNamingContextFactory"); 53 p.put(Context.PROVIDER_URL, "http://localhost:8080/unified-invoker/JNDIFactory/?return-exception=true"); 54 p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); 55 Context ctx = new InitialContext(p); 56 57 //Hello bean = (Hello) ctx.lookup("ProxyFactory/helloWorld/HelloBean/HelloBean/http"); 58 Object o = ctx.lookup("HelloBean/http"); there is sometimes an attempt to connect via the HTTPS URL, which indicates the clustered proxy sees the https binding as a 2nd target. Stack trace showing the attempt to use HTTPS: test: [java] 17:20:02,578 ERROR [HTTPClientInvoker] Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url. Leads to: [java] javax.naming.NamingException: Could not dereference object [Root exception is java.lang.RuntimeException: cluster invocation failed, last exception was: ] [java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1504) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) [java] at javax.naming.InitialContext.lookup(InitialContext.java:392) [java] at com.jboss.examples.ejb3.client.Client.testHTTPHA(Client.java:58) [java] at com.jboss.examples.ejb3.client.Client.main(Client.java:25) [java] Caused by: java.lang.RuntimeException: cluster invocation failed, last exception was: [java] at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:173) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:104) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.aspects.remoting.ClusteredPojiProxy.invoke(ClusteredPojiProxy.java:79) [java] at $Proxy1.createProxyBusiness(Unknown Source) [java] at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129) [java] at org.jboss.ejb3.proxy.clustered.objectfactory.session.SessionClusteredProxyObjectFactory.getProxy(SessionClusteredProxyObjectFactory.java:89) [java] at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:161) [java] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) [java] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479) [java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496) [java] ... 5 more [java] Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:250) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:162) [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167) [java] at org.jboss.remoting.Client.invoke(Client.java:1927) [java] at org.jboss.remoting.Client.invoke(Client.java:770) [java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:84) [java] ... 16 more [java] Caused by: java.net.ConnectException: Connection refused [java] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [java] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [java] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [java] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [java] at java.net.Socket.connect(Socket.java:529) [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550) [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:158) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) [java] at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272) [java] at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:801) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) [java] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:904) [java] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.getOutputStream(HTTPClientInvoker.java:1245) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:346) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:232) [java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:162) [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167) [java] at org.jboss.remoting.Client.invoke(Client.java:1927) [java] at org.jboss.remoting.Client.invoke(Client.java:770) [java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:84) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.ejb3.proxy.impl.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:104) [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [java] at org.jboss.aspects.remoting.ClusteredPojiProxy.invoke(ClusteredPojiProxy.java:79) [java] at $Proxy1.createProxyBusiness(Unknown Source) [java] at org.jboss.ejb3.proxy.impl.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:129) [java] at org.jboss.ejb3.proxy.clustered.objectfactory.session.SessionClusteredProxyObjectFactory.getProxy(SessionClusteredProxyObjectFactory.java:89) [java] at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:161) [java] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) [java] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479) [java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822) [java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) [java] at javax.naming.InitialContext.lookup(InitialContext.java:392) [java] at com.jboss.examples.ejb3.client.Client.testHTTPHA(Client.java:58) [java] at com.jboss.examples.ejb3.client.Client.main(Client.java:25) [java] at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) [java] ... 18 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8439) Create JMX Subsystem

by John Bailey (JIRA)

Create JMX Subsystem -------------------- Key: JBAS-8439 URL: https://jira.jboss.org/browse/JBAS-8439 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Bailey Assignee: John Bailey Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8437) Move SAR deployment into its own subsystem

by John Bailey (JIRA)

Move SAR deployment into its own subsystem ------------------------------------------ Key: JBAS-8437 URL: https://jira.jboss.org/browse/JBAS-8437 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Reporter: John Bailey Assignee: John Bailey Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8441) Update SAR deployer to register mbeans using the JMX Subsystem

by John Bailey (JIRA)

Update SAR deployer to register mbeans using the JMX Subsystem -------------------------------------------------------------- Key: JBAS-8441 URL: https://jira.jboss.org/browse/JBAS-8441 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Bailey Assignee: John Bailey Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8442) Property names in ServerEnvironment are incorrect

by Brian Stansberry (JIRA)

Property names in ServerEnvironment are incorrect ------------------------------------------------- Key: JBAS-8442 URL: https://jira.jboss.org/browse/JBAS-8442 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.0.0.M1 ServerEnvironment was cut-and-pasted from ServerManagerEnvironment and then I forgot to rename the accessor methods from getDomainXXX to getServerXXX. The internal fields and constant names were fixed, just the accessor method names need correction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2171) Incorrect timeout date calculated when schedule has a combination of non-wildcard day-of-week and non-wildcard day-of-month

by jaikiran pai (JIRA)

Incorrect timeout date calculated when schedule has a combination of non-wildcard day-of-week and non-wildcard day-of-month --------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2171 URL: https://jira.jboss.org/browse/EJBTHREE-2171 Project: EJB 3.0 Issue Type: Bug Components: timerservice-mk2 Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec (section 18.2.1.2) says this: <quote> If dayOfMonth has a non-wildcard value and dayOfWeek has a non-wildcard value, then either the dayOfMonth field or the dayOfWeek field must match the current day (even though the other of the two fields need not match the current day). </quote> However, we currently "and" (instead of "or") the day-of-month and "day-of-week" for non-wildcard values during timeout computation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2172) Integrate singleton with newly released reloaded-naming

by jaikiran pai (JIRA)

Integrate singleton with newly released reloaded-naming ------------------------------------------------------- Key: EJBTHREE-2172 URL: https://jira.jboss.org/browse/EJBTHREE-2172 Project: EJB 3.0 Issue Type: Task Components: singleton Reporter: jaikiran pai Assignee: jaikiran pai There have been API changes in reloaded-naming. These need to be incorporated in singleton. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Moved: (JBBUILD-649) Cannot browse org.hibernate index in Sonatype Nexus releases repository

by Mark Newton (JIRA)

[ https://jira.jboss.org/browse/JBBUILD-649?page=com.atlassian.jira.plugin.... ] Mark Newton moved ORG-688 to JBBUILD-649: ----------------------------------------- Project: JBoss Build System (was: jboss.org) Key: JBBUILD-649 (was: ORG-688) Component/s: Artifact Repositories (was: Content) > Cannot browse org.hibernate index in Sonatype Nexus releases repository > ----------------------------------------------------------------------- > > Key: JBBUILD-649 > URL: https://jira.jboss.org/browse/JBBUILD-649 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Environment: Windows XP, > Firefox 3.6.6 > Reporter: Alex Jboss > > 1. Navigate to `https://repository.jboss.org/nexus/index.html#view-repositories;releases` > 2. Click `Browse Index` tab > 3. Expand org > 4. Try to expand org/hibernate > BUG >> > System shows a wait cursor next to `hibernate` for a while, after which it shows an error message: > Nexus returned an error: ERROR -1: transaction aborted. > Out of curiosity I tried to expand some other directories and some of them display a similar problem ( drools, jboss ), and others work ( e.g. hornetq ) > I suspect that repository's index is corrupt. The other tell-tail sign of it is that proxy repository on my local nexus can only see hibernate-core-3.5.2-Final, although the latest version is hibernate-core-3.5.3-Final ( which is what I am after ), and which is clearly available in your repository. You can verify this fact by clicking 'Browse Storage' tab and navigating to /org/hibernate/hibernate-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2693) More sophisticated way of deploying archives to Drools guvnor

by Geoffrey De Smet (JIRA)

More sophisticated way of deploying archives to Drools guvnor ------------------------------------------------------------- Key: JBRULES-2693 URL: https://jira.jboss.org/browse/JBRULES-2693 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: FUTURE - the .ddj would have a meta-inf that tells you the original url for that artifact you are loading - we don't want to lose the link between loading the artifact and where it was published from and which version. - in general this comes under making an enterprise class flexible deployment architecture - some of the more complex stuff comes from "diffs" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2704) Guvnor pom depends on gwt-diagrams 0.2-RC00, but ant gwt compile build uses a different version (0.1) of gwt-diagrams

by Geoffrey De Smet (JIRA)

Guvnor pom depends on gwt-diagrams 0.2-RC00, but ant gwt compile build uses a different version (0.1) of gwt-diagrams --------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2704 URL: https://jira.jboss.org/browse/JBRULES-2704 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 5.2.0.M1 Working on getting rid of the ant gwt compile build and it's own dependency list. Having a problem with: http://code.google.com/p/google-web-toolkit/issues/detail?id=4479 Very maybe this gwt-diagrams version difference is causing it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010