[JBoss JIRA] (JGRP-1813) JDBC_PING failes to recover for corruption issue
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1813?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1813:
---------------------------
Fix Version/s: 3.5
> JDBC_PING failes to recover for corruption issue
> ------------------------------------------------
>
> Key: JGRP-1813
> URL: https://issues.jboss.org/browse/JGRP-1813
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 3.4
> Environment: Windows 7
> Reporter: Brett Donahue
> Assignee: Bela Ban
> Priority: Minor
> Labels: EOFException, JDBC_PING,, corruption
> Fix For: 3.5
>
>
> heap space was exhausted and issues occurred. In the end, one node in the cluster must have corrupted the data in the JDBC_PING table. From this point onward, our log is full of these (every two seconds):
> 2014 03 23 04:00:25#+0100#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Thread-15###Error java.io.EOFException: null
> at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:340)
> at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:226)
> at org.jgroups.util.Util.readAddress(Util.java:929)
> at org.jgroups.util.Util.readAddresses(Util.java:1047)
> at org.jgroups.protocols.PingData.readFrom(PingData.java:163)
> at org.jgroups.util.Util.streamableFromByteBuffer(Util.java:753)
> at org.jgroups.protocols.Discovery.deserialize(Discovery.java:625)
> at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:221)
> at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:201)
> at org.jgroups.protocols.FILE_PING.fetchClusterMembers(FILE_PING.java:68)
> at org.jgroups.protocols.Discovery.sendDiscoveryRequest(Discovery.java:263)
> at org.jgroups.protocols.Discovery.findMembers(Discovery.java:227)
> at org.jgroups.protocols.Discovery.findInitialMembers(Discovery.java:208)
> at org.jgroups.protocols.Discovery.down(Discovery.java:551)
> at org.jgroups.protocols.FILE_PING.down(FILE_PING.java:101)
> at org.jgroups.protocols.MERGE2.down(MERGE2.java:185)
> at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:363)
> at org.jgroups.protocols.FD.down(FD.java:307)
> at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:84)
> at org.jgroups.protocols.BARRIER.down(BARRIER.java:95)
> at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:533)
> at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:575)
> at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:347)
> at org.jgroups.protocols.ENCRYPT.down(ENCRYPT.java:925)
> at org.jgroups.protocols.pbcast.ClientGmsImpl.findInitialMembers(ClientGmsImpl.java:201)
> at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:75)
> at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40)
> at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1052)
> at org.jgroups.protocols.FlowControl.down(FlowControl.java:340)
> at org.jgroups.protocols.FRAG2.down(FRAG2.java:136)
> at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:237)
> at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1024)
> at org.jgroups.JChannel.down(JChannel.java:760)
> at org.jgroups.JChannel._connect(JChannel.java:538)
> at org.jgroups.JChannel.connect(JChannel.java:290)
> at org.jgroups.JChannel.connect(JChannel.java:275)
> at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.startCommunications(ClusterCommunicationsJGroupImpl.java:45)
> at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.<init>(ClusterCommunicationsJGroupImpl.java:59)
> at com.sap.mobile.platform.server.cluster.service.impl.ClusterServiceImpl.run(ClusterServiceImpl.java:187)
> at java.lang.Thread.run(Thread.java:791)
--
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
10 years, 9 months
[JBoss JIRA] (WFLY-1904) Usage of vault for system-properties throws java.lang.SecurityException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1904?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1904:
-----------------------------------------------
Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1076507|https://bugzilla.redhat.com/show_bug.cgi?id=1076507] from NEW to POST
> Usage of vault for system-properties throws java.lang.SecurityException
> -----------------------------------------------------------------------
>
> Key: WFLY-1904
> URL: https://issues.jboss.org/browse/WFLY-1904
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: 8.0.0.Beta1
> Reporter: Navin Surtani
> Assignee: Brian Stansberry
> Fix For: 8.0.1.Final
>
>
> Steps to Reproduce: 1. add the lines in standalone.xml:-
> {code}
> <system-properties>
> <property name="javax.net.ssl.trustStore" value="/dir/truststore.jks"/>
> <property name="javax.net.ssl.trustStorePassword" value="${VAULT::blk::attr::MTBlYWUzNDEtMjI2MC00NWYzLWFiZmUtM2EyYjZkNDgyZWM4TElORV9CUkVBS215YWxpYXM=}" />
> </system-properties>
> <vault>
> <vault-option name="KEYSTORE_URL" value="/opt/jboss-eap-6.0/standalone/configuration/vault.jks"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-2gTQPnrWJaqrh0pURMKAOw"/>
> <vault-option name="KEYSTORE_ALIAS" value="myalias"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="44"/>
> <vault-option name="ENC_FILE_DIR" value="/opt/jboss-eap-6.0/standalone/configuration/"/>
> </vault>
> {code}
> 2. start EAP6 in standalone mode
> project_key: JBPAPP6
> Usage of vault for system-properties throws java.lang.SecurityException.
> boot.log:-
> {code}
> 20:35:30,267 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([("system-property" => "javax.net.ssl.trustStorePassword")]): java.lang.SecurityException: JBAS013322: Vault is not initialized
> at org.jboss.as.security.vault.RuntimeVaultReader.retrieveFromVault(RuntimeVaultReader.java:98) [jboss-as-security-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.RuntimeExpressionResolver.resolvePluggableExpression(RuntimeExpressionResolver.java:45) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressionsRecursively(ExpressionResolverImpl.java:58) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ExpressionResolverImpl.resolveExpressions(ExpressionResolverImpl.java:40) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ModelControllerImpl.resolveExpressions(ModelControllerImpl.java:455) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.OperationContextImpl.resolveExpressions(OperationContextImpl.java:689) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.operations.common.SystemPropertyAddHandler.execute(SystemPropertyAddHandler.java:112) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:175) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:295) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_37]
> {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
10 years, 9 months
[JBoss JIRA] (WFLY-1013) Can't set attribute "suffix" on web access-log
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1013?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-1013:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080233
> Can't set attribute "suffix" on web access-log
> ----------------------------------------------
>
> Key: WFLY-1013
> URL: https://issues.jboss.org/browse/WFLY-1013
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Environment: N/A
> Reporter: Ed Roberts
> Assignee: Tomaz Cerar
> Labels: logging, suffix, web
>
> In JBoss 5.x you used to be able to specify a suffix attribute value for the JBossWeb access log file, which would be appended to generated log file names.
> In JBoss 7.x you can only specify a prefix. For the logging handlers you can specify both a prefix and a suffix, which is inconsistent.
> Please add the suffix attribute to the access-log element within the parent virtual-server element of the web subsystem xml configuration.
--
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
10 years, 9 months
[JBoss JIRA] (WFLY-3158) @Model does not work
by Stefan Dilk (JIRA)
Stefan Dilk created WFLY-3158:
---------------------------------
Summary: @Model does not work
Key: WFLY-3158
URL: https://issues.jboss.org/browse/WFLY-3158
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CDI / Weld, JSF
Affects Versions: 8.0.0.Final
Reporter: Stefan Dilk
Assignee: Stuart Douglas
hi,
wildfly not work with @Model annotated beans in JSF.
@RequestScoped and @Named work.
in this ticket it is already reported, but closed:
https://issues.jboss.org/browse/WFLY-2372
in the related CDI ticket the change is made, so please implement this in the next wildfly update. in glassfish4 the @Model annotation works fine.
--
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
10 years, 9 months
[JBoss JIRA] (JGRP-1813) JDBC_PING failes to recover for corruption issue
by Brett Donahue (JIRA)
Brett Donahue created JGRP-1813:
-----------------------------------
Summary: JDBC_PING failes to recover for corruption issue
Key: JGRP-1813
URL: https://issues.jboss.org/browse/JGRP-1813
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.4
Environment: Windows 7
Reporter: Brett Donahue
Assignee: Bela Ban
Priority: Minor
heap space was exhausted and issues occurred. In the end, one node in the cluster must have corrupted the data in the JDBC_PING table. From this point onward, our log is full of these (every two seconds):
2014 03 23 04:00:25#+0100#ERROR#org.jgroups.protocols.SMP_JDBC_PING##anonymous#Thread-15###Error java.io.EOFException: null
at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:340)
at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:226)
at org.jgroups.util.Util.readAddress(Util.java:929)
at org.jgroups.util.Util.readAddresses(Util.java:1047)
at org.jgroups.protocols.PingData.readFrom(PingData.java:163)
at org.jgroups.util.Util.streamableFromByteBuffer(Util.java:753)
at org.jgroups.protocols.Discovery.deserialize(Discovery.java:625)
at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:221)
at org.jgroups.protocols.JDBC_PING.readAll(JDBC_PING.java:201)
at org.jgroups.protocols.FILE_PING.fetchClusterMembers(FILE_PING.java:68)
at org.jgroups.protocols.Discovery.sendDiscoveryRequest(Discovery.java:263)
at org.jgroups.protocols.Discovery.findMembers(Discovery.java:227)
at org.jgroups.protocols.Discovery.findInitialMembers(Discovery.java:208)
at org.jgroups.protocols.Discovery.down(Discovery.java:551)
at org.jgroups.protocols.FILE_PING.down(FILE_PING.java:101)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:185)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:363)
at org.jgroups.protocols.FD.down(FD.java:307)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:84)
at org.jgroups.protocols.BARRIER.down(BARRIER.java:95)
at org.jgroups.protocols.pbcast.NAKACK2.down(NAKACK2.java:533)
at org.jgroups.protocols.UNICAST3.down(UNICAST3.java:575)
at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:347)
at org.jgroups.protocols.ENCRYPT.down(ENCRYPT.java:925)
at org.jgroups.protocols.pbcast.ClientGmsImpl.findInitialMembers(ClientGmsImpl.java:201)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:75)
at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:40)
at org.jgroups.protocols.pbcast.GMS.down(GMS.java:1052)
at org.jgroups.protocols.FlowControl.down(FlowControl.java:340)
at org.jgroups.protocols.FRAG2.down(FRAG2.java:136)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:237)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1024)
at org.jgroups.JChannel.down(JChannel.java:760)
at org.jgroups.JChannel._connect(JChannel.java:538)
at org.jgroups.JChannel.connect(JChannel.java:290)
at org.jgroups.JChannel.connect(JChannel.java:275)
at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.startCommunications(ClusterCommunicationsJGroupImpl.java:45)
at com.sap.mobile.platform.server.cluster.service.impl.ClusterCommunicationsJGroupImpl.<init>(ClusterCommunicationsJGroupImpl.java:59)
at com.sap.mobile.platform.server.cluster.service.impl.ClusterServiceImpl.run(ClusterServiceImpl.java:187)
at java.lang.Thread.run(Thread.java:791)
--
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
10 years, 9 months
[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-439:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1079950|https://bugzilla.redhat.com/show_bug.cgi?id=1079950] from ASSIGNED to MODIFIED
> Package builder unable to find declared array class
> ---------------------------------------------------
>
> Key: DROOLS-439
> URL: https://issues.jboss.org/browse/DROOLS-439
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.1.Final
> Reporter: Mark Sullivan
> Assignee: Mario Fusco
>
> When declaring a fact type with an array field, where the array type is declared in the same package, for example:
> {code}
> declare Owner
> name : String
> end
> declare Pet
> owners : Owner[]
> end
> {code}
> The following build error occurs:
> {code}
> [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0
> text=Unable to find class 'Owner']]
> {code}
> This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed.
> PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types.
> The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies:
> {code}
> for (TypeFieldDescr field : tdescr.getFields().values()) {
> QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType());
> if (!hasCircularDependency(name, typeName, taxonomy)) {
> supers.add(typeName);
> }
> }
> {code}
> However I don't think it correctly spots the dependency when the field type is an array.
> This issue can be worked around by declaring an unused field of the same type as the array:
> {code}
> declare Owner
> name : String
> end
> declare Pet
> owners : Owner[]
> _unused: Owner
> end
> {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
10 years, 9 months
[JBoss JIRA] (WFLY-2709) Connector Subsystem is Missing connection-definitions.clear-statistics resource key
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2709?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-2709:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080126
> Connector Subsystem is Missing connection-definitions.clear-statistics resource key
> -----------------------------------------------------------------------------------
>
> Key: WFLY-2709
> URL: https://issues.jboss.org/browse/WFLY-2709
> Project: WildFly
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.CR1
> Reporter: Philippe Marschall
> Assignee: Philippe Marschall
> Fix For: 8.0.0.Final
>
>
> The connector subsystem is missing the resource key: {{“connection-definitions.clear-statistics”}}. This results in the following exception when looking at the connection definitions of a resource adapter in VisualVM:
> {code}
> 16:06:10,884 ERROR [org.jboss.as.controller.management-operation] (RMI TCP Connection(2)-192.168.0.21) JBAS014612: Operation ("read-resource-description") failed - address: ([
> ("deployment" => "XADisk.rar"),
> ("subsystem" => "resource-adapters"),
> ("statistics" => "statistics"),
> ("resource-adapter" => "XADisk.rar"),
> ("connection-definitions" => "java:global/XADiskCF")
> ]): java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key connection-definitions.clear-statistics
> at java.util.ResourceBundle.getObject(ResourceBundle.java:450) [rt.jar:1.8.0-ea]
> at java.util.ResourceBundle.getString(ResourceBundle.java:407) [rt.jar:1.8.0-ea]
> at org.jboss.as.controller.descriptions.StandardResourceDescriptionResolver.getOperationDescription(StandardResourceDescriptionResolver.java:184)
> at org.jboss.as.controller.descriptions.DefaultOperationDescriptionProvider.getModelDescription(DefaultOperationDescriptionProvider.java:157)
> at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler.doExecuteInternal(ReadResourceDescriptionHandler.java:213)
> at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler.doExecute(ReadResourceDescriptionHandler.java:157)
> at org.jboss.as.controller.operations.global.ReadResourceDescriptionHandler.execute(ReadResourceDescriptionHandler.java:150)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:272)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:146)
> at org.jboss.as.jmx.model.ResourceAccessControlUtil.getResourceAccess(ResourceAccessControlUtil.java:85)
> at org.jboss.as.jmx.model.ResourceAccessControlUtil.getResourceAccessWithInstanceNotFoundExceptionIfNotAccessible(ResourceAccessControlUtil.java:70)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanInfo(ModelControllerMBeanHelper.java:199)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanInfo(ModelControllerMBeanServerPlugin.java:131)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:582)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:570)
> at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1460) [rt.jar:1.8.0-ea]
> at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) [rt.jar:1.8.0-ea]
> at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1307) [rt.jar:1.8.0-ea]
> at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1399) [rt.jar:1.8.0-ea]
> at javax.management.remote.rmi.RMIConnectionImpl.getMBeanInfo(RMIConnectionImpl.java:904) [rt.jar:1.8.0-ea]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0-ea]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0-ea]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-ea]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-ea]
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:323) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.Transport$1.run(Transport.java:178) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.Transport$1.run(Transport.java:175) [rt.jar:1.8.0-ea]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.Transport.serviceCall(Transport.java:174) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:557) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:812) [rt.jar:1.8.0-ea]
> at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:671) [rt.jar:1.8.0-ea]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-ea]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-ea]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-ea]
> {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
10 years, 9 months