November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2591) CLI can not connect to the server started with port-offset

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-2591: -------------------------------------- Summary: CLI can not connect to the server started with port-offset Key: WFLY-2591 URL: https://issues.jboss.org/browse/WFLY-2591 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Environment: used actual WildFly Beta from github: commit 96160520ce245d6a85cbb77cad92a021564aa376 Date: Wed Nov 20 17:05:00 2013 +0100 Reporter: Wolf-Dieter Fink Assignee: Alexey Loubyansky Priority: Blocker If a standalone server is started with a binding port-offset it is not possible to connect to the native management interface. To reproduce start a WildFly Beta server (Alpha3 has the same problem) bin/standalone.sh -Djboss.socket.binding.port-offset=100 and a cli client: bin/jboss-cli.sh -c --controller=localhost:10099 It makes no difference whether the port is changed by port-offset or configuration. All other ports (i.e. 10090 8180) can be used correct for http-management or ejb invocation. The server log an ERROR message: ERROR [org.jboss.remoting.remote.connection] (Remoting "home:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: XNIO000804: Received an invalid message length of 1195725856 The jboss-cli.sh client show: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:240) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:218) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.modules.Module.run(Module.java:292) at org.jboss.modules.Main.main(Main.java:455) Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:10099 at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:960) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:772) at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:238) ... 8 more Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:938) ... 11 more Caused by: java.net.ConnectException: JBAS012174: Could not connect to http-remoting://localhost:10099. The connection failed at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:166) at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:127) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) ... 13 more Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:283) at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:266) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80) at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99) ... 23 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-359) Kie-spring tests should not use InternalSpringUtils.

by Vinod Kiran Paidimarry (JIRA)

[ https://issues.jboss.org/browse/DROOLS-359?page=com.atlassian.jira.plugin... ] Vinod Kiran Paidimarry updated DROOLS-359: ------------------------------------------ Git Pull Request: https://github.com/droolsjbpm/droolsjbpm-integration/pull/76 > Kie-spring tests should not use InternalSpringUtils. > ---------------------------------------------------- > > Key: DROOLS-359 > URL: https://issues.jboss.org/browse/DROOLS-359 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Vinod Kiran Paidimarry > Assignee: Mark Proctor > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-359) Kie-spring tests should not use InternalSpringUtils.

by Vinod Kiran Paidimarry (JIRA)

Vinod Kiran Paidimarry created DROOLS-359: --------------------------------------------- Summary: Kie-spring tests should not use InternalSpringUtils. Key: DROOLS-359 URL: https://issues.jboss.org/browse/DROOLS-359 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Vinod Kiran Paidimarry Assignee: Mark Proctor Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-409) JPA should allow for a bean validator factory per persistence unit or per application deployment

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-409?page=com.atlassian.jira.plugin.s... ] Hardy Ferentschik commented on WFLY-409: ---------------------------------------- [~smarlow], why was this issue closed? Also, I am not sure I am follwoing. The title says {quote} JPA should allow for a bean validator factory per persistence unit or per application deployment {quote} and then in the summary you say: {quote} Currently, a new bean validator factory instance is associated with each deployed persistence unit. {quote} Is there, or is there not a new {{ValidatorFactory}} per PU/application? There should be, because each application could configure its own {{ValidatorFactory}} via {{validation.xml}}. > JPA should allow for a bean validator factory per persistence unit or per application deployment > ------------------------------------------------------------------------------------------------ > > Key: WFLY-409 > URL: https://issues.jboss.org/browse/WFLY-409 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Labels: open_to_community > Fix For: 8.0.0.Beta1 > > > Currently, a new bean validator factory instance is associated with each deployed persistence unit. This jira calls for adding a new PU property that specifies that a 'per app bean validator factory' should be used for a persistence unit (via a persistence unit property). > This can be controlled by a new persistence unit property (see existing ones [here|https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide#JPARe...]). > The new property can be something like "org.jboss.as.jpa.shareValidatorFactory" which defaults to false. > Look at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit() to make this change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-260) Drools not writing calendars when marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-260: ------------------------------------------------ Tomas David <tdavid(a)redhat.com> changed the Status of [bug 1007385|https://bugzilla.redhat.com/show_bug.cgi?id=1007385] from ON_QA to VERIFIED > Drools not writing calendars when marshalling > --------------------------------------------- > > Key: DROOLS-260 > URL: https://issues.jboss.org/browse/DROOLS-260 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Demian Calcaprina > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > > When serializing Rule class, https://github.com/droolsjbpm/drools/blob/5.5.x/drools-core/src/main/java..., the write and read external methods does not write and read calendars properties. > This causes that, if there is a rule which has a calendar in guvnor, for example, > rule "CalendarTest" > calendars "my cal" > no-loop true > dialect "mvel" > when > then > System.out.println("CALENDAR IS FIRIUNG!!!"); > end > when rule is retrieved, calendars are not took into account. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-356) KieScanner doesn't work on a KieContainer using a maven version range

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-356?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-356: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1035685|https://bugzilla.redhat.com/show_bug.cgi?id=1035685] from ASSIGNED to MODIFIED > KieScanner doesn't work on a KieContainer using a maven version range > --------------------------------------------------------------------- > > Key: DROOLS-356 > URL: https://issues.jboss.org/browse/DROOLS-356 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > It is currently possible to create a KieContainer with a ranged version instead of a fixed one, but this range is not used by the KieScanner that instead consider only the fixed version of the first fetched project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-72) Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-72?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated DROOLS-72: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=995023, https://bugzilla.redhat.com/show_bug.cgi?id=1036126 (was: https://bugzilla.redhat.com/show_bug.cgi?id=995023) > Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-72 > URL: https://issues.jboss.org/browse/DROOLS-72 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Trung Nguyen > Assignee: Mario Fusco > Fix For: 5.5.1.Final, 6.0.0.Alpha9 > > > when {{ksession.fireAllRules()}} throws RuntimeException, it cause {{ksession}} never gets released. > {code:lang=java} > public void execute(Object object) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > ksession.insert( object ); > ksession.fireAllRules( ); > ksession.dispose(); > } > public void execute(Iterable objects) { > StatefulKnowledgeSession ksession = newWorkingMemory(); > for ( Object object : objects ) { > ksession.insert( object ); > } > ksession.fireAllRules( ); > ksession.dispose(); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-671) Failure in CalendarUtilTestCase.testEveryMinuteEveryHourEveryDay

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-671?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim commented on WFLY-671: --------------------------------------- in the latest wildfly I see CalendarBasedTimeoutTestCase#testWithStartInTheFutureAndLaterSchedule failing with {code} java.lang.AssertionError: Unexpected first schedule if start date is in the past, must be at 00:00 but is 1. 0:50 {code} > Failure in CalendarUtilTestCase.testEveryMinuteEveryHourEveryDay > ---------------------------------------------------------------- > > Key: WFLY-671 > URL: https://issues.jboss.org/browse/WFLY-671 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Carlo de Wolf > Priority: Minor > Fix For: Awaiting Volunteers > > > I'm unable to compile AS 7. > {noformat} > Failed tests: testEveryMinuteEveryHourEveryDay[379](org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase): Unexpected timeout value: java.util.GregorianCalendar[time=1314918060000,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="Asia/Gaza",offset=7200000,dstSavings=3600000,useDaylight=true,transitions=144,lastRule=java.util.SimpleTimeZone[id=Asia/Gaza,offset=7200000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=7,startTime=60000,startTimeMode=0,endMode=3,endMonth=8,endDay=1,endDayOfWeek=6,endTime=7200000,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2011,MONTH=8,WEEK_OF_YEAR=36,WEEK_OF_MONTH=1,DAY_OF_MONTH=2,DAY_OF_YEAR=245,DAY_OF_WEEK=6,DAY_OF_WEEK_IN_MONTH=1,AM_PM=0,HOUR=1,HOUR_OF_DAY=1,MINUTE=1,SECOND=0,MILLISECOND=0,ZONE_OFFSET=7200000,DST_OFFSET=0] expected:<60000> but was:<3660000> > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2364) Uninformative NPE in PoolAnnotationInformationFactory

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-2364?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on WFLY-2364: ---------------------------------------- My patch seems correct in matching our implementation which requires a value. I wanted to verify if our impl would match the specs, checked jsr-322 but could not find the answer unfortunately. Assigning to David Loyd, since you're apparently the guy in charge of EE. Please review my simple patch. > Uninformative NPE in PoolAnnotationInformationFactory > ------------------------------------------------------ > > Key: WFLY-2364 > URL: https://issues.jboss.org/browse/WFLY-2364 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Denis Borovikov > Assignee: David Lloyd > > I got NPE on jboss startup: > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:43) > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:35) > at org.jboss.as.ee.metadata.ClassAnnotationInformationFactory.createAnnotationInformation(ClassAnnotationInformationFactory.java:127) > at org.jboss.as.ee.metadata.AbstractEEAnnotationProcessor.deploy(AbstractEEAnnotationProcessor.java:54) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > Root cause is empty value for Pool annotation in my code. I think it would be better to generate more informative exception message in this place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2364) Uninformative NPE in PoolAnnotationInformationFactory

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/WFLY-2364?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere reassigned WFLY-2364: ----------------------------------------- Assignee: David Lloyd > Uninformative NPE in PoolAnnotationInformationFactory > ------------------------------------------------------ > > Key: WFLY-2364 > URL: https://issues.jboss.org/browse/WFLY-2364 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Denis Borovikov > Assignee: David Lloyd > > I got NPE on jboss startup: > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:43) > at org.jboss.as.ejb3.deployment.processors.annotation.PoolAnnotationInformationFactory.fromAnnotation(PoolAnnotationInformationFactory.java:35) > at org.jboss.as.ee.metadata.ClassAnnotationInformationFactory.createAnnotationInformation(ClassAnnotationInformationFactory.java:127) > at org.jboss.as.ee.metadata.AbstractEEAnnotationProcessor.deploy(AbstractEEAnnotationProcessor.java:54) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > Root cause is empty value for Pool annotation in my code. I think it would be better to generate more informative exception message in this place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
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 November 2013