Manually Changing Glassfish domain.xml for Debug Error - debugging

I have this line of code at domain.xml:
<java-config classpath-suffix="" debug-enabled="false" debug-options="-Xdebug -Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=9009" env-classpath-ignored="true" java-home="${com.sun.aas.javaRoot}" javac-options="-g" rmic-options="-iiop -poa -alwaysgenerate -keepgenerated -g" system-classpath="">
If I start the domain there is no error. However I want to get debug feature so I changed this part like this:
debug-enabled="true"
When I want to start the domain it gives error:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
What may be the problem?

Change
-Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=9009
to
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009

Within Glassfish 3.0.1 there are many domain.xml files. You must be sure to modify the one corresponding to your domain like:
<GLASSFISH_HOME>/domains/domain1/config/domain.xml

Related

How do you hide Socket.io error messages in C++?

So I get error messages like this printed to the console from Socket.io:
[2023-02-09 17:53:43] [info] asio async_resolve error: asio.system:11001 (No such host is known.)
[2023-02-09 17:53:43] [info] Error getting remote endpoint: asio.system:10009 (The file handle supplied is not valid.)
[2023-02-09 17:53:43] [error] handle_connect error: No such host is known.
[2023-02-09 17:53:43] [info] asio async_shutdown error: asio.ssl:336462100 (uninitialized)
I just need to hide them from the console but cannot figure out how to do it. I've tried using off_error, set logs quiet, and try/catch but none worked.
Does anyone know how to solve this?

composer-rest-server Error: throw er; // Unhandled 'error' event

I installed and startet my business network. Now I want to do composer-rest-server -c admin#test-network but I get the following output:
Discovering types from business network definition ...
Discovering the Returning Transactions..
Discovered types from business network definition
Generating schemas for all types in business network definition ...
Generated schemas for all types in business network definition
Adding schemas for all types to Loopback ...
Added schemas for all types to Loopback
events.js:183
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::3000
at Server.setupListenHandle [as _listen2] (net.js:1360:14)
at listenInCluster (net.js:1401:12)
at Server.listen (net.js:1485:7)
at module.exports.promise.then.then (/home/dany/.nvm/versions/node/v8.15.0/lib/node_modules/composer-rest-server/cli.js:143:19)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
The funny thing is, that everything worked fine before. Then I restarted the fabric and reinstalled the bna file and now I get this error. Thanks for your help
It seems you have not stopped your script properly that's why this error is coming. This error comes when your port is already occupied and you are trying to start something on same port. So you can kill process on this port then it should work fine.
If you are using linux OS then this command might help you.
fuser -n tcp -k 3000

BYFN.sh failed with error when setting up MSP of type bccsp

I am trying the first-network demo on OS X and am getting the following error. I have tried searching for an answer. I did found one here but it appears that is for Ubuntu. All the commands didn't work on OS X.
Can anyone suggest a solution on OS X? Thanks!
2018-11-02 03:13:45.696 UTC [main] main -> ERRO 001 Cannot run peer
because error when setting up MSP of type bccsp from directory
/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin#org1.example.com/msp:
could not initialize BCCSP Factories: Failed initializing PKCS11.BCCSP
%!s(): Could not initialize BCCSP PKCS11 [Failed to initialize
software key store: An invalid KeyStore path provided. Path cannot be
an empty string.] !!!!!!!!!!!!!!! Channel creation failed
!!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ==========
The error message is not very specific.
In my case, I was trying to connect to a peer from my fabric-tools container, and there was a TLS enabled mismatch (fabric-tools has TLS enabled, and fabric-peer had TLS disabled). Aligning the TLS configuration made the error go away.
Might help someone out...

: API error (404): network hlfv11_hyperledger not found

✖ Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: failed to execute transaction b5c260c02b4792c4ae4b85b3d4ccb4565a495da399d27917dccc1a84244e631f: error starting container: error starting container: API error (404): network hlfv11_hyperledger not found
Response from attempted peer comms was an error: Error: failed to execute transaction b5c260c02b4792c4ae4b85b3d4ccb4565a495da399d27917dccc1a84244e631f: error starting container: error starting container: API error (404): network hlfv11_hyperledger not found
This looks like it is a Docker problem trying to start a new ChainCode container on a Docker Network bridge called "hlfv11_hyperledger" which doesn't exist.
(The word 'network' here is ambiguous in the error message :-( )
This is the same problem and hopefully the same solution as a previous post.

Configuring the REST server with a persistent data store

I am having problems trying to deploy the rest server with persistence storage (mongo db) I ge this message when deploying the rest server:
docker logs -f rest
[2018-03-12 00:01:13] PM2 log: Launching in no daemon mode
[2018-03-12 00:01:14] PM2 log: Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
[2018-03-12 00:01:14] PM2 log: App name:composer-rest-server id:0 online
WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Discovering types from business network definition ...
Connection fails: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
It will be retried for the next request.
Exception: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
at _checkRuntimeVersions.then.catch (/home/composer/.npm-global/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:699:34)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
[2018-03-12 00:07:03] PM2 log: App [composer-rest-server] with id [0] and pid [14], exited with code [1] via signal [SIGINT]
I am using composer v.18
is there any work around to fix this error. when I run the composer-rest- server alone it work. but if I try to add the mongodb it does not work

Resources