[JBoss JIRA] (AS7-3964) Running IPv6 clustering tests results in [UDP] failed sending message to cluster (69 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (72 bytes), cause: java.io.IOException: Network is unreachable
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3964:
-----------------------------------
Summary: Running IPv6 clustering tests results in [UDP] failed sending message to cluster (69 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (72 bytes), cause: java.io.IOException: Network is unreachable
Key: AS7-3964
URL: https://issues.jboss.org/browse/AS7-3964
Project: Application Server 7
Issue Type: Task
Components: Clustering, Test Suite
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 7.1.1.Final
Attachments: ipv6log.txt
Binding to IPv6 address is OK but multicast communication fails.
We need to figure out whats causing this, should be just missing configuration.
{noformat}
04:06:22,794 INFO [stdout] (pool-19-thread-1)
04:06:22,801 INFO [stdout] (pool-19-thread-1) -------------------------------------------------------------------
04:06:22,802 INFO [stdout] (pool-19-thread-1) GMS: address=node-udp-1/ejb, cluster=ejb, physical address=0:0:0:0:0:0:0:1:55300
04:06:22,802 INFO [stdout] (pool-19-thread-1) -------------------------------------------------------------------
04:06:22,811 SEVERE [org.jgroups.protocols.UDP] (pool-19-thread-1) failed sending message to cluster (107 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (110 bytes), cause: java.io.IOException: Network is unreachable
04:06:22,836 INFO [stdout] (pool-14-thread-1)
04:06:22,845 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
04:06:22,846 INFO [stdout] (pool-14-thread-1) GMS: address=node-udp-1/web, cluster=web, physical address=0:0:0:0:0:0:0:1:55300
04:06:22,846 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
04:06:22,860 SEVERE [org.jgroups.protocols.UDP] (pool-14-thread-1) failed sending message to cluster (107 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (110 bytes), cause: java.io.IOException: Network is unreachable
04:06:23,577 SEVERE [org.jgroups.protocols.UDP] (Timer-4,<ADDR>) failed sending message to cluster (69 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (72 bytes), cause: java.io.IOException: Network is unreachable
04:06:24,405 SEVERE [org.jgroups.protocols.UDP] (Timer-2,<ADDR>) failed sending message to cluster (69 bytes): java.lang.Exception: dest=/ff0e:0:0:0:0:0:e600:4:45688 (72 bytes), cause: java.io.IOException: Network is unreachable
04:06:25,795 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
04:06:25,810 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
04:06:25,829 INFO [org.infinispan.config.ConfigurationValidatingVisitor] (pool-15-thread-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
04:06:26,044 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000078: Starting JGroups Channel
04:06:26,044 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-20-thread-1) ISPN000078: Starting JGroups Channel
04:06:26,059 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000094: Received new cluster view: [node-udp-1/web|0] [node-udp-1/web]
04:06:26,059 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-20-thread-1) ISPN000094: Received new cluster view: [node-udp-1/ejb|0] [node-udp-1/ejb]
04:06:26,061 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000079: Cache local address is node-udp-1/web, physical addresses are [0:0:0:0:0:0:0:1:55300]
04:06:26,062 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-20-thread-1) ISPN000079: Cache local address is node-udp-1/ejb, physical addresses are [0:0:0:0:0:0:0:1:55300]
04:06:26,130 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-15-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.1.FINAL
04:06:26,131 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-20-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.1.FINAL
{noformat}
--
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, 3 months
[JBoss JIRA] (AS7-3932) DataSource connection property problems
by Heiko Braun (JIRA)
Heiko Braun created AS7-3932:
--------------------------------
Summary: DataSource connection property problems
Key: AS7-3932
URL: https://issues.jboss.org/browse/AS7-3932
Project: Application Server 7
Issue Type: Bug
Components: JCA
Reporter: Heiko Braun
Assignee: Stefano Maestri
Fix For: 7.1.2.Final
We have several problems with DS connection properties:
A) they cannot be removed
1.) create a datasource
2.) add connection property
3.) enable, then disable DS
4.) try to remove connection property
leads to
{noformat}
[Server:server-one] 08:31:18,978 INFO [org.jboss.as.controller] (host-controller-connection-threads - 1) JBAS014774: Service status report
[Server:server-one] JBAS014775: New missing/unsatisfied dependencies:
[Server:server-one] service jboss.data-source-config.MyDS.connection-properties.testProp (missing) dependents: [service jboss.data-source-config.MyDS]
[Server:server-one]
{noformat}
--
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, 3 months
[JBoss JIRA] (AS7-3931) After removing datasource param, accessing Runtime DS subsystem view in Domain causes No handler for read-resource at address error
by William Bendrot (JIRA)
William Bendrot created AS7-3931:
------------------------------------
Summary: After removing datasource param, accessing Runtime DS subsystem view in Domain causes No handler for read-resource at address error
Key: AS7-3931
URL: https://issues.jboss.org/browse/AS7-3931
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.Final
Environment: RHEL 5.4x in a Domain with one DC/1Server and one HC
Reporter: William Bendrot
Assignee: Heiko Braun
After removing a parameter from a data source in the console, when accessing the Datasource Subsystem panel on the Runtime page the following error is displayed:
Unknown error
Unexpected HTTP response: 500
Request
{
"address" => [
("host" => "SovereignIntDC"),
("server" => "SovereignInt01"),
("subsystem" => "datasources"),
("data-source" => "sovereign"),
("statistics" => "pool")
],
"operation" => "read-resource",
"include-runtime" => true
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "JBAS014739: No handler for read-resource at address [
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"sovereign\"),
(\"statistics\" => \"pool\")
]",
"rolled-back" => true
}
--
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, 3 months
[JBoss JIRA] (AS7-3408) Classloading issue with HornetQLoggerFactory - possilbe problem with failback
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3408:
-----------------------------------
Summary: Classloading issue with HornetQLoggerFactory - possilbe problem with failback
Key: AS7-3408
URL: https://issues.jboss.org/browse/AS7-3408
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Andy Taylor
Priority: Critical
Fix For: 7.1.0.Final
Attachments: console-log-backup-server.txt, console-log-live-server.txt, reproducer.zip
Test scenario:
1. Start two servers AS7/EAP6 servers - live and its backup in dedicated topology - each on different machine
2. Kill live server using "kill -9 ..."
3. Start live server again
In step 3. there are unexpected messages in console log of live and backup server.
>From backup server:
{code}
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [17700d86-45b2-11e1-a575-d48564b8e1e7] stopped
12:07:26,165 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (Thread-78) unable to restart server, please kill and restart manually: java.lang.IllegalArgumentException: Could not find class org.jboss.as.messaging.HornetQLoggerFactory
at org.hornetq.utils.ClassloadingUtil$1.run(ClassloadingUtil.java:42) [hornetq-core-2.2.7.Final.jar:]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_22]
at org.hornetq.utils.ClassloadingUtil.safeInitNewInstance(ClassloadingUtil.java:16) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.instantiateInstance(HornetQServerImpl.java:1868) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.initialiseLogging(HornetQServerImpl.java:1301) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:541) [hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation$1FailbackChecker$1.run(HornetQServerImpl.java:430) [hornetq-core-2.2.7.Final.jar:]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
>From live server:
{code}
12:07:51,993 INFO [org.jboss.as.messaging] (MSC service thread 1-3) JBAS011601: Bound messaging object to jndi name java:/topic/test
12:07:52,007 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 31092ms - Started 155 of 263 services (103 services are passive or on-demand)
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 1
12:07:53,292 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:53,292 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:53,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup configured now!
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying reconnection attempt 2
12:07:55,293 DEBUG [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Started Netty Connector version 3.2.3.Final-r${buildNumber}
12:07:55,293 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Trying to connect at the main server using connector :org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5446&host=192-168-10-4
12:07:55,294 DEBUG [org.hornetq.core.client.impl.ClientSessionFactoryImpl] (Thread-1 (group:HornetQ-client-global-threads-1954829789)) Main server is not up. Hopefully there's a backup
{code}
I'm not fully sure but it looks like that backup server did not manage to get to "waiting for live to fail" state and live server is not able to detect it.
There is set "DEBUG" level logging for "org.hornetq" in attached logs.
I've attached reproducer.zip - steps to use:
1. Download and unzip "reproducer.zip"
2. Prepare live and backup server - "sh prepare.sh"
3. Start live - "sh start-server1.sh server1_hostname"
4. Start backup - "sh start-server2.sh server2_hostname"
5. Kill live server using "kill -9 server1_process_id"
6. Start live server again - "sh start-server1.sh server1_hostname"
Note:
In reproducer.zip are configuration files standalone-ha-A.xml, standalone-ha-B.xml (A for live, B for backup).
--
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, 3 months
[JBoss JIRA] (AS7-3317) ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3317:
-----------------------------------
Summary: ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator
Key: AS7-3317
URL: https://issues.jboss.org/browse/AS7-3317
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Fix For: 7.1.0.Final
When logging subsystem is set to DEBUG level for "org.hornetq" then ClassNotFoundException exception appears in console log:
{code}
12:45:01,163 DEBUG [org.hornetq.ra.Util] (MSC service thread 1-4) org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]: java.lang.ClassNotFoundException: org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:473)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:461)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:403)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:125)
at org.hornetq.ra.Util.locateTM(Util.java:261) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.locateTM(HornetQResourceAdapter.java:1555) [hornetq-ra-2.2.7.Final.jar:]
at org.hornetq.ra.HornetQResourceAdapter.start(HornetQResourceAdapter.java:210) [hornetq-ra-2.2.7.Final.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:345) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2127) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1030) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final]
at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:148) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:94) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
{code}
--
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, 3 months
[JBoss JIRA] (JASSIST-152) instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null
by Yanic Inghelbrecht (JIRA)
Yanic Inghelbrecht created JASSIST-152:
------------------------------------------
Summary: instrumentation fails when building stackmap for local var of array type : bad array type for AALOAD: null
Key: JASSIST-152
URL: https://issues.jboss.org/browse/JASSIST-152
Project: Javassist
Issue Type: Bug
Affects Versions: 3.15.0-GA
Environment: Any
Reporter: Yanic Inghelbrecht
Assignee: Shigeru Chiba
When trying to instrument the attached org.hibernate.cfg.AbstractPropertyHolder (copied from the hibernate 4.0.1 final distribution), instrumentation fails with the following exception :
java.lang.RuntimeException: fatal error:
at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:177)
at javassist.bytecode.stackmap.MapMaker.fillStackMap(MapMaker.java:410)
at javassist.bytecode.stackmap.MapMaker.toStackMapBody(MapMaker.java:393)
at javassist.bytecode.stackmap.MapMaker.toStackMap(MapMaker.java:323)
at javassist.bytecode.stackmap.MapMaker.make(MapMaker.java:98)
at javassist.bytecode.MethodInfo.rebuildStackMap(MethodInfo.java:417)
at javassist.bytecode.MethodInfo.rebuildStackMapIf6(MethodInfo.java:399)
at javassist.expr.ExprEditor.doit(ExprEditor.java:113)
at javassist.CtBehavior.instrument(CtBehavior.java:672)
at test_abstractpropertyholder.SimpleTranslator.modify(SimpleTranslator.java:25)
at test_abstractpropertyholder.SimpleTranslator.onLoad(SimpleTranslator.java:19)
at test_abstractpropertyholder.JavassistInstrumenter.getInstrumentedClass(JavassistInstrumenter.java:21)
at test_abstractpropertyholder.Main.main(Main.java:32)transforming org.hibernate.cfg.AbstractPropertyHolder
Caused by: javassist.bytecode.BadBytecode: bad array type for AALOAD: null
at javassist.bytecode.stackmap.TypeData$ArrayElement.getName(TypeData.java:422)
at javassist.bytecode.stackmap.TypeData$TypeName.getExpected(TypeData.java:292)
at javassist.bytecode.stackmap.TypeData$TypeName.getTypeData(TypeData.java:175)
... 12 more
--
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, 3 months
[JBoss JIRA] (AS7-3910) How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS
by Mustafa Khambatta (JIRA)
Mustafa Khambatta created AS7-3910:
--------------------------------------
Summary: How to create server instances and then a cluster for JBoss AS 7.1.0 for Windows OS
Key: AS7-3910
URL: https://issues.jboss.org/browse/AS7-3910
Project: Application Server 7
Issue Type: Task
Components: Clustering
Affects Versions: 7.1.0.Final
Environment: Windows 2003 EE OS
32bit 4GB RAM
Reporter: Mustafa Khambatta
Assignee: Paul Ferraro
Fix For: No Release
I am unable to find any information on creating server instances on windows OS for JBoss AS7.1.0.
I have tried the other ways mentioned but nothing.
The admin console doesnot have any function of creating a server instance and I cant find any instruction for doing it through command prompt.
Also after creating the server instances how to you create the cluster and what are the steps for it. Then after that, what is the steps for creating a High Availability clustering
Thankyou in advance
Appreciate your help
--
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, 3 months