[JBoss JIRA] (AS7-3460) FLUSH dominates MSC service start, and never returns
by Jason Greene (JIRA)
Jason Greene created AS7-3460:
---------------------------------
Summary: FLUSH dominates MSC service start, and never returns
Key: AS7-3460
URL: https://issues.jboss.org/browse/AS7-3460
Project: Application Server 7
Issue Type: Bug
Reporter: Jason Greene
"MSC service thread 1-6" prio=10 tid=0x00007f207c038000 nid=0x23be waiting on condition [0x00007f209d475000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000e1539140> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2116)
at org.jgroups.util.Promise.doWait(Promise.java:116)
at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:72)
at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:41)
at org.jgroups.util.Promise.getResult(Promise.java:103)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:137)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinWithStateTransfer(ClientGmsImpl.java:42)
at org.jgroups.protocols.pbcast.GMS.down(GMS.java:921)
at org.jgroups.protocols.FlowControl.down(FlowControl.java:351)
at org.jgroups.protocols.FlowControl.down(FlowControl.java:351)
at org.jgroups.protocols.FRAG2.down(FRAG2.java:147)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:238)
at org.jgroups.protocols.pbcast.FLUSH.handleConnect(FLUSH.java:300)
at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:265)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1033)
at org.jgroups.JChannel.down(JChannel.java:732)
at org.jgroups.JChannel.connect(JChannel.java:347)
- locked <0x00000000e1537880> (a org.jboss.as.clustering.jgroups.MuxChannel)
at org.jgroups.JChannel.connect(JChannel.java:305)
- locked <0x00000000e1537880> (a org.jboss.as.clustering.jgroups.MuxChannel)
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:38)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Log:
12:46:12,235 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:15,240 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:17,242 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:20,244 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:22,248 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:25,252 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:27,256 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:30,261 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:32,263 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:35,266 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:37,268 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
12:46:40,269 WARNING [org.jgroups.protocols.pbcast.GMS] (MSC service thread 1-6) JOIN(node-udp-0/ejb) sent to node-udp-0/ejb timed out (after 3000 ms), retrying
12:46:42,270 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-6) null: no physical address for node-udp-0/ejb, dropping message
(repeats)
--
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
[JBoss JIRA] (AS7-3316) stanalonde.xml, xa-datasource/security, <user-name> cannot be parametrised
by ivan khoosty (JIRA)
ivan khoosty created AS7-3316:
---------------------------------
Summary: stanalonde.xml, xa-datasource/security, <user-name> cannot be parametrised
Key: AS7-3316
URL: https://issues.jboss.org/browse/AS7-3316
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.0.CR1b
Reporter: ivan khoosty
Assignee: Jesper Pedersen
Priority: Minor
in standalone.xml, i've got a system property declared
<system-properties>
<property name="sql.user" value="sa"/>
... </system-properties>
it does not get resolved further down in datasource declaration,
...
<security>
<user-name>${sql.user}</user-name>
...
</security>
interestingly, all other properties resolve no problem, ie password, server etc.
there is a workaround (hardcode the username value!), thus setting the bug priority to minor.
--
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
[JBoss JIRA] Created: (AS7-1917) Supporting URIEncoding and useBodyEncodingForURI in Connector
by Marek Smigielski (JIRA)
Supporting URIEncoding and useBodyEncodingForURI in Connector
-------------------------------------------------------------
Key: AS7-1917
URL: https://issues.jboss.org/browse/AS7-1917
Project: Application Server 7
Issue Type: Feature Request
Components: Web
Affects Versions: 7.0.1.Final
Reporter: Marek Smigielski
Assignee: Remy Maucherat
I need to set URIEncoding and useBodyEncodingForURI in jbossas7 but I
didn't find any way of doing it. The way it can be done in previous
versions can't be applied because server will not start up properly.
It would be great if you could configure connector like that:
<Connector name="http" protocol="HTTP/1.1" socket-binding="http" scheme="http" URIEncoding="UTF-8" useBodyEncodingForURI="true"/>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBAS-8827) Deal with expression values in all operation handlers
by Brian Stansberry (JIRA)
Deal with expression values in all operation handlers
-----------------------------------------------------
Key: JBAS-8827
URL: https://issues.jboss.org/browse/JBAS-8827
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.Beta1
Pretty much any simple value in a detyped operation can be of type ModelType.EXPRESSION instead something an OperationHandler might expect, like ModelType.STRING or ModelType.INT. All handlers need to deal with this fact.
There are two main aspects to this:
1) Any parameter validation that goes on needs to account for the presence of expression values. Basically that means
a) accept the expression for storage in the model
b) call resolve() on the operation and use the resolved version for application to the runtime.
c) re-validation of the resolved value may be necessary
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3182) Admin console: standalone server doesn't require distinct socket binding groups
by Jan Martiska (Created) (JIRA)
Admin console: standalone server doesn't require distinct socket binding groups
-------------------------------------------------------------------------------
Key: AS7-3182
URL: https://issues.jboss.org/browse/AS7-3182
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Dustin Kut Moy Cheung
Priority: Minor
see screenshot. In standalone mode, a standalone server does not support defining multiple socket binding groups, there can be only one, by default it is named 'standard-sockets' (at least I understand it this way, it is specified in jboss-as-config_1.1 xml schema). Therefore the checkbox for picking one of socket binding groups is irrelevant, because it cannot provide any choices.
By the way, it could be useful to have the possibility to change the name 'standard-sockets' using admin console.
--
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
[JBoss JIRA] (AS7-2968) @PreUpdate entity callback not running in caller's context when Container Managed Transactions are used
by jw (Created) (JIRA)
@PreUpdate entity callback not running in caller's context when Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but fails on @PreUpdate with a NullPointerException if container managed transactions are used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
[JBoss JIRA] (JBAS-9470) JBoss 51.0 - Third party Jar Deployment fail with : Unable to find class path entry ClassPathEntryImpl {path=MyApp/APP-INF/lib/batik-all-1.7.jar} from fop.jar
by Mehul Kapadia (JIRA)
Mehul Kapadia created JBAS-9470:
-----------------------------------
Summary: JBoss 51.0 - Third party Jar Deployment fail with : Unable to find class path entry ClassPathEntryImpl {path=MyApp/APP-INF/lib/batik-all-1.7.jar} from fop.jar
Key: JBAS-9470
URL: https://issues.jboss.org/browse/JBAS-9470
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading, Deployers, EJB, VFS
Affects Versions: JBossAS-5.1.0.GA
Reporter: Mehul Kapadia
Assignee: Ales Justin
Fix For: No Release
While Trying to Deploy My EJB2.0 Application on JBoss 5.1.0 GA I am getting following Exception on Application server Startup for some of the Jars in MyApp/APP-INF/lib/
I have fop.jar and batik-all-1.7.jar present in my application's APP-INF/lib directory (But Exception complaining those file are not present in that location).
As per my understanding it looks like some bug in JBoss 5.1.0 GA , for the way third party jars are being loaded to JBoss Container. Because After we have removed Class-Path Entry from respective Jar(fop.jar and batik-all-1.7.jar)'s MANIFEST.mf file. This Exception is not coming.
Please guide me to get rid of this error, without performing manual step to remove Class-Path entry from Each jar's MANIFEST.mf file.
Please let me know if you need anymore information for clarification.
DETAILS:
****************
JBoss Version : jboss-5.1.0.GA
JDK Version:
--------------------------
java version "1.6.0_02-ea"
Java(TM) SE Runtime Environment (build 1.6.0_02-ea-b02)
Java HotSpot(TM) Client VM (build 1.6.0_02-ea-b02, mixed mode, sharing)
Exception Trace :
--------------------
2011-12-28 15:21:51,961 INFO [org.jboss.web.WebService] |Logger.java:296| Using RMI server codebase: http://172.19.102.61:8083/
2011-12-28 15:22:06,696 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] |Logger.java:296| JBoss Web Services - Stack Native Core
2011-12-28 15:22:06,696 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] |Logger.java:296| 3.1.2.GA
2011-12-28 15:22:08,009 INFO [org.jboss.dependency.plugins.AttributeCallbackItem] |Logger.java:296| Owner callback not implemented.
2011-12-28 15:22:10,009 INFO [org.jboss.logbridge.LogNotificationListener] |LogNotificationListener.java:71| Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@1135cd9[ defaultDomain='jboss' ]
2011-12-28 15:22:16,743 ERROR [org.jboss.system.server.profileservice.repository.ProfileDeployAction] |Logger.java:419| Failed to add deployment: fop.jar
org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=BancsApp/APP-INF/lib/batik-all-1.7.jar} from fop.jar
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Child not found BancsApp/APP-INF/lib/batik-all-1.7.jar for DelegatingHandler(a)12804443[path=BancsApp/APP-INF/lib/fop.jar context=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/BancsApp/APP-INF/lib/fop.jar], available children: [ZipEntryHandler(a)19703023[path=BancsApp/APP-INF/lib/fop.jar/META-INF context=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/BancsApp/APP-INF/lib/fop.jar/META-INF], ZipEntryHandler(a)26185[path=BancsApp/APP-INF/lib/fop.jar/org context=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/BancsApp/APP-INF/lib/fop.jar/org]]
at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)
at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)
... 23 more
2011-12-28 15:22:17,900 ERROR [org.jboss.system.server.profileservice.repository.ProfileDeployAction] |Logger.java:419| Failed to add deployment: xalan.jar
org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=BancsApp/APP-INF/lib/serializer.jar} from xalan.jar
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Child not found BancsApp/APP-INF/lib/serializer.jar for DelegatingHandler(a)13335932[path=BancsApp/APP-INF/lib/xalan.jar context=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/ real=file:/D:/Mehul/JBoss/jboss-5.1.0.GA/server/default/deploy/BancsApp/
Regards,
Mehul Kapadia
--
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