[JBoss JIRA] Created: (JBMESSAGING-1878) Duplicated Messages received during failover process
by Yong Hao Gao (JIRA)
Duplicated Messages received during failover process
----------------------------------------------------
Key: JBMESSAGING-1878
URL: https://issues.jboss.org/browse/JBMESSAGING-1878
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Priority: Critical
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1
If a message is delivered to the client when failover happens, there is a chance that this message won't get cleaned up and put into client buffer, and the message will be recovered after failover and delivered to client so that the client may have received this message twice.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (AS7-836) non JPA app using hibernate doesn't cause org.hibernate classes to be loaded
by Darrin Mison (JIRA)
non JPA app using hibernate doesn't cause org.hibernate classes to be loaded
----------------------------------------------------------------------------
Key: AS7-836
URL: https://issues.jboss.org/browse/AS7-836
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Reporter: Darrin Mison
Assignee: Jason Greene
I'm using hibernate but not not using @PersistenceContext or @PersistenceUnit and so my deployment is not being marked as a JPA deployment, and therefore the hibernate jars are not available.
I've worked around it by adding a Dependencies: org.hibernate to my manifest.mf file
{quote}
16:46:34,843 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "TopicSearch.war"
16:46:36,090 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/TopicSearch]] (MSC service thread 1-2) Exception sending context initialized event to listener instance of class org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap: java.lang.RuntimeException: Failed to construct public com.redhat.ecs.topic.webservice.MyRESTApplication()
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:144) [resteasy-jaxrs-2.1.0.GA.jar:]
at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:249) [resteasy-jaxrs-2.1.0.GA.jar:]
at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:192) [resteasy-jaxrs-2.1.0.GA.jar:]
at org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap.contextInitialized(ResteasyBootstrap.java:28) [resteasy-jaxrs-2.1.0.GA.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3817) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:61) [jboss-as-web-7.0.0.Beta3.jar:7.0.0.Beta3]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
Caused by: java.lang.NoClassDefFoundError: org/hibernate/Session
at com.redhat.ecs.topic.webservice.MyRESTApplication.<init>(MyRESTApplication.java:12) [classes:]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_24]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_24]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_24]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_24]
at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:132) [resteasy-jaxrs-2.1.0.GA.jar:]
... 10 more
Caused by: java.lang.ClassNotFoundException: org.hibernate.Session from [Module "deployment.TopicSearch.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:184) [:1.0.0.Beta17]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:357) [:1.0.0.Beta17]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:329) [:1.0.0.Beta17]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:306) [:1.0.0.Beta17]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:100) [:1.0.0.Beta17]
... 16 more
16:46:36,100 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart
16:46:36,100 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/TopicSearch] startup failed due to previous errors
16:46:36,120 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /TopicSearch
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-9129) If a JAX-RS is bundled it can break JAX-RS for other deployments
by Stuart Douglas (JIRA)
If a JAX-RS is bundled it can break JAX-RS for other deployments
-----------------------------------------------------------------
Key: JBAS-9129
URL: https://issues.jboss.org/browse/JBAS-9129
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XML Services/Frameworks
Affects Versions: 7.0.0.Beta1
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 7.0.0.Final
The JAX-RS API uses a service loader pattern to locate the actual implementation, which is then cached in static values.
Unfortunately the TCCL is used, which results in the deployments CL to be used to load the impl. This means that if a JAX-RS impl is bundled, it's classes will be used for all deployments, rather than using resteasy.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-9373) Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
by Scott Stark (JIRA)
Arjuna service creating an anonymous localhost binding outside of standalone.xml configuration.
-----------------------------------------------------------------------------------------------
Key: JBAS-9373
URL: https://issues.jboss.org/browse/JBAS-9373
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager Integration (Arjuna)
Affects Versions: 7.0.0.Beta3
Reporter: Scott Stark
Assignee: Jonathan Halliday
I'm seeing an attempt to bind an anonymous socket to localhost/127.0.0.1 even when the standalone.xml configuration has specified a loopback-address other than localhost/127.0.0.1 as the default:
<interfaces>
<interface name="default">
<loopback-address value="127.0.250.1"/>
</interface>
The port is also not one listed in the socket-binding-group section. Both the interface and port should be coming from the server configuration.
Thread attempting bind call:
Socket[addr=localhost/127.0.0.1,port=0,localport=52394]
Transaction Expired Entry Monitor@2745 daemon, prio=5, in group 'main', status: 'RUNNING'
blocks MSC service thread 1-1@1104
at java.net.PlainSocketImpl.listen(PlainSocketImpl.java:398)
at java.net.ServerSocket.bind(ServerSocket.java:329)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at com.arjuna.ats.internal.arjuna.utils.SocketProcessId.createSocket(SocketProcessId.java:99)
at com.arjuna.ats.internal.arjuna.utils.SocketProcessId.<init>(SocketProcessId.java:76)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-1)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.arjuna.ats.arjuna.utils.Utility.initDefaultProcess(Utility.java:336)
at com.arjuna.ats.arjuna.utils.Utility.getProcess(Utility.java:348)
at com.arjuna.ats.arjuna.utils.Utility.getpid(Utility.java:287)
at com.arjuna.ats.arjuna.common.Uid.<init>(Uid.java:84)
at com.arjuna.ats.arjuna.state.OutputObjectState.<init>(OutputObjectState.java:63)
at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:158)
at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:70)
at com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:82)
at com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:172)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month