February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3619) Upgrade JBoss Marshalling to 1.3.7.GA

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3619: --------------------------------- Summary: Upgrade JBoss Marshalling to 1.3.7.GA Key: AS7-3619 URL: https://issues.jboss.org/browse/AS7-3619 Project: Application Server 7 Issue Type: Component Upgrade Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.1.Final Needed to pull in JBMAR-128 fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3589) CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3589?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reopened AS7-3589: ----------------------------------- > CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-3589 > URL: https://issues.jboss.org/browse/AS7-3589 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.0.CR1b > Environment: RHEL 6, JBoss EAP 6 DR12 > Reporter: Serge Emmanuel Pagop > Assignee: Paul Ferraro > Fix For: 7.1.1.Final > > > I create multiple IP Addresses on a single NIC for this use case. > Use-Case: Clustering in Standalone mode with 2 nodes installed in different Datacenter > Action: deployment of a distributable web application in the node 1 from datacenter 1 > Expectation: consequence should be also the deployment of the distributable application in the running node2 from datacenter 2 > Result: no deployment of application in the running node2 from datacenter2 > Info: find the web application example as attach > All the steps: > 1) from datacenter 1 > + Start node1 in Standalone mode from datacenter with IP 192.168.178.31 > $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.31 -bmanagement=192.168.178.31 -Djboss.node.name=node1 > 2)from datacenter 2 > + Start node2 in standalone mode from datacenter with IP 192.168.178.32 > $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.32 -bmanagement=192.168.178.32 -Djboss.node.name=node2 > 3)from datacenter 1 > + deploy a distributable application in the running standalone node1 - copy the application into the directory $EAP6_HOME/standalone/deployments > during the deployment server log shows this infos: > - Start Server log infos > 22:26:28,506 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "version3.war" > 22:26:29,285 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.DatagramSocket@40993028 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) > 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.DatagramSocket@40993028 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) > 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.MulticastSocket@928b33a was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) > 22:26:29,288 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.MulticastSocket@928b33a was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) > 22:26:29,303 INFO [stdout] (MSC service thread 1-1) > 22:26:29,304 INFO [stdout] (MSC service thread 1-1) ------------------------------------------------------------------- > 22:26:29,304 INFO [stdout] (MSC service thread 1-1) GMS: address=node1/web, cluster=web, physical address=192.168.178.31:55200 > 22:26:29,304 INFO [stdout] (MSC service thread 1-1) ------------------------------------------------------------------- > 22:26:31,359 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-4) JBAS010207: Number of cluster members: 1 > 22:26:31,781 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually. > 22:26:31,971 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups Channel > 22:26:31,972 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-4) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@6b7fb9d5) but now it is being overridden > 22:26:31,972 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view: [node1/web|0] [node1/web] > 22:26:31,973 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Cache local address is node1/web, physical addresses are [192.168.178.31:55200] > 22:26:31,976 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1 > 22:26:32,077 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server. > 22:26:32,145 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server. > 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010301: Started registry cache from web container > 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010301: Started repl cache from web container > 22:26:32,347 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /version3 > 22:26:32,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "version3.war" > - End Server log infos > 4) From datacenter 2 > No action deployment in node2 > - Start Server log info > ... > 22:25:36,179 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /192.168.178.32:9999 > 22:25:36,233 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /NotBackedUp/spagop/EAP6_TRAINING/my-labs/clustering/standalone-lab/node2/jboss-eap-6.0/standalone/deployments > 22:25:36,986 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 8096ms - Started 152 of 259 services (102 services are passive or on-demand) > - End Server log info -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3349) Data-source add allows adding data sources with non existing JDBC driver

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3349: ------------------------------------- Summary: Data-source add allows adding data sources with non existing JDBC driver Key: AS7-3349 URL: https://issues.jboss.org/browse/AS7-3349 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Alexey Loubyansky Data-source add allows adding data sources with non existing JDBC driver. The data-source add command should warn / prevent user from doing such thing. [standalone@localhost:9999 /] ls /subsystem=datasources/data-source ExampleDS [standalone@localhost:9999 /] data-source add --jndi-name=java:/TestDS --connection-url=jdbc:postgresql://localhost/test --driver-name=NON_EXISTING_DRIVER [standalone@localhost:9999 /] ls /subsystem=datasources/data-source ExampleDS java:/TestDS [standalone@localhost:9999 /] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
10
0 / 0

[JBoss JIRA] (AS7-1820) CLONE - CLI - provide description for "add-jms-cf " command with examples

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1820?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-1820. ----------------------------------- Fix Version/s: 7.1.0.Final (was: 7.1.1.Final) Resolution: Won't Fix > CLONE - CLI - provide description for "add-jms-cf " command with examples > ------------------------------------------------------------------------- > > Key: AS7-1820 > URL: https://issues.jboss.org/browse/AS7-1820 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.0.Final > > > Command "add-jms-cf" is missing description for all attributes. Could it be improved, please? Also examples of usages would be very helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3477) If DataSourceDisable fails the stopped/removed services need bringing back to their original state

by Kabir Khan (JIRA)

Kabir Khan created AS7-3477: ------------------------------- Summary: If DataSourceDisable fails the stopped/removed services need bringing back to their original state Key: AS7-3477 URL: https://issues.jboss.org/browse/AS7-3477 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Kabir Khan Assignee: Jesper Pedersen Priority: Critical Fix For: 7.1.0.Final In my https://github.com/kabir/jboss-as/commits/recycle_data_source_AS7_3085 branch I changed DataSourceDisable to use OperationContext.remove() meaning that the operation will be rolled back if other services have the DS injected. I've added a skeleton rollback handler which should reinstate the services to their original state if it does get rolled back. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-1820) CLONE - CLI - provide description for "add-jms-cf " command with examples

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1820?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reopened AS7-1820: ----------------------------------- > CLONE - CLI - provide description for "add-jms-cf " command with examples > ------------------------------------------------------------------------- > > Key: AS7-1820 > URL: https://issues.jboss.org/browse/AS7-1820 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.1.Final > > > Command "add-jms-cf" is missing description for all attributes. Could it be improved, please? Also examples of usages would be very helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-351) Implement the HttpService ontop of JBossWeb

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat updated AS7-351: ------------------------------- Attachment: registerServlet Here's a snippet for how the registerServlet method could be implemented inside a clone of the WelcomeContextService class. The WebServerService must be injected, as well as the desired host. The problems are: how to decide which host gets the thing, and which context too. Also, the spec doesn't do filters [but Felix does]. > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Web > Reporter: Thomas Diesler > Priority: Critical > Attachments: DefaultHttpContext.java, http-service-1.2.pdf, HttpServiceImpl.java, registerServlet, ResourceServlet.java > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-351) Implement the HttpService ontop of JBossWeb

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/AS7-351?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat updated AS7-351: ------------------------------- Attachment: HttpServiceImpl.java ResourceServlet.java DefaultHttpContext.java The code from Felix. > Implement the HttpService ontop of JBossWeb > ------------------------------------------- > > Key: AS7-351 > URL: https://issues.jboss.org/browse/AS7-351 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Web > Reporter: Thomas Diesler > Priority: Critical > Attachments: DefaultHttpContext.java, http-service-1.2.pdf, HttpServiceImpl.java, ResourceServlet.java > > > Resolving this issue consolidates the Http services that we ship and should replace pax-web with an HttpService implemenation based on JBossWeb. > RFC-66 (WebApp) support is also covered by this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3395) org.osgi.util.tracker.* classes duplicated in several bundles.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3395: --------------------------------- Summary: org.osgi.util.tracker.* classes duplicated in several bundles. Key: AS7-3395 URL: https://issues.jboss.org/browse/AS7-3395 Project: Application Server 7 Issue Type: Quality Risk Reporter: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-3215) EJB remote client context does not survive server restart

by Ivo Studensky (Created) (JIRA)

EJB remote client context does not survive server restart --------------------------------------------------------- Key: AS7-3215 URL: https://issues.jboss.org/browse/AS7-3215 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.0.CR1b Reporter: Ivo Studensky Assignee: Stuart Douglas Let's say we have an AS7 server with a stateless bean deployed at it and a client application which: 1. calls remotely the stateless bean 2. restarts the server 3. and calls the stateless bean again The first invocation of the stateless bean instantiates some static fields in EJBInvocationHandler, EJBClientContext, etc. like a new remote connection, an ejb receiver and so on, and returns a proxy for the bean and does the remote call successfully. But after the server is restarted, the second invocation of the stateless bean does not re-create/re-instantiate any new remote connection or other ejb client utils and fails with IllegalStateException: No EJB receiver available for handling ... combination. Note that EJBClientContext#ejbReceiverAssociations is empty at that time. See the following stacktrace snippet: {noformat} java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:crash,distinctname:] combination at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:344) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:92) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:83) at $Proxy22.test(Unknown Source) at org.jboss.as.test.jbossts.ejbclienttest.EJBClientCrashTestCase.testCrashOnClient(EJBClientCrashTestCase.java:103) {noformat} Test-case for this issue can be found here: https://github.com/istudens/jboss-as/compare/crash_rec_tests#diff-36 More detailed info how to reproduce the bug has been attached to 'Steps to Reproduce' of this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012