[JBoss JIRA] (DROOLS-1227) Drools cannot be configured to expire Events properly
by Cristobal Arellano (JIRA)
Cristobal Arellano created DROOLS-1227:
------------------------------------------
Summary: Drools cannot be configured to expire Events properly
Key: DROOLS-1227
URL: https://issues.jboss.org/browse/DROOLS-1227
Project: Drools
Issue Type: Feature Request
Affects Versions: 6.2.0.Final
Environment: Windows, Java SE 1.8
Reporter: Cristobal Arellano
Assignee: Mark Proctor
Priority: Critical
Hello,
I want to configure Drools (CEP) to expire events when no longer needed. There are two scenarios:
==SCENARIO A==
I configured Event with no explicit expires. In this scenario, if there is a rule with temporal constraints, the expiration is automatically calculated based on the constrains. If there is a rule with no temporal constraints, the expiration is INFINITE. The following example shows the scenario:
dialect "mvel"
declare Event
@role(event)
end
rule "ExampleRule1"
when
( $a : Event(name == "event a")
then
System.out.println("ExampleRule1Triggered");
end
rule "ExampleRule2"
when
( $a : Event(name == "event a") ) and
( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
then
System.out.println("ExampleRule2Triggered");
end
With the previous Event definition:
* If only ExampleRule1 loaded, expires INFINITE. Expected expires 0. ERROR?
* If ExampleRule1 loaded and ExampleRule2 loaded, expires 15s. Expected expires 15. OK!
To solve this situation a tried the following scenario:
== SCENARIO B==
I configured Event with explicit expires. In this scenario, if there is a rule with temporal constraints, the expiration is not taken into account because it is overriden by the explicit expires. The following example shows the scenario:
dialect "mvel"
declare Event
@role(event)
@expires(0s)
end
rule "ExampleRule1"
when
( $a : Event(name == "event a")
then
System.out.println("ExampleRule1Triggered");
end
rule "ExampleRule2"
when
( $a : Event(name == "event a") ) and
( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
then
System.out.println("ExampleRule2Triggered");
end
With the previous Event definition:
* ExampleRule1 is triggered and event removed. OK!
* ExampleRule2 is not triggered inserting two events because the first one expires. ERROR?
I suppose that SCENARIO B is not factible because explicit expires overrides implicit expires (according to issue DROOLS-586).
Could you please help me to solve this situation? Should Drools set inferred expiration time to 1ms when there are rules with no temporal constraints?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (DROOLS-1227) Drools cannot be configured to expire Events properly
by Cristobal Arellano (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1227?page=com.atlassian.jira.plugi... ]
Cristobal Arellano updated DROOLS-1227:
---------------------------------------
Issue Type: Bug (was: Feature Request)
> Drools cannot be configured to expire Events properly
> -----------------------------------------------------
>
> Key: DROOLS-1227
> URL: https://issues.jboss.org/browse/DROOLS-1227
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.Final
> Environment: Windows, Java SE 1.8
> Reporter: Cristobal Arellano
> Assignee: Mark Proctor
> Priority: Critical
>
> Hello,
> I want to configure Drools (CEP) to expire events when no longer needed. There are two scenarios:
> ==SCENARIO A==
> I configured Event with no explicit expires. In this scenario, if there is a rule with temporal constraints, the expiration is automatically calculated based on the constrains. If there is a rule with no temporal constraints, the expiration is INFINITE. The following example shows the scenario:
> dialect "mvel"
> declare Event
> @role(event)
> end
> rule "ExampleRule1"
> when
> ( $a : Event(name == "event a")
> then
> System.out.println("ExampleRule1Triggered");
> end
> rule "ExampleRule2"
> when
> ( $a : Event(name == "event a") ) and
> ( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
> then
> System.out.println("ExampleRule2Triggered");
> end
> With the previous Event definition:
> * If only ExampleRule1 loaded, expires INFINITE. Expected expires 0. ERROR?
> * If ExampleRule1 loaded and ExampleRule2 loaded, expires 15s. Expected expires 15. OK!
> To solve this situation a tried the following scenario:
> == SCENARIO B==
> I configured Event with explicit expires. In this scenario, if there is a rule with temporal constraints, the expiration is not taken into account because it is overriden by the explicit expires. The following example shows the scenario:
> dialect "mvel"
> declare Event
> @role(event)
> @expires(0s)
> end
> rule "ExampleRule1"
> when
> ( $a : Event(name == "event a")
> then
> System.out.println("ExampleRule1Triggered");
> end
> rule "ExampleRule2"
> when
> ( $a : Event(name == "event a") ) and
> ( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
> then
> System.out.println("ExampleRule2Triggered");
> end
> With the previous Event definition:
> * ExampleRule1 is triggered and event removed. OK!
> * ExampleRule2 is not triggered inserting two events because the first one expires. ERROR?
> I suppose that SCENARIO B is not factible because explicit expires overrides implicit expires (according to issue DROOLS-586).
> Could you please help me to solve this situation? Should Drools set inferred expiration time to 1ms when there are rules with no temporal constraints?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-5739) Subject not populated with groups/roles when authenticated via JASPIC
by Guillermo González de Agüero (JIRA)
[ https://issues.jboss.org/browse/WFLY-5739?page=com.atlassian.jira.plugin.... ]
Guillermo González de Agüero updated WFLY-5739:
-----------------------------------------------
Attachment: CustomAuth.zip
picketbox.zip
Hi [~stoty2], I've tested the patch and I confirm it works. However, it still doesn't restore groups
for a given CallerPrincipalCallback called with a principal stored from an earlier request (enabling "javax.servlet.http.registerSession").
To reproduce, compile and deploy CustomAuth war. Update PicketBox module with my attached picketbox.zip (compiled from your GH commit) and follow the steps below:
- Go to /index.jsp and you'll see a login form. Enter anything and a page with the the specified name will be shown. Do a GET request and you'll see the roles are restored.
- You'll be able to see /protected.jsp, which requires "admin" role.
- Now go to /TestServlet. A NullPointerException will be shown, cause groups are not restored.
- Going to /TestServlet?username=Guillermo correctly propagates roles thanks to your patch.
> Subject not populated with groups/roles when authenticated via JASPIC
> ---------------------------------------------------------------------
>
> Key: WFLY-5739
> URL: https://issues.jboss.org/browse/WFLY-5739
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.CR4
> Reporter: Arjan t
> Assignee: Darran Lofthouse
> Labels: jacc, jaspic
> Attachments: CustomAuth.zip, picketbox.zip
>
>
> After having authenticated via JASPIC, requesting the current {{Subject}} via JACC and then using that for permission checks fails.
> For instance the following code will always set {{hasAccess}} to false given that "/protected/*" requires a role and the authenticated user is in that role:
> {code:java}
> Subject subject = (Subject) PolicyContext.getContext("javax.security.auth.Subject.container");
>
> boolean hasAccess = Policy.getPolicy().implies(
> new ProtectionDomain(
> new CodeSource(null, (Certificate[]) null),
> null, null,
> subject.getPrincipals().toArray(new Principal[subject.getPrincipals().size()])
> ),
> new WebResourcePermission("/protected/Servlet", "GET"))
> ;
> {code}
> As it appears, the problem originates from the fact that {{subject.getPrincipals()}} does not contain the roles.
> This can be traced back to {{org.jboss.security.auth.callback.JASPICallbackHandler.handleCallBack}}, where it becomes clear that the roles are only put into the "util", but not in the "authenticatedSubject":
> {code:java}
> String[] rolesArray = groupPrincipalCallback.getGroups();
> int sizeOfRoles = rolesArray != null ? rolesArray.length : 0;
>
> if( sizeOfRoles > 0 )
> {
> List<Role> rolesList = new ArrayList<Role>();
> for( int i = 0; i < sizeOfRoles ; i++ )
> {
> Role role = new SimpleRole( rolesArray[ i ] );
> rolesList.add( role );
> }
> RoleGroup roles = new SimpleRoleGroup( SecurityConstants.ROLES_IDENTIFIER, rolesList );
> // if the current security context already has roles, we merge them with the incoming roles.
> RoleGroup currentRoles = currentSC.getUtil().getRoles();
> // *** ROLES ARE ONLY SET HERE ***
> if (currentRoles != null) {
> currentRoles.addAll(roles.getRoles());
> }
> else {
> currentSC.getUtil().setRoles( roles );
> }
> }
> // *** BELOW THIS LINE ROLES ARE NOT REFERENCED ANYMORE
> // *** SUBJECT IS NOT POPULATED WITH ANY ROLE INFO
> Subject subject = groupPrincipalCallback.getSubject();
> if( subject != null )
> {
> // if the current security context already has an associated subject, we merge it with the incoming subject.
> Subject currentSubject = currentSC.getSubjectInfo().getAuthenticatedSubject();
> if (currentSubject != null) {
> subject.getPrincipals().addAll(currentSubject.getPrincipals());
> subject.getPublicCredentials().addAll(currentSubject.getPublicCredentials());
> subject.getPrivateCredentials().addAll(currentSubject.getPrivateCredentials());
> }
> currentSC.getSubjectInfo().setAuthenticatedSubject(subject);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JGRP-2088) ArrayIndexOutOfBoundsException on ClassConfigurator.get()
by Manuel Dominguez Sarmiento (JIRA)
Manuel Dominguez Sarmiento created JGRP-2088:
------------------------------------------------
Summary: ArrayIndexOutOfBoundsException on ClassConfigurator.get()
Key: JGRP-2088
URL: https://issues.jboss.org/browse/JGRP-2088
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.10
Reporter: Manuel Dominguez Sarmiento
Assignee: Bela Ban
Attachments: jgroups.xml
See the following stack trace:
[ERROR] 2016-07-09 14:26:05 [UDP-multicast receiver,shared=jgroups-shared-transport] - JGRP000030: null: failed handling incoming message: java.lang.ArrayIndexOutOfBoundsException: -1
java.lang.ArrayIndexOutOfBoundsException: -1
at org.jgroups.conf.ClassConfigurator.get(ClassConfigurator.java:161)
at org.jgroups.Message.readHeader(Message.java:936)
at org.jgroups.Message.readFrom(Message.java:811)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1712)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Stepping through the code with the debugger should that the following line is failing at ClassConfigurator.get() with magic = -1 thus the java.lang.ArrayIndexOutOfBoundsException
return magic < 1024 ? magicMap[magic] : (Class)magicMapUser.get(Short.valueOf(magic));
See attached jgroups.xml for configuration. This showed up when upgrading to 3.6.10 from 3.6.8 which worked fine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JGRP-2088) ArrayIndexOutOfBoundsException on ClassConfigurator.get()
by Manuel Dominguez Sarmiento (JIRA)
[ https://issues.jboss.org/browse/JGRP-2088?page=com.atlassian.jira.plugin.... ]
Manuel Dominguez Sarmiento updated JGRP-2088:
---------------------------------------------
Description:
See the following stack trace:
[ERROR] 2016-07-09 14:26:05 [UDP-multicast receiver,shared=jgroups-shared-transport] - JGRP000030: null: failed handling incoming message: java.lang.ArrayIndexOutOfBoundsException: -1
java.lang.ArrayIndexOutOfBoundsException: -1
at org.jgroups.conf.ClassConfigurator.get(ClassConfigurator.java:161)
at org.jgroups.Message.readHeader(Message.java:936)
at org.jgroups.Message.readFrom(Message.java:811)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1712)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Stepping through the code with the debugger shows that the following line is failing at ClassConfigurator.get() with magic = -1 thus the java.lang.ArrayIndexOutOfBoundsException
return magic < 1024 ? magicMap[magic] : (Class)magicMapUser.get(Short.valueOf(magic));
See attached jgroups.xml for configuration. This showed up when upgrading to 3.6.10 from 3.6.8 which worked fine.
was:
See the following stack trace:
[ERROR] 2016-07-09 14:26:05 [UDP-multicast receiver,shared=jgroups-shared-transport] - JGRP000030: null: failed handling incoming message: java.lang.ArrayIndexOutOfBoundsException: -1
java.lang.ArrayIndexOutOfBoundsException: -1
at org.jgroups.conf.ClassConfigurator.get(ClassConfigurator.java:161)
at org.jgroups.Message.readHeader(Message.java:936)
at org.jgroups.Message.readFrom(Message.java:811)
at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1712)
at org.jgroups.protocols.TP.receive(TP.java:1654)
at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
at java.lang.Thread.run(Thread.java:745)
Stepping through the code with the debugger should that the following line is failing at ClassConfigurator.get() with magic = -1 thus the java.lang.ArrayIndexOutOfBoundsException
return magic < 1024 ? magicMap[magic] : (Class)magicMapUser.get(Short.valueOf(magic));
See attached jgroups.xml for configuration. This showed up when upgrading to 3.6.10 from 3.6.8 which worked fine.
> ArrayIndexOutOfBoundsException on ClassConfigurator.get()
> ---------------------------------------------------------
>
> Key: JGRP-2088
> URL: https://issues.jboss.org/browse/JGRP-2088
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Manuel Dominguez Sarmiento
> Assignee: Bela Ban
> Attachments: jgroups.xml
>
>
> See the following stack trace:
> [ERROR] 2016-07-09 14:26:05 [UDP-multicast receiver,shared=jgroups-shared-transport] - JGRP000030: null: failed handling incoming message: java.lang.ArrayIndexOutOfBoundsException: -1
> java.lang.ArrayIndexOutOfBoundsException: -1
> at org.jgroups.conf.ClassConfigurator.get(ClassConfigurator.java:161)
> at org.jgroups.Message.readHeader(Message.java:936)
> at org.jgroups.Message.readFrom(Message.java:811)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1712)
> at org.jgroups.protocols.TP.receive(TP.java:1654)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:745)
> Stepping through the code with the debugger shows that the following line is failing at ClassConfigurator.get() with magic = -1 thus the java.lang.ArrayIndexOutOfBoundsException
> return magic < 1024 ? magicMap[magic] : (Class)magicMapUser.get(Short.valueOf(magic));
> See attached jgroups.xml for configuration. This showed up when upgrading to 3.6.10 from 3.6.8 which worked fine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1615) Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1615?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1615:
----------------------------------------
Fix Version/s: 3.0.0.Alpha4
Assignee: Jorge Solorzano
Resolution: Done
> Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh
> ------------------------------------------------------------------
>
> Key: WFCORE-1615
> URL: https://issues.jboss.org/browse/WFCORE-1615
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 3.0.0.Alpha2
> Reporter: Jorge Solorzano
> Assignee: Jorge Solorzano
> Priority: Trivial
> Fix For: 3.0.0.Alpha4
>
>
> To make both scripts more consistent in terms of functionality.
> Changes include:
> * Add LSB INIT INFO
> * Validate user and permisions.
> * Make output of status more standard.
> * Improve output messages.
> * Include WFCORE-1604
> Tested enviroments:
> * CentOS 6.8
> * CentOS 7.2
> * Fedora 24 Server
> The script should be functional on both pre-systemd and systemd without weird behaivior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1604) Fail-fast start up init.d scripts on error
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1604?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1604:
----------------------------------------
Assignee: Jorge Solorzano (was: Tomaz Cerar)
> Fail-fast start up init.d scripts on error
> ------------------------------------------
>
> Key: WFCORE-1604
> URL: https://issues.jboss.org/browse/WFCORE-1604
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 3.0.0.Alpha1
> Environment: Debian/Ubuntu - Red Hat/Fedora
> Reporter: Jorge Solorzano
> Assignee: Jorge Solorzano
> Priority: Optional
> Fix For: 3.0.0.Alpha4
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Now that WildFly creates an startup-marker we can detect an error before timeout of the init.d startup scripts and detect if the error is from timeout or from an error in application server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-711) Detect/assume duplicate instances running
by Ricardo Arguello (JIRA)
[ https://issues.jboss.org/browse/WFLY-711?page=com.atlassian.jira.plugin.s... ]
Ricardo Arguello commented on WFLY-711:
---------------------------------------
Please close as resolved, all PRs have been merged: https://github.com/wildfly/wildfly/pull/9024
> Detect/assume duplicate instances running
> -----------------------------------------
>
> Key: WFLY-711
> URL: https://issues.jboss.org/browse/WFLY-711
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Jim Tyrrell
> Fix For: Awaiting Volunteers
>
>
> I do like the fact that address in use do not leave a running instance laying around, I would much rather see one error message rather then pages and pages. To our users this is very overwhelming, especially when they come from our competitors. Also how does this kind of error not have an error code associated with it.
> How many other exceptions do not have error codes?
> Jim-Tyrrells-MacBook-Pro-2:bin jimtyrrell$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1
> JAVA: java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman
> =========================================================================
> 08:38:37,622 INFO [org.jboss.modules] JBoss Modules version 1.0.0.CR4
> 08:38:37,772 INFO [org.jboss.msc] JBoss MSC version 1.0.0.CR2
> 08:38:37,812 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" starting
> 08:38:38,328 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
> 08:38:38,333 INFO [org.jboss.as.logging] Removing bootstrap log handlers
> 08:38:38,343 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
> 08:38:38,413 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
> 08:38:38,420 INFO [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service
> 08:38:38,425 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
> 08:38:38,436 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
> 08:38:38,442 INFO [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 3.2.0.Beta2
> 08:38:38,448 INFO [org.xnio] (MSC service thread 1-10) XNIO Version 3.0.0.Beta3
> 08:38:38,457 INFO [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.0.0.Beta3
> 08:38:38,606 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
> 08:38:38,616 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-10) Starting remote JMX connector
> 08:38:38,618 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
> 08:38:38,618 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC00001: Failed to start service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:98)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [:1.6.0_24]
> at org.xnio.nio.NioXnio.createTcpServer(NioXnio.java:162)
> at org.xnio.Xnio.createStreamServer(Xnio.java:230)
> at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:162)
> at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:93)
> ... 5 more
> 08:38:38,623 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the URLStreamHandlerFactory
> 08:38:38,624 WARN [org.jboss.osgi.framework.internal.URLHandlerPlugin] (MSC service thread 1-6) Unable to set the ContentHandlerFactory
> 08:38:38,625 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
> at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:89)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method) [:1.6.0_24]
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [:1.6.0_24]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [:1.6.0_24]
> at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:112)
> at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:47)
> at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:37)
> at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:126)
> at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:99)
> at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:86)
> ... 5 more
> 08:38:38,632 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:106)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393) [:1.6.0_24]
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129) [:1.6.0_24]
> at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:190) [:1.6.0_24]
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) [:1.6.0_24]
> at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:68) [:1.6.0_24]
> at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222) [:1.6.0_24]
> at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:97)
> ... 5 more
> Caused by: java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24]
> at org.jboss.as.network.ManagedServerSocketBinding.bind(ManagedServerSocketBinding.java:73)
> at org.jboss.as.network.SocketBinding.createServerSocket(SocketBinding.java:149)
> at org.jboss.as.jmx.JMXConnectorService$JMXServerSocketFactory.createServerSocket(JMXConnectorService.java:194)
> at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649) [:1.6.0_24]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299) [:1.6.0_24]
> ... 13 more
> 08:38:38,634 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190)
> at org.apache.catalina.connector.Connector.init(Connector.java:976)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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]
> 08:38:38,636 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.initialize: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.catalina.connector.Connector.init(Connector.java:978)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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]
> 08:38:38,638 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Error starting endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:1004)
> at org.apache.tomcat.util.net.JIoEndpoint.start(JIoEndpoint.java:1020)
> at org.apache.coyote.http11.Http11Protocol.start(Http11Protocol.java:218)
> at org.apache.catalina.connector.Connector.start(Connector.java:1051)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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]
> 08:38:38,639 ERROR [org.apache.catalina.core.StandardService] (MSC service thread 1-13) Connector.start: LifecycleException: service.getName(): "jboss.web"; Protocol handler start failed: java.net.BindException: Address already in use /127.0.0.1:8080
> at org.apache.catalina.connector.Connector.start(Connector.java:1058)
> at org.apache.catalina.core.StandardService.addConnector(StandardService.java:359)
> at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:121)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
> at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
> 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]
> 08:38:38,675 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
> 08:38:38,700 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) Bound data source [java:jboss/datasources/ExampleDS]
> 08:38:38,920 INFO [org.jboss.as.deployment] (MSC service thread 1-10) Started FileSystemDeploymentService for directory /Users/jimtyrrell 1/Servers/jboss-7.0.0.CR1/standalone/deployments
> 08:38:39,130 INFO [org.jboss.as.controller] (Controller Boot Thread) Service status report
> Services which failed to start:
> service jboss.remoting.server.management.9999: org.jboss.msc.service.StartException in service jboss.remoting.server.management.9999: java.net.BindException: Address already in use
> service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
> service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
> java.net.BindException: Address already in use
> 08:38:39,134 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.CR1 "White Rabbit" started (with errors) in 1668ms - Started 87 of 146 services (4 services failed or missing dependencies, 55 services are passive or on-demand)
> ^C08:39:03,929 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
> 08:39:03,933 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
> 08:39:03,934 INFO [org.jboss.as] JBoss AS 7.0.0.CR1 "White Rabbit" stopped in 4ms
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1644) PersistenceResourceXmlDescription marshals attributes in the reverse order they are added
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1644?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1644:
-------------------------------------
Affects Version/s: 2.1.0.Final
2.0.0.Final
> PersistenceResourceXmlDescription marshals attributes in the reverse order they are added
> -----------------------------------------------------------------------------------------
>
> Key: WFCORE-1644
> URL: https://issues.jboss.org/browse/WFCORE-1644
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Final, 2.1.0.Final, 2.2.0.CR5, 3.0.0.Alpha3
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 2.2.0.CR6, 3.0.0.Alpha4
>
>
> This in marshalAttributes results in iterating over a reversed list:
> {code}
> //we sort attributes to make sure that attributes that marshall to elements are last
> for (AttributeDefinition ad : attributes.stream().sorted((o1, o2) -> o1.getParser().isParseAsElement() ? 1 : -1).collect(Collectors.toList())) {
> {code}
> The sorter returning -1 for all non-element attributes has that effect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFCORE-1644) PersistenceResourceXmlDescription marshals attributes in the reverse order they are added
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1644:
----------------------------------------
Summary: PersistenceResourceXmlDescription marshals attributes in the reverse order they are added
Key: WFCORE-1644
URL: https://issues.jboss.org/browse/WFCORE-1644
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha3, 2.2.0.CR5
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.2.0.CR6, 3.0.0.Alpha4
This in marshalAttributes results in iterating over a reversed list:
{code}
//we sort attributes to make sure that attributes that marshall to elements are last
for (AttributeDefinition ad : attributes.stream().sorted((o1, o2) -> o1.getParser().isParseAsElement() ? 1 : -1).collect(Collectors.toList())) {
{code}
The sorter returning -1 for all non-element attributes has that effect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months